Configuration Guide (V100R006C001 02)

OptiX OSN 8800/6800/3800 V100R006C01
Configuration Guide
Issue Date 02 2011-10-31
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 http://www.huawei.com support@huawei.com
Website: Email:
Issue 02 (2011-10-31)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
OptiX OSN 8800/6800/3800 Configuration Guide
About This Document
About This Document

Related Versions
The following table lists the product versions related to this document. Product Name OptiX OSN 8800 OptiX OSN 6800 OptiX OSN 3800 iManager U2000 iManager U2000 Web LCT Version V100R006C01 V100R006C01 V100R006C01 V100R005C00 V100R005C00
Intended Audience
This document describes how to configure optical network elements, WDM services, and Ethernet services. This document is intended for: l l l Installation and commissioning engineers Data configuration engineers System maintenance engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows. Symbol Description
DANGER
Issue 02 (2011-10-31)
Indicates a hazard with a high level of risk, which if not avoided, will result in death or serious injury.
ii
About This Document
Symbol
Description Indicates a hazard with a medium or low level of risk, which if not avoided, could result in minor or moderate injury. Indicates a potentially hazardous situation, which if not avoided, could result in equipment damage, data loss, performance degradation, or unexpected results. Indicates a tip that may help you solve a problem or save time. Provides additional information to emphasize or supplement important points of the main text.
WARNING
CAUTION
TIP
NOTE
GUI Conventions
The GUI conventions that may be found in this document are defined as follows. Convention Boldface > Description Buttons, menus, parameters, tabs, window, and dialog titles are in boldface. For example, click OK. Multi-level menus are in boldface and separated by the ">" signs. For example, choose File > Create > Folder.
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains all updates made in previous issues.
Updates in Issue 02 (2011-10-31) Based on Product Version V100R006C01

This issue is the second official release for OptiX OSN 8800/6800/3800 V100R006C01. Compared with the issue 01, the manual of this issue provides the following updates. Update 2 Configuring WDM Services (Manually by Station)
Issue 02 (2011-10-31)
Description l 2.1.3 Board Model (Standard Mode and Compatible Mode) is modified. l 2.1.4 ODUflex is modified.
iii
About This Document
Update 5.7 Application Scenario 5: ODUflex NonConvergence Mode 6.6 Application Scenario 4: Conversion Between Two 3G-SDI Services and One OTU2 Optical Signals
Description l 5.7.3 Configuration Process is modified.
l 6.6.3 Configuration Process is modified.

This issue is the first official release for OptiX OSN 8800/6800/3800 V100R006C01. Compared with the OptiX OSN 8800/6800/3800 V100R006C00, the manual of this issue provides the following updates. Update Whole manual Description l Structure is adjusted. l The title of some charpters are changed. l 1 Guidelines for Configuring Equipment by Referring to This Manual is added. l 6 Configuring the LOA Board (Manually by Station) is added. l 7 Configuring WDM Services (by Station Service Package) is added. l The charpter Managing NE Power Consumption removes to Commissioning Guide. 2 Configuring WDM Services (Manually by Station) l 2.1.3 Board Model (Standard Mode and Compatible Mode) is added. l 2.1.4 ODUflex is added. l The charpter Configuring WDM Services for Tributary Boards and Line Boards (with ODUK SNCP Protection) is deleted. l 5.2 Configuration Procedures is added. l 5.7 Application Scenario 5: ODUflex Non-Convergence Mode is added.
5 Configuring the THA/TOA Board (Manually by Station)
Issue 02 (2011-10-31)
iv
About This Document
Update 11 Modifying the Configuration Data 12 Configuration Tasks
Description "Converting a Normal WDM Service to an SNCP Service" and "Converting an SNCP Service to a Normal WDM Service" are deleted. 12.1 Configuring Working Modes is added.

This issue is the third official release for OptiX OSN 8800/6800/3800 V100R006C00. Compared with the issue 02, the manual of this issue provides the following updates. Update Whole manual Description l Structure is adjusted. l The charpter Managing NE Power Consumption removes to Commissioning Guide. 2 Configuring WDM Services (Manually by Station) 5 Configuring the THA/TOA Board (Manually by Station) 11 Modifying the Configuration Data 12 Configuration Tasks l The charpter Configuring WDM Services for Tributary Boards and Line Boards (with ODUK SNCP Protection) is deleted.
l 5.2 Configuration Procedures is added.
"Converting a Normal WDM Service to an SNCP Service" and "Converting an SNCP Service to a Normal WDM Service" are deleted. 12.1 Configuring Working Modes is added.

This issue is the second official release for OptiX OSN 8800/6800/3800 V100R006C00. Compared with the issue 01, the manual of this issue provides the following updates.
Issue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. v
About This Document
Update Whole manual
Description Add the chapter 5 Configuring the THA/TOA Board (Manually by Station).

This issue is the first official release for OptiX OSN 8800/6800/3800 V100R006C00. Compared with the OptiX OSN 8800/6800/3800 V100R005C00, the manual of this issue provides the following updates. Update Whole manual Description l Delete the "WDM Network Management Process". l Delete the "Quick Guide". l Delete the "Creating a Network". l Delete the "Performance Management". l Delete the "Configuring Wavelength Grooming". l Delete the "Configuring Broadcast Data Port Services". l Delete the "Backing Up and Restoring the NE Data". 2 Configuring WDM Services (Manually by Station) 8 Configuring WDM Services (by Trail) The name of the chapter is changed from "Configuring WDM Services" to "Configuring WDM Services (By Station)".
Make configuring WDM Services by trail as an independent chapter.

This issue is the fourth official release for OptiX OSN 8800/6800/3800 V100R005C00. Compared with the issue 03, the manual of this issue provides the following updates.
Issue 02 (2011-10-31)
vi
About This Document
Update Whole manual
Description l Delete the "WDM Network Management Process". l Delete the "Quick Guide". l Delete the "Creating a Network". l Delete the "Performance Management". l Delete the "Configuring Wavelength Grooming". l Delete the "Configuring Broadcast Data Port Services". l Delete the "Backing Up and Restoring the NE Data".
2 Configuring WDM Services (Manually by Station) 8 Configuring WDM Services (by Trail)
The name of the chapter is changed from "Configuring WDM Services" to "Configuring WDM Services (By Station)".
Make configuring WDM Services by trail as an independent chapter.

Update Whole manual Description Some bugs are fixed.

This issue is the second official release for OptiX OSN 8800/6800/3800 V100R005C00. Compared with the issue 01, the manual of this issue provides the following updates. Update Configuring WDM Services for Tributary Boards and Line Boards (with ODUK SNCP Protection) Description Modify the "service signal flow".
Issue 02 (2011-10-31)
vii
About This Document
Update 8.3 Configuration Example 10.6 Configuration Example: Configuring EPL Services
Description Modify the "configuration process".
Modify the "configuration process".

This issue is the first official release for OptiX OSN 8800/6800/3800 V100R005C00. In this release, the manuals for OptiX OSN 8800 V100R002C02, OptiX OSN 6800 V100R004C04, and OptiX OSN 3800 V100R004C04 are combined into one manual. Update Whole manual Description This manual provides descriptions according to product series OptiX OSN 8800, OptiX OSN 6800A, and OptiX OSN 3800A. Any difference between the products is described in the manual. Enabling the Port Blocking Function is added.
Enabling the Port Blocking Function 8.2 Creating OCh Trails by Trail Search
8.2 Creating OCh Trails by Trail Search is added.
Issue 02 (2011-10-31)
viii
About This Document
Update 2.3 Configuring WDM Services for OTU Boards Without CrossConnect Capability 2.4 Configuring WDM Services for OTU Boards with CrossConnect Capability 2.5 Configuring WDM Services for Tributary Boards and Line Boards 2.6 Configuring WDM Services for Boards with the Layer 2 Switching Function 8.4 Parameters: End to End Service Configuration Configuring WDM Services for Tributary Boards and Line Boards (with ODUK SNCP Protection) 8.3 Configuration Example
Description 2.3 Configuring WDM Services for OTU Boards Without CrossConnect Capability, 2.4 Configuring WDM Services for OTU Boards with Cross-Connect Capability, 2.5 Configuring WDM Services for Tributary Boards and Line Boards, and 2.6 Configuring WDM Services for Boards with the Layer 2 Switching Function are added.
8.4 Parameters: End to End Service Configuration is added.
Configuring WDM Services for Tributary Boards and Line Boards (with ODUK SNCP Protection) is added.
The name of the section is changed from "Configuring End-to-End GE Services" to "Configuring GE Services (By Trail)".
Issue 02 (2011-10-31)
ix
About This Document
Update Configuring the Transparent Transmission of the GE Service Configuring the Transparent Transmission of the SAN Services Configuring the Transparent Transmission of the OTN Service Configuring the Transparent Transmission of the SDH Services
Description Sections "Configuring the Transparent Transmission of the GE Service", "Configuring the Transparent Transmission of the SAN Services", "Configuring the Transparent Transmission of the OTN Service", and "Configuring the Transparent Transmission of the SDH Services" are deleted.
Issue 02 (2011-10-31)
About This Document
Update 10.8 Configuration Example: Configuring EPLAN Services (IEEE 802.1d Bridge) on a WDM Network 10.9 Configuration Example: Configuring EVPLAN Services (IEEE 802.1q Bridge) on a WDM Network 10.10 Configuration Example: Configuring EVPLAN Services (IEEE 802.1 ad Bridge) on a WDM Network 10.11 Configuration Example: Configuring EVPL and EVPLAN Services (IEEE 802.1q Bridge) on a WDM Network Configuring the Receive Wavelength of Boards
Description 10.8 Configuration Example: Configuring EPLAN Services (IEEE 802.1d Bridge) on a WDM Network, 10.9 Configuration Example: Configuring EVPLAN Services (IEEE 802.1q Bridge) on a WDM Network, 10.10 Configuration Example: Configuring EVPLAN Services (IEEE 802.1 ad Bridge) on a WDM Network, and 10.11 Configuration Example: Configuring EVPL and EVPLAN Services (IEEE 802.1q Bridge) on a WDM Network are added.
Configuring the Receive Wavelength of Boards is added.
Issue 02 (2011-10-31)
xi
Contents
Contents
About This Document.....................................................................................................................ii 1 Guidelines for Configuring Equipment by Referring to This Manual..............................1 2 Configuring WDM Services (Manually by Station)...............................................................4
2.1 Basic Concepts...................................................................................................................................................5 2.1.1 Electrical Cross-Connections....................................................................................................................5 2.1.2 Service Types............................................................................................................................................9 2.1.3 Board Model (Standard Mode and Compatible Mode)...........................................................................18 2.1.4 ODUflex..................................................................................................................................................24 2.2 WDM Service Configuration Flow..................................................................................................................27 2.3 Configuring WDM Services for OTU Boards Without Cross-Connect Capability.........................................31 2.3.1 Configuration Networking Diagram........................................................................................................31 2.3.2 Service Signal Flow.................................................................................................................................32 2.3.3 Configuration Process..............................................................................................................................32 2.4 Configuring WDM Services for OTU Boards with Cross-Connect Capability...............................................33 2.4.1 Configuration Networking Diagram........................................................................................................33 2.4.2 Service Signal Flow.................................................................................................................................34 2.4.3 Configuration Process..............................................................................................................................34 2.5 Configuring WDM Services for Tributary Boards and Line Boards...............................................................37 2.5.1 Configuration Networking Diagram........................................................................................................38 2.5.2 Service Signal Flow.................................................................................................................................38 2.5.3 Configuration Process..............................................................................................................................39 2.6 Configuring WDM Services for Boards with the Layer 2 Switching Function...............................................44 2.6.1 Configuration Networking Diagram........................................................................................................44 2.6.2 Service Signal Flow.................................................................................................................................45 2.6.3 Configuration Process..............................................................................................................................45 2.7 Configuring 10GE LAN Services by Using the TDX and NS2 Boards...........................................................49 2.7.1 Configuration Networking Diagram........................................................................................................50 2.7.2 Service Signal Flow.................................................................................................................................50 2.7.3 Configuration Process..............................................................................................................................52 2.8 Parameters........................................................................................................................................................55 2.8.1 WDM Cross-Connection Configuration..................................................................................................55 2.8.2 WDM Timeslot Configuration................................................................................................................57 Issue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xii
Contents
3 Configuring the TN11TOM Board (Manually by Station)..................................................59

3.1 Application Scenario 1: Conversion Between Eight Any Services and Four ODU1 Electrical Signals..........61 3.1.1 Configuration Networking Diagram........................................................................................................61 3.1.2 Service Signal Flow.................................................................................................................................62 3.1.3 Configuration Process..............................................................................................................................62 3.2 Application Scenario 2: Conversion Between Four OTU1 Optical Signals and Four ODU1 Electrical Signals ................................................................................................................................................................................65 3.2.1 Configuration Networking Diagram........................................................................................................65 3.2.2 Service Signal Flow.................................................................................................................................66 3.2.3 Configuration Process..............................................................................................................................67 3.3 Application Scenario 3: Conversion Between Four Any Services and Four OTU1 Optical Signals...............69 3.3.1 Configuration Networking Diagram........................................................................................................69 3.3.2 Service Signal Flow.................................................................................................................................70 3.3.3 Configuration Process..............................................................................................................................71 3.4 Application Scenario 4: Conversion Between Seven Any Services and One OTU1 Optical Signal...............73 3.4.1 Configuration Networking Diagram........................................................................................................73 3.4.2 Service Signal Flow.................................................................................................................................74 3.4.3 Configuration Process..............................................................................................................................75 3.5 Application Scenario 5: Conversion Between Six Any Services and One OTU1 Optical Signal and Dual Feeding and Selective Receiving on the WDM Side...........................................................................................................78 3.5.1 Configuration Networking Diagram........................................................................................................78 3.5.2 Service Signal Flow.................................................................................................................................79 3.5.3 Configuration Process..............................................................................................................................80
4 Configuring the TN52TOM Board (Manually by Station)..................................................85

4.1 Overview of the Working Modes.....................................................................................................................88 4.2 Configuration Principles...................................................................................................................................89 4.3 Application Scenario 1: Conversion Between Eight Any Services and Two ODU0 or One ODU1 Electrical Signals....................................................................................................................................................................90 4.3.1 Configuration Networking Diagram........................................................................................................91 4.3.2 Service Signal Flow.................................................................................................................................91 4.3.3 Configuration Process..............................................................................................................................92 4.4 Application Scenario 2: Conversion Between Six Any Services and One OTU1 Optical Signal (with ODU0 Mapping)................................................................................................................................................................96 4.4.1 Configuration Networking Diagram........................................................................................................96 4.4.2 Service Signal Flow.................................................................................................................................97 4.4.3 Configuration Process..............................................................................................................................98 4.5 Application Scenario 3: Conversion Between Eight Any Services and One ODU1 Electrical Signal..........101 4.5.1 Configuration Networking Diagram......................................................................................................101 4.5.2 Service Signal Flow...............................................................................................................................102 4.5.3 Configuration Process............................................................................................................................103 4.6 Application Scenario 4: Conversion Between Six Any Services and One OTU1 Optical Signal (with ODU1 Mapping)..............................................................................................................................................................105 4.6.1 Configuration Networking Diagram......................................................................................................105 Issue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xiii
Contents
4.6.2 Service Signal Flow...............................................................................................................................106 4.6.3 Configuration Process............................................................................................................................107 4.7 Application Scenario 5: Conversion Between Eight Any Services and Eight ODU0 or Four ODU1 Electrical Signals..................................................................................................................................................................110 4.7.1 Configuration Networking Diagram......................................................................................................110 4.7.2 Service Signal Flow...............................................................................................................................111 4.7.3 Configuration Process............................................................................................................................112 4.8 Application Scenario 6: Conversion Between Four Any Services and Two OTU1 Optical Signals.............116 4.8.1 Configuration Networking Diagram......................................................................................................116 4.8.2 Service Signal Flow...............................................................................................................................117 4.8.3 Configuration Process............................................................................................................................118 4.9 Application Scenario 7: Conversion Between Eight Any or Four OTU1 Services and Four ODU1 Electrical Signals..................................................................................................................................................................121 4.9.1 Configuration Networking Diagram......................................................................................................121 4.9.2 Service Signal Flow...............................................................................................................................122 4.9.3 Configuration Process............................................................................................................................123 4.10 Application Scenario 8: Conversion Between Four OTU1 Services and Eight ODU0 Electrical Signals ..............................................................................................................................................................................126 4.10.1 Configuration Networking Diagram....................................................................................................126 4.10.2 Service Signal Flow.............................................................................................................................127 4.10.3 Configuration Process..........................................................................................................................127 4.11 Application Scenario 9: Conversion Between Four OTU1 Optical Signals and Eight ODU0 Electrical Signals (Through Any Re-Encapsulation)........................................................................................................................129 4.11.1 Configuration Networking Diagram....................................................................................................129 4.11.2 Service Signal Flow.............................................................................................................................130 4.11.3 Configuration Process..........................................................................................................................131 4.12 Application Scenario 10: Conversion Between Four OTU1 Optical Signals and Four ODU1 Electrical Signals (Through Any Re-Encapsulation)........................................................................................................................134 4.12.1 Configuration Networking Diagram....................................................................................................134 4.12.2 Service Signal Flow.............................................................................................................................135 4.12.3 Configuration Process..........................................................................................................................135 4.13 Application Scenario 11: Conversion Between Two OTU1 Optical Signals and Two OTU1 Optical Signals (Through Any Re-Encapsulation)........................................................................................................................138 4.13.1 Configuration Networking Diagram....................................................................................................138 4.13.2 Service Signal Flow.............................................................................................................................139 4.13.3 Configuration Process..........................................................................................................................140 4.14 Application Scenario 12: Regeneration of Four OTU1 Optical Signals......................................................143 4.14.1 Configuration Networking Diagram....................................................................................................143 4.14.2 Service Signal Flow.............................................................................................................................144 4.14.3 Configuration Process..........................................................................................................................145
5 Configuring the THA/TOA Board (Manually by Station)................................................148

5.1 Overview of the Working Mode.....................................................................................................................150 5.2 Configuration Procedures...............................................................................................................................150 5.3 Application Scenario 1: ODU0 Non-Convergence Mode..............................................................................162 Issue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xiv
Contents
5.3.1 Networking Diagram.............................................................................................................................162 5.3.2 Service Signal Flow...............................................................................................................................163 5.3.3 Configuration Process............................................................................................................................164 5.4 Application Scenario 2: ODU1 Non-Convergence Mode..............................................................................164 5.4.1 Networking Diagram.............................................................................................................................164 5.4.2 Service Signal Flow...............................................................................................................................165 5.4.3 Configuration Process............................................................................................................................166 5.5 Application Scenario 3: ODU1 Convergence Mode......................................................................................166 5.5.1 Networking Diagram.............................................................................................................................167 5.5.2 Service Signal Flow...............................................................................................................................167 5.5.3 Configuration Process............................................................................................................................168 5.6 Application Scenario 4: ODU1_ODU0 Mode................................................................................................169 5.6.1 Networking Diagram.............................................................................................................................169 5.6.2 Service Signal Flow...............................................................................................................................170 5.6.3 Configuration Process............................................................................................................................170 5.7 Application Scenario 5: ODUflex Non-Convergence Mode..........................................................................171 5.7.1 Networking Diagram.............................................................................................................................171 5.7.2 Service Signal Flow...............................................................................................................................172 5.7.3 Configuration Process............................................................................................................................172
6 Configuring the LOA Board (Manually by Station)...........................................................174

6.1 Overview of the Working Mode.....................................................................................................................176 6.2 Configuration Procedures...............................................................................................................................176 6.3 Application Scenario 1: Conversion Between Eight Any Services and One OTU2 Optical Signals (with ODU0 Mapping)..............................................................................................................................................................187 6.3.1 Networking Diagram.............................................................................................................................187 6.3.2 Service Signal Flow...............................................................................................................................188 6.3.3 Configuration Process............................................................................................................................189 6.4 Application Scenario 2: Conversion Between Four Any Services and One OTU2 Optical Signals..............191 6.4.1 Networking Diagram.............................................................................................................................191 6.4.2 Service Signal Flow...............................................................................................................................192 6.4.3 Configuration Process............................................................................................................................193 6.5 Application Scenario 3: Conversion Between Four OTU1 Services and One OTU2 Optical Signals (with ODU0 Mapping)..............................................................................................................................................................194 6.5.1 Networking Diagram.............................................................................................................................194 6.5.2 Service Signal Flow...............................................................................................................................195 6.5.3 Configuration Process............................................................................................................................196 6.6 Application Scenario 4: Conversion Between Two 3G-SDI Services and One OTU2 Optical Signals........197 6.6.1 Networking Diagram.............................................................................................................................197 6.6.2 Service Signal Flow...............................................................................................................................198 6.6.3 Configuration Process............................................................................................................................199 6.7 Application Scenario 5: Conversion Between One FC800 Services and One OTU2 Optical Signals...........200 6.7.1 Networking Diagram.............................................................................................................................201 6.7.2 Service Signal Flow...............................................................................................................................201 Issue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xv
Contents
6.7.3 Configuration Process............................................................................................................................202
7 Configuring WDM Services (by Station Service Package)...............................................204

7.1 Overview of the Service Packages.................................................................................................................205 7.1.1 Service Packages for the TN52TOM Board..........................................................................................205 7.1.2 Service Packages for the THA/TOA Board...........................................................................................211 7.1.3 Service Packages for the LOA Board....................................................................................................212 7.2 Configuring Service Packages........................................................................................................................213
8 Configuring WDM Services (by Trail)..................................................................................218

8.1 WDM Trail.....................................................................................................................................................219 8.2 Creating OCh Trails by Trail Search..............................................................................................................223 8.3 Configuration Example...................................................................................................................................225 8.3.1 Configuration Networking Diagram......................................................................................................225 8.3.2 Service Signal Flow...............................................................................................................................226 8.3.3 Configuration Process............................................................................................................................227 8.4 Parameters: End to End Service Configuration..............................................................................................230
9 Configuring SDH Services......................................................................................................234

9.1 SDH Service Configuration Process...............................................................................................................236 9.2 SDH Service Overhead...................................................................................................................................236 9.2.1 Trace Byte..............................................................................................................................................237 9.2.2 Signal Label Byte..................................................................................................................................237 9.3 Configuring Services on the Non-Protection Ring.........................................................................................237 9.3.1 Networking Diagram.............................................................................................................................237 9.3.2 Signal Flow and Timeslot Allocation....................................................................................................238 9.3.3 Configuration Process............................................................................................................................239 9.4 Configuring 1+1 Linear MSP Services..........................................................................................................243 9.4.1 Networking Diagram.............................................................................................................................243 9.4.2 Signal Flow and Timeslot Allocation....................................................................................................243 9.4.3 Configuration Process............................................................................................................................245 9.5 Configuring the Two-Fiber Bidirectional MSP Ring Services......................................................................252 9.5.1 Networking Diagram.............................................................................................................................253 9.5.2 Signal Flow and Timeslot Allocation....................................................................................................253 9.5.3 Configuration Process............................................................................................................................254 9.6 Configuring the SNCP Tangent Ring Services..............................................................................................259 9.6.1 Configuration Networking Diagram......................................................................................................260 9.6.2 Service Signal Flow and Timeslot Allocation.......................................................................................261 9.6.3 Configuration Process............................................................................................................................262 9.7 Parameter........................................................................................................................................................267 9.7.1 SDH Service Configuration...................................................................................................................267 9.7.2 SNCP Service Control...........................................................................................................................268 9.7.3 VC4 Path Overhead...............................................................................................................................270
10 Configuring Ethernet Services..............................................................................................275

Issue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xvi
Contents
10.1 Ethernet Service Types.................................................................................................................................278 10.1.1 Ethernet Private Line Service..............................................................................................................278 10.1.2 Ethernet LAN Service.........................................................................................................................279 10.2 Basic Concepts.............................................................................................................................................282 10.2.1 Tag Attributes......................................................................................................................................282 10.2.2 VLAN Group.......................................................................................................................................283 10.2.3 QinQ....................................................................................................................................................284 10.2.4 MAC Address Filtering.......................................................................................................................285 10.2.5 IGMP Snooping...................................................................................................................................286 10.2.6 STP/RSTP/MSTP................................................................................................................................289 10.3 Configuration Process of Ethernet Services.................................................................................................292 10.3.1 EPL Service Configuration Process....................................................................................................292 10.3.2 EVPL (QinQ) Service Configuration Process.....................................................................................293 10.3.3 EPLAN Service Configuration Process...............................................................................................294 10.4 Configuring Ethernet Services in an OTN System.......................................................................................295 10.4.1 Creating Cross-Connections on an Ethernet Board.............................................................................295 10.4.2 Creating EPL Services.........................................................................................................................297 10.4.3 Creating EPLAN Services...................................................................................................................299 10.4.4 Creating VLANs Filtering...................................................................................................................301 10.4.5 Creating VLAN Unicast......................................................................................................................302 10.4.6 Configuring the Aging Time for MAC Addresses..............................................................................303 10.4.7 Creating EVPL (QinQ) Services.........................................................................................................304 10.5 Configuring Ethernet Services in an OCS System.......................................................................................306 10.5.1 Creating Cross-Connections Between an Ethernet Board and a Line Board......................................306 10.5.2 Creating EPL Services.........................................................................................................................307 10.5.3 Creating EPLAN Services...................................................................................................................308 10.5.4 Creating VLANs Filtering...................................................................................................................309 10.5.5 Creating VLAN Unicast......................................................................................................................310 10.5.6 Configuring the Aging Time for MAC Addresses..............................................................................311 10.5.7 Creating EVPL (QinQ) Services.........................................................................................................312 10.5.8 Creating EVPL (QinQ) Services.........................................................................................................314 10.6 Configuration Example: Configuring EPL Services....................................................................................315 10.6.1 Networking Diagram...........................................................................................................................315 10.6.2 Service Signal Flow and Wavelength Allocation................................................................................316 10.6.3 Configuration Process..........................................................................................................................318 10.7 Configuration Example: Configuring EVPL (QinQ) Services on a WDM Network...................................323 10.7.1 Networking Diagram...........................................................................................................................323 10.7.2 Service Signal Flow and Wavelength Allocation................................................................................324 10.7.3 Configuration Process..........................................................................................................................326 10.8 Configuration Example: Configuring EPLAN Services (IEEE 802.1d Bridge) on a WDM Network........329 10.8.1 Networking Diagram...........................................................................................................................329 10.8.2 Service Signals Flow and Wavelength Allocation..............................................................................330 Issue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xvii
Contents
10.8.3 Configuration Process..........................................................................................................................332 10.9 Configuration Example: Configuring EVPLAN Services (IEEE 802.1q Bridge) on a WDM Network ..............................................................................................................................................................................337 10.9.1 Networking Diagram...........................................................................................................................337 10.9.2 Service Signals Flow...........................................................................................................................338 10.9.3 Configuration Process..........................................................................................................................340 10.10 Configuration Example: Configuring EVPLAN Services (IEEE 802.1 ad Bridge) on a WDM Network ..............................................................................................................................................................................346 10.10.1 Networking Diagram.........................................................................................................................346 10.10.2 Service Signals Flow and Wavelength Allocation............................................................................347 10.10.3 Configuration Process........................................................................................................................349 10.11 Configuration Example: Configuring EVPL and EVPLAN Services (IEEE 802.1q Bridge) on a WDM Network................................................................................................................................................................355 10.11.1 Networking Diagram.........................................................................................................................355 10.11.2 Service Signals Flow.........................................................................................................................356 10.11.3 Configuration Process........................................................................................................................359 10.12 Configuration Example: Configuring EPL Services on a SDH Network..................................................360 10.12.1 Networking Diagram.........................................................................................................................360 10.12.2 Signal Flow and Timeslot Allocation................................................................................................361 10.12.3 Configuration Process........................................................................................................................363 10.13 Configuration Example: Configuring EVPL (QinQ) Services on a SDH Network...................................372 10.13.1 Networking Diagram.........................................................................................................................372 10.13.2 Signal Flow and Timeslot Allocation................................................................................................374 10.13.3 Configuration Process........................................................................................................................376 10.14 Configuration Example: Configuring PORT-Shared EVPL (VLAN) Services on a SDH Network.........383 10.14.1 Networking Diagram.........................................................................................................................383 10.14.2 Signal Flow and Timeslot Allocation................................................................................................384 10.14.3 Configuration Process........................................................................................................................386 10.15 Configuration Example: Configuring VCTRUNK-Shared EVPL Services on a SDH Network...............396 10.15.1 Networking Diagram.........................................................................................................................396 10.15.2 Signal Flow and Timeslot Allocation................................................................................................397 10.15.3 Configuration Process........................................................................................................................399 10.16 Configuration Example: Configuring EPLAN Services (IEEE 802.1d Bridge) on a SDH Network ..............................................................................................................................................................................407 10.16.1 Networking Diagram.........................................................................................................................407 10.16.2 Signal Flow and Timeslot Allocation................................................................................................408 10.16.3 Configuration Process........................................................................................................................410 10.17 Configuration Example: Configuring EVPLAN Services (IEEE 802.1q Bridge) on a SDH Network ..............................................................................................................................................................................419 10.17.1 Networking Diagram.........................................................................................................................419 10.17.2 Signal Flow and Timeslot Allocation................................................................................................421 10.17.3 Configuration Process........................................................................................................................424 10.18 Configuration Example: Configuring EVPLAN Services (IEEE 802.1ad Bridge) on a SDH Network ..............................................................................................................................................................................436 Issue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xviii
Contents
10.18.1 Networking Diagram.........................................................................................................................436 10.18.2 Signal Flow and Timeslot Allocation................................................................................................438 10.18.3 Configuration Process........................................................................................................................441 10.19 Configuration Example: Configuring EVPL and EVPLAN Services (IEEE 802.1q Bridge) on a SDH Network................................................................................................................................................................451 10.19.1 Networking Diagram.........................................................................................................................451 10.19.2 Signal Flow and Timeslot Allocation................................................................................................452 10.19.3 Configuration Process........................................................................................................................456 10.20 Parameters..................................................................................................................................................456 10.20.1 Parameters: Basic Attributes (External Port).....................................................................................457 10.20.2 Parameters: Basic Attributes (Internal Port)......................................................................................458 10.20.3 Parameters: Flow Control (External Port).........................................................................................459 10.20.4 Parameters: Advanced Attributes (External Port).............................................................................459 10.20.5 Parameters: Advanced Attributes (Internal Port)..............................................................................460 10.20.6 Parameters: TAG Attributes..............................................................................................................460 10.20.7 Parameters: Network Attributes........................................................................................................462 10.20.8 Parameters: Ethernet Line Service.....................................................................................................462 10.20.9 Parameters: VLAN Group.................................................................................................................466 10.20.10 Parameters: Ethernet LAN Service..................................................................................................467 10.20.11 Parameters: Aging Time..................................................................................................................473 10.20.12 Parameters: VLAN Unicast.............................................................................................................474 10.20.13 Parameters: Port Mirroring..............................................................................................................474 10.20.14 Parameters: Ethernet Test................................................................................................................474 10.20.15 Parameters: Protocol Fault Management.........................................................................................477 10.20.16 Parameters: Port MAC Address Filtering........................................................................................477
11 Modifying the Configuration Data......................................................................................479

11.1 Modifying Port.............................................................................................................................................480 11.2 Modifying the Services Configuration.........................................................................................................481 11.2.1 Deactivating Cross-Connection Service..............................................................................................481 11.2.2 Deleting Cross-Connections................................................................................................................482 11.2.3 Modifying SDH Services.....................................................................................................................483 11.2.4 Deleting SDH Services........................................................................................................................484 11.2.5 Converting a Non-Protection Service to an SNCP Service.................................................................485 11.2.6 Converting an SNCP Service to a Non-Protection Service.................................................................486 11.3 Conversion Between EPL Ethernet Services and VLAN SNCP Services...................................................487 11.3.1 Converting an EPL Ethernet Service to a VLAN SNCP Service........................................................487 11.3.2 Converting a VLAN SNCP Service to an EPL Ethernet Service........................................................489 11.3.3 Deleting EPL Services.........................................................................................................................490 11.3.4 Deleting EVPL (QinQ) Services.........................................................................................................491 11.3.5 Deleting EPLAN Services...................................................................................................................491 11.3.6 Modifying a VLAN Group..................................................................................................................492 11.3.7 Deleting a VLAN Group.....................................................................................................................493 Issue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xix
Contents
12 Configuration Tasks...............................................................................................................495
12.1 Configuring Working Modes........................................................................................................................497 12.2 Configuring the Service Type.......................................................................................................................497 12.3 Configuring the Service Mode.....................................................................................................................499 12.4 Configuring Common Cross-Connections...................................................................................................499 12.4.1 Creating Cross-Connections................................................................................................................500 12.4.2 Activating Cross-Connections.............................................................................................................502 12.5 Configuring Service Timeslots.....................................................................................................................503 12.6 Configuring SDH Cross-Connections..........................................................................................................504 12.6.1 Querying the Lower Order Cross-Connection Capacity.....................................................................504 12.6.2 Creating SDH Cross-Connections.......................................................................................................505 12.7 Configuring Path Overhead for SDH Services.............................................................................................506 12.7.1 Configuring Trace Byte.......................................................................................................................506 12.7.2 Configuring C2 Byte...........................................................................................................................507 12.8 Configuring the Board Mode........................................................................................................................508 12.9 Creating a VLAN Group..............................................................................................................................509 12.10 Configuring the Aging Time for MAC Addresses.....................................................................................510 12.11 Configuring MAC Address Filtering..........................................................................................................511 12.11.1 Adding the MAC Address of the Opposite Router............................................................................511 12.11.2 Deleting the MAC Address of the Opposite Router..........................................................................513 12.12 Configuring Port Mirroring........................................................................................................................514 12.13 Diagnosing Ethernet Protocol Faults..........................................................................................................515 12.14 Configuring Non-Intrusive Monitoring......................................................................................................515
A Parameters Description...........................................................................................................517
A.1 Enabled/Disabled ..........................................................................................................................................519 A.2 Max. Frame Length ......................................................................................................................................519 A.3 Non-Autonegotiation Flow Control Mode ...................................................................................................520 A.4 Autonegotiation Flow Control Mode ............................................................................................................521 A.5 MAC Loopback ............................................................................................................................................522 A.6 PHY Loopback .............................................................................................................................................523 A.7 QinQ Type Area............................................................................................................................................524 A.8 Port (Ethernet Port Attribute) .......................................................................................................................525 A.9 Port Physical Parameters (Ethernet Port Attribute).......................................................................................525 A.10 Working Mode.............................................................................................................................................528 A.11 Broadcast Packet Suppression Threshold....................................................................................................529 A.12 Enabling Broadcast Packet Suppression .....................................................................................................531 A.13 Default VLAN ID .......................................................................................................................................532 A.14 VLAN Priority ............................................................................................................................................532 A.15 Entry Detection ...........................................................................................................................................533 A.16 Tag Identifier...............................................................................................................................................533 A.17 Source Channel (WDM Cross-Connection)................................................................................................534 A.18 Sink Channel (WDM Cross-Connection Configuration)............................................................................535 Issue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xx
Contents
A.19 Activation Status (WDM Cross-Connection Configuration)......................................................................536 A.20 Level (WDM Cross-Connection Configuration).........................................................................................537 A.21 Direction (WDM Cross-Connection Configuration)...................................................................................539 A.22 Service Timeslot (WDM Services)..............................................................................................................540 A.23 Service Mode (WDM Interface)..................................................................................................................542 A.24 Board Mode (WDM Interface)....................................................................................................................543 A.25 Explicit Link................................................................................................................................................545 A.26 Explicit Node...............................................................................................................................................546 A.27 Excluded Node.............................................................................................................................................547 A.28 Auto-Calculation..........................................................................................................................................547 A.29 Copy after Creation......................................................................................................................................548 A.30 Level (WDM Trail Creation).......................................................................................................................549 A.31 Direction (WDM Trail Creation).................................................................................................................550 A.32 Rate (WDM Trail Creation).........................................................................................................................550 A.33 Source (WDM Trail Creation).....................................................................................................................551 A.34 Sink (WDM Trail Creation).........................................................................................................................552 A.35 OVPN Customer (ASON Trail Management).............................................................................................554 A.36 Non-Intrusive Monitoring............................................................................................................................555
B Glossary......................................................................................................................................556
Issue 02 (2011-10-31)
xxi
1 Guidelines for Configuring Equipment by Referring to This Manual
Guidelines for Configuring Equipment by Referring to This Manual

This manual describes how to configure services on the NMS and other NMS operations involved in service configuration. This section provides guidelines to use this manual and obtain reference information. l l See Table 1-1 to obtain the service configuration guidelines. See Table 1-2 to obtain reference information, such as NMS configurations, NE and network configurations, and feature configurations.
Table 1-1 Guidelines for Service Configuration To... Configure WDM services Then... Select the Manually by Station, by Station Service Package, or by Trail mode to configure WDM services as required. For boards that support multiple application scenarios, guidelines are provided for configuring services manually by station in each application scenario. For details, see: l 3 Configuring the TN11TOM Board (Manually by Station) l 4 Configuring the TN52TOM Board (Manually by Station) l 5 Configuring the THA/TOA Board (Manually by Station) l 6 Configuring the LOA Board (Manually by Station) Configure Ethernet services See Configuring Ethernet Services to understand Ethernet Basic Concepts and complete Ethernet service configurations by referring to Configuration Process of Ethernet Services.
NOTE
l To configure services with ODUk SNCP protection, see ODUk SNCP Protection in the Feature Description. l To configure PID boards, see PID in the Feature Description.
Issue 02 (2011-10-31)
Table 1-2 Guidelines for Reference Information To... Quickly understand NMS operations Then... See the Commissioning Guide: l Connecting the NMS Computer Connecting the U2000 Server Directly Connecting the U2000 Server Through a LAN l U2000 Quick Guide Logging In to the U2000 Client Exiting a U2000 Client l Web LCT Quick Guide Connecting the Web LCT to NEs Starting the Web LCT Logging In to the Web LCT Shutting Down the Web LCT l Entering the Common Views Opening the Main Topology on the U2000 NE List on the Web LCT Opening the NE Explorer Opening the NE Panel l Using Online Help Configure NEs and networks See Configuring NE and Network in the Commissioning Guide. Configure each functional part of a network according to the network creation process so that services can be created on the network topology. See Performance Management in the Commissioning Guide to query and set performance monitoring. See the description of each board in the Hardware Description: l Physical and Logical Ports: Describes physical ports displayed on the NMS and logical ports of each board. l Configuration of Cross-connection: Describes crossconnection configurations of each board. l Parameters Can Be Set or Queried by NMS: Describes parameters that can be set or queried on the NMS for each board, default values of the parameters, and parameter configuration principles. Complete optical-layer configurations or service grooming See Configuring Wavelength Grooming in the Commissioning Guide. Complete wavelength grooming by referring to Wavelength Grooming Configuration Flow.
Monitor performance using the NMS Understand detailed information about boards
Issue 02 (2011-10-31)
To... Configure features
Then... See the Feature Description to understand features, such as: l Optical Line Protection l Intra-Board 1+1 Protection l Intelligent Power Adjustment (IPA) l Clock Feature(OTN) l OTN Overheads l QoS (OTN) l DCN l Master-Slave Subrack l 40G Transmission System To understand more features, see Mapping Relationship Between Products and Features in the Feature Description.
Back up NE data
See Backing Up the NE Database to the SCC Board, Manually Backing Up the NE Database to a CF Card, and Backing Up Device Data to the NMS Server or the NMS Client in the Commissioning Guide.
Issue 02 (2011-10-31)
2 Configuring WDM Services (Manually by Station)
Configuring WDM Services (Manually by Station)
About This Chapter

When manually configuring WDM services by station, you need to perform various operations such as configuring board service types and creating cross-connections. Configuring WDM services in this mode involves multiple NMS GUIs and the configuration process is complex. However, the mode is applicable to various scenarios and very flexible. 2.1 Basic Concepts The basic concepts involved in WDM service configuration include electrical cross-connections, WDM service types, and board models. Understanding the basic concepts helps you successfully configure services. 2.2 WDM Service Configuration Flow This section describes the configuration process of boards and services. Before configuring WDM services according to the configuration flow, complete the basic configuration of NEs according to the configuration flow of creating a network. 2.3 Configuring WDM Services for OTU Boards Without Cross-Connect Capability This section describes how to configure the GE services by using the LDM board, which is a type of OTU board that does not require cross-connection configuration. 2.4 Configuring WDM Services for OTU Boards with Cross-Connect Capability This section describes how to configure GE services by using the LQMS board. 2.5 Configuring WDM Services for Tributary Boards and Line Boards This section describes how to configure GE services by using the TQM and NQ2 boards. 2.6 Configuring WDM Services for Boards with the Layer 2 Switching Function This section describes how to configure GE services by using the boards with Layer 2 processing functions (the TBE and L4G boards in this example). 2.7 Configuring 10GE LAN Services by Using the TDX and NS2 Boards This section describes how to configure 10GE LAN services by using the TDX and NS2 boards. 2.8 Parameters Describes the parameters involved in the WDM services configuration.
Issue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 4
2.1 Basic Concepts

The basic concepts involved in WDM service configuration include electrical cross-connections, WDM service types, and board models. Understanding the basic concepts helps you successfully configure services.
2.1.1 Electrical Cross-Connections

Cross-connections on WDM equipment can be classified into two types: optical crossconnections and electrical cross-connections. Optical cross-connections cross-connect optical 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. Before configuring WDM services, you need to be familiar with basic types of cross-connections.
Overview of Cross-Connections
The grooming function of electrical cross-connections of WDM equipment helps WDM networks to change from static networks to dynamic networks. The MUX/DMUX of the traditional WDM equipment supports only the point-to-point multiplexing scheme, whereas the MUX/DMUX of the NG WDM equipment supports the end-to-end management capability. In addition, the NG WDM equipment supports cross-connections such as GE and ODUk crossconnections. Electrical cross-connections are classified as follows: l l According to the cross-connection level and granularity, electrical cross-connections are classified into, for example, GE, 10GE, Any, and ODUk cross-connections. According to the cross-connection mode, cross-connections are classified into centralized cross-connections, distributed cross-connections, and mesh-group cross-connections. Centralized cross-connections: Cross-connections are implemented using crossconnect boards. The board where a cross-connect service is created can be housed in any slot that supports the board. Distributed cross-connections: Cross-connections are implemented using boards that are housed in paired slots. Mesh-group cross-connections: Cross-connections are implemented using boards that are housed in mesh-group slots. 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 2-1, 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 2-1 Intra-board cross-connections
3(RX1/TX1)-1 4(RX2/TX2)-1 5(RX3/TX3)-1 6(RX4/TX4)-1 201(LP1/LP1)-1 201(LP1/LP1)-2 201(LP1/LP1)-3 201(LP1/LP1)-4 1(IN1/OUT1)-1
Issue 02 (2011-10-31)
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 2-2. Figure 2-2 Direct cross-connections
A 3(RX1/TX1)-1 4(RX2/TX2)-1 5(RX3/TX3)-1 6(RX4/TX4)-1 201(LP1/LP1)-1 201(LP1/LP1)-2 201(LP1/LP1)-3 201(LP1/LP1)-4 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 2-3. Figure 2-3 Inter-board cross-connections
A 3(RX1/TX1)-1 4(RX2/TX2)-1 5(RX3/TX3)-1 6(RX4/TX4)-1 201(LP1/LP1)-1 201(LP1/LP1)-2 201(LP1/LP1)-3 201(LP1/LP1)-4 1(IN1/OUT1)-1
B 3(RX1/TX1)-1 4(RX2/TX2)-1 5(RX3/TX3)-1 6(RX4/TX4)-1 201(LP1/LP1)-1 201(LP1/LP1)-2 201(LP1/LP1)-3 201(LP1/LP1)-4 1(IN1/OUT1)-1
Signal Flow of Electrical Cross-Connections

For WDM equipment, the OTU board, tributary board, and line board work together to complete service grooming. Client services are transmitted from the client side of the WDM equipment, and then modulated to the WDM system for transmission after service grooming and convergence. Figure 2-4 considers the OTU board with the GE/Any and ODUk crossconnection function as a module to describe the signal flow of the electrical cross-connections. Figure 2-4 describes the signal flow of the SDH electrical cross-connection service of the OptiX OSN 8800.
Issue 02 (2011-10-31)
Figure 2-4 Signal flow of electrical cross-connections for the OptiX OSN 6800/3800
L2 processing
VCTRUNK AP1 Optical module L2 APn GE/Any crossconnection LP1.X
Backplane bus
Backplane bus
RX1/TX1 RXn/TXn
LP1.1 ODUk crossconnection
LP1 OTN
Optical module
IN/OUT
Tributary board Line board OTU board (tributary-and-line-joint board)

NOTE
The boards that support the grooming of electrical cross-connections have both external ports and internal ports. These ports are classified into the following types: l TX/RX port: client-side optical port of the board that receives and transmits signals. l IP port: internal port that corresponds to the RX/TX port. It can be regarded as a RX/TX port. l AP port: convergence port that represents the internal port of the L2 module. In this case, the corresponding IP port is an external port. l LP: logical port that functions as the connection point of cross-connections. l OP port: internal port that corresponds to the IN/OUT port. It can be regarded as an IN/OUT port. l IN/OUT port: line-side optical port of the board that receives and transmits signals.
The signals are cross-connected in the following process: 1. The optical signals are transmitted to the OTU board through the RX/TX port and become electrical signals. After the possible L2 processing, the electrical signals are transmitted to the GE/Any cross-connect module through the AP port and work with the possible crossconnect signals from the backplane, to implement the GE/Any cross-connections. The electrical signals are transmitted to the ODUk cross-connect module through the LP port and work with the possible ODUk signals from the backplane, to implement the ODUk cross-connections. Then, the signals are transmitted to the optical module through an OP port and added to the WDM line for transmission.
NOTE
2.
The OptiX OSN 8800 supports the electrical signals that are transmitted to the ODUk cross-connect module through the LP port and work with the possible ODUk signals from the backplane, to implement the ODUk cross-connections. Then, the signals are transmitted to the optical module through an OP port and added to the WDM line for transmission.
Issue 02 (2011-10-31)
Figure 2-5 Signal flow of electrical cross-connections for the OptiX OSN 8800 SDH
Backplane bus
RX1/TX1 RXn/TXn Optical module
VC4/VC3/ VC12 crossconnection
LP1 SDH
Optical module
IN/OUT
Tributary board Line board
NOTE
The boards that support the grooming of electrical cross-connections have both external ports and internal ports. These ports are classified into the following types: l l l l TX/RX port: client-side optical port of the board that receives and transmits signals. LP: logical port that functions as the connection point of cross-connections. OP port: internal port that corresponds to the IN/OUT port. It can be regarded as an IN/OUT port. IN/OUT port: line-side optical port of the board that receives and transmits signals.
The signals are cross-connected in the following process: Signals are transmitted to an SDH board through the RX/TX port and become electrical signals. Then, the electrical signals are transmitted to the VC4/VC3/VC12 cross-connect module, and work with the cross-connect signals that may come from the backplane to implement VC-4/ VC-3/VC-12 cross-connections. After being transmitted to the SDH processing module on the SDH board, the electrical signals are transmitted to a WDM-side optical module and become the optical signals that have the DWDM standard wavelengths compliant with ITU-T G.694.1.
For details on how to choose ports of a board for cross-connections, see service configuration descriptions of the board in the Hardware Description.
Restrictions on Cross-Connection Configuration

l The slots that support cross-connections vary according to different types of equipment and boards. The OptiX OSN 8800 supports only centralized cross-connections with the granularity of ODU0, ODU1, ODU2/ODU2e, ODUflex, and ODU3. The OptiX OSN 6800 supports both centralized cross-connections and distributed crossconnections. When both types of cross-connections are configured, the system uses distributed cross-connections with preference.
The granularity of centralized cross-connections can be GE, 10GE, ODU1, or ODU2. The granularity of distributed cross-connections can be GE, ODU1, OTU1, or Any. Cross-connections can be implemented using boards that are housed in seven groups of paired slots: IU1 and IU2, IU3 and IU4, IU5 and IU6, IU7 and IU8, IU11 and IU12, IU13 and IU14, and IU15 and IU16. The OptiX OSN 3800 supports both distributed cross-connections and mesh-group cross-connections. The granularity of distributed cross-connections is GE. Cross-connections can be implemented using boards that are housed in two groups of paired slots: IU2 and IU3, and IU4 and IU5. For the OptiX OSN 3800, only the 52TOM board supports distributed cross-connections. The granularity of mesh-group cross-connections can be GE, ODU1, or Any. Crossconnections can be implemented using boards that are housed in four slots in the mesh group: IU2, IU3, IU4, and IU5. l If you configure a cross-connection between the two optical ports on the OTU board, the source of a normal cross-connection can also serve as the source of other normal crossconnections, but its sink cannot be the sink of other cross-connections. The two sources of an SNCP cross-connection cannot be the source of other cross-connections, and its sinks cannot be the sink of other cross-connections. When configuring the electrical cross-connection for a service on the OptiX OSN 3800, OptiX OSN 6800, and OptiX OSN 8800, you must make sure that the WDM-side optical channel numbers at the transmit and receive ends of the service in a direction must be the same. Otherwise, the service fails.
2.1.2 Service Types

This topic describes the service types that are supported in the WDM service configuration. Table 2-1 lists the services that can be accessed by the OptiX OSN 8800. Table 2-1 Service access types (OTN) Service Category SDH/POS/ATM Service Type STM-1, STM-4, STM-16, STM-64, STM-256 Reference Standard ITU-T G.707 ITU-T G.691 ITU-T G.957 ITU-T G.693 ITU-T G.783 ITU-T G.825 SONET OC-3, OC-12, OC-48, OC-192, OC-768 GR-253-CORE GR-1377-CORE ANSI T1.105 Ethernet service FE, GE, 10GE WAN, 10GE LAN IEEE 802.3u IEEE 802.3z IEEE 802.3ae
Service Category SAN service
Service Type ESCON FICON, FICON Express, FC100, FC200, FC400, FC800, FICON 8G, FC1200, FICON 4G ISC 1G, ISC 2G, ETR, CLO InfiniBand 2.5G, InfiniBand 5G
Reference Standard ANSI X3.296 ANSI X3.230 ANSI X3.303 InfiniBandTM Architecture Release 1.2.1 ITU-T G.709 ITU-T G.959.1
OTN service
OTU1, OTU2, OTU2e, OTU3
Video service and others
HD-SDI DVB-ASI SDI FDDI 3G-SDI
SMPTE 292M EN 50083-9 SMPTE 259M ISO 9314 SMPTE 424M
FE: fast Ethernet GE: gigabit Ethernet ESCON: enterprise systems connection FICON: fiber connection FC: fiber channel HD-SDI: bit-serial digital interface for high-definition television systems DVB-ASI: digital video broadcasting-asynchronous serial interface SDI: serial digital interface FDDI: fiber distributed data interface 3G-SDI: 3G-serial digital interface
NOTE As specified in the SMPTE-259M, SDI is also called SD-SDI.
Table 2-2 lists the services that can be accessed by the OptiX OSN 6800. Table 2-2 Service access types Service Category SDH/POS/ATM Service Type STM-1, STM-4, STM-16, STM-64, STM-256 Reference Standard ITU-T G.707 ITU-T G.691 ITU-T G.957 ITU-T G.693 ITU-T G.783 ITU-T G.825
Service Category SONET
Service Type OC-3, OC-12, OC-48, OC-192, OC-768
Reference Standard GR-253-CORE GR-1377-CORE ANSI T1.105
Ethernet service
FE GE 10GE WAN, 10GE LAN
IEEE 802.3u IEEE 802.3z IEEE 802.3ae ANSI X3.296 ANSI X3.230 ANSI X3.303 InfiniBandTM Architecture Release 1.2.1
SAN service
ESCON FICON, FICON Express, FICON 4G FC100, FC200, FC400, FC800, FICON 8G, FC1200 ISC 1G, ISC 2G, ETR, CLO InfiniBand 2.5G, InfiniBand 5G
OTN service
OTU1, OTU2, OTU2e, OTU3
ITU-T G.709 ITU-T G.959.1
SMPTE 292M EN 50083-9 SMPTE 259M ISO 9314 SMPTE 424M
FE: fast Ethernet GE: gigabit Ethernet ESCON: enterprise systems connection FICON: fiber connection FC: fiber channel HD-SDI: bit-serial digital interface for high-definition television Systems DVB-ASI: digital video broadcasting-asynchronous serial interface SDI: serial digital interface FDDI: fiber distributed data interface 3G-SDI: 3G-serial digital interface
Table 2-3 lists the services that can be accessed by the OptiX OSN 3800.
Issue 02 (2011-10-31)
11
Table 2-3 Service access types Service Category SDH/POS/ATM Service Type STM-1, STM-4, STM-16, STM-64 Reference Standard ITU-T G.707 ITU-T G.691 ITU-T G.957 ITU-T G.783 ITU-T G.825 SONET OC-3, OC-12, OC-48, OC-192 GR-253-CORE GR-1377-CORE ANSI T1.105 Ethernet service FE GE 10GE WAN, 10GE LAN SAN service ESCON FICON, FICON Express, FICON 4G FC100, FC200, FC400, FC800, FICON 8G, FC1200 ISC 1G, ISC 2G, ETR, CLO InfiniBand 2.5G, InfiniBand 5G OTN service OTU1, OTU2, OTU2e ITU-T G.709 ITU-T G.959.1 Video service and others HD-SDI DVB-ASI SDI FDDI 3G-SDI SMPTE 292M EN 50083-9 SMPTE 259M ISO 9314 SMPTE 424M IEEE 802.3u IEEE 802.3z IEEE 802.3ae ANSI X3.296 ANSI X3.230 ANSI X3.303 InfiniBandTM Architecture Release 1.2.1
Issue 02 (2011-10-31)
12
Service Category FE: fast Ethernet GE: gigabit Ethernet
Service Type
Reference Standard
ESCON: enterprise systems connection FICON: fiber connection FC: fiber channel HD-SDI: bit-serial digital interface for high-definition television Systems DVB-ASI: digital video broadcasting-asynchronous serial interface SDI: serial digital interface FDDI: fiber distributed data interface
Table 2-4 lists the rates of the services that can be accessed by the OptiX OSN 8800. Table 2-4 Service type and service rate Service Category SDH/POS/ ATM Service Type STM-1 STM-4 STM-16 STM-64 STM-256 SONET OC-3 OC-12 OC-48 OC-192 OC-768 Ethernet service FE GE 10GE WAN 10GE LAN SAN service ESCON FICON
Issue 02 (2011-10-31)
Service Rate 155.52 Mbit/s 622.08 Mbit/s 2.5 Gbit/s 9.95 Gbit/s 39.81 Gbit/s 155.52 Mbit/s 622.08 Mbit/s 2.5 Gbit/s 9.95 Gbit/s 39.81 Gbit/s
Legend
OTU3 STM-256/OC-768
40G
OTU2e OTU2 FC1200 10GE LAN
10G
STM-64/OC-192/10GE WAN FC800/FICON8G
4G
FC400/FICON4G 3G-SDI OTU1 STM-16/OC-48 FICON Express/FC200 HD-SDI GE FICON/FC100 STM-4/OC-12 SDI/DVB-ASI ESCON STM-1/OC-3 FE
2G
1G
0.1G
125 Mbit/s 1.25 Gbit/s 9.95 Gbit/s 10.31 Gbit/s 200 Mbit/s 1.06 Gbit/s
13
Service Category
Service Type FICON Express FC100 FC200 FC400 FC800 FC1200 FICON4G FICON8G ISC 1G ISC 2G ETR CLO InfiniBand 2.5G InfiniBand 5G
Service Rate 2.12 Gbit/s 1.06 Gbit/s 2.12 Gbit/s 4.25 Gbit/s 8.5 Gbit/s 10.51 Gbit/s 4.25 Gbit/s 8.5 Gbit/s 1.06 Gbit/s 2.12 Gbit/s 16 Mbit/s 16 Mbit/s 2.5 Gbit/s 5 Gbit/s 2.67 Gbit/s 10.71 Gbit/s 11.10 Gbit/s 43.02 Gbit/s 1.485 Gbit/s 270 Mbit/s 270 Mbit/s 125 Mbit/s 2.97 Gbit/s
Legend
OTN service
OTU1 OTU2 OTU2e OTU3
Table 2-5 lists the rates of the services that can be accessed by the OptiX OSN 6800.
Issue 02 (2011-10-31)
14
Table 2-5 Service type and service rate Service Category SDH/POS/ ATM Service Type STM-1 STM-4 STM-16 STM-64 STM-256 SONET OC-3 OC-12 OC-48 OC-192 OC-768 Ethernet service FE GE 10GE WAN 10GE LAN SAN service ESCON FICON FICON Express FC100 FC200 FC400 FC800 FC1200 FICON4G FICON8G ISC 1G ISC 2G ETR Service Rate 155.52 Mbit/s 622.08 Mbit/s 2.5 Gbit/s 9.95 Gbit/s 39.81 Gbit/s 155.52 Mbit/s 622.08 Mbit/s 2.5 Gbit/s 9.95 Gbit/s 39.81 Gbit/s
0.1G 2G 10G
OTU2e OTU2 FC1200 10GE LAN STM-64/OC-192/10GE WAN FC800/FICON8G
Legend
OTU3 STM-256/OC-768
40G
4G
1G
125 Mbit/s 1.25 Gbit/s 9.95 Gbit/s 10.31 Gbit/s 200 Mbit/s 1.06 Gbit/s 2.12 Gbit/s 1.06 Gbit/s 2.12 Gbit/s 4.25 Gbit/s 8.5 Gbit/s 10.51 Gbit/s 4.25 Gbit/s 8.5 Gbit/s 1.06 Gbit/s 2.12 Gbit/s 16 Mbit/s
Issue 02 (2011-10-31)
15
Service Category
Service Type CLO InfiniBand 2.5G InfiniBand 5G
Service Rate 16 Mbit/s 2.5 Gbit/s 5 Gbit/s 2.67 Gbit/s 10.71 Gbit/s 11.10 Gbit/s 43.02 Gbit/s 1.485 Gbit/s 270 Mbit/s 270 Mbit/s 125 Mbit/s 2.97 Gbit/s
Legend
OTN service
Table 2-6 lists the rates of the services that can be accessed by the OptiX OSN 3800. Table 2-6 Service type and service rate Service Category SDH/POS/ ATM Service Type STM-1 STM-4 STM-16 STM-64 STM-256 SONET OC-3 OC-12 OC-48 OC-192 OC-768 Ethernet service
Issue 02 (2011-10-31)
Service Rate 155.52 Mbit/s 622.08 Mbit/s 2.5 Gbit/s 9.95 Gbit/s 39.81 Gbit/s 155.52 Mbit/s 622.08 Mbit/s 2.5 Gbit/s 9.95 Gbit/s 39.81 Gbit/s
Legend
OTU3 STM-256/OC-768
40G
OTU2e OTU2 FC1200 10GE LAN
10G
STM-64/OC-192/10GE WAN FC800/FICON8G
4G
2G
1G
0.1G
FE
125 Mbit/s
16
Service Category
Service Type GE 10GE WAN 10GE LAN
Service Rate 1.25 Gbit/s 9.95 Gbit/s 10.31 Gbit/s 200 Mbit/s 1.06 Gbit/s 2.12 Gbit/s 1.06 Gbit/s 2.12 Gbit/s 4.25 Gbit/s 8.5 Gbit/s 10.51 Gbit/s 4.25 Gbit/s 8.5 Gbit/s 1.06 Gbit/s 2.12 Gbit/s 16 Mbit/s 16 Mbit/s 2.5 Gbit/s 5 Gbit/s 2.67 Gbit/s 10.71 Gbit/s 11.10 Gbit/s 43.02 Gbit/s 1.485 Gbit/s 270 Mbit/s 270 Mbit/s 125 Mbit/s
Legend
SAN service
ESCON FICON FICON Express FC100 FC200 FC400 FC800 FC1200 FICON4G FICON8G ISC 1G ISC 2G ETR CLO InfiniBand 2.5G InfiniBand 5G
OTN service
HD-SDI DVB-ASI SDI FDDI
Issue 02 (2011-10-31)
17
Service Category
Service Type 3G-SDI
Service Rate 2.97 Gbit/s
Legend
2.1.3 Board Model (Standard Mode and Compatible Mode)

Starting from V100R006C01, 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 2-7 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 2-7 Names displayed on the NMS and availability on different types of equipment Name in Standard Mode (Standard Mode, adding logical board) 53ND2 53NQ2 53NS2 11LOA 54ENQ2 (STND) 55NPO2 (STND) 55NPO2E Name in Compatibl e Mode (Compatibl e Mode, adding logical board) 53ND2 (COMP) 53NQ2 (COMP) 53NS2 (COMP) 54ENQ2 55NPO2 Name in Compatibl e Mode (NE Panel) OptiX OSN OptiX OSN OptiX OSN 8800 6800 3800
53ND2 53ND2 53ND2 11LOA 54ENQ2 55NPO2 55NPO2E
Y Y Y Y Y Y Y
Y Y Y Y N N N
N N Y Y N N N
Issue 02 (2011-10-31)
18

NOTE
l The LOA and NPO2E boards support only the standard mode. l Y indicates that a board is available on the equipment and N indicates that a board is unavailable on the equipment. 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.
Available Channels in Different Modes

The following uses the TN53NS2 board as an example to illustrate available channels on the board in different modes. For the board models of other boards in different modes, see the Hardware Description. l Compatible mode Figure 2-6 shows the board model of the TN53NS2 board in compatible mode. Figure 2-6 Board model of the TN53NS2 board in compatible mode
Other tributary/ line/PID board Other tributary/ line/PID board Other tributary/ line/PID board
8 x ODU0 161 (ODU0LP1/ODU0LP1)-1 161 (ODU0LP1/ODU0LP1)-2
4 x ODU1 51 ODU1 (ODU1LP1/ODU1LP1)-1
1 x ODU2/ODU2e
Backplane
71 (ODU2LP1/ODU2LP1)-1 164 (ODU0LP4/ODU0LP4)-1 164 (ODU0LP4/ODU0LP4)-2 51 ODU1 (ODU1LP1/ODU1LP1)-4 ODU2
1 (IN1/OUT1)-1
Crossconnect module Multiplexin g module Service processing module
ODU1 mapping path
ODU2 mapping path
Automatic cross-connection, which does not need to be configured on the NMS. For example, if ODU0 signals are required, users only need to configure cross-connections from other boards to the ODU0LP port on the board using the NMS. The board's internal structure enables transmission of the multiplexed signal to the ODU2LP port. Users do not need to configure a cross-connection for transmitting the multiplexed signal. Cross-connection that must be configured on the NMS to receive ODUk signals from other boards
ODU0 mapping path
l
Issue 02 (2011-10-31)
Standard mode
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 19
Figure 2-7 shows the board model of the TN53NS2 board in standard mode. Figure 2-7 Board model of the TN53NS2 board in standard mode
IN/OUT-OCH:1-ODU2:1-ODUflex:(1~2)
ODUflex:1 2XODUflex ODUflex:2 ODU2:1 OCH:1
IN/OUT-OCH:1
1 xODU2/ 1xODU 2e
OCH :1
Other tributary/line/PID board
IN/OUT-OCH:1-ODU2:1-ODU1:(1~4)
ODU1:1 4 xODU1 ODU2:1 ODU1:4 OCH : 1 IN/OUT
ODU0:1
IN/OUT-OCH:1-ODU2:1-ODU1:(1~4)-ODU0:(1~2)
ODU1:1 ODU2:1 OCH :1
ODU0:2 8 xODU0 ODU 0:1 ODU 0:2
ODU 1:4
IN/OUT-OCH:1-ODU2:1-ODU0:(1~8)
ODU0:1 8 xODU0 ODU2:1 ODU0: 8 OCH :1
Backplane
Cross-connect module Multiplexing module Service processing module ODU0 mapping path (ODU0>ODU1>ODU2) ODU0 mapping path (ODU0>ODU2)
ODU1 mapping path
ODU2 mapping path
ODUflex mapping path
Cross-connection that must be configured on the NMS to receive ODUk signals from other boards
Issue 02 (2011-10-31)
20
Table 2-8 Comparison of the two modes Item Internal logical ports Compatible Mode Internal logical ports are reserved. Standard Mode Internal logical ports are removed. Instead, all ODU-level internal logical ports are configured as channels for each physical port and they can be ignored during configuration. Services can be transmitted if there are sufficient timeslots and timeslot continuity is not required. For example, the maximum permitted bandwidth of a TN53NS2 board is 10 Gbit/s. After the board receives one channel of ODU1 services, it can still receive ODU0, ODUflex, or ODU1 services on the remaining bandwidth.
Number of timeslots
The number of timeslots allocated to each service is fixed.
Comparison of NMS GUIs for Different Modes

Service creation operations on the NMS vary according to board models. Table 2-9 uses the TN53NS2 board as an example to illustrate the differences in the board operation GUIs. Table 2-9 GUIs on the NMS GUI on the NMS Path View Navigation Path In the NE panel, select a board, double-click the board icon or right-click and choose Path View from the shortcut menu. In the NE Explorer, select the required board and choose Configuration > WDM Interface from the Function Tree. tab. In the NE Explorer, select the required NE and choose Configuration > WDM Service Management from the Function Tree. Compatible Mode See Figure 2-8. Standard Mode See Figure 2-9.
WDM Interface
See Figure 2-10.
See Figure 2-11.
Create CrossConnection Service
See Figure 2-12.
See Figure 2-13.
Issue 02 (2011-10-31)
21
Figure 2-8 Path View (compatible mode)
Figure 2-9 Path View (standard mode)
Issue 02 (2011-10-31)
22
Figure 2-10 WDM Interface (compatible mode)
Figure 2-11 WDM Interface (standard mode)
Issue 02 (2011-10-31)
23
Figure 2-12 Create Cross-Connection Service (compatible mode)
Figure 2-13 Create Cross-Connection Service (standard mode)
2.1.4 ODUflex
Starting from V100R006C01, 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
Only OptiX OSN 8800 supports ODUflex that is applicable to the following boards:
l l l
Tributary boards: TN55TQX, TN53TDX and TN54TOA Line boards: TN53NQ2, TN53ND2, and TN53NS2 Tributary-line integrated board: LOA
NOTE
The TN11LOA, TN53NQ2, TN53ND2, and TN53NS2 boards 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 2-10 GUIs and navigation paths GUI on the NMS WDM Interface Description 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. When Level is set to ODUflex, you must set Service Type. Navigation Path In the NE Explorer, select the required board and choose Configuration > WDM Interface > Advanced Attributes from the Function Tree. In the NE Explorer, select the required NE and choose Configuration > WDM Service Management from the Function Tree. In the displayed window, click New.
Create CrossConnection Service
NOTE
l The value of Occupied ODUTUk Slot Count 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).
ODUflex Configuration Procedure

Figure 2-14 shows the ODUflex configuration flowchart.
Issue 02 (2011-10-31)
25
Figure 2-14 ODUflex configuration flowchart

1 Configure the port working mode
Configure the timeslot configuration mode
Configure the service type
(Optional) Configure ODUflex Tolerance
Configure crossconnections
Table 2-11 describes the ODUflex configuration procedure. Table 2-11 Configuration procedure No.
1
Action Configure the port working mode.
Involved Board Tributary board or tributary-line integrated board
Description l Parameter settings: Set Port Working Mode to ODUflex non-convergence mode. l Operation description: In the NE Explorer, select the required board and choose Configuration > Working Mode from the Function Tree. In the displayed window.
Configure the timeslot configuration mode.
Line board or tributary-line integrated board
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.
Configure the service type.
Tributary board or tributary-line integrated board
l Parameter settings: Set the service type based on the service plan. l Operation description: Choose Configuration > WDM Interface from the Function Tree.
Issue 02 (2011-10-31)
26
No.
4
Action (Optional) Configure ODUflex tolerance
Involved Board Line board or tributary-line integrated board
Description l Parameter settings: Specifies the tolerance of deviation between the actual client-side service rate and the specified rate when the client-side service type is ODUflex. When the tributary board that connects to the ND2 board receives 3G-SDI services from client equipment, set this parameter to 10. If the tributary board receives other services, set it to 100. l Operation description: Choose Configuration > WDM Interface > Advanced Attributes from the Function Tree.
Configure crossconnections.
l Tributary board or line board: interboard crossconnections between tributary and line boards l Tributary-line integrated board: 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 Service Type to the actual clientside signals. 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.
2.2 WDM Service Configuration Flow

This section describes the configuration process of boards and services. Before configuring WDM services according to the configuration flow, complete the basic configuration of NEs according to the configuration flow of creating a network. Before configuring a WDM service, ensure that you have finished checking board parameters. To learn the information about the signal flow of each board, see the Hardware Description. No. OTU Boards Without Grooming Functions OTU Boards With Grooming Functions 12.8 Configuring the Board Mode Line Boards and Tributary Boards 12.8 Configuring the Board Mode Boards with Layer 2 Processing Functions 12.8 Configuring the Board Mode Task Description
Optional
Issue 02 (2011-10-31)
27
No.
OTU Boards Without Grooming Functions -
OTU Boards With Grooming Functions 12.3 Configuring the Service Mode 12.2 Configuring the Service Type
Line Boards and Tributary Boards 12.3 Configuring the Service Mode 12.2 Configuring the Service Type
Boards with Layer 2 Processing Functions 12.3 Configuring the Service Mode 12.2 Configuring the Service Type
Task Description
Optional
12.2 Configuring the Service Type
Mandatory The type of client-side services on boards needs to be set according to the type of services transmitted over the network. Different boards access different types of services. For details, see the client-side specifications of the OTU board and tributary board in the Hardware Description. Optional In addition to crossconnections, the connections between VCTRUNK ports and PORT ports of the boards with Layer 2 processing functions need to be established.
10.4.2 Creating EPL Services For details on creating Ethernet services, see 10 Configuring Ethernet Services.
Issue 02 (2011-10-31)
28
No.
OTU Boards With Grooming Functions Creating crossconnect services (intra-board)
Line Boards and Tributary Boards Creating cross-connect services (intra-board)
Boards with Layer 2 Processing Functions Creating crossconnections on an Ethernet board (intraboard)
Task Description
Optional There is no need to configure crossconnections for the OTU board without grooming functions. Crossconnections must be configured for tributary boards and other OTU boards. For details on how to choose ports of a board for crossconnections, see service configuration descriptions of the board in the Hardware Description.
Issue 02 (2011-10-31)
29
No.
OTU Boards With Grooming Functions -
Line Boards and Tributary Boards Creating cross-connect services (inter-board)
Boards with Layer 2 Processing Functions Creating crossconnections on an Ethernet board (interboard)
Task Description
Optional When tributary boards work with line boards, the inter-board crossconnections must be configured. For details on how to choose ports of a board for crossconnections, see service configuration descriptions of the board in the Hardware Description. Optional When the timeslot configuration mode is set to manual, Send Timeslots and Receive Timeslots need to be set for certain boards.
12.5 Configuring Service Timeslots
Issue 02 (2011-10-31)
30
No.
OTU Boards With Grooming Functions Creating WDM trails by using the trail search function
Line Boards and Tributary Boards Creating WDM trails by using the trail search function
Boards with Layer 2 Processing Functions Creating WDM trails by using the trail search function
Task Description
Optional Create WDM trails by using the trail search function and check whether service configurations are correct. If the end-to-end services on the client side are correctly configured, the client trails of the corresponding level can be searched out. -
2.3 Configuring WDM Services for OTU Boards Without CrossConnect Capability is provided.
2.4 Configuring WDM Services for OTU Boards with CrossConnect Capability is provided.
2.5 Configuring WDM Services for Tributary Boards and Line Boards is provided.
2.6 Configuring WDM Services for Boards with the Layer 2 Switching Function is provided.
NOTE
If a board supports electrical ports, you must configure electrical ports on the U2000 before the board receives electrical signals. See "Configuring Electrical Ports of a Board" in the Commissioning Guide .
2.3 Configuring WDM Services for OTU Boards Without Cross-Connect Capability
This section describes how to configure the GE services by using the LDM board, which is a type of OTU board that does not require cross-connection configuration.
2.3.1 Configuration Networking Diagram

This section describes how to configure a GE service on a ring network.
Service Requirement
See Figure 2-15. Optical NEs (ONEs) A, B, C, and D form a ring network. All the ONEs function as OADM stations. User1 and User2 communicate with each other. One bidirectional GE service is available between station A and station B. At station A, the LDM board accesses one GE service. At station B, the LDM board accesses one GE service. Figure 2-15 Configuration networking diagram of the GE service
User1 East 12LDM
East
West
NMS
West
12LDM
West B
East D
User2 East
West
:OADM West East
Board Configuration Information

In this example, a 12LDM board must be configured at station A and station B.
2.3.2 Service Signal Flow

This section describes how to configure the transparent transmission signal flow of a GE service. There is one bidirectional GE service between stations A and B.
NOTE
You do not need to configure cross-connections on the LDM board.
2.3.3 Configuration Process

This section describes how to configure a bidirectional GE service at stations A and B.
Prerequisite
Fibers are connected correctly according to the network structure. (Namely, OCh trails can be searched out. For details, see Searching for WDM Trails.) Check parameters of the OTU board and ensure that no error is found.
You must be an NM user with "NE operator" authority or higher.
Tools, Equipment, and Materials

U2000/Web LCT (U2000 is recommended)
Procedure on the U2000/Web LCT

Step 1 Set Service Type of the client-side ports on the TN12LDM boards at stations A and B to GE. For details, see 12.2 Configuring the Service Type. Step 2 Optional: Configure service timeslots of the logical port of the TN12LDM board at station A. For details, see 12.5 Configuring Service Timeslots. Step 3 Optional: Configure service timeslots of the logical port of the TN12LDM board at station B. For details, see 12.5 Configuring Service Timeslots. ----End
Verifying Configurations
Check whether service configurations are correct. If the end-to-end services on the client side are correctly configured, the client trails of GE levels can be searched out. For details, see Searching for WDM Trails.
2.4 Configuring WDM Services for OTU Boards with CrossConnect Capability
This section describes how to configure GE services by using the LQMS board.

Service Requirement
On the network shown in Figure 2-16, ONEs A, B, C, and D form a ring network. All the NEs function as OADM stations. The service requirement is as follows: User1 and User2 communicate with each other. One unidirectional GE service is available between station A and station B.
Issue 02 (2011-10-31)
33
Figure 2-16 Configuration networking diagram of the GE service

User1 East 12LQMS
East
West
NMS
West
12LQMS
West
East
B
User2 East
D C
West
:OADM West East

In this example, two 12LQMS boards must be configured at each station.

This section describes how to configure the transparent transmission signal flow of a GE service. One bidirectional GE service is available between station A and station B. Figure 2-17 shows the service signal flow between station A and station B. Figure 2-17 Unidirectional service at each station
Client side 3(RX1/TX1)-1 4(RX2/TX2)-1 5(RX3/TX3)-1 6(RX4/TX4)-1 201(ClientLP/ClientLP)-1 201(ClientLP/ClientLP)-2 201(ClientLP/ClientLP)-3 201(ClientLP/ClientLP)-4 Cross-connect module
NOTE
WDM side 201(ClientLP/ClientLP)-1
1(IN1/OUT1)-1
Service processing module
WDM-side optical module
ClientLP is a logical port. Cross-connections between client-side RX/TX ports and ClientLP ports need to be configured. There are connections between ClientLP ports and WDM-side IN/OUT ports, and therefore cross-connections do not need to be configured.

Prerequisite
Fibers are connected correctly according to the network structure. (Namely, OCh trails can be searched out. For details, see Searching for Trails.) Check parameters of the OTU board and ensure that no error is found. . You must be an NM user with "NE operator" authority or higher.

Background Information
Different boards have different cross-connection capacities. For details, see the functions and features of each board in the Hardware Description. If the capacity of the configured services is greater than the available cross-connection capacity, the service configuration fails.

Step 1 Set Board Mode of the TN12LQMS boards at stations A and B to LQM Mode. For details, see 12.8 Configuring the Board Mode.
NOTE
After Board Mode is set to LQM Mode, the TN12LQMS board can serve as a tributary and line board and convert four Any services into one OTU1 service.
Step 2 Set Service Mode of the client-side ports on the TN12LQMS boards at stations A and B to Client Mode. For details, see 12.3 Configuring the Service Mode.
NOTE
After Service Mode is set to Client Mode, the TN12LQMS board can access services other than OTN services.
Step 3 Set Service Type of the client-side ports on the TN12LQMS boards at stations A and B to GE. For details, see 12.2 Configuring the Service Type. Step 4 Configure the service to be added or dropped at station A. 1. Configure a GE service from the RX/TX port of the LQMS board to the ClientLP port. For details, see 12.4.1 Creating Cross-Connections. The following table lists the values of the parameters for station A. Field Level
NOTE On the Web LCT, this parameter is Service Level.
Value GE
Service Type Direction Source Slot

Issue 02 (2011-10-31)
Bidirectional Shelf0(subrack)-13-12LQMS
35
Field Source Optical Port

NOTE On the Web LCT, this parameter is Source Port.
Value 3(RX1/TX1)
Source Optical Channel

NOTE On the Web LCT, this parameter is Source Optical Path.
Sink Slot Sink Optical Port

NOTE On the Web LCT, this parameter is Sink Port.
Shelf0(subrack)-13-12LQMS 201(ClientLP/ClientLP)
Sink Optical Channel

NOTE On the Web LCT, this parameter is Sink Optical Path.
Activate Immediately
NOTE This parameter is valid only on the U2000. It is not applicable to the Web LCT.
Active
NOTE
For details on how to select a port for electrical cross-connection services, see 2.4.2 Service Signal Flow.
Step 5 Click Query. Ensure that the query result is consistent with the configuration. Step 6 Optional: Configure service timeslots of the logical port of the TN12LQMS board at station A. For details, see 12.5 Configuring Service Timeslots. Step 7 Configure the service to be added or dropped at station B. 1. Configure a GE service from the ClientLP port of the LQMS board to the RX/TX port. For details, see 12.4.1 Creating Cross-Connections. The following table lists the values of the parameters for station B. Field Level
Value GE
Service Type Direction
Bidirectional
Issue 02 (2011-10-31)
36
Field Source Slot Source Optical Port

Value Shelf0(subrack)-13-12LQMS 3(RX1/TX1)


Shelf0(subrack)-13-12LQMS 201(ClientLP/ClientLP)

Active
NOTE
Step 8 Click Query. Ensure that the query result is consistent with the configuration. Step 9 Optional: Configure service timeslots of the logical port of the TN12LQMS board at station B. For details on how to configure service timeslots, see 12.5 Configuring Service Timeslots. ----End
Check whether service configurations are correct. If the end-to-end services on the client side are correctly configured, the client trails of GE levels can be searched out. For details, see Searching for Trails.
2.5 Configuring WDM Services for Tributary Boards and Line Boards
This section describes how to configure GE services by using the TQM and NQ2 boards.
Issue 02 (2011-10-31)
37

Service Requirement
See Figure 2-18. ONEs A, B, C, and D form a ring network. All the ONEs function as OADM stations. User1 and User2 communicate with each other. One bidirectional GE service is available between station A and station B. At station A, the TN12TQM board accesses one GE service and multiplexes the GE service into one channel of ODU1 electrical signals, that is, one ODU1 service. Then, the ODU1 service is sent to the TN52NQ2 board and is multiplexed with other services into one OTU2 service. At station B, the TN12TQM board accesses one GE service and multiplexes the GE service into one channel of ODU1 electrical signals, that is, one ODU1 service. Then, the ODU1 service is sent to the TN52NQ2 board and is multiplexed with other services into one OTU2 service. Figure 2-18 Configuration networking diagram of the GE service
User1
East East
12TQM 52NQ2
East West
NMS
West
East
B User2 East West 12TQM West 52NQ2

West
D C
West
:OADM
East

In this example, a 12TQM board and a 52NQ2 board must be configured at station A and station B.

This section describes how to configure the transparent transmission signal flow of a GE service. One bidirectional GE service is available between station A and station B. Figure 2-19 shows the service signal flow between station A and station B.
Figure 2-19 Unidirectional service at each station

TQM Client side 3(RX1/TX1)-1 4(RX2/TX2)-1 5(RX3/TX3)-1 6(RX4/TX4)-1 201(ClientLP/ClientLP)-1 201(ClientLP/ClientLP)-2 201(ClientLP/ClientLP)-3 201(ClientLP/ClientLP)-4 Fixed crossconnection 51(ODU1LP/ODU1LP)-1 51(ODU1LP/ODU1LP)-2 51(ODU1LP/ODU1LP)-3 51(ODU1LP/ODU1LP)-4 Servive processing module 1(IN/OUT)-1 NQ2 WDM side
NOTE
ClientLP and ODU1LP are logical ports. Cross-connections between client-side RX/TX ports and ClientLP ports need to be configured. ODU1 cross-connections between the ClientLP ports of the TQM board and the ODU1LP ports of the NQ2 board need to be configured. There are connections between the ODU1LP ports of the NQ2 board and WDM-side IN/OUT ports, and therefore cross-connections do not need to be configured.

Prerequisite
Fibers are connected correctly according to the network structure. (Namely, OCh trails can be searched out. For details, see Searching for WDM Trails.) Check parameters of the OTU board and ensure that no error is found. You must be an NM user with "NE operator" authority or higher.

Due to the limitations of cross-connections over the backplane, the boards configured with interboard cross-connections must be installed in cross-connection slots. For the limitations of crossconnection slots, see the limitations on cross-connections in 2.1.1 Electrical CrossConnections. The available cross-connection capacity of a board depends on the slot where the board is installed. For the OptiX OSN 6800, the available cross-connection capacity of the slots 1, 4, 11, or 14 is 40 Gbit/s; the available cross-connection capacity of any other slots is 20 Gbit/s. For the OptiX OSN 8800, the available cross-connection capacity of all any slots is 40 Gbit/s. Different boards have different cross-connection capacities. For details, see the functions and features of each board in the Hardware Description. If the capacity of the configured services is greater than the available cross-connection capacity, the service configuration fails.

Step 1 Set Service Mode of the client-side ports on the TN12TQM boards at stations A and B to Client Mode. For details, see 12.3 Configuring the Service Mode.

NOTE
After Service Mode is set to Client Mode, the TN12TQM board can access services other than OTN services.
Step 2 Set Service Mode of the client-side ports on the TN52NQ2 boards at stations A and B to ODU1. For details, see 12.3 Configuring the Service Mode.
NOTE
After Service Mode is set to ODU1, the TN52NQ2 board can access ODU1 services.
Step 3 Set Service Type of the client-side ports on the TN12TQM boards at stations A and B to GE. For details, see 12.2 Configuring the Service Type. Step 4 Configure the internal cross-connections for the wavelengths that are added or dropped from the TN12TQM board at station A. 1. Configure a GE service from the RX/TX port of the TN12TQM board to the ClientLP port. For details, see 12.4.1 Creating Cross-Connections. The following table lists the values of the parameters for station A. Field Level
Value GE
Service Type Direction Source Slot Source Optical Port

Bidirectional Shelf0(subrack)-13-12TQM 3(RX1/TX1)


Shelf0(subrack)-13-12TQM 201(ClientLP/ClientLP)

Issue 02 (2011-10-31)
40
Field Activate Immediately

Value Active
NOTE
Step 5 Click Query. Ensure that the query result is consistent with the configuration. Step 6 Configure ODU1 services between the TN52NQ2 board and the TN12TQM board at station A. 1. Configure an ODU1 service from the ClientLP port of the TN12TQM board to the ODU1LP port of the TN52NQ2 board. For details, see 12.4.1 Creating Cross-Connections. The following table lists the values of the parameters for station A. Field Level
Value ODU1

Bidirectional Shelf0(subrack)-13-12TQM 201(ClientLP/ClientLP)


Shelf0(subrack)-12-52NQ2 51(ODU1LP/ODU1LP)

Issue 02 (2011-10-31)
41
Field Activate Immediately

Value Active
NOTE
Step 7 Click Query. Ensure that the query result is consistent with the configuration. Step 8 Optional: Configure service timeslots of the logical port of the TN12TQM board at station A. For details on how to configure service timeslots, see 12.5 Configuring Service Timeslots. Step 9 Configure the internal cross-connections for the wavelengths that are added or dropped from the TN12TQM board at station B. 1. Configure a GE service from the RX/TX port of the TN12TQM board to the ClientLP port. For details, see 12.4.1 Creating Cross-Connections.
The following table lists the values of the parameters for station B. Field Level
Value GE

Bidirectional Shelf0(subrack)-13-12TQM 3(RX1/TX1)


Shelf0(subrack)-13-12TQM 201(ClientLP/ClientLP)
Issue 02 (2011-10-31)
42
Field Sink Optical Channel

Value 1
Active
NOTE
Step 10 Click Query. Ensure that the query result is consistent with the configuration. Step 11 Configure ODU1 cross-connections between the TN52NQ2 board and the TN12TQM board at station B. 1. Configure an ODU1 service from the ClientLP port of the TN12TQM board to the ODU1LP port of the TN52NQ2 board. For details, see 12.4.1 Creating Cross-Connections. The following table lists the values of the parameters for station B. Field Level
Value ODU1

Bidirectional Shelf0(subrack)-13-12TQM 201(ClientLP/ClientLP)


Shelf0(subrack)-12-52NQ2 51(ODU1LP/ODU1LP)
Issue 02 (2011-10-31)
43
Field Sink Optical Channel

Value 1
Active
NOTE
Step 12 Click Query. Ensure that the query result is consistent with the configuration. Step 13 Optional: Configure service timeslots of the logical port of the TN12TQM board at NE B. For details, see 12.5 Configuring Service Timeslots. ----End
Check whether service configurations are correct. If the end-to-end services on the client side are correctly configured, the client trails of GE levels can be searched out. For details, see Searching for WDM Trails.
2.6 Configuring WDM Services for Boards with the Layer 2 Switching Function
This section describes how to configure GE services by using the boards with Layer 2 processing functions (the TBE and L4G boards in this example).

Service Requirement
See Figure 2-20. The optical NEs (ONEs) A, B, C, and D form a ring network. All the ONEs function as OADM stations. User1 and User2 communicate with each other. One bidirectional GE service is available between station A and station B. At station A, the TBE board accesses one GE service and converts the GE service into one channel of GE electrical signals. Then, the GE electrical signals are sent to the L4G board and are multiplexed with other services into one OTU 5G service. At station B, the TBE board accesses one GE service and converts the GE service into one channel of GE electrical signals. Then, the GE electrical signals are sent to the L4G board and are multiplexed with other services into one OTU 5G service.
Figure 2-20 Configuration networking diagram of the GE service

User1 EAST EAST TBE L4G EAST WEST NMS
WEST WEST
TBE L4G
WEST B EAST User2
EAST D WEST
WEST
EAST
:OADM

In this example, a TBE board and a L4G board must be configured at station A and station B.

This section describes how to configure the transparent transmission signal flow of a GE service. One bidirectional GE service is available between station A and station B. Figure 2-21 shows the service signal flow between station A and station B. Figure 2-21 Unidirectional service at each station
TBE Client side PORT3 PORT4 VCTRUNK1 VCTRUNK2 101(AP1/AP1)-1 102(AP2/AP2)-1 L4G 201(LP/LP)-1 201(LP/LP)-2 201(LP/LP)-3 201(LP/LP)-4 Servive processing WDM-side optical module module 201(LP/LP)-1 1(IN/OUT)-1 WDM side
PORT11
VCTRUNK16 116(AP16/AP16)-1 L2 switching module
NOTE
LP and AP are logical ports. Cross-connections between client-side PORT ports and VCTRUNK ports need to be configured. AP ports and VCTRUNK ports of the TBE board are bound to each other automatically, and therefore no configuration is required. Cross-connections between AP ports of the TBE board and LP ports of the L4G board need to be configured.

Prerequisite
Fibers are connected correctly according to the network structure. (Namely, OCh trails can be searched out. For details, see Searching for Trails.) You are an NMS user with "Operator Group" authority or higher.

Different boards have different cross-connection capacities. Fore details, see the functions and features of each board in the Hardware Description. If the capacity of the configured services is greater than the available cross-connection capacity, the service configuration fails.

Step 1 Set Service Mode of the line-side ports on the L4G boards at stations A and B to OTN. For details, see 12.3 Configuring the Service Mode.
NOTE
The mode of line-side services of the L4G boards on an NE at the local end must be the same as that at the opposite end.
Step 2 Set Service Type of the client-side ports on the TBE boards at stations A and B to GE. For details, see 12.2 Configuring the Service Type. Step 3 Configure the internal cross-connections for the wavelengths that are added or dropped from the TBE board at station A. 1. Configure EPL services from the VCTRUNK to the PORT of the TBE board. For details, see 10.4.2 Creating EPL Services. The following table lists the values of the parameters for station A. Field Board Service Type Direction Source Port Source C-VLAN Sink Port Sink C-VLAN Value Shelf0(subrack)-13-TBE EPL Bidirectional PORT3 1 VCTRUNK1 1
NOTE
For details on how to select a service port, see 2.6.2 Service Signal Flow.
Issue 02 (2011-10-31)
46

NOTE
l The services can be unidirectional or bidirectional. l The Enabled/Disabled and TAG fields in Port Type can be set in the Create Ethernet Line Service dialog box or Ethernet Interface. l Values of certain fields in Port Type can be changed. If port attribute settings are complete, retain the default values.
Step 4 Click Query. Ensure that the query result is consistent with the configuration. Step 5 Configure GE services between the L4G board and the TBE board at station A. 1. Configure a GE service from the AP port of the TBE board to the LP port of the L4G board. For details, see 12.4.1 Creating Cross-Connections. The following table lists the values of the parameters for station A. Field Level
Value GE

Bidirectional Shelf0(subrack)-13-TBE 101(AP1/AP1)


Shelf0(subrack)-12-L4G 201(LP/LP)

Active
Issue 02 (2011-10-31)
47

NOTE
Step 6 Click Query. Ensure that the query result is consistent with the configuration. Step 7 Configure the internal cross-connections for the wavelengths that are added or dropped from the TBE board at station B. 1. Configure EPL services from the VCTRUNK port to the PORT port of the TBE board. For details, see 10.4.2 Creating EPL Services. The following table lists the values of the parameters for station B. Field Board Service Type Direction Source Port Source C-VLAN Sink Port Sink C-VLAN Value Shelf0(subrack)-13-TBE EPL Bidirectional PORT3 1 VCTRUNK1 1
NOTE
NOTE
l The services can be unidirectional or bidirectional. l The Enabled/Disabled and TAG fields in Port Type can be set in the Create Ethernet Line Service dialog box or Ethernet Interface. l Values of certain fields in Port Type can be changed. If port attribute settings are complete, retain the default values.
Step 8 Click Query. Ensure that the query result is consistent with the configuration. Step 9 Configure GE services between the L4G board and the TBE board at station B. 1. Configure a GE service from the AP port of the TBE board to the LP port of the L4G board. For details, see 12.4.1 Creating Cross-Connections. The following table lists the values of the parameters for station B. Field Level
Value GE
Service Type
Issue 02 (2011-10-31)
48
Field Direction Source Slot Source Optical Port

Value Bidirectional Shelf0(subrack)-13-TBE 101(AP1/AP1)


Shelf0(subrack)-12-L4G 201(LP/LP)

Active
NOTE
Step 10 Click Query. Ensure that the query result is consistent with the configuration. ----End
Check whether service configurations are correct. If the end-to-end services on the client side are correctly configured, the client trails of GE levels can be searched out. For details, see Searching for Trails.
2.7 Configuring 10GE LAN Services by Using the TDX and NS2 Boards
This section describes how to configure 10GE LAN services by using the TDX and NS2 boards.
Issue 02 (2011-10-31)
49

This section describes how to configure a 10GE LAN service on a ring network.
Service Requirement
See Figure 2-22. The optical NEs (ONEs) A, B, C, and D form a ring network. All the ONEs function as OADM stations. User1 and User2 communicate with each other. One bidirectional 10GE LAN service is available between station A and station C. At station A, the TN52TDX board accesses one 10GE LAN service and encapsulates the 10GE LAN service into one channel of ODU2 electrical signals, that is, one ODU2 service. The TN52NS2 board accesses the ODU2 service and then outputs one OTU2 service. Station B transparently transmits the OTU2 service. At station C, the TN52NS2 board accesses the OTU2 service and converts the OTU2 service into ODU2 electrical signals, which are groomed to the TN52TDX board and then output as one 10GE LAN service. Figure 2-22 Configuration networking diagram of the GE service
User1
East East
52TDX 52NS2
East West
NMS
East West
52NS2 52NS2
West
East
B
East
D C
West
West West West
East
:OADM :REG
52TDX 52NS2 User2

In this example, the TN52TDX board and TN52NS2 boards must be configured at stations A and C. Two TN52NS2 boards must be configured at station B.

This topic describes how to configure the transmission signal flow of a 10GE LAN service. One bidirectional GE service is available among stations A, B, and C.
Figure 2-23 shows the service signal flow among stations A, B, and C. Figure 2-23 Service at each station
TDX backplane side backplane side NS2 WDM side
3(RX1/TX1)-1 4(RX2/TX2)-1
201(ClientLP1/ ClientLP1)-1 202(ClientLP2/ ClientLP2)-1
71(ODU2LP/ ODU2LP)-1
1(IN/OUT)-1
Servive processing module NS2 backplane side backplane NS2 side 71(ODU2LP/ ODU2LP)-1
WDM side
WDM side
1(IN/OUT)-1
1(IN/OUT)-1 Servive processing module NS2 backplane side Servive processing module backplane TDX side 201(ClientLP1/ ClientLP1)-1 202(ClientLP2/ ClientLP2)-1 Crossconnection
WDM side
Client side 3(RX1/TX1)-1 4(RX2/TX2)-1
1(IN/OUT)-1 Servive processing module

NOTE
ClientLP and ODU2LP are logical ports. There are cross-connections between client-side RX/TX ports and ClientLP ports and therefore cross-connections do not need to be configured. ODU2 cross-connections between the ClientLP ports of the TDX board and the ODU2LP ports of the NS2 board need to be configured. There are connections between the ODU2LP ports of the NS2 board and WDM-side IN/OUT ports and therefore cross-connections do not need to be configured.
Issue 02 (2011-10-31)
51
CAUTION
l When 10GE LAN signals are received on the client side of the TDX board and Port Mapping of the TDX board is set to Transparent Mapping (11.1 G), Line Rate of the 71 (ODU2LP/ODU2LP)-1 port on the backplane side of the TN52NS2 board that services pass through must be set to Speedup Mode. l When 10GE LAN signals are received on the client side of the TDX board and Port Mapping of the TDX board is set to MAC Transparent Mapping (10.7 G), Line Rate of the 71(ODU2LP/ODU2LP)-1 port on the backplane side of the TN52NS2 board that services pass through must be set to Standard Mode. l The Service Mode must be set to ODU2 or Automatic.

This section describes how to configure a bidirectional 10GE LAN service at stations A, B, and C.
Prerequisite
You are an NMS user with "Operator Group" authority or higher.

l The port mapping mode of 10GE LAN services can be configured as Bit Transparent Mapping (11.1 G) or MAC Transparent Mapping (10.7 G). Users can select a proper mapping mode according to the service transmission requirements. Bit Transparent Mapping (11.1 G) meets customer requirement for transparent bit transport of 10GE LAN signals. In the Bit Transparent Mapping (11.1 G) 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, however, the bit rate is higher than the standard bit rate of OTU2 signals. MAC Transparent Mapping (10.7 G) is specific to transparent transmission of 10GE MAC frames as required by customers. In this port mapping mode, a 10GE LAN signal is encapsulated in the GFP-F format and then mapped into a standard OTU frame. This mode supports transparent transmission of only client 10GE MAC frames. In this mode, the signals are in standard OTU2 frames. In addition, the FEC/AFEC code pattern is applicable to 10GE LAN services in this mode. Originally, the FEC/AFEC code pattern is intended for 10G SDH services. The port mapping modes of the upstream and downstream board must be the same.

Step 1 Configure attributes of client-side ports on the TN52TDX board of station A.
1. 2. 3. 4.
In the NE Explorer, select the TN52TDX board that you want to configure, and then choose Configuration > WDM Interface from the Function Tree. Click By Board/Port (Channel), and select Channel from the drop-down list. Select the Basic Attributes tab. Select the ClientLP port, the service type that needs to be set, and then double-click the corresponding parameter domain to set the following parameters. l Service Type: 10GE LAN l Port Mapping: Bit Transparent Mapping (11.1G)
5. 6. 7.
Select the board, click State and choose IS to set Primary, Secondary State. Click Apply. In the dialog box that is displayed, click OK. Click Query. Ensure that the query result is consistent with the configuration.
Step 2 Configure attributes of client-side ports on the TN52NS2 board of station A. 1. 2. 3. 4. In the NE Explorer, select the TN52NS2 board and choose Configuration > WDM Interface from the Function Tree. Click By Board/Port (Channel), and then choose Channel from the drop-down list. Select the Basic Attributes tab. Select the ODU2LP port. Double-click the Service Type parameter and then select ODU2.
NOTE
Set Service Type to ODU2 or Automatic and then the NS2 board can access ODU2 services.
5.
On the Advanced Attributes tab, select the ODU2LP port and then double-click the Line Rate parameter and select Speedup Mode.
NOTE
l When Port Mapping of the ClientLP port on the TDX board is set to Bit Transparent Mapping (11.1 G), Line Rate of the ODU2LP port on the NS2 board must be set to Speedup Mode. l When Port Mapping is set to MAC Transparent Mapping (10.7 G) , Line Rate must be set to Standard Mode.
CAUTION
Port Mapping and Line Rate of the boards that services pass must be consistent; otherwise, service interruption occurs. 6. Select the board, click State and choose IS to set Primary, Secondary State.
Step 3 Repeat step 2 to configure attributes of ports on the TN52NS2 board at station B. Step 4 Repeat steps 1 and 2 to configure attributes of ports on the TN52TDX and TN52NS2 boards of station C. Step 5 Configure ODU2 services between the TN52NS2 board and the TN52TDX board at station A. 1. Configure ODU2 services from the ClientLP port of the TN52TDX board to the ODU2LP port of the TN52NS2 board. For details, see 12.4.1 Creating Cross-Connections. The following table lists the values of the parameters.
Field Level Service Type Direction Source Slot Source Optical Port Source Optical Channel Sink Slot Sink Optical Port Sink Optical Channel Activate Immediately
Value ODU2 Bidirectional Shelf0(subrack)-13-52TDX 201(ClientLP/ClientLP) 1 Shelf0(subrack)-12-52NS2 71(ODU2LP/ODU2LP) 1 Active
NOTE
Step 6 Click Query. Ensure that the query result is consistent with the configuration. Step 7 Configure ODU2 services between the TN52NS2 boards at station B. The following table lists the values of the parameters. Field Level Service Type Direction Source Slot Source Optical Port Source Optical Channel Sink Slot Sink Optical Port Sink Optical Channel Activate Immediately Value ODU2 Bidirectional Shelf0(subrack)-07-52NS2 71(ODU2LP/ODU2LP) 1 Shelf0(subrack)-12-52NS2 71(ODU2LP/ODU2LP) 1 Active
Issue 02 (2011-10-31)
54

NOTE
Step 8 Click Query. Ensure that the query result is consistent with the configuration. Step 9 Configure ODU2 services between the TN52NS2 board and the TN52TDX board at station C. 1. Configure ODU2 services from the ClientLP port of the TN52TDX board to the ODU2LP port of the TN52NS2 board. For details, see 12.4.1 Creating Cross-Connections. The following table lists the values of the parameters. Field Level Service Type Direction Source Slot Source Optical Port Source Optical Channel Sink Slot Sink Optical Port Sink Optical Channel Activate Immediately Value ODU2 Bidirectional Shelf0(subrack)-13-52TQM 201(ClientLP/ClientLP) 1 Shelf0(subrack)-12-52NS2 71(ODU2LP/ODU2LP) 1 Active
NOTE
Step 10 Click Query. Ensure that the query result is consistent with the configuration. ----End
2.8 Parameters
Describes the parameters involved in the WDM services configuration.
2.8.1 WDM Cross-Connection Configuration

In this user interface, you can configure the cross-connections of various WDM services.
Issue 02 (2011-10-31)
55
Table 2-12 WDM Cross-Connection Configuration Field Level Value Values of parameters vary with different boards and products. Description The Level parameter is used to differentiate the service types configured when electrical cross-connections are configured. Click A.20 Level (WDM Cross-Connection Configuration) for more information. When Level of a new service is set to Any, you can select a specific service type. The Direction parameter indicates the service direction mode when the service cross-connection is configured. It can be set to either Unidirectional or Bidirectional. Click A.21 Direction (WDM Cross-Connection Configuration) for more information.
Service Type
For example, FE, STM-1, FICON Unidirectional, Bidirectional. Default: Unidirectional
Direction
Source Channel
Slot ID-Board Name-Optical The Source Channel Interface ID-Optical Channel parameter is used to query the ID transmit channel of a certain electrical cross-connect Default: Null service (unidirectional service flow). Click A.17 Source Channel (WDM Cross-Connection) for more information. Slot ID - Board Name Optical Interface ID - Optical Channel ID Default: Null The Sink Channel parameter is used to query the receive channel of a certain electrical cross-connect service (unidirectional service flow). Click A.18 Sink Channel (WDM Cross-Connection Configuration) for more information.
Sink Channel
Issue 02 (2011-10-31)
56
Field Occupied ODUTUk Slot Count
Value l When ODUflex Service Type is set to Custom: 1-8 Default: 8 l When ODUflex Service Type is set to FC400: this patameter is 4 l When ODUflex Service Type is set to FC800: this patameter is 7 l When ODUflex Service Type is set to 3GSDI or InfiniBand 2.5G: this patameter is 3
Description Specifies the number of ODUflex timeslots for received services. This parameter is set based on the type and rate of the service received by the port. The parameter value ranges from 1 to 8.
NOTE The OptiX OSN 3800/6800 doesn't support this parameter.
Service Rate(bit/s)
1249245570-9993964557
The parameter value varies according to the value of Occupied ODUTUk Slot Count in the range of 1249245570 to 9993964557. It cannot be set manually.
NOTE The OptiX OSN 3800/6800 doesn't support this parameter.
Activation Status
Active, Inactive Default: Active
The Activation Status parameter is used to display whether the service crossconnection configuration is activated. Click A.19 Activation Status (WDM CrossConnection Configuration) for more information. Displays the mode of creating WDM crossconnections.
Service Origin
Create Manually, Intelligently Generate
2.8.2 WDM Timeslot Configuration

In this user interface, you can configure WDM services. You can specify ports and timeslots for transmitting and receiving services, and set the client-side service protocol.
Issue 02 (2011-10-31)
57
Table 2-13 Parameters of WDM services Parameters Port Value NE-Slot-Board-Optical Interface-Channel Description The Port parameter indicates the location of the service timeslots, including the channel, optical interface, board, slot, and NE where the timeslots reside. The Service Type parameter is used to set the type of the services at an optical port when the cross-connections of any services are configured, to match the type of the actual services. The Transmit Timeslot parameter is used to select the service timeslots in the transmit direction. The Send Timeslot parameter is used to select the service timeslots in the transmit direction. Click A.22 Service Timeslot (WDM Services) for more information. Receive Timeslot 1 to 32 The Receive Timeslot parameter is used to select the service timeslots on the receive direction. Click A.22 Service Timeslot (WDM Services) for more information.
Service Type
For example: FE, STM-1, FICON
Transmit Timeslot
1 to 32
Issue 02 (2011-10-31)
58
3 Configuring the TN11TOM Board (Manually by Station)
3
NOTE
Configuring the TN11TOM Board (Manually by Station)
About This Chapter

A TN11TOM board can work in cascading or non-cascading mode and be configured with different port working modes. Based on different working modes, the TN11TOM board is applicable to five scenarios. You need to manually configure the TN11TOM board by station on the NMS for the five application scenarios.
When a TN11TOM board is used to configure ODU1 cross-connections, the TN11TOM board working with the TN12NS2 or the TN52NS2 board in the OptiX OSN 3800 must be installed in the following slots: l IU2 and IU4 l IU2 and IU5 l IU3 and IU4 l IU3 and IU5
3.1 Application Scenario 1: Conversion Between Eight Any Services and Four ODU1 Electrical Signals This configuration example shows how the TN11TOM board is configured to implement conversion between eight channels of optical signals of any rate from 100 Mbit/s to 2.5 Gbit/s and four channels of ODU1 electrical signals. 3.2 Application Scenario 2: Conversion Between Four OTU1 Optical Signals and Four ODU1 Electrical Signals This configuration example shows how the TN11TOM board is configured to implement conversion between four channels of OTU1 optical signals and four channels of ODU1 electrical signals. 3.3 Application Scenario 3: Conversion Between Four Any Services and Four OTU1 Optical Signals This configuration example shows how the TN11TOM board is configured to implement conversion between four channels of optical signals of any rate from 100 Mbit/s to 2.5 Gbit/s and four channels of OTU1 optical signals. 3.4 Application Scenario 4: Conversion Between Seven Any Services and One OTU1 Optical Signal
This configuration example shows how the TN11TOM board is configured to implement conversion between seven channels of optical signals of any rate from 100 Mbit/s to 2.5 Gbit/s and one channel of OTU1 optical signals. 3.5 Application Scenario 5: Conversion Between Six Any Services and One OTU1 Optical Signal and Dual Feeding and Selective Receiving on the WDM Side This configuration example shows how the TOM board is configured to implement conversion between six channels of optical signals of any rate from 100 Mbit/s to 2.5 Gbit/s and one channel of OTU1 optical signals, and how to implement the function of dual feeding and selective receiving on the WDM side.
Issue 02 (2011-10-31)
60
3.1 Application Scenario 1: Conversion Between Eight Any Services and Four ODU1 Electrical Signals
This configuration example shows how the TN11TOM board is configured to implement conversion between eight channels of optical signals of any rate from 100 Mbit/s to 2.5 Gbit/s and four channels of ODU1 electrical signals.

This section describes how to configure services on a ring network.
Service Requirement
See Figure 3-1. The optical NEs (ONEs) A, B, C and D form a ring network. All the ONEs function as OADM stations. User1 and User2 communicate with each other. One bidirectional OTU2 service is available between station A and station B. At station A, the TN11TOM board accesses eight Any services (100 Mbit/s to 2.5 Gbit/s) and then converts them into four ODU1 services. The ODU1 services are then sent to the 12NS2 board at station A, where they are converted into one OTU2 service. Figure 3-1 Networking diagram for the TOM board (tributary board in non-cascading mode) in application scenario 1
User1 SLOT 12 SLOT 15 EAST NMS WEST B EAST SLOT 12 SLOT 15 12NS2 11TOM C EAST D WEST WEST
12NS2 11TOM
User2
WEST
EAST
:OADM
Issue 02 (2011-10-31)
61

In this example, a TN11TOM board and a 12NS2 board must be configured at stations A and B each.

This section provides the signal flow diagram of station A. One OTU2 service is available between station A and station B. Figure 3-2 shows the service signal flow at station A. Figure 3-2 Bidirectional service at station A
11TOM 3(RX1/TX1) 4(RX2/TX2) 5(RX3/TX3) 6(RX4/TX4) 7(RX5/TX5) 8(RX6/TX6) 9(RX7/TX7) 10(RX8/TX8) 204(ClientLP4/ClientLP4) 51(ODU1LP/ODU1LP)-4 203(ClientLP3/ClientLP3) 51(ODU1LP/ODU1LP)-3 202(ClientLP2/ClientLP2) 51(ODU1LP/ODU1LP)-2 1(IN/OUT) 201(ClientLP1/ClientLP1) 12NS2 51(ODU1LP/ODU1LP)-1
: 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

This section considers station A as an example to describe the configuration process of the TN11TOM board.
Prerequisite

Precautions
NOTE
The value of Board Mode is Non-cascading mode by default. In this case, the 201 (ClientLP1/ ClientLP1) and 203 (ClientLP3/ ClientLP3) ports can access a maximum of four services, and the 202 (ClientLP2/ ClientLP2) and 204 (ClientLP4/ ClientLP4) ports can access a maximum of two services.
Issue 02 (2011-10-31)
62

NOTE
A ClientLP port can access only one service that has a rate higher than 1.25 Gbit/s, and this service can be configured in only the first channel of the ClientLP port. The total rate of services accessed by a ClientLP port must be equal to or lower than 2.5 Gbit/s. The client-side eight pairs of optical ports can access services at a maximum rate of 10 Gbit/s. The client-side ports can be grouped as required.

Step 1 Set Board Mode to Non-cascading. 1. 2. 3. In the NE Explorer, select the TN11TOM board and choose Configuration > WDM Interface from the Function Tree. Click By Board/Port (Channel) and choose Board from the drop-down list. Click the Board Mode and select Non-cascading from the drop-down list.
NOTE
If a cross-connection is configured on the board, delete the cross-connection on the board before setting Board Mode.
NOTE
If the Board Mode of the board is changed, the default port configuration data and service configuration data will be restored, and as a result the services will be interrupted.
4. 5.
Select the board, click State and choose IS to set Primary, Secondary State. Click Apply.
Step 2 Configure Service Type at the WDM-side port of the TN11TOM board according to the service planning. For details, see 12.2 Configuring the Service Type. Step 3 Configure the intra-board electrical cross-connections of Any services for the TN11TOM board. 1. Configure the cross-connections from the RX/TX ports to the ClientLP ports on the TN11TOM board for the Any services that are input to the board. For details, see 12.4.1 Creating Cross-Connections.
NOTE
The service type must be the same as Service Type in the WDM Interface window of the TN11TOM board.
Issue 02 (2011-10-31)
63
2. 3. 4.
Click Query. Confirm that the query results are the same as the values that are set. Repeat Step 3.1 to configure the remaining seven Any services. Optional: Configure service timeslots of the logical port. For details on how to configure service timeslots, see 12.5 Configuring Service Timeslots.
Step 4 Configure electrical cross-connections for the ODU1 service between the TN11TOM and 12NS2 boards. 1. Configure electrical cross-connections for the ODU1 service between the TN11TOM and 12NS2 boards. For details, see 12.4.1 Creating Cross-Connections.
Issue 02 (2011-10-31)
64
2. 3. 4.
Click Query. Confirm that the query results are the same as the values that are set. Repeat Step 4.1 to configure the remaining cross-connect services between the TN11TOM and 12NS2 boards. Optional: Configure service timeslots of the logical port. For details on how to configure service timeslots, see 12.5 Configuring Service Timeslots.
----End
3.2 Application Scenario 2: Conversion Between Four OTU1 Optical Signals and Four ODU1 Electrical Signals
This configuration example shows how the TN11TOM board is configured to implement conversion between four channels of OTU1 optical signals and four channels of ODU1 electrical signals.

Issue 02 (2011-10-31)
65
Service Requirement
See Figure 3-3. The optical NEs (ONEs) A, B, C, and D form a ring network. All the ONEs function as OADM stations. User1, User2, and User3 communicate with each other through one OTU2 service each. At station A, the TN11TOM board accesses four OTU1 services and then converts them into four ODU1 services. The four ODU1 services are then sent to two 12NS2 boards at station A according to the actual service requirement. Each 12NS2 board converges the received ODU1 services and other accessed services into one OTU2 service. Figure 3-3 Networking diagram for the TN11TOM board (tributary board in non-cascading mode) in application scenario 2
User1 SLOT 12 SLOT 13 SLOT 15 EAST NMS WEST B EAST SLOT 13 SLOT 15 12NS2 11TOM C WEST 12NS2 12NS2 11TOM
User2
A D
EAST
User3
WEST SLOT 13 SLOT 15 12NS2 11TOM
WEST
EAST
:OADM

In this example, a TN11TOM board and two 12NS2 boards must be configured at station A, and a TN11TOM board and a 12NS2 board must be configured at stations B and C each.

This section provides the signal flow diagram of station A. One OTU2 service is available between station A and station B. Another OTU2 service is available between station A and station C. Figure 3-4 shows the service signal flow at station A.
Figure 3-4 Bidirectional service at station A

Prerequisite

Precautions
NOTE
The client-side optical ports can be selected as required. A ClientLP port can access only one service that has a rate higher than 1.25 Gbit/s, and this service can be configured on only the first channel of the ClientLP port.

Step 1 Set Service Mode of the TN11TOM board to OTN Mode. For details, see 12.3 Configuring the Service Mode.

NOTE
When the TN11TOM board accesses OTU1 services on the client side, you first need to set the Service Mode of the TN11TOM board to OTN Mode.
Step 2 Configure Service Type at the WDM side port of the TN11TOM board as OTU1. For details, see 12.2 Configuring the Service Type. Step 3 Configure the intra-board electrical cross-connections of OTU1 services for the TN11TOM board. 1. Configure an OTU1 cross-connection between the 3(RX1/TX1) port and the 201 (ClientLP1/ClientLP1) port on the TN11TOM board. For details, see 12.4.1 Creating Cross-Connections.
NOTE
2. 3. 4.
Click Query. Confirm that the query results are the same as the values that are set. Repeat Step 3.1 to configure the remaining three OTU1 services. Optional: Configure service timeslots of the logical port. For details on how to configure service timeslots, see 12.5 Configuring Service Timeslots.
Step 4 Configure electrical cross-connections for the ODU1 service between the TN11TOM and 12NS2 boards. 1. Configure electrical cross-connections for the ODU1 service between the TN11TOM and 12NS2 boards. For details, see 12.4.1 Creating Cross-Connections.
Issue 02 (2011-10-31)
2. 3. 4.
Click Query. Confirm that the query results are the same as the values that are set. Repeat Step 4.1 to configure the remaining cross-connect services between the TN11TOM and 12NS2 boards. Optional: Configure service timeslots of the logical port. For details on how to configure service timeslots, see 12.5 Configuring Service Timeslots.
----End
3.3 Application Scenario 3: Conversion Between Four Any Services and Four OTU1 Optical Signals
This configuration example shows how the TN11TOM board is configured to implement conversion between four channels of optical signals of any rate from 100 Mbit/s to 2.5 Gbit/s and four channels of OTU1 optical signals.

Service Requirement
See Figure 3-5. The optical NEs (ONEs) A, B, C, and D form a ring network. All the ONEs function as OADM stations.
User1 and User2 communicate with each other. One bidirectional OTU1 service is available between station A and station B. At station A, the TN11TOM board accesses four GE services and then converts them into four OTU1 services. Figure 3-5 Networking diagram for the TN11TOM board (tributary-line board in non-cascading mode) in application scenario 3
User1
SLOT 14 EAST NMS WEST
11TOM
User2
WEST B EAST
A D C
EAST
WEST
SLOT 14
11TOM WEST EAST :OADM

In this example, a TN11TOM board must be configured at station A and station B each.

This section provides the signal flow diagram of station A. Four OTU1 services are available between station A and station B. Figure 3-6 shows the service signal flow at station A.
Issue 02 (2011-10-31)
70

11TOM 3(RX1/TX1) 4(RX2/TX2) 201(ClientLP1/ClientLP1) 202(ClientLP2/ClientLP2) 51(ODU1LP1/ODU1LP1) 52(ODU1LP2/ODU1LP2) 7(RX5/TX5) 8(RX6/TX6)
5(RX3/TX3) 6(RX4/TX4)
203(ClientLP3/ClientLP3) 204(ClientLP4/ClientLP4)
53(ODU1LP3/ODU1LP3) 54(ODU1LP4/ODU1LP4)
9(RX7/TX7) 10(RX8/TX8)

Prerequisite

Precautions
NOTE
The client-side optical ports and WDM-side optical ports can be selected as required. A ClientLP port can access only one service that has a rate higher than 1.25 Gbit/s, and this service can be configured on only the first channel of the ClientLP port.
NOTE
When the service type on both the client side and the WDM side of the TOM board is OTU1, the TOM board also can regenerate the OTU1 service. l l In cascading mode, the TOM implements the electrical regeneration of one channel of OTU1 signal. Only RX7/TX7 and RX8/TX8 can be used as the WDM-side optical ports. In non-cascading mode, the TOM implements the electrical regeneration of four channels of OTU1 signals. Any four of RX1/TX1-RX8/TX8 can be configured as WDM-side optical ports.

Step 1 Set the type of ports 7 (RX5/TX5), 8 (RX6/TX6), 9 (RX7/TX7), and 10 (RX8/TX8) to Line Side Color Optical Port. For details, see 11.1 Modifying Port.

NOTE
When the TOM board is used as a tributary-line board, a corresponding WDM-side optical module must be inserted in the WDM-side optical port, and the Type of this optical port must be changed to Line Side Color Optical Port.
Step 2 Configure Service Type at the WDM-side port of the TN11TOM board according to the service planning. For details, see 12.2 Configuring the Service Type. Step 3 Configure the intra-board electrical cross-connections of Any services for the TN11TOM board. 1. Configure the Any cross-connection between the 3(RX1/TX1) port and the 201(ClientLP1/ ClientLP1) port on TN11TOM board. For details, see 12.4.1 Creating CrossConnections.
NOTE
2. 3. 4.
Click Query. Confirm that the query results are the same as the values that are set. Repeat Step 3.1 to configure the remaining three Any services. Optional: Configure service timeslots of the logical port. For details on how to configure service timeslots, see 12.5 Configuring Service Timeslots.
Step 4 Configure the intra-board electrical cross-connections for the OTU1 services on the TN11TOM board. 1. Configure electrical cross-connections for the OTU1 service on the TN11TOM board. For details, see 12.4.1 Creating Cross-Connections.
Issue 02 (2011-10-31)
2. 3. 4.
Click Query. Confirm that the query results are the same as the values that are set. Repeat Step 4.1 to configure the remaining three OTU1 services. Optional: Configure service timeslots of the logical port. For details on how to configure service timeslots, see 12.5 Configuring Service Timeslots.
----End
3.4 Application Scenario 4: Conversion Between Seven Any Services and One OTU1 Optical Signal
This configuration example shows how the TN11TOM board is configured to implement conversion between seven channels of optical signals of any rate from 100 Mbit/s to 2.5 Gbit/s and one channel of OTU1 optical signals.

Service Requirement
See Figure 3-7. The optical NEs (ONEs) A, B, C and D form a ring network. All the ONEs function as OADM stations.
Issue 02 (2011-10-31)
73
User1 and User2 communicate with each other. One bidirectional OTU1 service is available between station A and station B. At station A, the TN11TOM board accesses seven Any services (100 Mbit/s to 2.5 Gbit/s) and then converts them into one OTU1 service. Figure 3-7 Networking diagram for the TN11TOM board (tributary-line board in cascading mode) in application scenario 4
User 1
11TOM
User 2
WEST B EAST
A D C
EAST
WEST
SLOT 15


This section provides the signal flow diagram of station A. One OTU1 service is available between station A and station B. Figure 3-8 shows the service signal flow at station A.
Issue 02 (2011-10-31)
74

11TOM 3(RX1/TX1) 4(RX2/TX2) 5(RX3/TX3) 6(RX4/TX4) 7(RX5/TX5) 8(RX6/TX6) 9(RX7/TX7) 201(ClientLP1/ClientLP1)-1 201(ClientLP1/ClientLP1)-2 201(ClientLP1/ClientLP1)-3 201(ClientLP1/ClientLP1)-4 201(ClientLP1/ClientLP1)-5 201(ClientLP1/ClientLP1)-6 201(ClientLP1/ClientLP1)-7 51(ODU1LP1/ODU1LP1) 10(RX8/TX8)
: Client-side services : 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

Prerequisite

Precautions
NOTE
For the client services at a rate of greater than 1.25 Gbit/s (OC-48, STM-16, OTU1, FC200, FICON Express, HD-SDI), the client-side ports can access up to only one channel. And this service can be configured in the first optical channel at the ClientLP port. The client-side seven pairs of optical ports can access services at a maximum rate of 2.5 Gbit/s.
NOTE
In cascading mode, only RX7/TX7 or RX8/TX8 can be used as the WDM-side optical ports.
Issue 02 (2011-10-31)
75

NOTE
When the service type on both the client side and the WDM side of the TOM board is OTU1, the TOM board also can regenerate the OTU1 service. l l In cascading mode, the TOM implements the electrical regeneration of one channel of OTU1 signal. Only RX7/TX7 and RX8/TX8 can be used as the WDM-side optical ports. In non-cascading mode, the TOM implements the electrical regeneration of four channels of OTU1 signals. Any four of RX1/TX1-RX8/TX8 can be configured as WDM-side optical ports.

Step 1 Set Board Mode to Cascading mode. 1. 2. 3. In the NE Explorer, select the TN11TOM board and choose Configuration > WDM Interface from the Function Tree. Click By Board/Port (Channel) and choose Board from the drop-down list. Click the Board Mode and select Cascading mode from the drop-down list.
NOTE
NOTE
4. 5.
Step 2 Set the type of ports 10 (RX8/TX8) to Line Side Color Optical Port. For details, see 11.1 Modifying Port.
NOTE
Step 3 Configure Service Type at the WDM-side port of the TN11TOM board according to the service planning. For details, see 12.2 Configuring the Service Type. Step 4 Configure the intra-board electrical cross-connections of Any services for the TN11TOM board 1. Configure the intra-board electrical cross-connections as the figure below.
Issue 02 (2011-10-31)
76
NOTE
The service type must be the same as Service Type in the WDM Interface window of the TOM board.
2. 3. 4.
Click Query. Confirm that the query results are the same as the values that are set. Repeat Step 4.1 to configure the remaining six Any services. Optional: Configure service timeslots of the logical port. For details on how to configure service timeslots, see 12.5 Configuring Service Timeslots.
Step 5 Configure the intra-board electrical cross-connections of OTU1 services for the TN11TOM board 1. Configure electrical cross-connections for the OTU1 service on the TN11TOM board. For details, see 12.4.1 Creating Cross-Connections.
Issue 02 (2011-10-31)
77
2. 3.
Click Query. Confirm that the query results are the same as the values that are set. Optional: Configure service timeslots of the logical port. For details on how to configure service timeslots, see 12.5 Configuring Service Timeslots.
----End
3.5 Application Scenario 5: Conversion Between Six Any Services and One OTU1 Optical Signal and Dual Feeding and Selective Receiving on the WDM Side
This configuration example shows how the TOM board is configured to implement conversion between six channels of optical signals of any rate from 100 Mbit/s to 2.5 Gbit/s and one channel of OTU1 optical signals, and how to implement the function of dual feeding and selective receiving on the WDM side.

Service Requirement
User1 and User2 communicate with each other. One bidirectional OTU1 service is available between station A and station B. At station A, the TN11TOM board accesses six Any services (100 Mbit/s to 2.5 Gbit/s) and then converts them into one OTU1 service. On the WDM side, the TN11TOM board performs dual feeding and selective receiving. Figure 3-9 Networking diagram for the TN11TOM board (tributary-line board in cascading mode) in application scenario 5
User1
11TOM
User2
WEST B EAST
A D C
EAST
WEST
SLOT 14

In this example, a TN11TOM board must be configured at station A and station B.

This section provides the signal flow diagram of station A. One OTU1 service is available between station A and station B. Figure 3-10 shows the service signal flow at station A.
Issue 02 (2011-10-31)
79

11TOM 3(RX1/TX1) 4(RX2/TX2) 5(RX3/TX3) 6(RX4/TX4) 7(RX5/TX5) 201(ClientLP1/ClientLP1)-1 201(ClientLP1/ClientLP1)-2 201(ClientLP1/ClientLP1)-3 51(ODU1LP1/ODU1LP1) 201(ClientLP1/ClientLP1)-4 201(ClientLP1/ClientLP1)-5 10(RX8/TX8) 9(RX7/TX7)
8(RX6/TX6) 201(ClientLP1/ClientLP1)-6 : Client-side services : 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

Prerequisite

Precautions
NOTE
For the client services at a rate greater than 1.25 Gbit/s (OC-48, STM-16, OTU1, FC200, FICON Express, HD-SDI), the client-side ports can access up to only one channel. And this service can be configured in the first optical channel at the ClientLP port. The client-side six pairs of optical ports can access services at a maximum rate of 2.5 Gbit/s.
NOTE
In cascading mode, only RX7/TX7 and RX8/TX8 can be used as the WDM-side optical ports.

Step 1 Set Board Mode to Cascading mode. 1. 2.
Issue 02 (2011-10-31)
In the NE Explorer, select the TN11TOM board and choose Configuration > WDM Interface from the Function Tree. Click By Board/Port (Channel) and choose Board from the drop-down list.
3.
Click the Board Mode and select Cascading mode from the drop-down list.
NOTE
NOTE
4. 5.
Step 2 Set the type of ports 9 (RX7/TX7) and 10 (RX8/TX8) to Line Side Color Optical Port. For details, see 11.1 Modifying Port.
NOTE
Step 3 Configure Service Type at the WDM-side port of the TN11TOM board according to the service planning. For details, see 12.2 Configuring the Service Type. Step 4 Configure the intra-board electrical cross-connections of Any services for the TN11TOM board. 1. Configure the Any cross-connection between the 3(RX1/TX1) port and the 201(ClientLP1/ ClientLP1) port on TN11TOM board. For details, see 12.4.1 Creating CrossConnections.
NOTE
The service type must be the same as Service Type in the WDM Interface window of the TOM board.
Issue 02 (2011-10-31)
81
2. 3. 4.
Click Query. Confirm that the query results are the same as the values that are set. Repeat Step 4.1 to configure the remaining five Any services. Optional: Configure service timeslots of the logical port. For details on how to configure service timeslots, see 12.5 Configuring Service Timeslots.
Step 5 Configure two separate cross-connections from the internal logical port to ports 9 (RX7/TX7) and 10 (RX8/TX8) for the TN11TOM board to achieve dual feeding. 1. Configure the OTU1 cross-connection between the ODU1LP port and the RX/TX port on TN11TOM board. For details, see 12.4.1 Creating Cross-Connections.
NOTE
The working channel port and the protection channel port are the two ports for dual feeding. The service on the working channel must be set as bidirectional, and the service on the protection channel must be set as unidirectional. In this example, port 9 (RX7/TX7) is the working channel port, and port 10 (RX8/TX8) is the protection channel port.
Issue 02 (2011-10-31)
82
Issue 02 (2011-10-31)
83
2. 3.
Click Query. Confirm that the query results are the same as the values that are set. Optional: Configure service timeslots of the logical port. For details on how to configure service timeslots, see 12.5 Configuring Service Timeslots. In the NE Explorer, click the NE and choose Configuration > Port Protection from the Function Tree. In the Port Protection window, click New. In the displayed Confirm dialog box, click OK. The Create Protection Group dialog box displayed. Select Intra-Board 1+1 Protection from Protection Type. Enter the other parameters of the protection group. For details of parameters, see the Feature Description.
Step 6 Configure selective receiving on the WDM side of the TN11TOM board. 1. 2.
3. 4.
Click OK. In the window that is displayed, click Close. The created protection group is displayed in the window. Confirm that the values of the parameters for the protection group are the same as the values that are set.
----End
Issue 02 (2011-10-31)
84
Configuring the TN52TOM Board (Manually by Station)
About This Chapter

A TN52TOM board can work in cascading or non-cascading mode and be configured with different port working modes. Based on different working modes, the TN52TOM board is applicable to 12 scenarios. You need to manually configure the TN52TOM board by station on the NMS for the 12 application scenarios. 4.1 Overview of the Working Modes This section describes the board working mode and port working mode. A specific service signal flow of a board is available when the board working mode and port working mode are set to specific values. 4.2 Configuration Principles This section describes the principles for configuring the TN52TOM board. 4.3 Application Scenario 1: Conversion Between Eight Any Services and Two ODU0 or One ODU1 Electrical Signals This configuration example shows how the TN52TOM board is configured to implement conversion between eight channels of optical signals of any rate from 100 Mbit/s to 2.5 Gbit/s and two ODU0 or one ODU1 (with ODU0 mapping) electrical signals. 4.4 Application Scenario 2: Conversion Between Six Any Services and One OTU1 Optical Signal (with ODU0 Mapping) This configuration example shows how the TN52TOM board is configured to implement conversion between six channels of optical signals of any rate from 100 Mbit/s to 2.5 Gbit/s and one channel of OTU1 optical signals (with ODU0 mapping), and how to implement the function of dual feeding and selective receiving on the WDM side. If only one of optical ports 9 (RX7/ TX7) or 10 (RX8/TX8) is used as the WDM-side optical port, the TN52TOM board can implement conversion between seven Any services and one channel of OTU1 optical signals (with ODU0 mapping). Perform the configurations by referring to the following steps. 4.5 Application Scenario 3: Conversion Between Eight Any Services and One ODU1 Electrical Signal
Issue 02 (2011-10-31)
85
This configuration example shows how the TN52TOM board is configured to implement conversion between eight channels of optical signals of any rate from 100 Mbit/s to 2.5 Gbit/s and one ODU1 electrical signal. 4.6 Application Scenario 4: Conversion Between Six Any Services and One OTU1 Optical Signal (with ODU1 Mapping) This configuration example shows how the TN52TOM board is configured to implement conversion between six channels of optical signals of any rate from 100 Mbit/s to 2.5 Gbit/s and one channel of OTU1 optical signals (with ODU1 mapping), and how to implement the function of dual feeding and selective receiving at the WDM side. If only one of optical ports 9 (RX7/ TX7) and 10 (RX8/TX8) is used as the WDM-side optical port, the TN52TOM board can implement conversion between seven Any services and one channel of OTU1 optical signals (with ODU0 mapping). Perform the configurations by referring to the following steps. 4.7 Application Scenario 5: Conversion Between Eight Any Services and Eight ODU0 or Four ODU1 Electrical Signals This configuration example shows how the TN52TOM board is configured to implement conversion between eight channels of optical signals of any rate from 100 Mbit/s to 2.5 Gbit/s and eight channels of ODU0 electrical signals or four channels of ODU1 electrical signals. 4.8 Application Scenario 6: Conversion Between Four Any Services and Two OTU1 Optical Signals This configuration example shows how the TN52TOM board is configured to implement conversion between four channels of optical signals of any rate from 100 Mbit/s to 2.5 Gbit/s and two channels of OTU1 optical signals, and how to implement the function of dual feeding and selective receiving at the WDM side. If only two of optical ports 7 (RX5/TX5), 8 (RX6/ TX6), 9 (RX7/TX7), or 10 (RX8/TX8) are used as the WDM-side optical ports, the TN52TOM can implement conversion between six Any services and two channels of OTU1 optical signals. Perform the configurations by referring to the following steps. 4.9 Application Scenario 7: Conversion Between Eight Any or Four OTU1 Services and Four ODU1 Electrical Signals This configuration example shows how the TN52TOM board is configured to implement conversion between eight channels of Any or four channels of OTU1 services and four channels ODU1 electrical signals. 4.10 Application Scenario 8: Conversion Between Four OTU1 Services and Eight ODU0 Electrical Signals This configuration example shows how the TN52TOM board is configured to implement conversion between four channels of OTU1 services and eight channels of ODU0 electrical signals. 4.11 Application Scenario 9: Conversion Between Four OTU1 Optical Signals and Eight ODU0 Electrical Signals (Through Any Re-Encapsulation) This configuration example shows how the TN52TOM board is configured to implement conversion between four channels OTU1 optical signals and eight channels of ODU0 electrical signals through Any re-encapsulation. 4.12 Application Scenario 10: Conversion Between Four OTU1 Optical Signals and Four ODU1 Electrical Signals (Through Any Re-Encapsulation) This configuration example shows how the TN52TOM board is configured to implement conversion between four channels OTU1 optical signals and four channels of ODU1 electrical signals through Any re-encapsulation. 4.13 Application Scenario 11: Conversion Between Two OTU1 Optical Signals and Two OTU1 Optical Signals (Through Any Re-Encapsulation)
This configuration example shows how the TN52TOM board is configured to implement conversion between two channels OTU1 optical signals and two channels OTU1 optical signals through Any re-encapsulation. 4.14 Application Scenario 12: Regeneration of Four OTU1 Optical Signals This configuration example shows how the TN52TOM board is configured to implement electrical regeneration of four OTU1 optical signals. If you set only two of the 7(RX5/TX5), 8 (RX6/TX6), 9(RX7/TX7), and 10(RX8/TX8) optical ports as WDM-side optical ports, the TN52TOM board can implement conversion between six Any services and two channels of OTU1 optical signals. If the 7(RX5/TX5) and 8(RX6/TX6) optical ports are configured as one protection group and the 9(RX7/TX7) and 10(RX8/TX8) optical ports are configured are another protection group, the TN52TOM board can implement conversion between four Any services and two channels of OTU1 optical signals and implement the function of dual feeding and selective receiving at the WDM side.
Issue 02 (2011-10-31)
87
4.1 Overview of the Working Modes

This section describes the board working mode and port working mode. A specific service signal flow of a board is available when the board working mode and port working mode are set to specific values.
Board Working mode

The TN11TOM and TN52TOM boards support the cascading and non-cascading modes. l In cascading mode, a maximum of eight multi-rate (< 2.5 Gbit/s) Any services can be input to the TN11TOM or TN52TOM board through the SFP module on the client side. The services are then multiplexed into different timeslots of one or two ODU0 services or one ODU1 service. Each group of ClientLP ports, for example, 201(ClientLP1/ClientLP1)-1 to 201(ClientLP1/ClientLP1)-8 ports, can access a maximum of eight Any services. In non-cascading mode, a maximum of eight multi-rate (< 2.5 Gbit/s) Any services can be input to the TN11TOM or TN52TOM board through the SFP module on the client side. The services are then multiplexed into different timeslots of one to eight ODU0 services or one to four ODU1 services. Each group of ClientLP ports, for example, 201(ClientLP1/ ClientLP1)-1 to 201(ClientLP1/ClientLP1)-4 ports, can access a maximum of four Any services.
NOTE
l The navigation path for setting the TN11TOM board is Configuration > WDM Interface > By Board/ Port(Channel) > Board. l The navigation path for setting the TN52TOM board is Configuration > Working Mode. A specific service signal flow of the TN52TOM board is available only when both the board working mode and port working mode are set to specific values.
Port Working Mode

The TN52TOM board should be set to the cascading or non-cascading mode. In addition, application scenarios such as the ODU0 or ODU1 mapping mode and tributary-line mode of the ports on the board should be set. As shown in Table 4-1, the TN52TOM board supports 14 working modes. Table 4-1 Mapping between the working modes and signal flows of the TN52TOM board Board Working mode Port Working Mode ODU0 mode ODU0 TributaryLine Mode ODU1 Mode ODU1 TributaryLine Mode
Issue 02 (2011-10-31)
Signal Flow Any->ODU0[>ODU1] Any->ODU0>ODU1->OTU1 Any->ODU1 Any->ODU1>OTU1
Flow Chart 4.3.2 Service Signal Flow 4.4.2 Service Signal Flow 4.5.2 Service Signal Flow 4.6.2 Service Signal Flow
88
Cascading
Board Working mode
Port Working Mode None (not for ports) ODU0 mode ODU0 TributaryLine Mode ODU1 Mode ODU1_ODU0 mode ODU1_ANY_ODU 0 re-encapsulation mode ODU1_ANY_ODU 0_ODU1 reencapsulation mode ODU1_ANY_ODU 0_ODU1 reencapsulation tributary-line mode ODU1 tributary-line mode None (not for ports)
Signal Flow Any->ODU0[>ODU1] Any->ODU0>ODU1->OTU1 OTU1/Any->ODU1 OTU1->ODU1>ODU0 OTU1->ODU1>Any->ODU0 OTU1->ODU1>Any->ODU0>ODU1 OTU1->ODU1>Any->ODU0>ODU1->OTU1 OTU1/Any>ODU1->OTU1 -
Flow Chart 4.7.2 Service Signal Flow 4.8.2 Service Signal Flow 4.9.2 Service Signal Flow 4.10.2 Service Signal Flow 4.11.2 Service Signal Flow 4.12.2 Service Signal Flow 4.13.2 Service Signal Flow
Non-Cascading
4.14.2 Service Signal Flow -
NOTE
l [->ODU1]: indicates that "ODU1" is optional. For example, in non-cascading ODU0 tributary mode, there are two service signal flows: Any->ODU0 and Any->ODU0->ODU1. l None (not for ports): indicates that the resources at this port are not used and are released to other ports.
4.2 Configuration Principles

This section describes the principles for configuring the TN52TOM board. The rules for configuring the TN52TOM board are as follows: l l The OptiX OSN 8800 does not support distributed cross-connection. For the OptiX OSN 6800, The TN52TOM board can groom a maximum of six Any services through the backplane. The TN52TOM board can groom Any services on the opposite board. l
Issue 02 (2011-10-31)
For the OptiX OSN 3800,

The TN52TOM board can groom a maximum of six Any services through the backplane. The TN52TOM board cannot groom Any services throughout the full-mesh network. Inter-board ODU1 cross-connections between the TN52TOM and TN52NS2 boards, if required, should be configured in such a manner that the ClientLP3-1 port on the TN52TOM board is cross-connected to the ODU1LP1-3 port on the TN52NS2 board, the ClientLP5-1 port on the TN52TOM board is cross-connected to the ODU1LP1-2 port on the TN52NS2 board. When a TN52TOM board is used to configure GE service and Any service crossconnections, the TN52TOM board working with another board must be installed in the following slots: IU2 and IU3 IU4 and IU5 When a TN52TOM board is used to configure ODU1 cross-connections, the TN52TOM board working with another board must be installed in the following slots: IU2 and IU4 IU2 and IU5 IU3 and IU4 IU3 and IU5 l When the board works in any mode, the source and sink channel IDs for services must be consistent. For example, if a client-side service is configured at ClientLPX.1, the service must be also configured at ClientLPY.1 on the interconnected board. If a client-side service is configured at ClientLPX.2, the service must be also configured at ClientLPY.2 on the interconnected board. That is, service interconnection must be implemented at channels with the same ID (port numbers may be different). This is due to hardware limitations. In non-cascading board working mode, the ports on the board can be set to different port working modes. In tributary-line mode, the ODU1 service does not support centralized cross-connection. When the cross-connect board is the XCS board, the ODU0 scheduling is not supported and thus the following port working mode application scenarios are not supported: Application Scenario 8: Non-cascading ODU1_ODU0 mode (OTU1->ODU1->ODU0) Application Scenario 9: Non-cascading ODU1_ANY_ODU0 re-encapsulation mode (OTU1->ODU1->Any->ODU0) l When the cross-connect board is the XCM or XCH board, the following port working mode application scenario is not supported: Application Scenario 10: Non-cascading ODU1_ANY_ODU0_ODU1 reencapsulation mode (OTU1->ODU1->Any->ODU0->ODU1)
l l l
4.3 Application Scenario 1: Conversion Between Eight Any Services and Two ODU0 or One ODU1 Electrical Signals
This configuration example shows how the TN52TOM board is configured to implement conversion between eight channels of optical signals of any rate from 100 Mbit/s to 2.5 Gbit/s and two ODU0 or one ODU1 (with ODU0 mapping) electrical signals.
Issue 02 (2011-10-31)
90

This section describes how to configure the TN52TOM board on a ring network.
Service Requirement
See Figure 4-1. The optical NEs (ONEs) A, B, C, and D form a ring network. All the ONEs function as OADM stations. User1 and User2 communicate with each other. One bidirectional OTU2 service is available between station A and station B. At station A, the TN52TOM board accesses eight Any services (100 Mbit/s to 2.5 Gbit/s) and then converts them into two ODU0 services or one ODU1 service. The two ODU0 services or one ODU1 service is accessed by the TN52NS2 board at station A, and is then converged with other accessed services as one OTU2 service. Figure 4-1 Networking diagram for the TN52TOM board (ODU0 mode in cascading mode) in application scenario 1
User1 SLOT 15 SLOT 12 EAST NMS EAST D C WEST WEST 52TOM 52NS2
User2
WEST B EAST
SLOT 12 SLOT 15
52NS2 52TOM WEST EAST
:OADM

In this example, a TN52TOM board and a TN52NS2 board must be configured at station A and station B each.

This section describes the service signal flow at station A. One OTU2 service is available between station A and station B.
When the cross-connect board is the XCM or XCH board, the signal flow at station A is as shown in Figure 4-2. When the cross-connect board is the XCS board, the signal flow at station A is as shown in Figure 4-3. Figure 4-2 Signal flow at station A when the cross-connect board is the XCM or XCH board
A 52TOM 3(RX1/TX1) 201(ClientLP1/ClientLP1)-1 4(RX2/TX2) 5(RX3/TX3) 6(RX4/TX4) 7(RX5/TX5) 8(RX6/TX6) 202(ClientLP2/ClientLP2)-1 9(RX7/TX7) 202(ClientLP2/ClientLP2)-8 10(RX8/TX8) 164(ODU0LP4/ODU0LP4)-2 164(ODU0LP4/ODU0LP4)-1 51(ODU1LP1/ODU1LP1)-4 201(ClientLP1/ClientLP1)-8 201(ClientLP1/ClientLP1)-1 161(ODU0LP1/ODU0LP1)-2 162(ODU0LP2/ODU0LP2)-1 51(ODU1LP1/ODU1LP1)-2 162(ODU0LP2/ODU0LP2)-2 1(IN/OUT) 202(ClientLP2/ClientLP2)-1 163(ODU0LP3/ODU0LP3)-1 51(ODU1LP1/ODU1LP1)-3 163(ODU0LP3/ODU0LP3)-2 161(ODU0LP1/ODU0LP1)-1 51(ODU1LP1/ODU1LP1)-1 A 52NS2
: Client-side services : WDM-side services : Working service direction : Virtual channel
Figure 4-3 Signal flow at station A when the cross-connect board is the XCS board
52TOM 3(RX1/TX1) 201(ClientLP1/ClientLP1)-1 4(RX2/TX2) 5(RX3/TX3) 6(RX4/TX4) 7(RX5/TX5) 8(RX6/TX6) 202(ClientLP2/ClientLP2)-1 9(RX7/TX7) 202(ClientLP2/ClientLP2)-8 10(RX8/TX8) 51(ODU1LP1/ODU1LP1)-4 161(ODU0LP1/ODU0LP1)-2 201(ClientLP1/ClientLP1)-8 161(ODU0LP1/ODU0LP1)-1 202(ClientLP2/ClientLP2)-1 51(ODU1LP1/ODU1LP1)-3 201(ClientLP1/ClientLP1)-1 161(ODU0LP1/ODU0LP1)-1 51(ODU1LP1/ODU1LP1)-2 1(IN/OUT) 51(ODU1LP1/ODU1LP1)-1 52NS2
: Client-side services : WDM-side services : Working service direction : Virtual channel

Prerequisite

Issue 02 (2011-10-31)
92
Precautions
NOTE
l When the cross-connect board is the XCM or XCH board, the TN52TOM board cannot groom the ODU1 service in cascading ODU0 mode (Any->ODU0[->ODU1]). l When the cross-connect board is the XCS board, the TN52TOM board cannot groom the ODU0 service in cascading ODU0 mode (Any->ODU0[->ODU1]).
NOTE
The client-side optical port cannot be set to Line Side Color Optical Port or Line Side Colorless Optical Port.
NOTE
Services can be input at each client-side optical port at a maximum rate of 1.25 Gbit/s.
NOTE
Services can be input at the eight pairs of client-side optical ports at a maximum rate of 2.5 Gbit/s.
NOTE
l The total rate of services that are input at each group of ClientLP ports, such as 201(ClientLP1/ ClientLP1)-1 to 201(ClientLP1/ClientLP)-8, cannot be higher than 1.25 Gbit/s. l Only one GE service can be input at each group of ClientLP ports.
NOTE
If a channel of the ClientLP1 port and a channel of the ClientLP2 port are identified by the same number, these two channels cannot be used at the same time. For example, if the 201(ClientLP1/ClientLP1)-1 channel is configured with a service type, you cannot configure a service type for the 202(ClientLP2/ ClientLP2)-1 channel.

Step 1 Set the Working Mode of the TN52TOM board: Set Board Working mode to Cascading and then set Port Working Mode to ODU0 mode (Any->ODU0[->ODU1]). For details, see 12.1 Configuring Working Modes. Step 2 Configure the Service Type at the WDM Interface of the TN52TOM according to the service planning. For details, see 12.2 Configuring the Service Type. Step 3 Configure the cross-connections from the RX/TX ports to the ClientLP ports on the TN52TOM board for the Any services of the board. 1. Configure the cross-connections from the RX/TX ports to the ClientLP ports on the TN52TOM board for the Any services that are input to the board. For details, see 12.4.1 Creating Cross-Connections.
NOTE
In this configuration, you can set Level to GE or ANY. If you set Level to ANY, you can set Service Type to only FE, FC100, FICON, DVB-ASI, SDI, ESCON, or FDDI. The service type must be the same as Service Type in the WDM Interface window of the TN52TOM board.
Issue 02 (2011-10-31)
93
2.
Repeat Step 3.1 to configure the remaining Any services.
Step 4 Configure electrical cross-connections for the two ODU0 services between the TN52TOM and TN52NS2 boards.
NOTE
In cascading ODU0 mode (Any->ODU0[->ODU1]), this configuration is supported only when the crossconnect board is the XCM or XCH board.
1.
Configure a cross-connection for one ODU0 service between the TN52TOM and TN52NS2 boards. For details, see 12.4.1 Creating Cross-Connections.
Issue 02 (2011-10-31)
94
2.
Repeat Step 4.1 to configure a cross-connection for the other ODU0 service between the TN52TOM and TN52NS2 boards.
Step 5 Configure electrical cross-connections for the ODU1 services between the TN52TOM and TN52NS2 boards.For details, see 12.4.1 Creating Cross-Connections.
NOTE
In cascading ODU0 mode (Any->ODU0[->ODU1]), this configuration is supported only when the crossconnect board is the XCM or XCH board. When ODU1 cross-connections are created, ODU0 cross-connections from the ClientLP port to ODU0LP on the TN52TOM board are automatically created.
Issue 02 (2011-10-31)
95
----End
4.4 Application Scenario 2: Conversion Between Six Any Services and One OTU1 Optical Signal (with ODU0 Mapping)
This configuration example shows how the TN52TOM board is configured to implement conversion between six channels of optical signals of any rate from 100 Mbit/s to 2.5 Gbit/s and one channel of OTU1 optical signals (with ODU0 mapping), and how to implement the function of dual feeding and selective receiving on the WDM side. If only one of optical ports 9 (RX7/ TX7) or 10 (RX8/TX8) is used as the WDM-side optical port, the TN52TOM board can implement conversion between seven Any services and one channel of OTU1 optical signals (with ODU0 mapping). Perform the configurations by referring to the following steps.

Service Requirement
See Figure 4-4. The optical NEs (ONEs) A, B, C, and D form a ring network. All the ONEs function as OADM stations. User1 and User2 communicate with each other. One bidirectional OTU1 service is available between station A and station B. At station A, the TN52TOM board accesses six Any services
(100 Mbit/s to 2.5 Gbit/s) and then converts them into one OTU1 service. On the WDM side, the TN52TOM board performs dual feeding and selective receiving. Figure 4-4 Networking diagram for the TN52TOM board (ODU0 tributary-line mode in cascading mode) in application scenario 2
User1
52TOM
User2
WEST B EAST
A D C
EAST
WEST
SLOT 15
52TOM WEST EAST
:OADM


This section describes the service signal flow at station A. One OTU1 service is available between station A and station B. Figure 4-5 shows the service signal flow at station A. Figure 4-5 Bidirectional service at station A
52TOM 3(RX1/TX1) 4(RX2/TX2) 201(ClientLP1/ClientLP1)-7 201(ClientLP1/ClientLP1)-8 161(ODU0LP1/ODU0LP1)-1 6(RX4/TX4) 7(RX5/TX5) 8(RX6/TX6) 202(ClientLP2/ClientLP2)-7 202(ClientLP2/ClientLP2)-8 202(ClientLP2/ClientLP2)-1 202(ClientLP2/ClientLP2)-2 202(ClientLP2/ClientLP2)-1 161(ODU0LP1/ODU0LP1)-2 51(ODU1LP1/ODU1LP1)-1 10(RX8/TX8) 201(ClientLP1/ClientLP1)-1 201(ClientLP1/ClientLP1)-2 201(ClientLP1/ClientLP1)-1 161(ODU0LP1/ODU0LP1)-1
5(RX3/TX3)
9(RX7/TX7)
Issue 02 (2011-10-31)
97

Prerequisite

Precautions
NOTE
Two channels with the same type of services at the ClientLP1 and ClientLP2 ports each cannot be used at the same time. For example, if the 201(ClientLP1/ClientLP1)-1 service type is configured, the 202(ClientLP2/ClientLP2)-1 service type cannot be configured. The total rate of services that are input at each group of ClientLP ports, such as 201(ClientLP1/ ClientLP1)-1 to 201(ClientLP1/ClientLP)-8, cannot be higher than 1.25 Gbit/s. Only one GE service can be input through each group of ClientLP ports. Services can be input at the six pairs of client-side optical ports at a maximum rate of 2.5 Gbit/s. Services can be input at each client-side optical port at a maximum rate of 1.25 Gbit/s. In cascading mode, only RX7/TX7 and RX8/TX8 can be used as the WDM-side optical ports.
l l l l l

Step 1 Set the Working Mode of the TN52TOM board: Set Board Working mode to Cascading and then set Port Working Mode to ODU0 Tributary-Line Mode(Any->ODU0->ODU1>OTU1). For details, see 12.1 Configuring Working Modes. Step 2 Set the type of ports 9 (RX7/TX7) and 10 (RX8/TX8) to Line Side Color Optical Port. For details, see 11.1 Modifying Port.
NOTE
When the TN52TOM board is used as a tributary-line board, Type of this optical port used as the WDM side port must be changed to Line Side Color Optical Port.
Step 3 Configure Service Type in the WDM Interface window of the TN52TOM board according to the service planning. For details, see 12.2 Configuring the Service Type. Step 4 Configure the cross-connections from the RX/TX ports to the ClientLP ports on the TN52TOM board for the Any services of the board. 1. Configure the cross-connections from the RX/TX ports to the ClientLP ports on the TN52TOM board for the Any services of the board. For details, see 12.4.1 Creating CrossConnections.
Issue 02 (2011-10-31)
98

NOTE
2.
Step 5 Configure two separate cross-connections from the internal logical port to ports 9 (RX7/TX7) and 10 (RX8/TX8) for the TN52TOM board to achieve dual feeding. 1. Configure two separate cross-connections from the internal logical port to ports 9 (RX7/ TX7) and 10 (RX8/TX8) for the TN52TOM board to achieve dual feeding. For details, see 12.4.1 Creating Cross-Connections.
NOTE
Issue 02 (2011-10-31)
99
Issue 02 (2011-10-31)
100
Step 6 Configure selective receiving at the WDM side of the TN52TOM board. 1. 2. In the NE Explorer, click the NE and choose Configuration > Port Protection. In the Port Protection window, click New. In the displayed Confirm dialog box, click OK. The Create Protection Group dialog box displayed. Select Intra-Board 1+1 Protection from Protection Type. Enter the other parameters of the protection group. For details of parameters, see the Feature Description.
3.
Click OK. In the window that is displayed, click Close. The created protection group is displayed in the window.
----End
4.5 Application Scenario 3: Conversion Between Eight Any Services and One ODU1 Electrical Signal
This configuration example shows how the TN52TOM board is configured to implement conversion between eight channels of optical signals of any rate from 100 Mbit/s to 2.5 Gbit/s and one ODU1 electrical signal.

Service Requirement
See Figure 4-6. The optical NEs (ONEs) A, B, C, and D form a ring network. All the ONEs function as OADM stations. User1 and User2 communicate with each other. One bidirectional OTU2 service is available between station A and station B. At station A, the TN52TOM board accesses eight Any services
(100 Mbit/s to 2.5 Gbit/s) and then converts them into one ODU1 service. The ODU1 service is accessed by the TN52NS2 board at station A, and is then converged with other accessed services as one OTU2 service. Figure 4-6 Networking diagram for the TN52TOM board (ODU1 mode in cascading mode) in application scenario 3
User1 SLOT 15 SLOT 12 EAST NMS EAST D C WEST WEST 52TOM 52NS2
User2
WEST B EAST
SLOT 12 SLOT 15
:OADM

In this example, a TN52TOM board and a TN52NS2 board must be configured at station A and station B each.

This section describes the service signal flow at station A. One OTU2 service is available between station A and station B. Figure 4-7 shows the service signal flow at station A.
Issue 02 (2011-10-31)
102

52TOM 3(RX1/TX1) 201(ClientLP1/ClientLP1)-1 4(RX2/TX2) 201(ClientLP1/ClientLP1)-2 5(RX3/TX3) 6(RX4/TX4) 201(ClientLP1/ClientLP1)-1 7(RX5/TX5) 8(RX6/TX6) 9(RX7/TX7) 10(RX8/TX8) : 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 201(ClientLP1/ClientLP1)-7 201(ClientLP1/ClientLP1)-8 51(ODU1LP1/ODU1LP1)-4 51(ODU1LP1/ODU1LP1)-3 51(ODU1LP1/ODU1LP1)-2 1(IN/OUT) 52NS2 51(ODU1LP1/ODU1LP1)-1

Prerequisite

Precautions
NOTE
The client-side optical port cannot be set to Line Side Color Optical Port or Line Side Colorless Optical Port.
NOTE
A ClientLP port can access only one service that has a rate higher than 1.25 Gbit/s, and this service can be configured on only the first channel of the ClientLP port.
NOTE
Services can be input at the eight pairs of client-side optical ports at a maximum rate of 2.5 Gbit/s.

Step 1 Set Working Mode of the TN52TOM board: Set Board Working mode to Cascading and then set Port Working Mode to ODU1 mode (Any->ODU1). For details, see 12.1 Configuring Working Modes. Step 2 Configure the Service Type at the WDM Interface of the TN52TOM according to the service planning. For details, see 12.2 Configuring the Service Type. Step 3 Configure the cross-connections from the RX/TX ports to the ClientLP ports on the TN52TOM board for the Any services of the board.
1.
Configure the cross-connections from the RX/TX ports to the ClientLP ports on the TN52TOM board for the Any services that are input to the board. For details, see 12.4.1 Creating Cross-Connections.
NOTE
In this configuration, you can set Level to GE or ANY. If you set Level to ANY, you can set Service Type to only FE, STM-1,.STM-4,.STM-16,.OC-3,.OC-12,.OC-48,.FC100,.FC200,.FICON,.FICON Express,.HD-SDI,.DVB-ASI, SDI, ESCON, or FDDI. The service type must be the same as Service Type in the WDM Interface window of the TN52TOM board.
2.
Step 4 Configure electrical cross-connections for the ODU1 services between the TN52TOM and TN52NS2 boards. For details, see 12.4.1 Creating Cross-Connections.
Issue 02 (2011-10-31)
104
----End
4.6 Application Scenario 4: Conversion Between Six Any Services and One OTU1 Optical Signal (with ODU1 Mapping)
This configuration example shows how the TN52TOM board is configured to implement conversion between six channels of optical signals of any rate from 100 Mbit/s to 2.5 Gbit/s and one channel of OTU1 optical signals (with ODU1 mapping), and how to implement the function of dual feeding and selective receiving at the WDM side. If only one of optical ports 9 (RX7/ TX7) and 10 (RX8/TX8) is used as the WDM-side optical port, the TN52TOM board can implement conversion between seven Any services and one channel of OTU1 optical signals (with ODU0 mapping). Perform the configurations by referring to the following steps.

Service Requirement
See Figure 4-8. The optical NEs (ONEs) A, B, C, and D form a ring network. All the ONEs function as OADM stations. User1 and User2 communicate with each other. One bidirectional OTU1 service is available between station A and station B. At station A, the TN52TOM board accesses six Any services
(100 Mbit/s to 2.5 Gbit/s) and then converts them into one OTU1 service. On the WDM side, the TN52TOM board performs dual feeding and selective receiving. Figure 4-8 Networking diagram for the TN52TOM board (ODU1 tributary-line mode in cascading mode) in application scenario 4
User1
52TOM
User2
WEST B EAST
A D C
EAST
WEST
SLOT 15
52TOM WEST EAST
:OADM


Issue 02 (2011-10-31)
106

52TOM 3(RX1/TX1) 201(ClientLP1/ClientLP1)-1 4(RX2/TX2) 5(RX3/TX3) 6(RX4/TX4) 7(RX5/TX5) 8(RX6/TX6) 201(ClientLP1/ClientLP1)-7 201(ClientLP1/ClientLP1)-8 201(ClientLP1/ClientLP1)-1 51(ODU1LP1/ODU1LP1) 201(ClientLP1/ClientLP1)-2 9(RX7/TX7 ) 10(RX8/TX8)

Prerequisite

Precautions
NOTE
The client-side six pairs of optical ports can access services at a maximum rate of 2.5 Gbit/s. For the client services at a rate of greater than 1.25 Gbit/s, the client-side ports can access up to only one channel. This service can be configured at only the first ClientLP port. In cascading mode, only RX7/TX7 and RX8/TX8 can be used as the WDM-side optical ports.

Step 1 Set the Working Mode of the TN52TOM board: Set Board Working mode to Cascading and then set Port Working Mode to ODU1 Tributary-Line Mode(Any->ODU1->OTU1). For details, see 12.1 Configuring Working Modes. Step 2 Set the type of ports 9 (RX7/TX7) and 10 (RX8/TX8) to Line Side Color Optical Port. For details, see 11.1 Modifying Port.
NOTE
When the TN52TOM board is used as a tributary-line board, Type of this optical port used as the WDM side port must be changed to Line Side Color Optical Port.
Step 3 Configure Service Type in the WDM Interface window of the TN52TOM board according to the service planning. For details, see 12.2 Configuring the Service Type.
Step 4 Configure the cross-connections from the RX/TX ports to the ClientLP ports on the TN52TOM board for the Any services of the board. 1. Configure the cross-connections from the RX/TX ports to the ClientLP ports on the TN52TOM board for the Any services of the board. For details, see 12.4.1 Creating CrossConnections.
NOTE
In this configuration, you can set Level to GE or ANY. If you set Level to ANY, you can set Service Type to only FE, STM-1,.STM-4,.STM-16,.OC-3,.OC-12,.OC-48,.FC100,.FC200,.FICON,.FICON Express,.HD-SDI,.DVB-ASI, SDI, ESCON, or FDDI. The service type must be the same as Service Type in the WDM Interface window of the TN52TOM board.
2.
Step 5 Configure two separate cross-connections from the internal logical port to ports 9 (RX7/TX7) and 10 (RX8/TX8) for the TN52TOM board to achieve dual feeding. For details, see 12.4.1 Creating Cross-Connections.
NOTE
Issue 02 (2011-10-31)
108
Issue 02 (2011-10-31)
109
Step 6 Configure selective receiving at the WDM side of the TN52TOM board. 1. 2. In the NE Explorer, click the NE and choose Configuration > Port Protection. In the Port Protection window, click New. In the displayed Confirm dialog box, click OK. The Create Protection Group dialog box displayed. Select Intra-Board 1+1 Protection from Protection Type. Enter the other parameters of the protection group. For details of parameters, see the Feature Description.
3. 4.
Click OK. In the window that is displayed, click Close. The created protection group is displayed in the window. Confirm that the values of the parameters for the protection group are the same as the values that are set.
----End
4.7 Application Scenario 5: Conversion Between Eight Any Services and Eight ODU0 or Four ODU1 Electrical Signals
This configuration example shows how the TN52TOM board is configured to implement conversion between eight channels of optical signals of any rate from 100 Mbit/s to 2.5 Gbit/s and eight channels of ODU0 electrical signals or four channels of ODU1 electrical signals.

Service Requirement
User1, User2, and User3 communicate with each other through one OTU2 service each. At station A, the TN52TOM board accesses eight Any services and then converts them into eight ODU0 or four ODU1 services. The eight ODU0 or four ODU1 services are then sent to two TN52NS2 boards at station A based on the actual service requirement. Each TN52NS2 board converges the received ODU0 or ODU1 services and other accessed services into one OTU2 service. Figure 4-10 Networking diagram for the TN52TOM board (ODU0 mode in non-cascading mode) in application scenario 5
User1 SLOT 15 SLOT 12 SLOT 13 EAST NMS EAST D C WEST SLOT 12 SLOT 15 WEST EAST 52NS2 52TOM WEST 52TOM 52NS2 52NS2
User2
WEST B EAST
User3
SLOT 12 SLOT 15
52NS2 52TOM
:OADM

In this example, a TN52TOM board and two TN52NS2 boards must be configured at station A. A TN52TOM board and a TN52NS2 board must be configured at station B and station D each.

This section describes the service signal flow at station A. One OTU2 service is available between station A and station B. When the cross-connect board is the XCM or XCH board, the signal flow at station A is as shown in Figure 4-11. When the cross-connect board is the XCS board, the signal flow at station A is as shown in Figure 4-12.
Issue 02 (2011-10-31)
111
Figure 4-11 Signal flow at station A when the cross-connect board is the XCM or XCH board
52TOM 3(RX1/TX1) 201(ClientLP1/ClientLP1)1 201(ClientLP1/ClientLP1)-1 201(ClientLP1/ClientLP1)4 4(RX2/TX2) 202(ClientLP2/ClientLP2)-1 202(ClientLP2/ClientLP2)-1 5(RX3/TX3) 202(ClientLP2/ClientLP2)-4 203(ClientLP3/ClientLP3)-1 203(ClientLP3/ClientLP3)-2 6(RX4/TX4) 204(ClientLP4/ClientLP4)-1 204(ClientLP4/ClientLP4)-2 205(ClientLP5/ClientLP5)1 205(ClientLP5/ClientLP5)-1 205(ClientLP5/ClientLP5)4 8(RX6/TX6) 206(ClientLP6/ClientLP6)-1 206(ClientLP6/ClientLP6)-1 206(ClientLP6/ClientLP6)-4 9(RX7/TX7) 207(ClientLP7/ClientLP7)-1 207(ClientLP7/ClientLP7)-2 208(ClientLP8/ClientLP8)-1 208(ClientLP8/ClientLP8)-2 164(ODU0LP4/ODU0LP4)-1 207(ClientLP7/ClientLP7)-1 208(ClientLP8/ClientLP8)-1 164(ODU0LP4/ODU0LP4)-2 51(ODU1LP1/ODU1LP1)-4 163(ODU0LP3/ODU0LP3)-2 203(ClientLP3/ClientLP3)-1 162(ODU0LP2/ODU0LP2)-2 204(ClientLP4/ClientLP4)-1 163(ODU0LP3/ODU0LP3)-1 51(ODU1LP1/ODU1LP1)-3 1(IN/OUT) 162(ODU0LP2/ODU0LP2)-1 51(ODU1LP1/ODU1LP1)-2 161(ODU0LP1/ODU0LP1)2 161(ODU0LP1/ODU0LP1)-1 51(ODU1LP1/ODU1LP1)-1 52NS2
7(RX5/TX5)
10(RX8/TX8)
Figure 4-12 Signal flow at station A when the cross-connect board is the XCS board
52TOM 3(RX1/TX1) 201(ClientLP1/ClientLP1)-1 201(ClientLP1/ClientLP1)-1 201(ClientLP1/ClientLP1)-4 4(RX2/TX2) 202(ClientLP2/ClientLP2)-1 202(ClientLP2/ClientLP2)-1 5(RX3/TX3) 202(ClientLP2/ClientLP2)-4 203(ClientLP3/ClientLP3)-1 203(ClientLP3/ClientLP3)-2 6(RX4/TX4) 204(ClientLP4/ClientLP4)-1 204(ClientLP4/ClientLP4)-2 205(ClientLP5/ClientLP5)-1 205(ClientLP5/ClientLP5)-1 205(ClientLP5/ClientLP5)-4 8(RX6/TX6) 206(ClientLP6/ClientLP6)-1 206(ClientLP6/ClientLP6)-1 206(ClientLP6/ClientLP6)-4 9(RX7/TX7) 207(ClientLP7/ClientLP7)-1 207(ClientLP7/ClientLP7)-2 208(ClientLP8/ClientLP8)-1 207(ClientLP7/ClientLP7)-1 164(ODU0LP4/ODU0LP4)-1 164(ODU0LP4/ODU0LP4)-1 51(ODU1LP1/ODU1LP1)-4 163(ODU0LP3/ODU0LP3)-2 163(ODU0LP3/ODU0LP3)-1 163(ODU0LP3/ODU0LP3)-1 51(ODU1LP1/ODU1LP1)-3 203(ClientLP3/ClientLP3)-1 204(ClientLP4/ClientLP4)-1 162(ODU0LP2/ODU0LP2)-1 162(ODU0LP2/ODU0LP2)-1 162(ODU0LP2/ODU0LP2)-2 1(IN/OUT) 51(ODU1LP1/ODU1LP1)-2 161(ODU0LP1/ODU0LP1)-2 161(ODU0LP1/ODU0LP1)-1 161(ODU0LP1/ODU0LP1)-1 51(ODU1LP1/ODU1LP1)-1 52NS2
7(RX5/TX5)
10(RX8/TX8)

Prerequisite

Precautions
NOTE
When the cross-connect board is the XCM or XCH board, the TN52TOM board cannot groom the ODU1 service in non-cascading ODU0 mode (Any->ODU0[->ODU1]). When the cross-connect board is the XCS board, the TN52TOM board cannot groom the ODU0 service in non-cascading ODU0 mode (Any->ODU0[->ODU1]).
NOTE
The total rate of services that are input at each group of ClientLP ports, such as 201(ClientLP1/ClientLP1)-1 to 201(ClientLP1/ClientLP)-4, cannot be higher than 1.25 Gbit/s. Only one GE service can be input at each group of ClientLP ports. The client-side eight pairs of optical ports can access services at a maximum rate of 10 Gbit/s. If a channel of the ClientLP1 port and a channel of the ClientLP2 port are identified by the same number, these two channels cannot be used at the same time. For example, if the 201(ClientLP1/ClientLP1)-1 channel is configured with a service type, you cannot configure a service type for the 202(ClientLP2/ ClientLP2)-1 channel. Service configurations at the ClentLP3 and ClientLP4, ClientLP5 and ClientLP6, and ClientLP7 and ClientLP8 ports must also comply with this restriction.

Step 1 Set Working Mode of the TN52TOM board: Set Board Working mode to Non-Cascading and then set Port Working Mode of all the ClientLP ports to ODU0 mode (Any->ODU0[>ODU1]). For details, see 12.1 Configuring Working Modes. Step 2 Configure the Service Type at the WDM Interface of the TN52TOM according to the service planning. For details, see 12.2 Configuring the Service Type. Step 3 Configure the cross-connections for the eight Any services that are input to the TN52TOM board. 1. Configure the cross-connections from the RX/TX ports to the ClientLP ports on the TN52TOM board for the Any services that are input to the board. For details, see 12.4.1 Creating Cross-Connections.
NOTE
Issue 02 (2011-10-31)
113
2.
Step 4 Configure cross-connections for the eight ODU0 services between the TN52TOM and TN52NS2 boards.
NOTE
In non-cascading ODU0 mode (Any->ODU0[->ODU1]), this configuration is supported only when the cross-connect board is the XCM or XCH board.
1.
Configure a cross-connection for one ODU0 service between the TN52TOM and TN52NS2 boards. For details, see 12.4.1 Creating Cross-Connections.
Issue 02 (2011-10-31)
114
2.
Repeat Step 4.1 to configure a cross-connection for the other ODU0 service between the TN52TOM and TN52NS2 boards.
Step 5 Configure cross-connections for the four ODU1 services between the TN52TOM and TN52NS2 boards. For details, see 12.4.1 Creating Cross-Connections.
NOTE
In non-cascading ODU0 mode (Any->ODU0[->ODU1]), this configuration is supported only for OptiX OSN 6800 and 3800. When an ODU1 cross-connection is created, an intra-board ODU0 cross-connection is created automatically from the ClientIP port to the ODU0LP port on the TN52TOM board.
Issue 02 (2011-10-31)
115
----End
4.8 Application Scenario 6: Conversion Between Four Any Services and Two OTU1 Optical Signals
This configuration example shows how the TN52TOM board is configured to implement conversion between four channels of optical signals of any rate from 100 Mbit/s to 2.5 Gbit/s and two channels of OTU1 optical signals, and how to implement the function of dual feeding and selective receiving at the WDM side. If only two of optical ports 7 (RX5/TX5), 8 (RX6/ TX6), 9 (RX7/TX7), or 10 (RX8/TX8) are used as the WDM-side optical ports, the TN52TOM can implement conversion between six Any services and two channels of OTU1 optical signals. Perform the configurations by referring to the following steps.

Service Requirement
See Figure 4-13. The optical NEs (ONEs) A, B, C, and D form a ring network. All the ONEs function as OADM stations. User1 and User2 communicate with each other. Two bidirectional OTU1 services are available between station A and station B. At station A, the TN52TOM board accesses four Any services and then converts them into two OTU2 services.
Figure 4-13 Networking diagram for the TN52TOM board (ODU0 tributary-line mode in noncascading mode) in application scenario 6
User1
52TOM
User2
WEST B EAST
A D C
EAST
WEST
SLOT 15
52TOM WEST EAST
:OADM


This section describes the service signal flow at station A. Two OTU1 services are available between station A and station B. Figure 4-14 shows the service signal flow at station A. Figure 4-14 Bidirectional service at station A
52TOM 3(RX1/TX1) 201(ClientLP1/ClientLP1)-1 201(ClientLP1/ClientLP1)-1 201(ClientLP1/ClientLP1)-4 4(RX2/TX2) 202(ClientLP2/ClientLP2)-1 202(ClientLP2/ClientLP2)-1 5(RX3/TX3) 202(ClientLP2/ClientLP2)-4 203(ClientLP3/ClientLP3)-1 203(ClientLP3/ClientLP3)-2 6(RX4/TX4) 204(ClientLP4/ClientLP4)-1 204(ClientLP4/ClientLP4)-2 203(ClientLP3/ClientLP3)-1 204(ClientLP4/ClientLP4)-1 162(ODU0LP2/ODU0LP2)-1 162(ODU0LP2/ODU0LP2)-1 162(ODU0LP2/ODU0LP2)-2 52(ODU1LP2/ODU1LP2)-1 10(RX8/TX8) 9(RX7/TX7) 161(ODU0LP1/ODU0LP1)-2 161(ODU0LP1/ODU0LP1)-1 51(ODU1LP1/ODU1LP1)-1 8(RX6/TX6) 161(ODU0LP1/ODU0LP1)-1 7(RX5/TX5)
Issue 02 (2011-10-31)
117

Prerequisite

Precautions
NOTE
The total rate of services that are input at each group of ClientLP ports, such as 201(ClientLP1/ClientLP1)-1 to 201(ClientLP1/ClientLP)-4, cannot be higher than 1.25 Gbit/s. Only one GE service can be input at each group of ClientLP ports. The client-side optical ports can access services at a maximum rate of 5 Gbit/s. When the number of a route of the ClientLP1 or ClientLP3 port is the same as that of a route of the ClientLP2 or ClientLP4 port, the two routes cannot be configured with cross-connections at the same time. For example, if the 201(ClientLP1/ClientLP1)-1 service type is configured, the 202(ClientLP2/ClientLP2)-1 service type cannot be configured.
NOTE
The client-side optical ports and WDM-side optical ports can be selected as required.
NOTE
l The ClientLP5 and ClientLP7 do not support the non-cascading ODU0 Tributary-Line Mode(Any>ODU0->ODU1->OTU1) mode. l Before the working modes of the ClientLP1 and ClientLP3 ports are set to ODU0 Tributary-Line Mode(Any->ODU0->ODU1->OTU1), the working modes of the ClientLP5 and ClientLP7 ports must be set to NONE Mode(Not for Port).

Step 1 Set Working Mode of the TN52TOM board: Set Board Working mode to Non-Cascading and then set Port Working Mode of all the ClientLP ports to ODU0 Tributary-Line Mode (Any->ODU0->ODU1->OTU1). For details, see 12.1 Configuring Working Modes. Step 2 Set the type of ports 7 (RX5/TX5), 8 (RX6/TX6), 9 (RX7/TX7) and 10 (RX8/TX8) to Line Side Color Optical Port. For details, see 11.1 Modifying Port.
NOTE
When the TN52TOM board is used as a tributary-line board, Type of the optical port used as the WDM side port must be changed to Line Side Color Optical Port.
Step 3 Configure the Service Type at the WDM Interface of the TN52TOM according to the service planning. For details, see 12.2 Configuring the Service Type. Step 4 Configure the cross-connections for the four Any services that are input to the TN52TOM board. 1. Configure the cross-connections from the RX/TX ports to the ClientLP ports on the TN52TOM board for the Any services that are input to the board. For details, see 12.4.1 Creating Cross-Connections.
Issue 02 (2011-10-31)

NOTE
2.
Step 5 Configure two separate cross-connections from the ODU1LP port to WDM side ports on the TN52TOM board to achieve dual feeding. 1. Configure two separate cross-connections from the ODU1LP port to ports 7 (RX5/TX5) and 8 (RX6/TX6) for the TN52TOM board to achieve dual feeding. For details, see 12.4.1 Creating Cross-Connections.
NOTE
Issue 02 (2011-10-31)
119
2.
Repeat Step 5.1 to configure two separate cross-connections from the internal logical port to ports 9 (RX7/TX7) and 10 (RX8/TX8) for the TN52TOM board to achieve dual feeding. In the NE Explorer, click the NE and choose Configuration > Port Protection. In the Port Protection user port, click New. In the displayed Confirm dialog box, click OK. The Create Protection Group dialog box displayed. Select Intra-Board 1+1 Protection from Protection Type. Enter the other parameters of the protection group. For details on the parameters, see the Feature Description.
Step 6 Configure selective receiving at the WDM side of the TN52TOM board. 1. 2.
Issue 02 (2011-10-31)
120
3. 4. 5.
Click OK. In the window that is displayed, click Close. The created protection group is displayed in the window. Confirm that the values of the parameters for the protection group are the same as the values that are set. Repeat Step 6.2 and Step 6.3 to configure the selective receiving feature of the ports 9 (RX7/TX7) and 10 (RX8/TX8) for the TN52TOM board.
----End
4.9 Application Scenario 7: Conversion Between Eight Any or Four OTU1 Services and Four ODU1 Electrical Signals
This configuration example shows how the TN52TOM board is configured to implement conversion between eight channels of Any or four channels of OTU1 services and four channels ODU1 electrical signals.

Service Requirement
See Figure 4-15. The optical NEs (ONEs) A, B, C, and D form a ring network. All the ONEs function as OADM stations. User1, User2, and User3 communicate with each other through one OTU2 service each. At station A, the TN52TOM board accesses eight Any services (100Mbit/s - 2.5Gbit/s) or four OTU1 services and then converts them into four ODU1 services. The four ODU1 services are
then sent to two TN52NS2 boards at station A based on the actual services requirement. Each TN52NS2 board converges the received ODU1 services and other accessed services into one OTU2 service. Figure 4-15 Networking diagram for the TN52TOM board (ODU1 mode in non-cascading mode) in application scenario 7
User2
WEST B EAST
User3
SLOT 12 SLOT 15
52NS2 52TOM
:OADM


Issue 02 (2011-10-31)
122

52NS2 52TOM 51(ODU1LP1/ODU1LP1)-1
3(RX1/TX1) 4(RX2/TX2) 5(RX3/TX3) 6(RX4/TX4) 7(RX5/TX5) 8(RX6/TX6) 9(RX7/TX7) 10(RX8/TX8)
201(ClientLP1/ClientLP1)-1 201(ClientLP1/ClientLP1)-1 201(ClientLP1/ClientLP1)-4 203(ClientLP3/ClientLP3)-1 203(ClientLP3/ClientLP3)-1 203(ClientLP3/ClientLP3)-2 205(ClientLP5/ClientLP5)-1 205(ClientLP5/ClientLP5)-1 205(ClientLP5/ClientLP5)-4 207(ClientLP7/ClientLP7)-1 207(ClientLP7/ClientLP7)-1 207(ClientLP7/ClientLP7)-2
51(ODU1LP1/ODU1LP1)-2 1(IN/OUT) 51(ODU1LP1/ODU1LP1)-3
51(ODU1LP1/ODU1LP1)-4
52NS2 51(ODU1LP1/ODU1LP1)-1
51(ODU1LP1/ODU1LP1)-2 1(IN/OUT) 51(ODU1LP1/ODU1LP1)-3
51(ODU1LP1/ODU1LP1)-4 : Client-side services : WDM-side services : Working service direction : Virtual channel

Prerequisite

Precautions
NOTE
A ClientLP port can access only one service that has a rate higher than 1.25 Gbit/s, and this service can be configured on only the first channel of the ClientLP port. The client-side eight pairs of optical ports can access services at a maximum rate of 10 Gbit/s.

Step 1 Set Working Mode of the TN52TOM board: Set Board Working mode to Non-Cascading and then set Port Working Mode to ODU1 mode (OTU1/Any->ODU1). For details, see 12.1 Configuring Working Modes. Step 2 Configure the Service Type at the WDM Interface of the TN52TOM according to the service planning. For details, see 12.2 Configuring the Service Type.
Step 3 Configure the cross-connections from the RX/TX ports to the ClientLP ports on the TN52TOM board for the Any services of the board. 1. Configure the cross-connections from the 3(RX1/TX1) ports to the 201(ClientLP1/ ClientLP1) ports on the TN52TOM board for the Any or OTU1 services of the board. For details, see 12.4.1 Creating Cross-Connections.
NOTE
In this configuration, you can set Level to GE, OTU1 or ANY. If you set Level to ANY, you can set Service Type to only FE, STM-1,.STM-4,.STM-16,.OC-3,.OC-12,.OC-48,.FC100,.FC200,.FICON,.FICON Express,.HD-SDI,.DVB-ASI, SDI, ESCON, or FDDI. The service type must be the same as Service Type in the WDM Interface window of the TN52TOM board.
2.
Issue 02 (2011-10-31)

Step 4 Configure electrical cross-connections for the ODU1 services between the TN52TOM and TN52NS2 boards. For details, see 12.4.1 Creating Cross-Connections.
Step 5 See the steps above to configure the station B, C, and D. Inter-board ODU1 cross-connections between the 52TOM and 52NS2 boards must be configured in the manner below. Product OptiX OSN 3800 52TOM board 201(ClientLP1/ClientLP1) 205(ClientLP5/ClientLP5) 203(ClientLP3/ClientLP3) 207(ClientLP7/ClientLP7) OptiX OSN 6800/ OptiX OSN 8800 201(ClientLP1/ClientLP1) 203(ClientLP3/ClientLP3) 205(ClientLP5/ClientLP5) 207(ClientLP7/ClientLP7) 52NS2 board 51(ODU1LP/ODU1LP)-1 51(ODU1LP/ODU1LP)-2 51(ODU1LP/ODU1LP)-3 51(ODU1LP/ODU1LP)-4 51(ODU1LP/ODU1LP)-1 51(ODU1LP/ODU1LP)-2 51(ODU1LP/ODU1LP)-3 51(ODU1LP/ODU1LP)-4
----End
Issue 02 (2011-10-31)
125
4.10 Application Scenario 8: Conversion Between Four OTU1 Services and Eight ODU0 Electrical Signals
This configuration example shows how the TN52TOM board is configured to implement conversion between four channels of OTU1 services and eight channels of ODU0 electrical signals.

Service Requirement
See Figure 4-17. The optical NEs (ONEs) A, B, C, and D form a ring network. All the ONEs function as OADM stations. User1, User2, and User3 communicate with each other through one OTU2 service each. At station A, the TN52TOM board accesses four OTU1 services and then converts them into eight ODU0 services. The eight ODU0 services are then sent to two TN52NS2 boards at station A based on the actual services requirement. Each TN52NS2 board converges the received ODU0 services and other accessed services into one OTU2 service. Figure 4-17 Networking diagram for the TN52TOM board (ODU1_ODU0 mode in noncascading mode) in application scenario 8
User2
WEST B EAST
User3
SLOT 12 SLOT 15
52NS2 52TOM
:OADM
Issue 02 (2011-10-31)
126


This section describes the service signal flow at station A. One OTU2 service is available between station A and station B. Figure 4-18 shows the service signal flow at station A. Figure 4-18 Bidirectional service at station A when the cross-connect board is the XCM or XCH board
52TOM 161(ODU0LP1/ODU0LP1)-1 3(RX1/TX1) 201(ClientLP1/ClientLP1)-1 161(ODU0LP1/ODU0LP1)-1 161(ODU0LP1/ODU0LP1)-2 162(ODU0LP2/ODU0LP2)-1 5(RX3/TX3) 203(ClientLP3/ClientLP3)-1 162(ODU0LP2/ODU0LP2)-1 162(ODU0LP2/ODU0LP2)-2 163(ODU0LP3/ODU0LP3)-1 7(RX5/TX5) 205(ClientLP5/ClientLP5)-1 163(ODU0LP3/ODU0LP3)-1 163(ODU0LP3/ODU0LP3)-2 163(ODU0LP3/ODU0LP3)-2 162(ODU0LP2/ODU0LP2)-2 1(IN/OUT) 163(ODU0LP3/ODU0LP3)-1 51(ODU1LP1/ODU1LP1)-3 161(ODU0LP1/ODU0LP1)-2 162(ODU0LP2/ODU0LP2)-1 51(ODU1LP1/ODU1LP1)-2 161(ODU0LP1/ODU0LP1)-1 51(ODU1LP1/ODU1LP1)-1 52NS2
164(ODU0LP4/ODU0LP4)-1 9(RX7/TX7) 207(ClientLP7/ClientLP7)-1 164(ODU0LP4/ODU0LP4)-1 164(ODU0LP4/ODU0LP4)-2
164(ODU0LP4/ODU0LP4)-1 51(ODU1LP1/ODU1LP1)-4 164(ODU0LP4/ODU0LP4)-2

Prerequisite

Precautions
NOTE
When the cross-connect board is the XCS board, the TN52TOM board does not support ODU1_ODU0 mode (OTU1->ODU1->ODU0) in non-cascading mode.
Issue 02 (2011-10-31)
127

NOTE
A ClientLP port can access only one service that has a rate higher than 1.25 Gbit/s, and this service can be configured on only the first channel of the ClientLP port. The client-side eight pairs of optical ports can access services at a maximum rate of 10 Gbit/s.
NOTE
The client-side optical ports can be selected as required.

Step 1 Set Working Mode of the TN52TOM board: Set Board Working mode to Non-Cascading and then set Port Working Mode of all the ClientLP ports to ODU1_ODU0 mode (OTU1>ODU1->ODU0). For details, see 12.1 Configuring Working Modes. Step 2 Set Service Mode of the client-side port of TN52TOM as OTN Mode. For details, see 12.3 Configuring the Service Mode.
NOTE
Step 3 Configure the Service Type at the WDM Interface of the TN52TOM as OTU1 according to the service planning. For details, see 12.2 Configuring the Service Type. Step 4 Configure the OTU1 cross-connection between the RX/TX and ClientLP ports on the TN52TOM board. 1. Configure an OTU1 cross-connection between the 3(RX1/TX1) port and the 201 (ClientLP1/ClientLP1) port on TN52TOM board. For details, see 12.4.1 Creating CrossConnections.
2. 1.
Repeat Step 4.1 to configure the remaining OTU1 services Configure an ODU0 cross-connection between the 161(ODU0LP1/ODU0LP1) port on TN52TOM board and the 161(ODU0LP1/ODU0LP1) port on TN52NS2 board. For details, see 12.4.1 Creating Cross-Connections.
Step 5 Configure ODU0 cross-connections between the TN52TOM and TN52NS2 boards.
Issue 02 (2011-10-31)
2.
Repeat Step 5.1 to configure ODU0 cross-connections between other TN52TOM and TN52NS2 boards.
----End
4.11 Application Scenario 9: Conversion Between Four OTU1 Optical Signals and Eight ODU0 Electrical Signals (Through Any Re-Encapsulation)
This configuration example shows how the TN52TOM board is configured to implement conversion between four channels OTU1 optical signals and eight channels of ODU0 electrical signals through Any re-encapsulation.

Service Requirement
See Figure 4-19. The optical NEs (ONEs) A, B, C, and D form a ring network. All the ONEs function as OADM stations. User1 and User2 communicate with each other. One bidirectional OTU2 service is available between station A and station B. At station A, the TN52TOM board accesses four OTU1 services and then converts them into eight ODU0 services through Any re-encapsulation. The ODU0 services are then sent to the TN52NS2 board at station A, where they are converted into one OTU2 service.
Issue 02 (2011-10-31)
129
Figure 4-19 Networking diagram for the TN52TOM board (ODU1_ANY_ODU0 reencapsulation mode in non-cascading mode) in application scenario 9
User1 SLOT 15 SLOT 14 SLOT 12 EAST NMS EAST D C WEST WEST 52TOM 52TOM 52NS2
User2
WEST B EAST
SLOT 12 SLOT 15
:OADM

In this example, two TN52TOM boards and a TN52NS2 board must be configured at station A. A TN52TOM board and a TN52NS2 board must be configured at station B.

Issue 02 (2011-10-31)
130

52TOM 237(AnyLP5/AnyLP5)-1 237(AnyLP5/AnyLP5)-1 233(AnyLP1/AnyLP1)-1 3(RX1/TX1) 201(ClientLP1/ClientLP1)-1 233(AnyLP1/AnyLP1)-8 238(AnyLP6/AnyLP6)-8 239(AnyLP7/AnyLP7)-1 239(AnyLP7/AnyLP7)-1 234(AnyLP2/AnyLP2)-1 5(RX3/TX3) 203(ClientLP3/ClientLP3)-1 234(AnyLP2/AnyLP2)-8 240(AnyLP8/AnyLP8)-8 241(AnyLP9/AnyLP9)-1 241(AnyLP9/AnyLP9)-1 235(AnyLP3/AnyLP3)-1 7(RX5/TX5) 205(ClientLP5/ClientLP5)-1 235(AnyLP3/AnyLP3)-8 242(AnyLP10/AnyLP10)-8 243(AnyLP11/AnyLP11)-1 243(AnyLP11/AnyLP11)-1 236(AnyLP4/AnyLP4)-1 9(RX7/TX7) 207(ClientLP7/ClientLP7)-1 236(AnyLP4/AnyLP4)-8 244(AnyLP12/AnyLP12)-8 243(AnyLP11/AnyLP11)-8 244(AnyLP12/AnyLP12)-1 244(AnyLP12/AnyLP12)-1 164(ODU0LP4/ODU0LP4)-2 164(ODU0LP4/ODU0LP4)-1 51(ODU1LP1/ODU1LP1)-4 241(AnyLP9/AnyLP9)-8 242(AnyLP10/AnyLP10)-1 242(AnyLP10/AnyLP10)-1 163(ODU0LP3/ODU0LP3)-2 163(ODU0LP3/ODU0LP3)-1 51(ODU1LP1/ODU1LP1)-3 1(IN/OUT) 239(AnyLP7/AnyLP7)-8 240(AnyLP8/AnyLP8)-1 240(AnyLP8/AnyLP8)-1 162(ODU0LP2/ODU0LP2)-2 162(ODU0LP2/ODU0LP2)-1 51(ODU1LP1/ODU1LP1)-2 237(AnyLP5/AnyLP5)-8 238(AnyLP6/AnyLP6)-1 238(AnyLP6/AnyLP6)-1 161(ODU0LP1/ODU0LP1)-2 161(ODU0LP1/ODU0LP1)-1 51(ODU1LP1/ODU1LP1)-1 52NS2

Prerequisite

Precautions
NOTE
When the cross-connect board is the XCM or XCH board, the TN52TOM board does not support ODU1_ANY_ODU0 re-encapsulation mode (OTU1->ODU1->Any->ODU0) in non-cascading mode.
NOTE
Each optical port supports access of services at a maximum rate of 1.25 Gbit/s. The client-side eight pairs of optical ports can access services at a maximum rate of 10 Gbit/s.
NOTE
When the Any service is mapped into the ODU0 service, the TN52TOM board supports de-encapsulation and then re-encapsulation of only 10 Any services.

Step 1 Set Working Mode of the TN52TOM board: Set Board Working mode to Non-Cascading and then set Port Working Mode of all the ClientLP ports to ODU1_ANY_ODU0 reIssue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 131
encapsulation mode (OTU1->ODU1->Any->ODU0). For details, see 12.1 Configuring Working Modes. Step 2 Set Service Mode of the client-side port of TN52TOM as OTN Mode. For details, see 12.3 Configuring the Service Mode.
NOTE
Step 3 Set Service Type in the WDM Interface window of the TN52TOM board to OTU1. For details, see 12.2 Configuring the Service Type. Step 4 Configure the OTU1 cross-connection between the RX/TX and ClientLP ports on the TN52TOM board. 1. Configure an OTU1 cross-connection between the 3(RX1/TX1) port and the 201 (ClientLP1/ClientLP1) port on TN52TOM board. For details, see 12.4.1 Creating CrossConnections.
2.
Repeat Step 4.1 to configure the remaining OTU1 services.
Step 5 Set Service Type in the WDM Interface window of the TN52TOM board. For details, see 12.2 Configuring the Service Type.
NOTE
When configuring internal cross-connections for Any services on the TN52TOM board. set the service type to the same as the type of services, which are encapsulated into the OTU1 services received on the client side of the TN52TOM board. For example, if FE services are encapsulated into OTU1 services on the upstream board of the TN52TOM board, set the service type to FE when configuring the internal crossconnections for Any services on the TN52TOM board.
Step 6 Configure internal cross-connections of the Any service on the TN52TOM board. 1. Configure an Any cross-connection on the TN52TOM board. For details, see 12.4.1 Creating Cross-Connections.
Issue 02 (2011-10-31)
132
NOTE
Services of the AnyLP1 port can only be configured at the AnyLP5 and AnyLP6 ports. Services of the AnyLP2 port can only be configured at the AnyLP7 and AnyLP8 ports, and so on.
2.
Step 7 Configure ODU0 cross-connections between the TN52TOM and TN52NS2 boards. 1. Configure an ODU0 cross-connection between the 237(AnyLP5/AnyLP5) port on TN52TOM board and the 161(ODU0LP1/ODU0LP1) port on TN52NS2 board. For details, see 12.4.1 Creating Cross-Connections.
2.
----End
4.12 Application Scenario 10: Conversion Between Four OTU1 Optical Signals and Four ODU1 Electrical Signals (Through Any Re-Encapsulation)
This configuration example shows how the TN52TOM board is configured to implement conversion between four channels OTU1 optical signals and four channels of ODU1 electrical signals through Any re-encapsulation.

Service Requirement
See Figure 4-21. The optical NEs (ONEs) A, B, C, and D form a ring network. All the ONEs function as OADM stations. User1 and User2 communicate with each other. One bidirectional OTU2 service is available between station A and station B. At station A, the TN52TOM board accesses four OTU1 services and then converts them into four ODU1 services through Any re-encapsulation. The ODU1 services are then sent to the TN52NS2 board at station A, where they are converted into one OTU2 service. Figure 4-21 Networking diagram for the TN52TOM board (ODU1_ANY_ODU0_ODU1 reencapsulation mode in non-cascading mode) in application scenario 10
User1 SLOT 15 SLOT 14 SLOT 12 EAST NMS EAST D C WEST WEST 52TOM 52TOM 52NS2
User2
WEST B EAST
SLOT 12 SLOT 15
:OADM
Issue 02 (2011-10-31)
134

In this example, two TN52TOM boards and a TN52NS2 board must be configured at station A. A TN52TOM board and a TN52NS2 board must be configured at station B.

This section describes the service signal flow at station A. One OTU2 service is available between station A and station B. Figure 4-22 shows the service signal flow at station A. Figure 4-22 Bidirectional service at station A
52TOM 237(AnyLP5/AnyLP5)-1 237(AnyLP5/AnyLP5)-1 233(AnyLP1/AnyLP1)-1 3(RX1/TX1) 201(ClientLP1/ClientLP1)-1 233(AnyLP1/AnyLP1)-8 238(AnyLP6/AnyLP6)-8 239(AnyLP7/AnyLP7)-1 239(AnyLP7/AnyLP7)-1 234(AnyLP2/AnyLP2)-1 5(RX3/TX3) 203(ClientLP3/ClientLP3)-1 234(AnyLP2/AnyLP2)-8 240(AnyLP8/AnyLP8)-8 241(AnyLP9/AnyLP9)-1 241(AnyLP9/AnyLP9)-1 235(AnyLP3/AnyLP3)-1 7(RX5/TX5) 205(ClientLP5/ClientLP5)-1 235(AnyLP3/AnyLP3)-8 242(AnyLP10/AnyLP10)-8 243(AnyLP11/AnyLP11)-1 243(AnyLP11/AnyLP11)-1 236(AnyLP4/AnyLP4)-1 9(RX7/TX7) 207(ClientLP7/ClientLP7)-1 236(AnyLP4/AnyLP4)-8 244(AnyLP12/AnyLP12)-8 243(AnyLP11/AnyLP11)-8 244(AnyLP12/AnyLP12)-1 244(AnyLP12/AnyLP12)-1 164(ODU0LP4/ODU0LP4)-2 164(ODU0LP4/ODU0LP4)-1 164(ODU0LP4/ODU0LP4)-1 51(ODU1LP1/ODU1LP1)-4 241(AnyLP9/AnyLP9)-8 242(AnyLP10/AnyLP10)-1 242(AnyLP10/AnyLP10)-1 163(ODU0LP3/ODU0LP3)-2 163(ODU0LP3/ODU0LP3)-1 163(ODU0LP3/ODU0LP3)-1 51(ODU1LP1/ODU1LP1)-3 1(IN/OUT) 239(AnyLP7/AnyLP7)-8 240(AnyLP8/AnyLP8)-1 240(AnyLP8/AnyLP8)-1 162(ODU0LP2/ODU0LP2)-2 162(ODU0LP2/ODU0LP2)-1 162(ODU0LP2/ODU0LP2)-1 51(ODU1LP1/ODU1LP1)-2 237(AnyLP5/AnyLP5)-8 238(AnyLP6/AnyLP6)-1 238(AnyLP6/AnyLP6)-1 161(ODU0LP1/ODU0LP1)-2 161(ODU0LP1/ODU0LP1)-1 161(ODU0LP1/ODU0LP1)-1 51(ODU1LP1/ODU1LP1)-1 52NS2

Prerequisite

Precautions
NOTE
When the cross-connect board is the XCM or XCH board, the TN52TOM board does not support ODU1_ANY_ODU0_ODU1 re-encapsulation mode (OTU1->ODU1->Any->ODU0->ODU1) in noncascading mode.
Issue 02 (2011-10-31)
135

NOTE
A ClientLP port can access only one service that has a rate higher than 1.25 Gbit/s, and this service can be configured on only the first channel of the ClientLP port.
NOTE
The client-side eight pairs of optical ports can access services at a maximum rate of 10 Gbit/s.
NOTE
When the Any service is mapped into the ODU0 service, the TN52TOM board supports de-encapsulation and then re-encapsulation of only 10 Any services.

Step 1 Set Working Mode of the TN52TOM board: Set Board Working mode to Non-Cascading and then set Port Working Mode of all the ClientLP ports to ODU1_ANY_ODU0_ODU1 reencapsulation mode (OTU1->ODU1->Any->ODU0->ODU1). Step 2 Set Service Mode of the client-side port of TN52TOM as OTN Mode. For details, see 12.3 Configuring the Service Mode.
NOTE
Step 3 Set Service Type in the WDM Interface window of the TN52TOM board to OTU1. For details, see 12.2 Configuring the Service Type. Step 4 Configure the OTU1 cross-connection between the RX/TX and ClientLP ports on the TN52TOM board. 1. Configure an OTU1 cross-connection between the 3(RX1/TX1) port and the 201 (ClientLP1/ClientLP1) port on TN52TOM board. For details, see 12.4.1 Creating CrossConnections.
2.

NOTE
Step 6 Configure internal cross-connections of the Any service on the TN52TOM board. 1. Configure an Any cross-connection on the TN52TOM board. For details, see 12.4.1 Creating Cross-Connections.
NOTE
2. 1.
Repeat Step 6.1 to configure the remaining Any services. Configure an ODU1 cross-connection between the 161(ODU0LP1/ODU0LP1) port on TN52TOM board and the 51(ODU1LP/ODU1LP) port on TN52NS2 board. For details, see 12.4.1 Creating Cross-Connections.
Step 7 Configure ODU1 cross-connections between the TN52TOM and TN52NS2 boards.
Issue 02 (2011-10-31)
137
2.
----End
4.13 Application Scenario 11: Conversion Between Two OTU1 Optical Signals and Two OTU1 Optical Signals (Through Any Re-Encapsulation)
This configuration example shows how the TN52TOM board is configured to implement conversion between two channels OTU1 optical signals and two channels OTU1 optical signals through Any re-encapsulation.

Service Requirement
See Figure 4-23. The optical NEs (ONEs) A, B, C, and D form a ring network. All the ONEs function as OADM stations. User1 and User2 communicate with each other. Two bidirectional OTU1 services are available between station A and station B. At station A, the TN52TOM board accesses two OTU1 services and then converts them into two OTU1 services through Any re-encapsulation.
Issue 02 (2011-10-31)
138
Figure 4-23 Networking diagram for the TN52TOM board (ODU1_ANY_ODU0_ODU1 reencapsulation tributary-line mode in non-cascading mode) in application scenario 11
User1
52TOM
User2
WEST B EAST
A D C
EAST
WEST
SLOT 15
52TOM WEST EAST
:OADM

In this example, a TN52TOM board must be configured at station A and station B.

This section describes the service signal flow at station A. Two OTU1 services are available between station A and station B. Figure 4-24 shows the service signal flow at station A. Figure 4-24 Bidirectional service at station A
52TOM 237(AnyLP5/AnyLP5)-1 237(AnyLP5/AnyLP5)-1 233(AnyLP1/AnyLP1)-1 3(RX1/TX1) 201(ClientLP1/ClientLP1)-1 233(AnyLP1/AnyLP1)-8 238(AnyLP6/AnyLP6)-8 239(AnyLP7/AnyLP7)-1 239(AnyLP7/AnyLP7)-1 234(AnyLP2/AnyLP2)-1 5(RX3/TX3) 203(ClientLP3/ClientLP3)-1 234(AnyLP2/AnyLP2)-8 240(AnyLP8/AnyLP8)-8 239(AnyLP7/AnyLP7)-8 240(AnyLP8/AnyLP8)-1 240(AnyLP8/AnyLP8)-1 162(ODU0LP2/ODU0LP2)-2 162(ODU0LP2/ODU0LP2)-1 9(RX7/TX7) 162(ODU0LP2/ODU0LP2)-1 52(ODU1LP2/ODU1LP2)-1 10(RX8/TX8) 237(AnyLP5/AnyLP5)-8 238(AnyLP6/AnyLP6)-1 238(AnyLP6/AnyLP6)-1 161(ODU0LP1/ODU0LP1)-2 161(ODU0LP1/ODU0LP1)-1 7(RX5/TX5) 161(ODU0LP1/ODU0LP1)-1 51(ODU1LP1/ODU1LP1)-1 8(RX6/TX6)
Issue 02 (2011-10-31)
139

Prerequisite

Precautions
NOTE
The client-side optical ports only can access two OTU1 services, and the OTU1 service can be configured on only the first channel of the ClientLP port. When the Any service is mapped into the ODU0 service, the TN52TOM board supports de-encapsulation and then re-encapsulation of only 10 Any services.
NOTE

Step 1 Set Working Mode of the TN52TOM board: Set Board Working mode to Non-Cascading and then set Port Working Mode of ClientLP1 and ClientLP3 to ODU1_ANY_ODU0_ODU1 re-encapsulation tributary-line mode (OTU1->ODU1->Any->ODU0->ODU1).
NOTE
l The ClientLP5 and ClientLP7 ports do not support the Non-Cascading ODU1_ANY_ODU0_ODU1 reencapsulation tributary-line mode (OTU1->ODU1->Any->ODU0->ODU1) mode l Before the working mode of the ClientLP1 and ClientLP3 are set to ODU1_ANY_ODU0_ODU1 reencapsulation tributary-line mode (OTU1->ODU1->Any->ODU0->ODU1), the working modes of the ClientLP5 and ClientLP7 ports must be set to NONE Mode (Not for Port).
Step 2 Set the type of ports 9 (RX7/TX7) and 10 (RX8/TX8) to Line Side Color Optical Port. For details, see 11.1 Modifying Port.
NOTE
When the TN52TOM board is used as a tributary & line board, a corresponding WDM-side optical module must be inserted in the WDM-side optical port, and the Type of this optical port must be changed to Line Side Color Optical Port.
Step 3 Set Service Mode of the client-side port of TN52TOM as OTN Mode. For details, see 12.3 Configuring the Service Mode.
NOTE
Step 4 Set Service Type in the WDM Interface window of the TN52TOM board to OTU1. For details, see 12.2 Configuring the Service Type.
Step 5 Configure OTU1 cross-connections between the RX/TX and ClientLP ports on the TN52TOM board. 1. Configure an OTU1 cross-connection between the 3(RX1/TX1) port and the 201 (ClientLP1/ClientLP1) port on TN52TOM board. For details, see 12.4.1 Creating CrossConnections.
2.
NOTE
Step 7 Configure internal cross-connections for Any services on the TN52TOM board. 1. Configure an Any cross-connection on the TN52TOM board. For details, see 12.4.1 Creating Cross-Connections.
Issue 02 (2011-10-31)
141
NOTE
2.
Step 8 Configure OTU1 cross-connections between the ODU1LP and RX/TX ports on the TN52TOM board. 1. Configure an OTU1 cross-connection between the 51(ODU1LP1/ODU1LP1) and 9(RX7/ TX7) ports on the TN52TOM board. For details, see 12.4.1 Creating CrossConnections.
NOTE
Issue 02 (2011-10-31)
142
2.
----End
4.14 Application Scenario 12: Regeneration of Four OTU1 Optical Signals

This configuration example shows how the TN52TOM board is configured to implement electrical regeneration of four OTU1 optical signals. If you set only two of the 7(RX5/TX5), 8 (RX6/TX6), 9(RX7/TX7), and 10(RX8/TX8) optical ports as WDM-side optical ports, the TN52TOM board can implement conversion between six Any services and two channels of OTU1 optical signals. If the 7(RX5/TX5) and 8(RX6/TX6) optical ports are configured as one protection group and the 9(RX7/TX7) and 10(RX8/TX8) optical ports are configured are another protection group, the TN52TOM board can implement conversion between four Any services and two channels of OTU1 optical signals and implement the function of dual feeding and selective receiving at the WDM side.

Service Requirement
See Figure 4-25. The optical NEs (ONEs) A, B, C, and D form a ring network. All the ONEs function as OADM stations. User1 and User2 communicate with each other. Four bidirectional OTU1 services are available between station A and station B. At station A, the TN52TOM board accesses four OTU1 services, decapsulates them into four ODU1 electrical signals, and then converts them into four OTU1 services. In this manner, the electrical regeneration is implemented.
Issue 02 (2011-10-31)
143
Figure 4-25 Networking diagram for the TN52TOM board (ODU1 tributary-line mode in noncascading mode) in application scenario 12
User1
52TOM
User2
WEST B EAST
A D C
EAST
WEST
SLOT 15
52TOM WEST EAST
:OADM


This section describes the service signal flow at station A. Four OTU1 services are available between station A and station B. Figure 4-26 shows the service signal flow at station A. Figure 4-26 Bidirectional service at station A
TOM 3(RX1/TX1) 4(RX2/TX2) 5(RX3/TX3) 6(RX4/TX4) 201(ClientLP1/ClientLP1)-1 203(ClientLP3/ClientLP3)-1 205(ClientLP5/ClientLP5)-1 207(ClientLP7/ClientLP7)-1 51(ODU1LP1/ODU1LP1)-1 52(ODU1LP2/ODU1LP2)-1 53(ODU1LP3/ODU1LP3)-1 54(ODU1LP4/ODU1LP4)-1 7(RX5/TX5) 8(RX6/TX6) 9(RX7/TX7) 10(RX8/TX8)
Issue 02 (2011-10-31)
144

This section considers station A at which the TN52TOM board accesses four OTU1 services as an example to describe the configuration process of the TN52TOM board.
Prerequisite

Precautions
NOTE

Step 1 Set Working Mode of the TN52TOM board: Set Board Working mode to Non-Cascading and then set Port Working Mode of all the ClientLP ports to ODU1 tributary-line mode (OTU1/Any->ODU1->OTU1). For details, see 12.1 Configuring Working Modes. Step 2 Set the type of ports 7 (RX5/TX5), 8 (RX6/TX6), 9 (RX7/TX7) and 10 (RX8/TX8) to Line Side Color Optical Port. For details, see 11.1 Modifying Port.
NOTE
When the TN52TOM board is used as a tributary-line board, a corresponding WDM-side optical module must be inserted in the WDM-side optical port, and the Type of this optical port must be changed to Line Side Color Optical Port.
Step 3 Set Service Mode of the TN52TOM board to OTN Mode. For details, see 12.3 Configuring the Service Mode.
NOTE
Step 4 Configure Service Type at the WDM-side port of the TN52TOM board as OTU1 according to the service planning. For details, see 12.2 Configuring the Service Type. Step 5 Configure the cross-connections from the RX/TX ports to the ClientLP ports on the TN52TOM board for the OTU1 services of the board. 1. Configure the cross-connections from the RX/TX ports to the ClientLP ports for the OTU1 services that are input to the TN52TOM board. For details, see 12.4.1 Creating CrossConnections.
Issue 02 (2011-10-31)
145
NOTE
2.
Repeat Step 5.1 to configure cross-connections for the other OTU1 services.
Step 6 Configure the OTU1 cross-connections between the ODU1LP and RX/TX port on the TN52TOM board. 1. Configure an OTU1 cross-connection between the 51(ODU1LP1/ODU1LP1) and the 7 (RX5/TX5) on the TN52TOM board. For details, see 12.4.1 Creating CrossConnections.
NOTE
Issue 02 (2011-10-31)
146
2.
----End
Issue 02 (2011-10-31)
147
Configuring the THA/TOA Board (Manually by Station)
About This Chapter

The THA/TOA board can be configured with different port working modes and is applicable to various scenarios accordingly. You need to manually configure the board by station on the NMS for the application scenarios. The THA and TOA boards are almost the same except for the number of optical ports. The THA board provides 16 optical ports while the TOA board provides 8 optical ports. This chapter uses the TOA board as an example for illustration. The descriptions and configuration of the THA board are similar to those of the TOA board. The THA board differs from the TOA board in the following aspects: l The first eight client-side ports on the THA board can be configured with cross-connections only to the first eight LP ports; the last eight client-side ports on the THA board can be configured with cross-connections only to the last eight LP ports. The THA board cannot receive SDI and HD-SDI services on the client side. The THA board does not support ODUflex non-convergence mode (Any->ODUflex). Therefore, all configurations related to this port working mode are applicable only to the TOA board.
l l
5.1 Overview of the Working Mode Each port on the TOA board can work in different modes so that services can be processed on different paths. 5.2 Configuration Procedures Six port working modes are available for the TOA board on the NMS. The port for the None (not for ports) mode does not require configurations. The other five modes require configurations. 5.3 Application Scenario 1: ODU0 Non-Convergence Mode When using the ODU0 non-convergence mode, the TOA board performs conversion between eight channels of optical signals with arbitrary bit rates (125 Mbit/s to 1.25 Gbit/s) and eight channels of ODU0 electrical signals. 5.4 Application Scenario 2: ODU1 Non-Convergence Mode
When using the ODU1 non-convergence mode, the TOA board performs conversion between eight channels of optical signals with arbitrary bit rates (1.49 Gbit/s to 2.67 Gbit/s) and eight channels of ODU1 electrical signals. 5.5 Application Scenario 3: ODU1 Convergence Mode When using the ODU1 convergence mode, the TOA board performs conversion between eight channels of optical signals with arbitrary bit rates (125 Mbit/s to 2.5 Gbit/s) and eight channels of ODU1 electrical signals. 5.6 Application Scenario 4: ODU1_ODU0 Mode In ODU1_ODU0 mode, the TOA board performs conversion between eight channels of OTU1 optical signals and 16 channels of ODU0 electrical signals. 5.7 Application Scenario 5: ODUflex Non-Convergence Mode When using the ODUflex non-convergence mode, the TOA board performs conversion between four channels of FC400 optical signals and four channels of ODUflex electrical signals or conversion between five channels of 3G-SDI optical signals and five channels of ODUflex electrical signals.
Issue 02 (2011-10-31)
149
5.1 Overview of the Working Mode

Each port on the TOA board can work in different modes so that services can be processed on different paths. The TOA board supports six port working modes listed in Table 5-1. You can set the port working modes on the NMS. Table 5-1 Port working modes on the TOA board Port Working Mode ODU0 non-convergence mode ODU1 non-convergence mode ODU1 convergence mode ODU1_ODU0 mode ODUflex non-convergence mode None (not for ports) Signal Flow Any->ODU0 OTU1/Any->ODU1 n x Any->ODU1 (1 n 8) OTU1->ODU1->ODU0 Any->ODUflex -
NOTE
None (not for ports): indicates that the resources at the port in this mode are not used and are released to other ports.
5.2 Configuration Procedures

Six port working modes are available for the TOA board on the NMS. The port for the None (not for ports) mode does not require configurations. The other five modes require configurations.
General Configuration Procedure

Figure 5-1 shows the general configuration procedure for the port working modes on the TOA board.
Issue 02 (2011-10-31)
150
Figure 5-1 General configuration procedure

Configure the port working mode
Configure the port type
Configure the timeslot configuration mode for the line board
Configure the service mode
Configure crossconnections from the client side to LP ports Mandatory Optional
Configure interboard crossconnections
In the flowchart, the mandatory actions are required for each port working mode and optional actions vary according to port working modes. The optional actions must be configured in the following scenarios: l l Configure the port type: Port Type must be set to Client Side Color Optical Port when colored optical signals are received on the client side. Configure the timeslot configuration mode: ODU Timeslot Configuration Mode must be set for the line board that is interconnected with the TOA board. When the port working mode of the TOA board is ODUflex, ODU Timeslot Configuration Mode must be set to Assign random for the line board that is interconnected with the TOA board. In other port working modes, set ODU Timeslot Configuration Mode for the line board to the same as the value that is set on the interconnected line board. The recommended value is Assign random. l l Configure the service mode: When Service Type is set to OTU1, Service Mode must be set to OTN Mode. Configure cross-connections from the client side to LP ports: This action is required only for the ODU0 non-convergence mode and ODU1 convergence mode.
The following describes the configuration procedure and involved parameter settings for each mode.
l l l l l
Table 5-2 describes the configuration procedure for the ODU0 non-convergence mode. Table 5-3 describes the configuration procedure for the ODU1 non-convergence mode. Table 5-4 describes the configuration procedure for the ODU1 convergence mode. Table 5-5 describes the configuration procedure for the ODU1_ODU0 mode. Table 5-6 describes the configuration procedure for the ODUflex non-convergence mode.
Configuration Procedure for the ODU0 Non-Convergence Mode

Table 5-2 Configuration procedure No. 1 Action Configure the port working mode. Description Optional l Parameter settings: The default value of Port Working Mode is ODU0 non-convergence mode (Any>ODU0). If the default value is used, skip this step. l Operation description: For details about the configuration procedure, see Configuring the Working Mode. 2 Configure the port type. Optional l Parameter settings: The default value of Port Type is Client Side Grey Optical Port. If colored optical signals are received on the client side, set Port Type to Client Side Color Optical Port. l Operation description: For details about the configuration procedure, see Modifying Port. 3 Configure the service type. Mandatory l Parameter settings: The available values for Service Type are FE, FDDI, GE(GFP-T), GE(TTT-AGMP), STM-1, STM-4, OC-3, OC-12, FC100, FICON, DVBASI, ESCON, and SDI. l Operation description: Configure the service type based on the service plan. For details about the configuration procedure, see Configuring the Service Type.
NOTE Two channels (channel 1 and channel 2) are available at each LP port. Set the service type for only one of the two channels. When the TOA board is interconnected with a TN52TOM board, the channel where you set the service type must be the same as the channel where the service type is set on the TN52TOM board. When the TOA board is interconnected with another board, set the service type for channel 1.
Issue 02 (2011-10-31)
152
No. 4
Action Configure crossconnections from the client side to LP ports on the TOA board.
Description Mandatory l Parameter settings: Level and Service Type: If you set Service Type to GE(GFP-T) or GE (TTT-AGMP) in step 3, retain the default value (GE) for Level. If you set Service Type to a value other than GE in step 3, set Level to Any and then set Service Type to the same value that you set in step 3. Direction: Set it to Bidirectional. Source Slot/Sink Slot: Set the two parameters to the ID of the slot where the TOA board is housed. Source Optical Port: Set it to a port in the range of 3 (RX1/TX1) to 10(RX8/TX8). Source Optical Channel: Set it to 1. Sink Optical Port: Set it to a port in the range of 201 (ClientLP1/ClientLP1) to 208(ClientLP8/ClientLP8). Ensure that the client-side port matches an LP port. That is, if you set the source optical port to RXi/TXi, set the sink optical port to ClientLPi. Sink Optical Channel: 1 or 2. Set it to the channel for which you configure the service type in step 3. l Operation description: Configure cross-connections from the client side to each LP port. For details about the configuration procedure, see Creating CrossConnections.
NOTE Set Port Working Mode to ODU0 non-convergence mode (Any>ODU0) for each sink optical port.
Configure inter-board cross-connections.
Mandatory l Parameter settings: See Table 5-7. l Operation description: Configure cross-connections from each LP port on the TOA board to other boards. For details about the configuration procedure, see Creating CrossConnections.
Issue 02 (2011-10-31)
153

Table 5-3 Configuration procedure No. 1 Action Configure the port working mode. Description Mandatory l Parameter settings: Set Port Working Mode to ODU1 non-convergence mode (OTU1/Any->ODU1). l Operation description: For details about the configuration procedure, see Configuring the Working Mode. 2 Configure the port type. Optional l Parameter settings: The default value of Port Type is Client Side Grey Optical Port. If colored optical signals are received on the client side, set Port Type to Client Side Color Optical Port. l Operation description: For details about the configuration procedure, see Modifying Port. 3 Configure the service type. Mandatory l Parameter settings: The available values for Service Type are HD-SDI, STM-16, OC-48, FC200, FICON Express, and OTU1. The total received service bandwidth cannot exceed 20 Gbit/s. l Operation description: Configure the service type based on the service plan. For details about the configuration procedure, see Configuring the Service Type. 4 Configure the service mode. Optional l Parameter settings: The default value of Service Mode is Client Mode. When you set Service Type to OTU1, set Service Mode to OTN Mode. l Operation description: For details about the configuration procedure, see Configuring the Service Mode. 5 Configure inter-board cross-connections. Mandatory l Parameter settings: See Table 5-7. l Operation description: Configure cross-connections from each LP port on the TOA board to other boards. For details about the configuration procedure, see Creating CrossConnections.
Issue 02 (2011-10-31)
154
Configuration Procedure for the ODU1 Convergence Mode

Table 5-4 Configuration procedure No. 1 Action Configure the port working mode. Description Mandatory l Parameter settings: Set Port Working Mode to ODU1 convergence mode (n*Any->ODU1). l Operation description: For details about the configuration procedure, see Configuring the Working Mode. 2 Configure the port type. Optional l Parameter settings: The default value of Port Type is Client Side Grey Optical Port. If colored optical signals are received on the client side, set Port Type to Client Side Color Optical Port. l Operation description: For details about the configuration procedure, see Modifying Port. 3 Configure the service type. Mandatory l Parameter settings: The available values for Service Type are ANY, FE, FDDI, GE(GFP-T), FC100, FC200, DVB-ASI, ESCON, STM-1, STM-4, OC-3, OC-12, SDI, HD-SDI, FICON, and FICON Express. l Operation description: Configure the service type based on the service plan. For details about the configuration procedure, see Configuring the Service Type.
NOTE l Only channel 1, for example, 201(ClientLP1/ClientLP1)-1, in each group of ClientLP ports can receive services with rates higher than 1.25 Gbit/s. l The total rate of services received by each group of ClientLP ports, for example, 201(ClientLP1/ClientLP1)-1 to 201 (ClientLP1/ClientLP1)-8, cannot exceed 2.5 Gbit/s. l The total rate of services received by all ClientLP ports from 201 (ClientLP1/ClientLP1)-1 to 208(ClientLP1/ClientLP1)-8, cannot exceed 20 Gbit/s.
Issue 02 (2011-10-31)
155
No. 4
Action Configure crossconnections from the client side to LP ports on the TOA board.
Description Mandatory l Parameter settings: Level and Service Type: If you set Service Type to GE(GFP-T) in step 3, retain the default value (GE) for Level. If you set Service Type to a value other than GE in step 3, set Level to Any and then set Service Type to the same value that you set in step 3. Direction: Set it to Bidirectional. Source Slot/Sink Slot: Set the two parameters to the ID of the slot where the TOA board is housed. Source Optical Port: Set it to a port in the range of 3 (RX1/TX1) to 10(RX8/TX8). Source Optical Channel: Set it to 1. Sink Optical Port: Set it to a port in the range of 201 (ClientLP1/ClientLP1) to 208(ClientLP8/ClientLP8). There is no mapping between client-side ports and LP ports. For example, if you set the source optical port to 3(RX1/TX1), you can set the sink optical port to any of the ports from 201(ClientLP1/ClientLP1) to 208(ClientLP8/ClientLP8). Sink Optical Channel: Set it to a value in the range of 1 to 8, which is the ID of the channel for which you configure the service type in step 3. l Operation description: Configure cross-connections from the client side to each LP port. For details about the configuration procedure, see Creating CrossConnections.
NOTE Set Port Working Mode to ODU1 convergence mode (n*Any>ODU1) for each sink optical port.
Issue 02 (2011-10-31)
156
Configuration Procedure for the ODU1_ODU0 Mode

Table 5-5 Configuration procedure No. 1 Action Configure the port working mode. Description Mandatory l Parameter settings: Set Port Working Mode to ODU1_ODU0 mode (OTU1->ODU1->ODU0). l Operation description: For details about the configuration procedure, see Configuring the Working Mode. 2 Configure the port type. Optional l Parameter settings: The default value of Port Type is Client Side Grey Optical Port. If colored optical signals are received on the client side, set Port Type to Client Side Color Optical Port. l Operation description: For details about the configuration procedure, see Modifying Port. 3 Configure the service type. Mandatory l Parameter settings: Set Service Type to OTU1. l Operation description: For details about the configuration procedure, see Configuring the Service Type. 4 Configure the service mode. Mandatory l Parameter settings: Set Service Mode to OTN Mode. l Operation description: For details about the configuration procedure, see Configuring the Service Mode. 5 Configure inter-board cross-connections. Mandatory l Parameter settings: See Table 5-7. l Operation description: Configure cross-connections from each ODU0LP port on the TOA board to other boards. For details about the configuration procedure, see Creating Cross-Connections.
Configuration Procedure for the ODUflex Non-Convergence Mode

Table 5-6 Configuration procedure No. 1 Action Configure the port working mode. Description Mandatory l Parameter settings: Set Port Working Mode to ODUflex non-convergence mode (Any->ODUflex). l Operation description: For details about the configuration procedure, see Configuring the Working Mode.
No. 2
Action Configure the port type.
Description Optional l Parameter settings: The default value of Port Type is Client Side Grey Optical Port. If colored optical signals are received on the client side, set Port Type to Client Side Color Optical Port. l Operation description: For details about the configuration procedure, see Modifying Port.
Configure the timeslot configuration mode for the line board that is interconnected with the TOA board.
Mandatory l Parameter settings: The default value of ODU Timeslot Configuration Mode is Assign random. If the default value is used, skip this step. l Operation description: In the NE Explorer, select the line board that is interconnected with the TOA board and choose Configuration > WDM Interface > Advanced Attributes from the Function Tree. In the displayed window, set ODU Timeslot Configuration Mode to Assign random for the required ports. Mandatory l Parameter settings: The available values for Service Type are 3G-SDI and FC400. l Operation description: Configure the service type based on the service plan. For details about the configuration procedure, see Configuring the Service Type.
Table 5-7 Parameters for configuring inter-board cross-connections Param eter ODU0 NonConvergence Mode ODU0 ODU1 NonConvergen ce Mode ODU1 ODU1 Convergence Mode ODU1 ODU1_OD U0 Mode ODUflex NonConvergen ce Mode ODUflex
Level
ODU0
Issue 02 (2011-10-31)
158
Param eter
ODU0 NonConvergence Mode -
ODU1 NonConvergen ce Mode -
ODU1 Convergence Mode -
ODU1_OD U0 Mode
ODUflex NonConvergen ce Mode Custom, PACKET, FC400, FC800, 3GSDI, InfiniBand 2.5G, or CPRI4
NOTE For the V100R006C 01 version, only support FC400, FC800, and 3GSDI.
Service Type
Directi on Source Slot
Bidirectional ID of the slot where the TOA board is housed 201 (ClientLP1/ ClientLP1) to 208 (ClientLP8/ ClientLP8) 1
Bidirectional ID of the slot where the TOA board is housed 161 (ODU0LP1/ ODU0LP1) to 168 (ODU0LP8/ ODU0LP8) 1 or 2
Source Optical Port
Source Optical Channe l Sink Slot
ID of the slot where the interconnected board is houseda Example: 161 (ODU0LP1/ ODU0LP1)
ID of the slot where the interconnecte d board is houseda Example: 51 (ODU1LP1/ ODU1LP1)
ID of the slot where the interconnected board is houseda Example: 51 (ODU1LP1/ ODU1LP1)
ID of the slot where the interconnecte d board is houseda Example: 161 (ODU0LP1/ ODU0LP1)
TN53NQ2, TN53ND2, TN53NS2
Sink Optical Port
1(IN1/ OUT1) to 2 (IN2/OUT2)
Issue 02 (2011-10-31)
159
Param eter
ODU0 NonConvergence Mode 1 or 2
ODU1 NonConvergen ce Mode 1 to 4
ODU1 Convergence Mode 1 to 4
ODU1_OD U0 Mode
ODUflex NonConvergen ce Mode OCH:1ODU2:1ODUflex:1 to OCH:1ODU2:1ODUflex:2
Sink Optical Channe l
1 or 2
Issue 02 (2011-10-31)
160
Param eter
ODU1_OD U0 Mode
ODUflex NonConvergen ce Mode l The value is 4 when the service type is FC400. l The value is 7 when the service type is FC800. l The value is 3 when the service type is 3GSDI. l The value is 3 when the service type is InfiniBan d 2.5G. l The value is 3 when the service type is CPRI4. l The value needs to be set to 1 to 8 based on the actual service when the service type is Custom or PACKET .
Occupi ed ODUT Uk Slot Count
Issue 02 (2011-10-31)
161
Param eter
ODU1_OD U0 Mode
ODUflex NonConvergen ce Mode The parameter value is automatically displayed according to the value of Occupied ODUTUk Slot Count.
Service Rate (bit/s)
l There is no mapping between source optical ports and sink optical ports. For example, if you set the source optical port to 201(ClientLP1/ClientLP1), you can set the sink optical port to 161(ODU0LP1/ODU0LP1) or any other ODU0LP port on the board in the sink slot. l a: The interconnected board can be TN52ND2, TN52NQ2, TN54NQ2, TN52NS2, TN53ND2, TN53NQ2, TN53NS2, TN52NS3, TN54NS3, TN54ENQ2, TN54NPO2, or TN55NPO2.
NOTE
To better understand the service signal flow and ports required for configuring cross-connections, see the section "Board Service Configuration" for each board in the Hardware Description, where detailed port models and working modes are provided.
5.3 Application Scenario 1: ODU0 Non-Convergence Mode

When using the ODU0 non-convergence mode, the TOA board performs conversion between eight channels of optical signals with arbitrary bit rates (125 Mbit/s to 1.25 Gbit/s) and eight channels of ODU0 electrical signals.
5.3.1 Networking Diagram

This section describes the networking diagram of TOA board in ODU0 non-convergence mode.
Service Requirement
As shown in Figure 5-2, optical NEs A, B, C and D form a ring network, and all the NEs function as OADM stations. The service requirements are as follows: l l l User1 and User2 communicate with each other. One bidirectional OTU2 service is available between NE A and NE B. At NE A, the TOA board receives eight Any services (125 Mbit/s to 1.25 Gbit/s) and converts them into eight ODU0 services. The TOA board then transmits the eight ODU0
Issue 02 (2011-10-31)
services to the TN52NQ2 board, where the ODU0 services are converged into one OTU2 service. Figure 5-2 Networking diagram for the TOA board (ODU0 Non-Convergence Mode)
User 1 SLOT 12 SLOT 15 East NMS East D C East SLOT 12 SLOT 15 TN52NQ2 TN54TOA West East West West
TN52NQ2 TN54TOA
User 2
West B
:OADM

In this example, a TOA board and a TN52NQ2 board should be configured on both station A and station B.

This section describes the service signal flow of TOA board in ODU0 non-convergence mode. One OTU2 service is available between station A and station B. Figure 5-3 shows the service signal flow on station A. Figure 5-3 Bidirectional service on station A
TN54TOA 3(RX1/TX1) 4(RX2/TX2) 5(RX3/TX3) 6(RX4/TX4) 7(RX5/TX5) 8(RX6/TX6) 9(RX7/TX7) 10(RX8/TX8) 201(ClientLP1/ClientLP1)-1 201(ClientLP1/ClientLP1)-2 202(ClientLP2/ClientLP2)-1 202(ClientLP2/ClientLP2)-2 203(ClientLP3/ClientLP3)-1 203(ClientLP3/ClientLP3)-2 204(ClientLP4/ClientLP4)-1 204(ClientLP4/ClientLP4)-2 205(ClientLP5/ClientLP5)-1 205(ClientLP5/ClientLP5)-2 206(ClientLP6/ClientLP6)-1 206(ClientLP6/ClientLP6)-2 207(ClientLP7/ClientLP7)-1 207(ClientLP7/ClientLP7)-2 208(ClientLP8/ClientLP8)-1 208(ClientLP8/ClientLP8)-2 161(ODU0LP1/ODU0LP1)-1 161(ODU0LP1/ODU0LP1)-2 162(ODU0LP2/ODU0LP2)-1 162(ODU0LP2/ODU0LP2)-2 51(ODU1LP1/ODU1LP1)-1 71(ODU2LP1/ODU2LP1)-1 51(ODU1LP1/ODU1LP1)-2 72(ODU2LP2/ODU2LP2)-1 2(IN2/OUT2) 1(IN1/OUT1) TN52NQ2
175(ODU0LP15/ODU0LP15)-1 175(ODU0LP15/ODU0LP15)-2 176(ODU0LP16/ODU0LP16)-1 176(ODU0LP16/ODU0LP16)-2
3(IN3/OUT3)
4(IN4/OUT4)
Issue 02 (2011-10-31)
163

This section describes how to configure the TOA board in ODU0 non-convergence mode.
Prerequisite
Tools, Equipment and Materials


Step 1 Set the Port Working Mode to ODU0 non-convergence mode (Any->ODU0) for the TOA board. For details, see Configuring the Working Mode. Step 2 Configure the Service Type at the WDM Interface of the TOA according to the service planning. For details, see 12.2 Configuring the Service Type. Step 3 Configure the cross-connections from the RX/TX ports to the ClientLP ports on the TOA board for the Any services that are input to the board.
NOTE
In this scenario, If you set the Level to ANY, the Service Type must be the same as the Service Type at the WDM interface of the TOA board.
Step 4 Configure electrical cross-connections for the ODU0 services between the TOA and TN52NQ2 boards. 1. 2. Configure a cross-connection for one ODU0 service between the TOA and TN52NQ2 boards. For details, see 12.4.1 Creating Cross-Connections. Repeat 4.a to configure a cross-connection for the other ODU0 services between the TOA and TN52NQ2 boards.
----End
5.4 Application Scenario 2: ODU1 Non-Convergence Mode

When using the ODU1 non-convergence mode, the TOA board performs conversion between eight channels of optical signals with arbitrary bit rates (1.49 Gbit/s to 2.67 Gbit/s) and eight channels of ODU1 electrical signals.

This section describes the networking diagram of TOA board in ODU1 non-convergence mode.
Service Requirement
As shown in Figure 5-4, optical NEs A, B, C and D form a ring network, and all the NEs function as OADM stations. The service requirements are as follows:
l l l
User1 and User2 communicate with each other. One bidirectional OTU2 service is available between NE A and NE B. At NE A, the TOA board receives eight Any services (1.49 Gbit/s to 2.67 Gbit/s) and converts them into eight channels of ODU1 services. The TOA board then transmits the eight ODU1 services to the TN52NQ2 board, where the ODU1 services are converged into two OTU2 services.
Figure 5-4 Networking diagram for the TOA board (ODU1 Non-Convergence Mode)
TN52NQ2 TN54TOA
User 2
West B
:OADM


This section describes the service signal flow of TOA board in ODU1 non-convergence mode. One OTU2 service is available between station A and station B. Figure 5-5 shows the service signal flow on station A.
Issue 02 (2011-10-31)
165
Figure 5-5 Bidirectional service on station A

TN54TOA 3(RX1/TX1) 4(RX2/TX2) 5(RX3/TX3) 6(RX4/TX4) 7(RX5/TX5) 8(RX6/TX6) 9(RX7/TX7) 10(RX8/TX8) 201(ClientLP1/ClientLP1)-1 202(ClientLP2/ClientLP2)-1 203(ClientLP3/ClientLP3)-1 204(ClientLP4/ClientLP4)-1 205(ClientLP5/ClientLP5)-1 206(ClientLP6/ClientLP6)-1 207(ClientLP7/ClientLP7)-1 208(ClientLP8/ClientLP8)-1 51(ODU1LP1/ODU1LP1)-1 71(ODU2LP1/ODU2LP1)-1 51(ODU1LP1/ODU1LP1)-4 52(ODU1LP2/ODU1LP2)-1 72(ODU2LP2/ODU2LP2)-1 52(ODU1LP2/ODU1LP2)-4 53(ODU1LP3/ODU1LP3)-1 73(ODU2LP3/ODU2LP3)-1 53(ODU1LP3/ODU1LP3)-4 54(ODU1LP4/ODU1LP4)-1 74(ODU2LP4/ODU2LP4)-1 54(ODU1LP4/ODU1LP4)-4 4(IN4/OUT4) 3(IN3/OUT3) 2(IN2/OUT2) 1(IN1/OUT1) TN52NQ2

This section describes how to configure the TOA board in ODU1 non-convergence mode.
Prerequisite


Step 1 Set the Port Working Mode to ODU1 non-convergence mode (OTU1/Any->ODU1) for the TOA board. For details, see Configuring the Working Mode. Step 2 Configure the Service Type at the WDM Interface of the TOA according to the service planning. For details, see 12.2 Configuring the Service Type. Step 3 Configure electrical cross-connections for the ODU1 services between the TOA and TN52NQ2 boards. 1. 2. Configure a cross-connection for one ODU1 service between the TOA and TN52NQ2 boards. For details, see 12.4.1 Creating Cross-Connections. Repeat 3.a to configure a cross-connection for the other ODU1 services between the TOA and TN52NQ2 boards.
----End
5.5 Application Scenario 3: ODU1 Convergence Mode

When using the ODU1 convergence mode, the TOA board performs conversion between eight channels of optical signals with arbitrary bit rates (125 Mbit/s to 2.5 Gbit/s) and eight channels of ODU1 electrical signals.

This section describes the networking diagram of TOA board in ODU1 convergence mode.
Service Requirement
As shown in Figure 5-6, optical NEs A, B, C and D form a ring network, and all the NEs function as OADM stations. The service requirements are as follows: l l l User1 and User2 communicate with each other. One bidirectional OTU2 service is available between station A and station B. At NE A, the TOA board receives eight Any services (125 Mbit/s to 2.5 Gbit/s) and converts them into eight channels of ODU1 services. The TOA board then transmits the eight ODU1 services to the TN52NQ2 board, where the ODU1 services are converged into two OTU2 services.
Figure 5-6 Networking diagram for the TOA board (ODU1 Convergence Mode)
TN52NQ2 TN54TOA
User 2
West B
:OADM


This section describes the service signal flow of TOA board in ODU1 convergence mode. One OTU2 service is available between station A and station B. Figure 5-7 shows the service signal flow on station A.
Figure 5-7 Bidirectional service on station A

TN54TOA 3(RX1/TX1) 4(RX2/TX2) 5(RX3/TX3) 6(RX4/TX4) 7(RX5/TX5) 8(RX6/TX6) 9(RX7/TX7) 10(RX8/TX8) 208(ClientLP8/ClientLP8)-8 54(ODU1LP4/ODU1LP4)-4 202(ClientLP2/ClientLP2)-8 201(ClientLP1/ClientLP1)-8 202(ClientLP2/ClientLP2)-1 202(ClientLP2/ClientLP2)-1 201(ClientLP1/ClientLP1)-1 201(ClientLP1/ClientLP1)-1 51(ODU1LP1/ODU1LP1)-1 71(ODU2LP1/ODU2LP1)-1 51(ODU1LP1/ODU1LP1)-4 52(ODU1LP2/ODU1LP2)-1 72(ODU2LP2/ODU2LP2)-1 52(ODU1LP2/ODU1LP2)-4 53(ODU1LP3/ODU1LP3)-1 73(ODU2LP3/ODU2LP3)-1 208(ClientLP8/ClientLP8)-1 208(ClientLP8/ClientLP8)-1 53(ODU1LP3/ODU1LP3)-4 54(ODU1LP4/ODU1LP4)-1 74(ODU2LP4/ODU2LP4)-1 4(IN4/OUT4) 3(IN3/OUT3) 2(IN2/OUT2) 1(IN1/OUT1) TN52NQ2

This section describes how to configure the TOA board in ODU1 convergence mode.
Prerequisite


Step 1 Set Port Working Mode to ODU1 convergence mode (n*Any->ODU1) for the TOA board. For details, see Configuring the Working Mode. Step 2 Configure the Service Type at WDM Interface of the TOA according to the service planning. For details, see 12.2 Configuring the Service Type. Step 3 Configure the cross-connections from the RX/TX ports to the ClientLP ports on the TOA board for the Any services that are input to the board.
NOTE
In this scenario, If you set the Level to ANY, Service Type must be the same as Service Type at WDM interface of the TOA board. To configure an indirect cross-connection between a TX/RX port and a ClientLP port, you must set Port Working Mode of the direct ClientLP port corresponding to the TX/RX port to ODU1 convergence mode (n*Any->ODU1) or None (not for ports).
Step 4 Configure electrical cross-connections for the ODU1 services between the TOA and TN52NQ2 boards. 1. 2. Configure a cross-connection for one ODU1 service between the TOA and TN52NQ2 boards. For details, see 12.4.1 Creating Cross-Connections. Repeat 4.a to configure a cross-connection for the other ODU1 services between the TOA and TN52NQ2 boards.
----End
5.6 Application Scenario 4: ODU1_ODU0 Mode

In ODU1_ODU0 mode, the TOA board performs conversion between eight channels of OTU1 optical signals and 16 channels of ODU0 electrical signals.

This section describes the networking diagram of TOA board in ODU0_ODU1 mode.
Service Requirement
As shown in Figure 5-8, optical NEs (ONEs) A, B, C, and D form a ring network. All the ONEs function as OADM stations. The service requirements are as follows: l l l User1 and User2 communicate with each other. One bidirectional OTU2 service is available between NE A and NE B. At NE A, the TOA board receives eight OTU1 services and converts them into 16 ODU0 services. The TOA board then transmits the 16 ODU0 to the TN52NQ2 board, where the ODU0 services are converged into two OTU2 services.
Figure 5-8 Networking diagram for the TOA board (ODU0_ODU1 Mode)
User1 SLOT 12 SLOT 15 EAST NMS WEST B EAST SLOT 12 SLOT 15 TN52NQ2 TN54TOA C EAST D WEST WEST
TN52NQ2 TN54TOA
User2
WEST
EAST
OADM

In this example, a TOA board and a TN52NQ2 board must be configured at station A and station B each.

This section describes the service signal flow of TOA board in ODU0_ODU1 mode. One OTU2 service is available between station A and station B. The signal flow at station A is as shown inFigure 5-9. Figure 5-9 Signal flow at station A
TN54TOA 3(RX1/TX1) 201(ClientLP1/ClientLP1)-1 161(ODU0LP1/ODU0LP1)-1 161(ODU0LP1/ODU0LP1)-2 162(ODU0LP2/ODU0LP2)-1 162(ODU0LP2/ODU0LP2)-2 161(ODU0LP1/ODU0LP1)-1 161(ODU0LP1/ODU0LP1)-2 162(ODU0LP2/ODU0LP2)-1 162(ODU0LP2/ODU0LP2)-2 51(ODU1LP1/ODU1LP1)-1 71(ODU2LP1/ODU2LP1)-1 51(ODU1LP1/ODU1LP1)-2 72(ODU2LP2/ODU2LP2)-1 2(IN2/OUT2) 1(IN1/OUT1) TN52NQ2
4(RX2/TX2)
202(ClientLP2/ClientLP2)-1
9(RX7/TX7)
175(ODU0LP15/ODU0LP15)-1 175(ODU0LP15/ODU0LP15)-2 176(ODU0LP16/ODU0LP16)-1 176(ODU0LP16/ODU0LP16)-2 54(ODU1LP4/ODU1LP4)-3
73(ODU2LP3/ODU2LP3)-1
3(IN3/OUT3)
74(ODU2LP4/ODU2LP4)-1 54(ODU1LP4/ODU1LP4)-4
4(IN4/OUT4)
10(RX8/TX8)
Client-side services WDM-side services Services cross-connection, which nedds to be configured on the NMS Virtual channel, which does not need to be configured on the NMS

This section describes how to configure the TOA board in ODU1_ODU0 mode.
Prerequisite


Step 1 Configure the port working modes for the TOA board. Set Port Working Mode to ODU1_ODU0 mode (OTU1->ODU1->ODU0). For details, see Configuring the Working Mode. Step 2 Configure the Service Type at the WDM Interface of the TOA as OTU1 according to the service planning. For details, see 12.2 Configuring the Service Type. Step 3 Configure electrical cross-connections for the two ODU0 services between the TOA and TN52NQ2 boards. 1. 2. Configure a cross-connection for one ODU0 service between the TOA and TN52NQ2 boards. For details, see 12.4.1 Creating Cross-Connections. Repeat 3.a to configure cross-connection for the other ODU0 service between the TOA and TN52NQ2 boards.
----End
5.7 Application Scenario 5: ODUflex Non-Convergence Mode

When using the ODUflex non-convergence mode, the TOA board performs conversion between four channels of FC400 optical signals and four channels of ODUflex electrical signals or conversion between five channels of 3G-SDI optical signals and five channels of ODUflex electrical signals.

This section describes the networking diagram of the TOA board in ODUflex mode.
Service Requirement
As shown in Figure 5-10, optical NEs A, B, C, and D form a ring network. All the NEs function as OADM stations. The service requirements are as follows: l l l User1 and User2 communicate with each other. Four bidirectional OTU2 service is available between station A and station B. FC400 services are used as an example. At station A, the TOA board receives four FC400 services and converts them into four ODUflex services. The TOA board then transmits the four ODUflex services to the TN53NQ2 board at station A. Then the TN53NQ2 board converges the four ODUflex services into four OTU2 services.
Figure 5-10 Networking diagram for the TOA board (ODUflex mode)
User1 SLOT 12 SLOT 15 EAST NMS WEST B EAST SLOT 12 SLOT 15 TN53NQ2 TN54TOA C EAST D WEST WEST
TN53NQ2 TN54TOA
User2
WEST
EAST
OADM
Issue 02 (2011-10-31)
171

In this example, one TOA board and one TN53NQ2 board must be configured at stations A and B each.

This section describes the service signal flow of the TOA board in ODUflex mode. One OTU2 service is available between station A and station B. Figure 5-11 shows the service signal flow at station A. Figure 5-11 Bidirectional service at station A
TN54TOA 3(RX1/TX1) 201(ClientLP1/ClientLP1)-1 ODUflex-1 ODUflex-2 ODUflex-1 ODUflex-2 ODUflex:1 ODUflex:2 ODUflex:1 ODUflex:2 9(RX7/TX7) 207(ClientLP7/ClientLP7)-1 ODUflex-1 ODUflex-2 ODUflex-1 ODUflex-2 Multiplexing Service processing module module IN4/OUT4-OCH:4-ODUflex:2 IN1/OUT1-OCH:1-ODUflex:1 ODU2:1 OCH:1 2(IN2/OUT2) ODU2:4 OCH:4 1(IN1/OUT1) TN53NQ2
4(RX2/TX2)
3(IN3/OUT3)
4(IN4/OUT4)
10(RX8/TX8)
Client-side services WDM-side services Services cross-connection, which nedds to be configured on the NMS Virtual channel, which does not need to be configured on the NMS

This section describes how to configure the TOA board in ODUflex mode.
Prerequisite
Precautions
After configurate cross-connections for four ODUflex services for the TOA board (service type is FC-400), any cross-connections cannot be configurated for the other ports of the TOA board.


Step 1 Set Port Working Mode to ODUflex non-convergence mode (Any->ODUflex) for the TOA board. For details about the configuration procedure, see Configuring the Working Mode.
Step 2 Set the service type of the ClientLP ports on the TOA board to FC-400 based on the service plan. For details about the configuration procedure, see 12.2 Configuring the Service Type. Step 3 Set ODU Timeslot Configuration Mode to Assign random for the TN53NQ2 board. Choose Configuration > WDM Interface > Advanced Attributes from the Function Tree. In the displayed window, set ODU Timeslot Configuration Mode to Assign random for the required ports. Step 4 Configure cross-connections for the ODUflex services between the TOA and TN53NQ2 boards. 1. Configure the cross-connection for the first ODUflex service between the TOA and TN53NQ2 boards. The following figure shows the parameters that you need to set. For details about the configuration procedure, see 12.4.1 Creating Cross-Connections.
2.
Repeat 4.a to configure cross-connections for the other three ODUflex services between the TOA and TN53NQ2 boards.
----End
Issue 02 (2011-10-31)
173
6 Configuring the LOA Board (Manually by Station)
Configuring the LOA Board (Manually by Station)
About This Chapter

The LOA board can be configured with different port working modes and is applicable to five scenarios accordingly. You need to manually configure the board by station on the NMS for the application scenarios. 6.1 Overview of the Working Mode Each port on the LOA board can work in different modes so that services can be processed on different paths. 6.2 Configuration Procedures Six port working modes are available for the LOA board on the NMS. The port for the None (not for ports) mode does not require configurations. The other five modes require configurations. 6.3 Application Scenario 1: Conversion Between Eight Any Services and One OTU2 Optical Signals (with ODU0 Mapping) This configuration example describes how the LOA board is configured to implement conversion between eight channels of optical signals at any rate from 125 Mbit/s to 1.25 Gbit/s and one channel of ODU2 optical signals by means of ODU0 mapping. 6.4 Application Scenario 2: Conversion Between Four Any Services and One OTU2 Optical Signals This configuration example describes how the LOA board is configured to implement conversion between four channels of optical signals at any rate from 1.49 Gbit/s to 2.67 Gbit/s and one channel of ODU2 optical signals by means of ODU1 mapping. 6.5 Application Scenario 3: Conversion Between Four OTU1 Services and One OTU2 Optical Signals (with ODU0 Mapping) This configuration example describes how the LOA board is configured to implement conversion between four channels of OTU1 optical signals and one channel of ODU2 optical signals by means of ODU0 mapping. 6.6 Application Scenario 4: Conversion Between Two 3G-SDI Services and One OTU2 Optical Signals
This configuration example describes how the LOA board is configured to implement conversion between two channels of 3G-SDI optical signals and one channel of ODU2 optical signals by means of ODU0 mapping. 6.7 Application Scenario 5: Conversion Between One FC800 Services and One OTU2 Optical Signals This configuration example describes how the LOA board is configured to implement conversion between one channels of FC800 optical signals and one channel of ODU2 optical signals by means of ODU0 mapping.
Issue 02 (2011-10-31)
175
6.1 Overview of the Working Mode

Each port on the LOA board can work in different modes so that services can be processed on different paths. The LOA board supports six port working modes listed in Table 6-1. You can set the port working modes on the NMS. Table 6-1 Port working modes on the LOA board Port Working Mode ODU0 non-convergence mode ODU1 non-convergence mode ODU1_ODU0 mode ODUflex non-convergence mode ODU2 non-convergence mode None (not for ports) Signal Flow Any->ODU0[->ODU1]->ODU2->OTU2 OTU1/Any->ODU1->ODU2->OTU2 OTU1->ODU1->ODU0[->ODU1]->ODU2>OTU2 Any->ODUflex->ODU2->OTU2 Any->ODU2->OTU2 -
NOTE
l [->ODU1]: indicates that "ODU1" is optional. For example, in ODU0 non-convergence mode, two service signal flows are available: Any->ODU0->ODU2->OTU2 and Any->ODU0->ODU1->ODU2>OTU2. l None (not for ports): indicates that the resources at the port in this mode are not used and are released to other ports.
6.2 Configuration Procedures

Six port working modes are available for the LOA board on the NMS. The port for the None (not for ports) mode does not require configurations. The other five modes require configurations.
General Configuration Procedure

Figure 6-1 shows the general configuration procedure for the port working modes on the LOA board.
Issue 02 (2011-10-31)
176
Figure 6-1 General configuration procedure

Configure the port working mode
Configure the port type
Configure the timeslot configuration mode
Configure the service mode
Configure crossconnections from the client side to LP ports
Configure ODU0-level cross-connections from LP ports to the WDM side
Mandatory Optional
In the flowchart, the mandatory actions are required for each port working mode and optional actions vary according to port working modes. The optional actions must be configured in the following scenarios: l l Configure the port type: Port Type must be set to Client Side Color Optical Port when colored optical signals are received on the client side. Configure the timeslot configuration mode: ODU Timeslot Configuration Mode must be set for the line side of the LOA board. When the signal flow is from ODU0 or ODUflex to ODU2, ODU Timeslot Configuration Mode must be set to Assign random. When the signal flow is ODU0 -> ODU1 -> ODU2, ODU Timeslot Configuration Mode must be set to Assign consecutive. When the signal flow is from Any or ODU1 to ODU2 directly, ODU Timeslot Configuration Mode can be set to Assign consecutive or Assign random. However, the value must be the same as the value that is set on the interconnected LOA or line board. l Configure the service mode: When Service Type is set to OTU1, Service Mode must be set to OTN Mode.
Issue 02 (2011-10-31)
Configure cross-connections from the client side to LP ports: This action is required only for the ODU0 non-convergence mode and ODU1 convergence mode.
The following describes the configuration procedure and involved parameter settings for each mode. l l l l l Table 6-2 describes the configuration procedure for the ODU0 non-convergence mode. Table 6-3 describes the configuration procedure for the ODU1 non-convergence mode. Table 6-4 describes the configuration procedure for the ODU1_ODU0 mode. Table 6-5 describes the configuration procedure for the ODUflex non-convergence mode. Table 6-6 describes the configuration procedure for the ODU2 non-convergence mode.

Table 6-2 Configuration procedure N o. 1 Action Configure the port working mode. Description Optional l Parameter settings: The default value of Port Working Mode is ODU0 non-convergence mode (Any->ODU0[>ODU1]->ODU2->OTU2). If the default value is used, skip this step. l Operation description: For details about the configuration procedure, see Configuring the Working Mode. 2 Configure the port type. Optional l Parameter settings: The default value of Port Type is Client Side Grey Optical Port. If colored optical signals are received on the client side, set Port Type to Client Side Color Optical Port. l Operation description: For details about the configuration procedure, see Modifying Port. 3 Configure the timeslot configuration mode. Optional l Parameter settings: The value of ODU Timeslot Configuration Mode varies according to the two signal flows in the ODU0 non-convergence mode. When the signal flow is Any->ODU0->ODU2->OTU2, set ODU Timeslot Configuration Mode to Assign random. When the signal flow is Any->ODU0->ODU1->ODU2>OTU2, set ODU Timeslot Configuration Mode to Assign consecutive. l Operation description: In the NE Explorer, select the LOA board and choose Configuration > WDM Interface > Advanced Attributes from the Function Tree. In the displayed window, set ODU Timeslot Configuration Mode for the WDM side port.
N o. 4
Action Configure the service type.
Description Mandatory l Parameter settings: The available values for Service Type are FE, GE(TTT-AGMP), GE(GFP-T), STM-1/OC-3, STM-4/ OC-12, FC100, ESCON, FICON, FDDI, SDI, and DVB-ASI. l Operation description: For details about the configuration procedure, see Configuring the Service Type.
NOTE Two channels (channel 1 and channel 2) are available at each LP port. Set the service type for only one of the two channels. When the LOA board is interconnected with a TN52TOM board, the channel where you set the service type must be the same as the channel where the service type is set on the TN52TOM board. When the LOA board is interconnected with another board, set the service type for channel 1.
Configure crossconnections from the client side to LP ports on the LOA board.
Mandatory l Parameter settings: Level and Service Type: If you set Service Type to GE in step 4, retain the default value (GE) for Level. If you set Service Type to a value other than GE in step 4, set Level to Any and then set Service Type to the same value that you set in step 4. Direction: Set it to Bidirectional. Source Slot/Sink Slot: Set the two parameters to the ID of the slot where the LOA board is housed. Source Optical Port: Set it to a port in the range of 3(RX1/ TX1) to 10(RX8/TX8). Source Optical Channel: Set it to 1. Sink Optical Port: Set it to a port in the range of 201 (ClientLP1/ClientLP1) to 208(ClientLP8/ClientLP8). Ensure that the client-side port matches an LP port. That is, if you set the source optical port to RXi/TXi, set the sink optical port to ClientLPi. Sink Optical Channel: 1 or 2. Set it to the channel for which you configure the service type in step 4. l Operation description: Configure cross-connections from the client side to each LP port. For details about the configuration procedure, see Creating Cross-Connections.
Configure ODU0level crossconnections from LP ports to the WDM side on the LOA board.
Mandatory l Parameter settings: See Table 6-7. l Operation description: Configure cross-connections from each LP port to the WDM side. For details about the configuration procedure, see Creating Cross-Connections.
Issue 02 (2011-10-31)
179

Table 6-3 Configuration procedure N o. 1 Action Configure the port working mode. Description Mandatory l Parameter settings: Set Port Working Mode to ODU1 nonconvergence mode (OTU1/Any->ODU1->ODU2->OTU2). l Operation description: For details about the configuration procedure, see Configuring the Working Mode. 2 Configure the port type. Optional l Parameter settings: The default value of Port Type is Client Side Grey Optical Port. If colored optical signals are received on the client side, set Port Type to Client Side Color Optical Port. l Operation description: For details about the configuration procedure, see Modifying Port. 3 Configure the timeslot configuration mode. Optional l Parameter settings: Set ODU Timeslot Configuration Mode to Assign consecutive or Assign random. l Operation description: In the NE Explorer, select the LOA board and choose Configuration > WDM Interface > Advanced Attributes from the Function Tree. In the displayed window, set ODU Timeslot Configuration Mode for the WDM side port. Mandatory l Parameter settings: The available values for Service Type are HD-SDI, FC200, FICON Express, OTU1, STM16, or OC-48. l Operation description: For details about the configuration procedure, see Configuring the Service Type. 5 Configure the service mode. Optional l Parameter settings: The default value of Service Mode is Client Mode. When you set Service Type to OTU1, set Service Mode to OTN Mode. l Operation description: For details about the configuration procedure, see Configuring the Service Mode. 6 Configure ODUklevel crossconnections from LP ports to the WDM side on the LOA board. Mandatory l Parameter settings: See Table 6-7. l Operation description: Configure cross-connections from each LP port to the WDM side. For details about the configuration procedure, see Creating Cross-Connections.
Issue 02 (2011-10-31)
180
Configuration Procedure for the ODU1_ODU0 Mode

Table 6-4 Configuration procedure N o. 1 Action Configure the port working mode. Description Mandatory l Parameter settings: Set Port Working Mode to ODU1_ODU0 mode (OTU1->ODU1->ODU0[->ODU1]->ODU2>OTU2). l Operation description: For details about the configuration procedure, see Configuring the Working Mode. 2 Configure the port type. Optional l Parameter settings: The default value of Port Type is Client Side Grey Optical Port. If colored optical signals are received on the client side, set Port Type to Client Side Color Optical Port. l Operation description: For details about the configuration procedure, see Modifying Port. 3 Configure the timeslot configuration mode. Optional l Parameter settings: The value of ODU Timeslot Configuration Mode varies according to the two signal flows in the ODU1_ODU0 mode. When the signal flow is OTU1->ODU1->ODU0->ODU2>OTU2, set ODU Timeslot Configuration Mode to Assign random. When the signal flow is OTU1->ODU1->ODU0->ODU1>ODU2->OTU2, set ODU Timeslot Configuration Mode to Assign consecutive. l Operation description: In the NE Explorer, select the LOA board and choose Configuration > WDM Interface > Advanced Attributes from the Function Tree. In the displayed window, set ODU Timeslot Configuration Mode for the WDM side port. 4 Configure the service type. Mandatory l Parameter settings: The available values for Service Type is OTU1 only. l Operation description: For details about the configuration procedure, see Configuring the Service Type. 5 Configure the service mode. Mandatory l Parameter settings: Set Service Mode to OTN Mode. l Operation description: For details about the configuration procedure, see Configuring the Service Mode.
Issue 02 (2011-10-31)
181
N o. 6
Action Configure ODUklevel crossconnections from LP ports to the WDM side on the LOA board.
Description Mandatory l Parameter settings: See Table 6-7. l Operation description: Configure cross-connections from each LP port to the WDM side. For details about the configuration procedure, see Creating Cross-Connections.
Configuration Procedure for the ODUflex Non-Convergence Mode

Table 6-5 Configuration procedure N o. 1 Action Configure the port working mode. Description Mandatory l Parameter settings: Set Port Working Mode to ODUflex nonconvergence mode (Any->ODUflex->ODU2->OTU2). l Operation description: For details about the configuration procedure, see Configuring the Working Mode.
NOTE When the RX1/TX1 port receives the FC800 service, set Port Working Mode to ODUflex non-convergence mode (Any->ODUflex->ODU2>OTU2) only for port LP1. And set Port Working Mode to None (not for ports) for the other seven LP ports.
Configure the port type.
Optional l Parameter settings: The default value of Port Type is Client Side Grey Optical Port. If colored optical signals are received on the client side, set Port Type to Client Side Color Optical Port. l Operation description: For details about the configuration procedure, see Modifying Port.
Configure the timeslot configuration mode.
Mandatory l Parameter settings: The default value of ODU Timeslot Configuration Mode is Assign random. If the default value is used, skip this step. l Operation description: In the NE Explorer, select the LOA board and choose Configuration > WDM Interface > Advanced Attributes from the Function Tree. In the displayed window, set ODU Timeslot Configuration Mode to Assign random for the WDM side port.
Issue 02 (2011-10-31)
182
N o. 4
Description Mandatory l Parameter settings: The available values for Service Type are 3GSDI, FC-400, or FC-800. FC-800 is only for the RX1/TX1 port. l Operation description: For details about the configuration procedure, see Configuring the Service Type.
Configure ODUklevel crossconnections from LP ports to the WDM side on the LOA board.

Table 6-6 Configuration procedure N o. 1 Action Configure the port working mode. Description Mandatory l Parameter settings: Before setting Port Working Mode to ODU2 non-convergence mode (Any->ODU2->OTU2) for port LP1, set to None (not for ports) for the other seven LP ports. l Operation description: For details about the configuration procedure, see Configuring the Working Mode. 2 Configure the port type. Optional l Parameter settings: The default value of Port Type is Client Side Grey Optical Port. If colored optical signals are received on the client side, set Port Type to Client Side Color Optical Port. l Operation description: For details about the configuration procedure, see Modifying Port. 3 Configure the timeslot configuration mode. Mandatory l Parameter settings: Set ODU Timeslot Configuration Mode to Assign random or Assign consecutive. l Operation description: In the NE Explorer, select the LOA board and choose Configuration > WDM Interface > Advanced Attributes from the Function Tree. In the displayed window, set ODU Timeslot Configuration Mode for the WDM side port.
Issue 02 (2011-10-31)
183
N o. 4
Description Mandatory l Parameter settings: Set Service Type to FC800 only for the RX1/TX1 port. l Operation description: For details about the configuration procedure, see Configuring the Service Type.
Configure ODUklevel crossconnections from LP ports to the WDM side on the LOA board.
Table 6-7 Parameters for configuring ODUk-level cross-connections from LP ports to the WDM side Paramete r ODU0 NonConvergenc e Mode ODU0 ODU1 NonConvergenc e Mode ODU1 ODU1_OD U0 Mode ODUflex NonConvergenc e Mode ODUflex Custom, PACKET, FC400, FC800, 3GSDI, InfiniBand 2.5G, or CPRI4
NOTE For the V100R006C 01 version, only support FC400, FC800, and 3GSDI.
ODU2 NonConvergen ce Mode ODU2 -
Level Service Type
ODU0 -
Direction Source Slot/Sink Slot
Bidirectional ID of the slot where the LOA board is housed
Issue 02 (2011-10-31)
184
Paramete r
ODU0 NonConvergenc e Mode 201 (ClientLP1/ ClientLP1) to 208 (ClientLP8/ ClientLP8) 1 or 2
ODU1 NonConvergenc e Mode 201 (ClientLP1/ ClientLP1) to 208 (ClientLP8/ ClientLP8) 1
ODU1_OD U0 Mode
ODUflex NonConvergenc e Mode 201 (ClientLP1/ ClientLP1) to 208 (ClientLP8/ ClientLP8)a 1
ODU2 NonConvergen ce Mode 201 (ClientLP1/ ClientLP1)
Source Optical Port
201 (ClientLP1/ ClientLP1) to 208 (ClientLP8/ ClientLP8) 1
Source Optical Channel Sink Optical Port Sink Optical Channel
1(IN1/ OUT1) OCH:1ODU2:1ODU0:1 to OCH:1ODU2:1ODU0:8 or OCH:1ODU2:1ODU1:1ODU0:1 to OCH:1ODU2:1ODU1:1ODU0:8
1(IN1/ OUT1) OCH:1ODU2:1ODU1:1 to OCH:1ODU2:1ODU1:8
1(IN1/ OUT1) OCH:1ODU2:1ODU0:1 to OCH:1ODU2:1ODU0:8 or OCH:1ODU2:1ODU1:1ODU0:1 to OCH:1ODU2:1ODU1:1ODU0:8
1(IN1/ OUT1) OCH:1ODU2:1ODUflex:1a OCH:1ODU2:1ODUflex:2
1(IN1/ OUT1) OCH:1ODU2:1
Issue 02 (2011-10-31)
185
Paramete r
ODU0 NonConvergenc e Mode -
ODU1_OD U0 Mode
ODUflex NonConvergenc e Mode l The value is 4 when the service type is FC400. l The value is 7 when the service type is FC800. l The value is 3 when the service type is 3GSDI. l The value is 3 when the service type is InfiniBan d 2.5G. l The value is 3 when the service type is CPRI4. l The value needs to be set to 1 to 8 based on the actual service when the service type is Custom or PACKET .
Occupied ODUTUk Slot Count
Issue 02 (2011-10-31)
186
Paramete r
ODU1_OD U0 Mode
ODUflex NonConvergenc e Mode The parameter value is automatically displayed according to the value of Occupied ODUTUk Slot Count.
Service Rate(bit/s)
l a: When the LOA board receives FC800 services, set Source Optical Port only to 201 (ClientLP1/ClientLP1) and Sink Optical Channel only to OCH:1-ODU2:1-ODUflex: 1.
NOTE
To better understand the service signal flow and ports required for configuring cross-connections, see the section "Physical and Logical Ports" for each board in the Hardware Description, where detailed port models and working modes are provided.
6.3 Application Scenario 1: Conversion Between Eight Any Services and One OTU2 Optical Signals (with ODU0 Mapping)
This configuration example describes how the LOA board is configured to implement conversion between eight channels of optical signals at any rate from 125 Mbit/s to 1.25 Gbit/s and one channel of ODU2 optical signals by means of ODU0 mapping.

This section describes how to configure the LOA board on a ring network.
Service Requirement
As shown in Figure 6-2, optical NEs A, B, C, and D form a ring network. All the NEs function as OADM stations. The service requirements are as follows: l l l User1 and User2 communicate with each other. One bidirectional OTU2 service is available between station A and station B. At station A, the LOA board receives eight services at any rate from 125 Mbit/s to 1.25 Gbit/s (GE services are used as an example) and converts them into one OTU2 service.
Issue 02 (2011-10-31)
Figure 6-2 Networking diagram for the LOA board (ODU0 Non-Convergence Mode)
User 1 LOA
SLOT 15 East NMS East D C East SLOT 15 LOA West East West West
User 2
West B
:OADM

In this example, one LOA board must be configured at stations A and B each.

This section describes the service signal flow of the LOA board in ODU0 non-convergence mode. One OTU2 service is available between station A and station B. Figure 6-3 shows the service signal flow (GE->ODU0->ODU2->OTU2) at station A. And Figure 6-4 shows the service signal flow (GE->ODU0->ODU1->ODU2->OTU2) at station A. Figure 6-3 Bidirectional service at station A (GE->ODU0->ODU2->OTU2)
Client Side 201(ClientLP1/ClientLP1)-1/ 201(ClientLP1/ClientLP1)-2 to 208(ClientLP8/ClientLP8)-1/ 208(ClientLP8/ClientLP8)-2 201(ClientLP1/ClientLP1)-1 201(ClientLP1/ClientLP1)-2 4(RX2/TX2)-1 202(ClientLP2/ClientLP2)-1 202(ClientLP2/ClientLP2)-2 ODU0:2 WDM Side
IN/OUT-OCH:1-ODU2:1-ODU0:(1 to 8) ODU0:1
3(RX1/TX1)-1
. . .
10(RX8/TX8)-1
. . .
208(ClientLP8/ClientLP8)-1 208(ClientLP8/ClientLP8)-2
. . .
ODU0:8
ODU2:1
OCH:1
IN/OUT
Issue 02 (2011-10-31)
188
Figure 6-4 Bidirectional service at station A (GE->ODU0->ODU1->ODU2->OTU2)

Client Side 201(ClientLP1/ClientLP1)-1/ 201(ClientLP1/ClientLP1)-2 to 208(ClientLP8/ClientLP8)-1/ 208(ClientLP8/ClientLP8)-2 201(ClientLP/ ClientLP1)-1 201(ClientLP1/ ClientLP1)-2 202(ClientLP2/ ClientLP2)-1 202(ClientLP2/ ClientLP2)-2 WDM Side
IN/OUT-OCH:1-ODU2:1-ODU1:(1 to 4)-ODU0:(1 to 2) ODU0:1 ODU1:1 ODU0:2
3(RX1/TX1)-1
4(RX2/TX2)-1
ODU2:1 207(ClientLP7/ ClientLP7)-1 207(ClientLP7/ ClientLP7)-2 208(ClientLP8/ ClientLP8)-1 208(ClientLP8/ ClientLP8)-2 ODU0:2
OCH:1
IN/OUT
9(RX7/TX7)-1
ODU0:1 ODU1:4
10(RX8/TX8)-1

This section uses station A as an example to describe the configuration process of the LOA board.
Prerequisite


Step 1 Set Port Working Mode to ODU0 non-convergence mode (Any->ODU0[->ODU1]->ODU2>OTU2) (the default value) for the LOA board. If the default value is used, skip this step. For details about the configuration procedure, see Configuring the Working Mode. Step 2 If the service signal flow is GE->ODU0->ODU2->OTU2, set ODU Timeslot Configuration Mode to Assign random (the default value) for the LOA board. If the service signal flow is GE->ODU0->ODU1->ODU2->OTU2, set ODU Timeslot Configuration Mode to Assign consecutive for the LOA board. If the default value is used, skip this step. To set the parameter, select the LOA board in the NE Explorer and choose Configuration > WDM Interface > Advanced Attributes from the Function Tree. In the displayed window, set ODU Timeslot Configuration Mode to Assign random or Assign consecutive for the "1(IN/ OUT)-OCh:1" port.
Step 3 Set the service type of the ClientLP ports on the LOA board to GE(TTT-AGMP) based on the service plan. For details about the configuration procedure, see 12.2 Configuring the Service Type.
NOTE
l The GE services that the LOA board supports include GE(GFP-T) and GE(TTT-AGMP). The recommended service type is GE(TTT-AGMP). l Two channels (channel 1 and channel 2) are available at each LP port. You can set the service type for only one of the two channels. When the LOA board is interconnected with a TN52TOM board, the channel where you set the service type must be the same as the channel where the service type is set on the TN52TOM board. When the LOA board is interconnected with another board, set the service type for channel 1.
Step 4 Configure cross-connections from the client side to LP ports on the LOA board. In the NE Explorer, select the NE and choose Configuration > WDM Service Management from the Function Tree. In the displayed window, click New to display the Create CrossConnection Service window. 1. Configure the cross-connection for the first GE service. See the following table to set the parameters. Parameter Level Direction Source Slot Source Optical Port Source Optical Channel Sink Slot Sink Optical Port Sink Optical Channel Value GE Bidirectional Subrack 0(subrack)-15-LOA 3(RX1/TX1) 1 Subrack 0(subrack)-15-LOA 201(ClientLP1/ClientLP1) 1
2.
Repeat substep a in step 4 to configure cross-connections for the other seven GE services. Retain the same values for the other parameters except Source Optical Port and Sink Optical Port. For each of the remaining seven GE services, set Source Optical Port to a value in the range of 4(RX2/TX2) to 10(RX8/TX8) and Sink Optical Port to a value in the range of 202(ClientLP2/ClientLP2) to 208(ClientLP8/ClientLP8). The sink optical port number must match the source optical port number. That is, if the source optical port is RXi/TXi, the sink optical port must be ClientLPi.
Step 5 Configure ODU0-level cross-connections from LP ports to the WDM side on the LOA board. Perform the following configurations in the Create Cross-Connection Service window. 1.
Issue 02 (2011-10-31)
Configure the first ODU0 cross-connection. See the following table to set the parameters.
Parameter Level Direction Source Slot Source Optical Port Source Optical Channel Sink Slot Sink Optical Port Sink Optical Channel
Value ODU0 Bidirectional Subrack 0(subrack)-15-LOA 201(ClientLP1/ClientLP1) 1 Subrack 0(subrack)-15-LOA 1(IN1/OUT1) OCH:1-ODU2:1-ODU0:1
2.
Repeat substep a in step 5 to configure the other seven ODU0 cross-connections. Retain the same values for the other parameters except Source Optical Port and Sink Optical Port. For each of the remaining seven ODU0 cross-connections, set Source Optical Port to a value in the range of 202(ClientLP2/ClientLP2) to 208(ClientLP8/ClientLP8) and Sink Optical Port to a value in the range of OCH:1-ODU2:1-ODU0:2 to OCH:1ODU2:1-ODU0:8. The sink optical port number does not need to match the source optical port number.
----End
6.4 Application Scenario 2: Conversion Between Four Any Services and One OTU2 Optical Signals
This configuration example describes how the LOA board is configured to implement conversion between four channels of optical signals at any rate from 1.49 Gbit/s to 2.67 Gbit/s and one channel of ODU2 optical signals by means of ODU1 mapping.

Service Requirement
As shown in Figure 6-5, optical NEs A, B, C, and D form a ring network. All the NEs function as OADM stations. The service requirements are as follows: l l l User1 and User2 communicate with each other. One bidirectional OTU2 service is available between station A and station B. At station A, the LOA board receives four services at any rate from 1.49 Gbit/s to 2.67 Gbit/s (STM-16 services are used as an example) and converts them into one OTU2 service.
Issue 02 (2011-10-31)
User 1 LOA
User 2
West B
:OADM


This section describes the service signal flow of the LOA board in ODU1 non-convergence mode. One OTU2 service is available between station A and station B. Figure 6-6 shows the service signal flow (STM-16->ODU1->ODU2->OTU2) at station A. Figure 6-6 Bidirectional service at station A
Client Side 201(ClientLP1/ClientLP1)-1 to 208(ClientLP8/ClientLP8)-1 201(ClientLP1/ClientLP1)-1 202(ClientLP2/ClientLP2)-1
WDM Side
IN/OUT-OCH:1-ODU2:1-ODU1:(1 to 4) ODU1:1 ODU1:2 IN/OUT
3(RX1/TX1)-1 4(RX2/TX2)-1
ODU2:1
OCH:1
9(RX7/TX7)-1 10(RX8/TX8)-1
207(ClientLP7/ClientLP7)-1 208(ClientLP8/ClientLP8)-1
ODU1:3 ODU1:4
Issue 02 (2011-10-31)
192

Prerequisite


Step 1 Set Port Working Mode to ODU1 non-convergence mode (OTU1/Any->ODU1->ODU2>OTU2) for the LOA board. For details about the configuration procedure, see Configuring the Working Mode. Step 2 Set ODU Timeslot Configuration Mode to Assign consecutive. To set the parameter, select the LOA board in the NE Explorer and choose Configuration > WDM Interface > Advanced Attributes from the Function Tree. In the displayed window, set ODU Timeslot Configuration Mode to Assign consecutive for the "1(IN/OUT)-OCh:1" port. Step 3 Set the service type of the ClientLP ports on the LOA board to STM-16 based on the service plan. For details about the configuration procedure, see 12.2 Configuring the Service Type. Step 4 Configure ODU1-level cross-connections from LP ports to the WDM side on the LOA board. In the NE Explorer, select the NE and choose Configuration > WDM Service Management from the Function Tree. In the displayed window, click New to display the Create CrossConnection Service window. 1. Configure the first ODU1 cross-connection. See the following table to set the parameters. Parameter Level Direction Source Slot Source Optical Port Source Optical Channel Sink Slot Sink Optical Port
Issue 02 (2011-10-31)
Value ODU1 Bidirectional Subrack 0(subrack)-15-LOA 201(ClientLP1/ClientLP1) 1 Subrack 0(subrack)-15-LOA 1(IN1/OUT1)

193
Parameter Sink Optical Channel 2.
Value OCH:1-ODU2:1-ODU1:1
Repeat substep a in step 4 to configure the other three ODU1 cross-connections. Retain the same values for the other parameters except Source Optical Port and Sink Optical Port. For each of the remaining three ODU1 cross-connections, set Source Optical Port to a value in the range of 202(ClientLP2/ClientLP2) to 208(ClientLP8/ClientLP8) and Sink Optical Port to a value in the range of OCH:1-ODU2:1-ODU1:2 to OCH:1-ODU2:1ODU1:4. The sink optical port number does not need to match the source optical port number.
----End
6.5 Application Scenario 3: Conversion Between Four OTU1 Services and One OTU2 Optical Signals (with ODU0 Mapping)
This configuration example describes how the LOA board is configured to implement conversion between four channels of OTU1 optical signals and one channel of ODU2 optical signals by means of ODU0 mapping.

Service Requirement
As shown in Figure 6-7, optical NEs A, B, C, and D form a ring network. All the NEs function as OADM stations. The service requirements are as follows: l l l User1 and User2 communicate with each other. One bidirectional OTU2 service is available between station A and station B. At station A, the LOA board receives four OTU1 services and converts them into one OTU2 service.
Issue 02 (2011-10-31)
194
Figure 6-7 Networking diagram for the LOA board (ODU1_ODU0 Mode)
User 1 LOA
User 2
West B
:OADM


This section describes the service signal flow of the LOA board in ODU1_ODU0 mode. One OTU2 service is available between station A and station B. Figure 6-8 shows the service signal flow (OTU1->ODU1->ODU0->ODU2->OTU2) at station A. Figure 6-8 Bidirectional service at station A
Client side
201(ClientLP1/ClientLP1)~ IN/OUT-OCH:1-ODU2:1-ODU0(1~8) 208(ClientLP8/ClientLP8) 201(ClientLP1/ ClientLP1)-1 ODU0:1 201(ClientLP1/ ClientLP1)-2 202(ClientLP2/ ClientLP2)-1 202(ClientLP2/ ClientLP2)-2 ODU0:2 ODU0:3 ODU2:1 ODU0:4 OCH:1 IN/OUT
WDM side
3(RX1/TX1)-1
4(RX2/TX2)-1
208(ClientLP8 /ClientLP8)-1 10(RX8/TX8)-1 208(ClientLP8 /ClientLP8)-2
ODU0:7 ODU0:8
Issue 02 (2011-10-31)
195

Prerequisite


Step 1 Set Port Working Mode to ODU1_ODU0 mode (OTU1->ODU1->ODU0[->ODU1]>ODU2->OTU2) for the LOA board. For details about the configuration procedure, see Configuring the Working Mode. Step 2 Set ODU Timeslot Configuration Mode to Assign random (the default value) for the LOA board. If the default value is used, skip this step. To set the parameter, select the LOA board in the NE Explorer and choose Configuration > WDM Interface > Advanced Attributes from the Function Tree. In the displayed window, set ODU Timeslot Configuration Mode to Assign random for the "1(IN/OUT)-OCh:1" port. Step 3 Set the service type of the ClientLP ports on the LOA board to OTU1 based on the service plan. For details about the configuration procedure, see 12.2 Configuring the Service Type. Step 4 Set the client ports of the LOA board Service Mode to OTN Mode. For details about the configuration procedure, see Configuring the Service Mode. Step 5 Configure ODU0-level cross-connections from LP ports to the WDM side on the LOA board. In the NE Explorer, select the NE and choose Configuration > WDM Service Management from the Function Tree. In the displayed window, click New to display the Create CrossConnection Service window. 1. Configure the first ODU0 cross-connection. See the following table to set the parameters. Parameter Level Direction Source Slot Source Optical Port Source Optical Channel
Issue 02 (2011-10-31)
Value ODU0 Bidirectional Subrack 0(subrack)-15-LOA 201(ClientLP1/ClientLP1) 1
196
Parameter Sink Slot Sink Optical Port Sink Optical Channel 2.
Value Subrack 0(subrack)-15-LOA 1(IN1/OUT1) OCH:1-ODU2:1-ODU0:1
Repeat substep a in step 5 to configure the other seven ODU0 cross-connections. Retain the same values for the other parameters except Source Optical Port and Sink Optical Port. For each of the remaining seven ODU0 cross-connections, set Source Optical Port to a value in the range of 202(ClientLP2/ClientLP2) to 208(ClientLP8/ClientLP8) and Sink Optical Port to a value in the range of OCH:1-ODU2:1-ODU0:2 to OCH:1ODU2:1-ODU0:8. The sink optical port number does not need to match the source optical port number.
----End
6.6 Application Scenario 4: Conversion Between Two 3GSDI Services and One OTU2 Optical Signals
This configuration example describes how the LOA board is configured to implement conversion between two channels of 3G-SDI optical signals and one channel of ODU2 optical signals by means of ODU0 mapping.

Service Requirement
As shown in Figure 6-9, optical NEs A, B, C, and D form a ring network. All the NEs function as OADM stations. The service requirements are as follows: l l l User1 and User2 communicate with each other. One bidirectional OTU2 service is available between station A and station B. At station A, the LOA board can receives two 3G-SDI or FC400 services, or receives one FC800 service and converts them into one OTU2 service. 3G-SDI services are used as an example.
Issue 02 (2011-10-31)
197
Figure 6-9 Networking diagram for the LOA board (ODUflex Non-Convergence Mode)
User 1 LOA
User 2
West B
:OADM


This section describes the service signal flow of the LOA board in ODUflex non-convergence mode. One OTU2 service is available between station A and station B. Figure 6-10 shows the service signal flow (3G-SDI->ODUflex->ODU2->OTU2) at station A. Figure 6-10 Bidirectional service at station A
Client Side 201(ClientLP1/ClientLP1) to 208(ClientLP2/ClientLP8) 201(ClientLP1/ ClientLP1)-1 WDM Side IN/OUT-OCH:1-ODU2:1-ODUflex:(1 to 2)
3(RX1/TX1)-1
ODUflex:1
ODU2:1 OCH:1 IN/OUT
10(RX8/TX8)-1
208(ClientLP8/ ClientLP8)-1
ODUflex:2
Issue 02 (2011-10-31)
198

Prerequisite


Step 1 Set Port Working Mode to ODUflex non-convergence mode (Any->ODUflex->ODU2>OTU2) for the LOA board. For details about the configuration procedure, see Configuring the Working Mode. Step 2 Set ODU Timeslot Configuration Mode to Assign random (the default value) for the LOA board. If the default value is used, skip this step. To set the parameter, select the LOA board in the NE Explorer and choose Configuration > WDM Interface > Advanced Attributes from the Function Tree. In the displayed window, set ODU Timeslot Configuration Mode to Assign random for the "1(IN/OUT)-OCh:1" port. Step 3 Set the service type of the ClientLP ports on the LOA board to 3GSDI based on the service plan. For details about the configuration procedure, see 12.2 Configuring the Service Type. Step 4 Set ODUflex Tolerance (ppm) to 10. To set the parameter, select the LOA board in the NE Explorer and choose Configuration > WDM Interface > Advanced Attributes from the Function Tree. In the displayed window, set ODUflex Tolerance (ppm) to 10 for the ODUflex port. Step 5 Configure ODUflex-level cross-connections from LP ports to the WDM side on the LOA board. In the NE Explorer, select the NE and choose Configuration > WDM Service Management from the Function Tree. In the displayed window, click New to display the Create CrossConnection Service window. 1. Configure the first ODUflex cross-connection. See the following table to set the parameters. Parameter Level Service Type Direction Source Slot Source Optical Port
Issue 02 (2011-10-31)
Value ODUflex 3GSDI Bidirectional Subrack 0(subrack)-7-11LOA 201(ClientLP1/ClientLP1)
199
Parameter Source Optical Channel Sink Slot Sink Optical Port Sink Optical Channel
Value 1 Subrack 0(subrack)-7-11LOA 1(IN/OUT) Och:1-ODU2:1-ODUflex:1
2.
Repeat substep a in step 5 to configure the other ODUflex cross-connection. Retain the same values for the other parameters except Source Optical Port and Sink Optical Port. For the other ODUflex cross-connection, set Source Optical Port to a value in the range of 202(ClientLP2/ClientLP2) to 208(ClientLP8/ClientLP8) and Sink Optical Port to OCH:1-ODU2:1-ODUflex:2. The sink optical port number does not need to match the source optical port number.
----End
6.7 Application Scenario 5: Conversion Between One FC800 Services and One OTU2 Optical Signals
This configuration example describes how the LOA board is configured to implement conversion between one channels of FC800 optical signals and one channel of ODU2 optical signals by means of ODU0 mapping.
Issue 02 (2011-10-31)
200

Service Requirement
As shown in Figure 6-11, optical NEs A, B, C, and D form a ring network. All the NEs function as OADM stations. The service requirements are as follows: l l l User1 and User2 communicate with each other. One bidirectional OTU2 service is available between station A and station B. At station A, the LOA board receives one FC800 service and converts the service into one OTU2 service.
User 1 LOA
User 2
West B
:OADM


This section describes the service signal flow of the LOA board in ODU2 non-convergence mode. One OTU2 service is available between station A and station B. Figure 6-12 shows the service signal flow (FC800->ODU2->OTU2) at station A.

Client Side WDM Side IN/OUT-OCH:1-ODU2:1
3(RX1/TX1)-1
ODU2:1
OCH:1
IN/OUT

Prerequisite


Step 1 Set Port Working Mode to None (not for ports) for the 202(ClientLP2/ClientLP2) to 208 (ClientLP8/ClientLP8) ports and then set the parameter to ODU2 non-convergence mode (Any->ODU2->OTU2) for the 201(ClientLP1/ClientLP1) port. For details about the configuration procedure, see Configuring the Working Mode. Step 2 Set ODU Timeslot Configuration Mode to Assign random (the default value) for the LOA board. If the default value is used, skip this step. To set the parameter, select the LOA board in the NE Explorer and choose Configuration > WDM Interface > Advanced Attributes from the Function Tree. In the displayed window, set ODU Timeslot Configuration Mode to Assign random for the "1(IN/OUT)-OCh:1" port. Step 3 Set the service type of the ClientLP ports on the LOA board to FC-800 based on the service plan. For details about the configuration procedure, see 12.2 Configuring the Service Type. Step 4 Configure ODU2-level cross-connections from LP ports to the WDM side on the LOA board. In the NE Explorer, select the NE and choose Configuration > WDM Service Management from the Function Tree. In the displayed window, click New to display the Create CrossConnection Service window. 1.
Issue 02 (2011-10-31)
Configure one ODU2 cross-connection. See the following table to set the parameters.
Parameter Level Direction Source Slot Source Optical Port Source Optical Channel Sink Slot Sink Optical Port Sink Optical Channel ----End
Value ODU2 Bidirectional Subrack 0(subrack)-15-11LOA 201(ClientLP1/ClientLP1) 1 Subrack 0(subrack)-15-11LOA 1(IN/OUT) Och:1-ODU2:1
Issue 02 (2011-10-31)
203
7 Configuring WDM Services (by Station Service Package)
Configuring WDM Services (by Station Service Package)
About This Chapter

This chapter describes how to configure the TN52TOM, THA/TOA, and LOA boards in station service package mode to achieve one-click configuration. In station service package mode, multiple configurations such as configuring port working modes and service types are performed on a single NMS GUI, facilitating operations and improving configuration efficiency. The station service package mode is applicable only to some fixed scenarios.
NOTE
You can also configure the TN52TOM, THA/TOA, and LOA boards in manual station mode. In this mode, you need to perform various operations such as configuring port working modes and service types on multiple NMS GUIs. The configuration process is complex but applicable to various scenarios. For details about the manual station mode, see the related sections for manually configuring the TN52TOM, THA/ TOA, and LOA boards by station.
7.1 Overview of the Service Packages Service packages enable one-click configuration of typical services by issuing multiple configuration commands in batches, facilitating product deployment commissioning and reducing maintenance costs. The configuration commands include commands for configuring working modes, service types, cross-connections, and port types. Configuration contents vary according to boards and service packages. Currently, service packages are available to the TN52TOM, THA/TOA, and LOA boards. 7.2 Configuring Service Packages You can configure service packages for multiple boards in batches or configure the service package for each board separately.
Issue 02 (2011-10-31)
204
7.1 Overview of the Service Packages

Service packages enable one-click configuration of typical services by issuing multiple configuration commands in batches, facilitating product deployment commissioning and reducing maintenance costs. The configuration commands include commands for configuring working modes, service types, cross-connections, and port types. Configuration contents vary according to boards and service packages. Currently, service packages are available to the TN52TOM, THA/TOA, and LOA boards.
7.1.1 Service Packages for the TN52TOM Board

Configuration contents vary according to service packages. Table 7-1 lists the service packages for the TN52TOM board and the corresponding configuration contents. Table 7-1 Service packages for the TN52TOM board and the corresponding configuration contents Service Package Name Board Working Mode Port Working Mode Service Type Port Type CrossConnectio n Configurat ion Bidirectional ANY-level crossconnections are configured between ports from RX1/TX1 to RX4/TX4 and channel 1 of ports ClientLP1, ClientLP3, ClientLP5, and ClientLP7.
Tributary 4*STM-16/ OC48>4*ODU1
NonCascading mode
Port Working Mode is set to ODU1 Mode (OTU1/ Any>ODU1) for ports ClientLP1, ClientLP3, ClientLP5, and ClientLP7.
Service Type is set to STM-16/ OC48 for channel 1 of ports ClientLP1, ClientLP3, ClientLP5, and ClientLP7.
Issue 02 (2011-10-31)
205
Service Package Name
Board Working Mode
Port Working Mode
Service Type
Port Type
CrossConnectio n Configurat ion l Bidirecti onal GElevel crossconnectio ns are configure d between ports RX1/ TX1, RX3/ TX3, RX5/ TX5, and RX7/ TX7 and channel 1 of ports ClientLP 1, ClientLP 3, ClientLP 5, and ClientLP 7. l Bidirecti onal GElevel crossconnectio ns are configure d between ports RX2/ TX2, RX4/ TX4, RX6/ TX6, and RX8/ TX8 and
Tributary 8*GE>8*ODU0
NonCascading mode
Port Working Mode is set to ODU0 Mode (Any>ODU0[>ODU1]) for ports ClientLP1, ClientLP3, ClientLP5, and ClientLP7.
Service Type is set to GE for channel 1 of ports from ClientLP1 to ClientLP8.
Issue 02 (2011-10-31)
206
Board Working Mode
Port Working Mode
Service Type
Port Type
CrossConnectio n Configurat ion channel 2 of ports ClientLP 2, ClientLP 4, ClientLP 6, and ClientLP 8.
Issue 02 (2011-10-31)
207
Board Working Mode
Port Working Mode
Service Type
Port Type
CrossConnectio n Configurat ion l Bidirecti onal ANYlevel crossconnectio ns are configure d between ports from RX1/ TX1 to RX7/ TX7 and channels 1 to 7 of port ClientLP 1. l Bidirecti onal OTU1level crossconnectio ns are configure d between port RX8/ TX8 and channel 1 of port ODU1LP 1.
Tributary line 7*STM-1/ OC3>ODU1
Cascading mode
Port Working Mode is set to ODU1 tributaryline (OTU1/ Any>ODU1>OTU1) for port ClientLP1.
Service Type is set to STM-1/ OC3 for channels 1 to 4 of port ClientLP1.
Port Type is set to Line Side Color Optical Port for port RX8/TX8.
Issue 02 (2011-10-31)
208
Board Working Mode
Port Working Mode
Service Type
Port Type
CrossConnectio n Configurat ion l Bidirecti onal ANYlevel crossconnectio ns are configure d between ports from RX1/ TX1 to RX7/ TX7 and channels 1 to 4 of port ClientLP 1 and channels 5 to 7 of port ClientLP 2. l Bidirecti onal OTU1level crossconnectio ns are configure d between port RX8/ TX8 and channel 1 of port ODU1LP 1.
Tributary line 7*FE>ODU0
Cascading mode
Port Working Mode is set to ODU0 tributaryline (Any>ODU0>ODU1>OTU1) for port ClientLP1.
l Service Type is set to FE for channels 1 to 4 of port ClientLP 1 and channels 5 to 7 for port ClientLP 2.
Port Type is set to Line Side Color Optical Port for port RX8/TX8.
Issue 02 (2011-10-31)
209
Board Working Mode
Port Working Mode
Service Type
Port Type
CrossConnectio n Configurat ion l Bidirecti onal OTU1level crossconnectio ns are configure d between ports from RX1/ TX1 to RX4/ TX4 and channel 1 of ports ClientLP 1, ClientLP 3, ClientLP 5, and ClientLP 7. l Bidirecti onal OTU1level crossconnectio ns are configure d between ports from RX5/ TX5 to RX8/ TX8 and channel 1 of ports from ODU1LP
4*OTU1 REG
NonCascading mode
Port Working Mode is set to ODU1 tributaryline (OTU1/ Any>ODU1>OTU1) for ports ClientLP1, ClientLP3, ClientLP5, and ClientLP7.
Service Type is set to OTU1 for channel 1 of ports ClientLP1, ClientLP3, ClientLP5, and ClientLP7.
Port Type is set to Line Side Color Optical Port for ports from RX5/TX5 to RX8/TX8.
Issue 02 (2011-10-31)
210
Board Working Mode
Port Working Mode
Service Type
Port Type
CrossConnectio n Configurat ion 1 to ODU1LP 4.
Tributary 4*OTU1>ODU1 (reencapsulated into ODU0)
NonCascading mode
Port Working Mode is set to ODU1_AN Y_ODU0_O DU1 reencapsulati on tributaryline mode (OTU1>ODU1>Any>ODU0>ODU1>OTU1) for ports ClientLP1, ClientLP3, ClientLP5, and ClientLP7.
Service Type is set to OTU1 for channel 1 of ports ClientLP1, ClientLP3, ClientLP5, and ClientLP7.
Bidirectional OTU1-level crossconnections are configured between ports from RX1/TX1 to RX4/TX4 and channel 1 of ports ClientLP1, ClientLP3, ClientLP5, and ClientLP7.
7.1.2 Service Packages for the THA/TOA Board

Configuration contents vary according to service packages. Table 7-2 lists the service packages for the TOA board and the corresponding configuration contents. Table 7-2 Service packages for the TOA board and the corresponding configuration contents Service Package Name 8*GE->8*ODU0 Port Working Mode Port Working Mode is set to ODU0 non-convergence mode (Any->ODU0) for ports from ClientLP1 to ClientLP8. Service Type Service Type is set to GE for ports from ClientLP1 to ClientLP8.
Issue 02 (2011-10-31)
211
Service Package Name 8*STM-16/OC48>4*ODU1
Port Working Mode Port Working Mode is set to ODU1 non-convergence mode (Any->ODU1) for ports from ClientLP1 to ClientLP8.
Service Type Service Type is set to STM-16/OC48 for ports from ClientLP1 to ClientLP8.
Table 7-3 lists the service packages for the THA board and the corresponding configuration contents. Table 7-3 Service packages for the THA board and the corresponding configuration contents Service Package Name 16*GE->16*ODU0 Port Working Mode Port Working Mode is set to ODU0 non-convergence mode (Any->ODU0) for ports from ClientLP1 to ClientLP16. Port Working Mode is set to ODU1 non-convergence mode (Any->ODU1) for ports from ClientLP1 to ClientLP16. Service Type Service Type is set to GE for ports from ClientLP1 to ClientLP16. Service Type is set to STM-16/OC48 for ports from ClientLP1 to ClientLP16.
16*STM-16/OC48>8*ODU1
7.1.3 Service Packages for the LOA Board

The LOA board supports only one service package (8 x GE->8 x ODU0). The configuration contents of the service package include port working modes, service types, ODU timeslot configuration modes, and cross-connections from the client side to LP ports, and crossconnections from the LP ports to the WDM side. Table 7-4 lists the service packages for the LOA board and the corresponding configuration contents.
Issue 02 (2011-10-31)
212
Table 7-4 Service packages for the LOA board and the corresponding configuration contents Service Package Name Port Working Mode Service Type ODU Timeslot Configurati on Mode CrossConnection s from the Client Side to LP Ports Bidirectional GE-level crossconnections are configured between ports from RX1/TX1 to RX8/TX8 and channel 1 at each port from ClientLP1 to ClientLP8. CrossConnection s from the LP ports to the WDM side Bidirectional ODU0-level crossconnections are configured between ports from OCH:1ODU2:1ODU0:1 to OCH:1ODU2:1ODU0:8 and channel 1 at each port from ClientLP1 to ClientLP8.
8*GE>8*ODU0
Port Working Mode is set to ODU0 nonconvergence mode (Any>ODU0) for ports from ClientLP1 to ClientLP8.
Service Type is set to GE for ports from ClientLP1 to ClientLP8.
ODU Timeslot Configurati on Mode is set to Assign random for WDM side ports IN/ OUT-OCH: 1.
7.2 Configuring Service Packages

You can configure service packages for multiple boards in batches or configure the service package for each board separately.
Prerequisite
l l l l You are an NMS user with "Operator Group" authority or higher. The boards that support service packages must be created. No cross-connection or protection is configured on the board. Port Type is not set to Line Side Color Optical Port for the port in tributary-line integrated mode on the TN52TOM board.
Precautions
l l Existing services on a board will be interrupted if you configure service packages on the board. After a service package is configured for a board, you can change the working mode, service type, and cross-connections at a port as required. After the change, the configurations on the board will be different from the fixed configuration contents of the service package.
Issue 02 (2011-10-31)
Configuration Process
Figure 7-1 Service package configuration process
Start
Are cross-connections and protection configured for the board? Yes Delete cross-connections and protection configured on the board
No
Select the required service package
Configure WDM services in one-click mode using the service package
Are the configurations successful? Yes End
No
NOTE
The following describes how to configure a service package in two modes.
NE Batch Configuration
This mode helps you configure service packages for all involved boards in batches on the NMS. Step 1 Choose Configuration > NE Batch Configuration > Batch Service Package Configuration from the main menu. Step 2 In the Batch Service Package Configuration window, click the Board Type drop-down list to select the required board type.
Issue 02 (2011-10-31)
214
Step 3 In the Service Package window, select the name of the service package that you want to configure and click Apply To.... In the Select Board dialog box that is displayed, all subnets containing the selected board type are displayed. Select the boards where you want to configure the service package and click OK.
TIP
To configure service packages for all boards on the NMS, click the Physical Root check box.
TIP
When configuring service packages, you can choose whether creating cross-connection or not.
Step 4 Click OK in the Confirm dialog box that is displayed asking you "Board services will be interrupted if you configure a service package. Are you sure you want to continue?" The Confirm dialog box will be displayed again for confirmation. Click OK.
Issue 02 (2011-10-31)
215
Step 5 The Configuring Service Package for Boards dialog box is displayed to show the operation progress. After the operation is completed, the Operation Result dialog box is displayed. ----End
Separate Board Configuration

This mode helps you to configure a service package for a separate board. Step 1 In the NE Explorer, select the required board and choose Configuration > Service Package from the Function Tree. Step 2 Select a service package from Service Package on the right and click Apply. Step 3 Click OK in the Confirm dialog box that is displayed asking you "Board services will be interrupted if you configure a service package. Are you sure you want to continue?" The Confirm dialog box will be displayed again for confirmation. Click OK. Step 4 The Configuring Service Package for Boards dialog box is displayed to show the operation progress. After the operation is completed, the Operation Result dialog box is displayed. ----End
Operation Result
l l If "Operation succeeded" is displayed in the Operation Result dialog box, click Close to complete the operation. If "Operation failed" or "Operation partially succeeded" is displayed in the Operation Result dialog box, click Details to view the cause. The possible causes are listed in the following table. Handle the problem based on the displayed cause. Cause Cross connection already exists Invalid port type Solution Delete all cross-connections on the board corresponding to the value of Object. Change the port type of all ports on the board corresponding to the value of Object to client-side ports.
Configuration Verification
After a service package is completed, verify that the service package is successfully configured. Step 1 In the NE Explorer, select the board where the service package is configured and choose Configuration > WDM Interface from the Function Tree. Verify that the value of Service Type is correctly set for the required ports according to the configured service package. Step 2 In the NE Explorer, select the board where the service package is configured and choose Configuration > Working Mode from the Function Tree. Verify that the values of Board Working Mode and Port Working Mode are correctly set according to the configured service package.
NOTE
Verify the value of Board Working Mode only for the TN52TOM board.
Step 3 If the board is TN52TOM, select the required NE in the NE Explorer and choose Configuration > WDM Service Management from the Function Tree. Click the WDM CrossIssue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 216
Connection Configuration tab and verify that the WDM cross-connections are correctly configured according to the configured service package. Step 4 If the board is TN52TOM and the configured service package is Tributary line 7*STM-1/OC3>ODU1, Tributary line 7*FE->ODU0, or 4*OTU1 REG, select the NE where the service package is configured in the Main Topology. Double-click the NE icon to open the NE panel. In the NE panel, select and right-click the required board, and then choose Path View from the shortcut menu that is displayed. Right-click the required port and choose Modify Port from the shortcut menu that is displayed. Verify that the value of Type is correctly set according to the configured service package. ----End
Issue 02 (2011-10-31)
217
8 Configuring WDM Services (by Trail)
Configuring WDM Services (by Trail)
About This Chapter

You can configure WDM services in end-to-end mode by searching for trails and creating trails at different layers. In addition, the NMS provides the signal flow diagram that visually displays the signal flow and the transmission media layer route of trails. This facilitates operations and improves the maintenance efficiency. 8.1 WDM Trail The concept, type, and relevant information about trails are described here. 8.2 Creating OCh Trails by Trail Search After you create fiber connections and configure services for WDM equipment on the U2000, the trail information does not exist in the network layer of the U2000. To manage OCh trails, you need to search for the data of cross-connections and fiber connections over the network to generate end-to-end WDM trails at the network layer of the U2000. 8.3 Configuration Example After you create fibers and configure services for WDM equipment on the U2000, the trail information does not exist in the network layer of the U2000. To manage WDM trails, you need to search for the data of cross-connections and fiber connections over the network to generate end-to-end WDM trails at the network layer of the U2000. 8.4 Parameters: End to End Service Configuration In this user interface, you can configure WDM trails.
Issue 02 (2011-10-31)
218
8.1 WDM Trail

The concept, type, and relevant information about trails are described here. Currently, the NMS provides the following OTN trail modules that comply with ITU-T G.872: l l l l l l l l l l Client trail ODUk trail: optical channel data unit (ODUk) trail OTUk trail: optical channel transport unit (OTUk) trail OCh trail: optical channel trail OMS trail: optical multiplexing section trail OTS trail: optical transmission section trail OSC trail: optical supervisory channel (OSC) trail The first six types are related to services, and the OSC trail is related to supervisory signals. The OTS trail cannot be deleted from the NMS. You must delete the fiber connection before deleting the OTS trail. The rate level varies with the value of "k" in ODUk/OTUk. For details, see Table 8-1. ODU5G/OTU5G is a level customized by Huawei.
Table 8-1 ODUk rate level Trail Level ODU0 ODU1/OTU1 ODU5G/OTU5G ODU2/OTU2 ODU3/OTU3 ODUflex Rate (Gbit/s) 1.25 2.5 5 10 40 1.25 to 10 (n x 1.25)
Trail Module
Figure 8-1 and Figure 8-2 illustrate the relationship and location of the trails.
Issue 02 (2011-10-31)
219
Figure 8-1 Trail

Client ODUk OTUk OCh OMS
OTS
:OTU
:MUX
:DMUX
:OA
NOTE
In the case of the NG WDM equipment, an OMS trail terminates at the MUX and DMUX cards.
Figure 8-2 OSC Trail

OSC Trail OSC Trail
TM
RM
TM
RM
OTM
OLA
OTM
:OSC
:FIU
ODUk Trail
Different from other trails, an ODUk/OTUk sets the source and sink at the internal ports of an OTU card, a tributary card or a line card. Figure 8-3 displays a typical ODUk trail module whose source and sink are set on the internal ports of tributary ports or of line cards.
Issue 02 (2011-10-31)
220
Figure 8-3 ODUk (k = 0, 1, 2, ...) trail

TQS STM-16 RX1 ODU0 LP1 O D U 1 NS2 ODU1 O D U 2 O T U 2 NS2 ODU1 TQS LP1 O D U 1 ODU0 STM-16 TX1
OUT
IN
O T U 2
O D U 2
OCh Trail OTU2 Trail ODU2 Trail ODU1 Trail ODU0 Trail Client Trail
Electrical Signal Optical Signal
In the case of the client-side service whose rate is less than 1.25 Gbit/s, an ODU0 trail is added, as shown in Figure 8-4. Figure 8-4 ODUk (k = 0, 1, 2, ...) trail
52TOM GE RX1
ODU0 LP1 O D U 1
52NS2
ODU1
52NS2
ODU1
52TOM
LP1 O D U 1 ODU0
GE TX1
O D U 2
O T U 2
OUT
IN
O T U 2
O D U 2
OCh Trail OTU2 Trail ODU2 Trail ODU1 Trail ODU0 Trail Client Trail
Electrical Signal Optical Signal
NOTE
The service rate of an ODUflex is in the range of 1.25 Gbit/s to 10 Gbit/s. Therefore, an ODUflex trail is a trail ranging from ODU0 to ODU2.
Issue 02 (2011-10-31)
221
Inverse Multiplexing Trail

The rate of the client layer of an inverse multiplexing trail is greater than the rate of the server layer. Hence, an inverse multiplexing client trail needs multiple trails to serve as its server layer. Currently, you can only search for an inverse multiplexing trail, but you cannot create an endto-end inverse multiplexing trail. An inverse multiplexing client trail can take an ODU1 or ODU2 trail as the server trail. That is, an inverse multiplexing client trail cannot take ODU1 and ODU2 trails as the server trails at the same time.
40G inverse multiplexing trail model

The transmission rate of a single wavelength is 40G, but a single wavelength cannot be used for long-distance transmission due to an optical layer index (such as dispersion) restriction. In a 40G inverse multiplexing transmission scheme, a 40G signal is converted to four 10G ODU2 signals, each of which uses one wavelength. This is equal to four 10G signals on the line side and lowers the optical layer index requirement. Figure 8-5 shows the inverse multiplexing trail model of the TSXL card. You cannot dynamically adjust the bandwidth of STM-256 or OC768 services whose rate is 40G. Hence, you can search for a client trail only after you configure four ODU2 trails. If you configure only one, two or three ODU2 trails, services are unavailable and you fail to search for the client trail. Figure 8-5 40G Inverse Multiplexing Trail
10G Inverse Multiplexing Trail Model

The TDX card is a 10G inverse multiplexing tributary card that has two individual transmission paths. Each path inversely multiplexes a 10G service to multiple ODU1 signals, which are crossconnected to a line card for transmission. The 10G service uses any or all of the four ODU1 signals according to bandwidth status. When the 10G service does not use all of the four ODU1 signals, the 10G service share an ODU2 trail with other ODU1 signals. This saves line resources.
Figure 8-6 shows the inverse multiplexing trail model of the IP3 port on the TDX card. A 10G service is an Ethernet service for which you can dynamically adjust bandwidth. The server layer allows one, two, three or four ODU1 trails. Hence, the client trail that you search out is of different rate levels. Figure 8-6 10G inverse multiplexing trail
8.2 Creating OCh Trails by Trail Search

After you create fiber connections and configure services for WDM equipment on the U2000, the trail information does not exist in the network layer of the U2000. To manage OCh trails, you need to search for the data of cross-connections and fiber connections over the network to generate end-to-end WDM trails at the network layer of the U2000.
Prerequisite
l l You are an NMS user with "Operator Group" authority or higher. Fiber connections must be created correctly for the WDM equipment.
Precautions
l If certain cross-connections exist, you can create an optical-layer trail by using any of the following methods: Delete the original cross-connection and create the optical-layer trail by using the trail function. This method affects services. Complement cross-connections on NEs and search for the trail. l You can create only single-NE optical cross-connections from the AM port to the OUT port of the RMU9 board, from the IN port to the DM port of the RDU9 board, from the AM port to the OUT port of the WSMD4/WSMD2 board and from the IN port to the DM port of the WSMD4/WSMD2 board. In this case, the board optical cross-connection is not supported. These single-NE optical cross-connections do not affect services. You need to create such single-NE optical cross-connections and search for trails if you want to manage the services transmitted in the cross-connections by using the trail management function.
Issue 02 (2011-10-31)

U2000
Procedure on the U2000

Step 1 In the Main Topology view, choose Service > WDM Trail > Search for WDM Trail from the Main Menu. Step 2 Under Advanced settings, set the search policies.
NOTE
In the mode of searching by subnet, the selected subnet range must be independent from the networking aspect. That is, no fiber connection exists between the selected subnet range and the area that is beyond the selected subnet range.
Step 3 Click Next to begin to search for trails. The U2000 takes some time to return the results, depending on the number of services.
NOTE
l If there are cross-connections that are collisions and these cross-connections cannot form end to end trails, the U2000 shows the conflicting trails after you perform the search operation. l The principles of verifying a conflict trail are as follows: The networking changes. The trail may cause interruption of service flow. For example, the key information of the trail, including deleting a crossconnection or fiber, is verified.
Step 4 Optional: Click Next to view the conflicting trail information. If you want to set a trail management flag, check the Management Flag check box or right-click it and select the management flag.
NOTE
Skip this step if the policy of automatically creating trails after searching is selected in Step 2.
Step 5 Click Next to view all discrete services in the network.

NOTE
If Step 4 is executed, the U2000 deletes trails that do not have the management flag from the network layer. This does not affect services of the actual NE or the data of an individual NE on the U2000.
Step 6 After the search is complete, click Finish. ----End
Follow-up Procedure
Step 1 In the Main Topology view, choose Service > WDM Trail > Manage WDM Trail from the Main Menu. Step 2 On the Basic Settings tab, select the level of the service being queried for Level. Step 3 Optional: On the Subnet Settings tab, select the subnet being queried. Step 4 Click Filter All. In Manage WDM Trail, check whether the trails on the subnet being queried are consistent with the network design. ----End
8.3 Configuration Example

After you create fibers and configure services for WDM equipment on the U2000, the trail information does not exist in the network layer of the U2000. To manage WDM trails, you need to search for the data of cross-connections and fiber connections over the network to generate end-to-end WDM trails at the network layer of the U2000.

This section describes how to configure end-to-end GE services on a ring network.
Service Requirements
On the network shown in Figure 8-7, ONEs A, B, C, and D form a ring network. All the NEs function as OADM stations. The service requirements are as follows: l l l User1 and User2 communicate with each other. One bidirectional OTN service is configured between station A and station C. One GE service is added and dropped for User1 and User2 each. ODUk SNCP protection is configured.
Figure 8-7 Network diagram of end-to-end services

User1
21-TOM 04- 16NQ2 NQ2
NMS
W 16NQ2 04NQ2 E
A B C D
E 04NQ2 16NQ2 W
Working service route Protection service route OADM
16- 04NQ2 NQ2 21-TOM
User2
Issue 02 (2011-10-31)
225
Boards Configured
Two NQ2 boards and one TOM board must be configured at stations A and C each. Two NQ2 boards must be configured at stations B and D each.

This section describes the service signal flow of end-to-end GE services. One OTN service is configured between NEs A and C. Figure 8-8 shows the service signal flow between station A and station C. Figure 8-8 Unidirectional service at each station
TOM 3(RX1/TX1) 4(RX2/TX2) 5(RX3/TX3) 6(RX4/TX4) 7(RX5/TX5) 8(RX6/TX6) 9(RX7/TX7) 10(RX8/TX8) 201(ClientLP1/Cli entLP1)-1 203(ClientLP3/Cli entLP3)-1 205(ClientLP5/Cli entLP5)-1 207(ClientLP7/Cli entLP7)-1 A NQ2 1(IN1/ OUT1) 2(IN2/ OUT2) 3(IN2/ OUT2) 4(IN2/ OUT2) 71(ODU2L P/ODU2LP) 72(ODU2L P/ODU2LP) 73(ODU2L P/ODU2LP) 74(ODU2L P/ODU2LP) 51(ODU1L P/ODU1LP) 52(ODU1L P/ODU1LP) 53(ODU1L P/ODU1LP) 54(ODU1L P/ODU1LP) B NQ2 1(IN1/ OUT1) 2(IN2/ OUT2) 3(IN2/ OUT2) 4(IN2/ OUT2) 71(ODU2L P/ODU2LP) 72(ODU2L P/ODU2LP) 73(ODU2L P/ODU2LP) 74(ODU2L P/ODU2LP) 51(ODU1L P/ODU1LP) 52(ODU1L P/ODU1LP) 53(ODU1L P/ODU1LP) 54(ODU1L P/ODU1LP) C 201(ClientLP1/Cli entLP1)-1 203(ClientLP3/Cli entLP3)-1 205(ClientLP5/Cli entLP5)-1 207(ClientLP7/Cli entLP7)-1 TOM 3(RX1/TX1) 4(RX2/TX2) 5(RX3/TX3) 6(RX4/TX4) 7(RX5/TX5) 8(RX6/TX6) 9(RX7/TX7) 10(RX8/TX8) 51(ODU1L P/ODU1LP) 52(ODU1L P/ODU1LP) 53(ODU1L P/ODU1LP) 54(ODU1L P/ODU1LP) NQ2 71(ODU2L P/ODU2LP) 72(ODU2L P/ODU2LP) 73(ODU2L P/ODU2LP) 74(ODU2L P/ODU2LP) 1(IN1/ OUT1) 2(IN2/ OUT2) 3(IN2/ OUT2) 4(IN2/ OUT2) 51(ODU1L P/ODU1LP) 52(ODU1L P/ODU1LP) 53(ODU1L P/ODU1LP) 54(ODU1L P/ODU1LP) NQ2 71(ODU2L P/ODU2LP) 72(ODU2L P/ODU2LP) 73(ODU2L P/ODU2LP) 74(ODU2L P/ODU2LP) 1(IN1/ OUT1) 2(IN2/ OUT2) 3(IN2/ OUT2) 4(IN2/ OUT2)
:Client-side services
:WDM-side services
:Vritual channel
Issue 02 (2011-10-31)
226
l l
At station A: Use the Rx1/Tx1 optical port on the TN52TOM board at station A to add a service. At station C: Use the Rx1/Tx1 optical port on the TN52TOM board at station C to drop a service.

After searching for the relevant trail information on the U2000, you can create OCh, ODUk, or client trails by specifying the sources and sinks of the trails. This section describes how to configure an end-to-end GE service between NEs A and C.
Prerequisite
l l l l You must be an NM user with "NE administrator" authority or higher. A license for trail management must be available. The OCh server trail must be searched out. The physical and logical fiber connections between and inside all relevant stations must be established correctly.

U2000
Precautions
NOTE
The value of TN52TOM Board Mode is NON-Cascading mode by default. In this case, the 201 (ClientLP1/ ClientLP1) and 205(ClientLP5/ ClientLP5) ports can access a maximum of four services, and the 203 (ClientLP3/ ClientLP3) and 207 (ClientLP7/ ClientLP7) ports can access a maximum of two services.
NOTE
A ClientLP port can access only one service that has a rate higher than 1.25 Gbit/s, and this service can be configured in only the first channel of the ClientLP port. The total rate of services accessed by a ClientLP port must be equal to or lower than 2.5 Gbit/s. The client-side eight pairs of optical ports can access services at a maximum rate of 10 Gbit/s. The client-side ports can be grouped as required.
ODUk SNCP is classified into three types: SNC/I, SNC/N, and SNC/S. The difference among the three types is that they have different monitoring abilities and therefore are triggered by different conditions. l SNC/I (inherent monitoring): inherent monitoring; the trigger condition is the state of overheads in the SM section. When there is neither need for ODU end to end protection nor need for TCM subnet application, select SNC/I. SNC/S (sub-layer monitoring): sub-layer monitoring; the trigger condition is the state of overheads in the SM and TCM sections. When there is no need for ODU end to end protection but there is need for TCM subnet application, select SNC/S.
Issue 02 (2011-10-31)
SNC/N (non-intrusive monitoring): non-intrusive monitoring; the trigger condition is the state of overheads in the SM, TCM or PM sections. When there is need for ODU end to end protection, select SNC/N.
For details on ODUk SNCP protection, see the Feature Description.

Step 1 Configure board attributes. 1. Configure port attributes of the TN52TOM boards in slot 21 at stations A and C. l Set Board Working mode to Non-cascading. For details, see Configuring the Working Mode. l Set Service Type of TOM-201 (ClientLP1/ClientLP)-1 to GE. For details, see 12.2 Configuring the Service Type. 2. Configure port attributes of the NQ2 boards in slots 4 and 16 at stations A, B, C, and D. l Set Configuring Non-Intrusive Monitoring of NQ2-51(ODU1LP1/ODU1LP)ODU1-1 to ENABLED. For details, see 12.14 Configuring Non-Intrusive Monitoring. l Set Service Mode of NQ2-51(ODU1LP1/ODU1LP)-ODU1 to ODU1. For details, see 12.3 Configuring the Service Mode.
CAUTION
l If you need to change Service Mode of a board, deactivate the services on the board first. Note that deactivation interrupts the services. l For a 51NQ2 board, the default value of Service Mode is ODU1. For a 52NQ2 board, the default value of Service Mode is AUTO. You can change the value to ODU1 or retain the default value. Step 2 Create ODU1 server trails. 1. 2. Choose Service > WDM Trail > Create WDM Trail from the Main Menu. Make the following settings in the Create WDM Trail window: l Level: ODU1 l Direction: Bidirectional l Rate: ODU1 3. Double-click NE A in the Physical Root. Then, select the TOM board in slot 21 in the displayed Select Board Port window and make the following settings: l Available Timeslots/Port: 201(ClientLP1) l Channel: 1 4. 5. Click OK. Double-click NE C in the Physical Root. Then, select the TOM board in slot 21 in the displayed Select Board Port window and make the following settings: l Available Timeslots/Port: 201(ClientLP1) l Channel: 1
6. 7. 8.
Click OK. Check values of Source and Sink in Route Information and ensure that the route is the design route. Optional: Click a server tail between the source and sink NEs, and select the included server trail in the displayed dialog box. You can click the trail again, and cancel the selected server trail in the displayed dialog box. Optional: Double-click the other NE in the subnet to specify the NE that the route cannot pass through. The selection. sign is shown on the NE. Double-click the NE again to cancel your
9.
10. Optional: Click Specify Route Channel and the Specify Route Channel dialog box is displayed. Select a path and click OK. 11. Click the Protection Setting tab, and set the SNCP protection route. l Right-click the NEA that dual feeds services and choose Set Dual-Feed Point from the shortcut menu. In the upper left corner of the NEA icon, is displayed.
l Right-click the NEC that dual feeds services and choose Set Selective-Receiving Point from the shortcut menu. In the upper left corner of the NEC icon, is displayed.
12. Right-click on the Node list window and choose Set SNCP Parameter. In the displayed Set SNCP Parameter window, set SNCP Type of NEs A and C to SNC/N. Click OK. 13. Click the General Attributes set the basic trail attributes, including the name and ID. 14. Click Apply. A dialog box is displayed, indicating that the operation is successful. Click Close.
NOTE
Select the Activate the trail check box. The trail is then delivered to the NE layer after it is created successfully. Otherwise, the trail configuration data is saved only on the U2000.
Step 3 Create client trails. 1. 2. Choose Service > WDM Trail > Create WDM Trail from the Main Menu. Make the following settings in the Create WDM Trail window: l Level: Client l Direction: Bidirectional l Rate: GE 3. Double-click NE A in Physical Root. Then, select the TOM board in slot 21 in the displayed Select Board Port window and make the following settings: l Available Timeslots/Port: 3(RX1/TX1) l Channel: 1 4. 5. Click OK Double-click NE C in Physical Root. Then, select the TOM board in slot 21 in the displayed Select Board Port window and make the following settings: l Available Timeslots/Port: 3(RX1/TX1) l Channel: 1 6.
Issue 02 (2011-10-31)
Click OK.
7. 8.
Click the General Attributes tab to set the basic trail attributes, including the name and ID. Click Apply. A dialog box is displayed, indicating that the operation is successful. Click Close.
NOTE
Select the Activate the trail check box. The trail is then delivered to the NE layer after it is created successfully. If you do not select the Activate the trail check box, the trail configuration data is saved only on the U2000.
NOTE
The preceding configuration procedure is described based on the scenario of ODU1 SNCP protection. In this scenario, cross-connect and pass-through services of the ODU1 level and optical ports 51-54 on the line board must be configured. If ODU0 SNCP protection is configured, cross-connect and pass-through services of the ODU0 level and optical ports 161-176 on the line board must be configured. If no SNCP protection is configured, you do not need to create ODUk server trails but directly create client trails.
----End
Result
Step 1 Choose Service > WDM Trail > WDM Trail Management from the Main Menu and select the proper filter criteria for the trails.
TIP
You can filter other trails based on the source and sink of the new trail.
Step 2 In the WDM Trail Management window, verify that the trail is correctly created. ----End
8.4 Parameters: End to End Service Configuration

In this user interface, you can configure WDM trails. Parameters Level Value OCh, ODU0, ODU1, ODU2, ODUflex, Client For example: GE Description Specifies the level of a trail. Click A.32 Rate (WDM Trail Creation) for more information. Selects the service type. Click A.30 Level (WDM Trail Creation) for more information. Direction Bidirectional, Unidirectional Selects the service direction. Click A.31 Direction (WDM Trail Creation) for more information. When checked, you can create ASONWDM trail, if the trail passes through the ASON domain.
Rate
SPC First
Checked, Unchecked
Issue 02 (2011-10-31)
230
Parameters OVPN Customer
Value For example, Shared Resource
Description Indicates the OVPN customer of the WDM ASON trail. Click A.35 OVPN Customer (ASON Trail Management) for more information.
NOTE This parameter is displayed only when you set Level to OCh and Direction to Bidirectional, and check SPC First.
Source
For example: NE6shelf0-21-52TOM-3 (RX1/TX1)-1 For example: NE7shelf0-21-52TOM-3 (RX1/TX1)-1 Explicit Link -
Selects the source of the route. Click A.33 Source (WDM Trail Creation) for more information. Selects the sink of the route. Click A.34 Sink (WDM Trail Creation) for more information. Specifies the explicit server link for the trail to be created. Click A.25 Explicit Link for more information.
Sink
Trail Setting
Explicit Node
For example: NE7
Specifies the explicit NE for the trail to be created. Click A.26 Explicit Node for more information.
Excluded Node
For example: NE7
Indicates the excluded node of the trail. Click A.27 Excluded Node for more information.
Platinum Service Group Route Constraint AutoCalculatio n
Indicates the reference trail selected when the platinum service of the trail is created. Indicates the calculation result of available trails. Calculates routes automatically when you select this parameter. Click A.28 Auto-Calculation for more information.
Source-Sink-Channel Occupied-Working/ Protection Checked, Unchecked
Protectio n Setting
Node list
Dual-Fed Point
To set or cancel the dual-fed point, rightclick the NE on the topology and select Set Dual-Feed Point or Cancel DualFeed Point from the shortcut menu.
Issue 02 (2011-10-31)
231
Parameters
Value Selective-Receiving Point
Description To set or cancel the selective-receiving point, right-click the NE on the topology and select Set Selective-Receiving Point or Cancel Selective-Receiving Point from the shortcut menu. Specifies the SNCP parameter of the dual fed point. Specifies the SNCP parameter of the selective receiving point. Specifies the SNCP type. For example, SNC/N. Specifies the OTN level. For example, TCM1. Indicates the calculation result of available trail. Selects the customer that the trail belongs to. Specifies the order number of the trail. Adds the remarks. Specifies the trail ID. Indicates the source of the server layer trail. Indicates the sink of the server layer trail. Indicates the name of the server layer trail. Indicates the channel that the trail occupies. Indicates the route description.
SNCP Parameter of Dual Fed Point SNCP Parameter of Selective Receiving Point Set SNCP Parameter SNCP Type OTN Level Route Informatio n General Attribute s Customer Order No Remarks ID Specify Route Channel Source Sink Server Layer Trail Name Server Layer Trail Route Descriptio n Select the included server trail Source/ Sink Level Trail Name
Issue 02 (2011-10-31)
Source-Sink-Channel Occupied-Working/ Protection Customer name Character string Character string For example: 1 For example: NE6 For example: NE7 Source-Sink-Trail Level-Trail NO For example: 5 Negative Working, Positive Working For example: NE6shelf0-21-52TOM-3 (RX1/TX1)-1 For example: OCh
Indicates the source/sink of a server trail.
Indicates the level of the server trail.
Source NE-Sink NEIndicates the name of a server trail. Trail Level-Trail Suffix
232
Parameters NE List Route Descriptio n Wavelengt h Activate the trail Copy after Creation
Value For example: NE6;NE7 Positive, Negative
Description Indicates the NE that a server trail passes through. Indicates the route information.
For example: 1\1560.61 \192.100 Checked, Unchecked -
Specifies the optical channel occupied by the trail. Applies trail configuration to the NE so that the service takes effect on the NE. Creates multiple trails whose share the same routes but have different channels. Click A.29 Copy after Creation for more information.
Set Optical Power After Creation
Switches to the Query Relevant Optical Power window to view the relevant optical power.
Issue 02 (2011-10-31)
233
9 Configuring SDH Services
9
About This Chapter
Configuring SDH Services
The OptiX OSN 8800 supports SDH boards. Hence, the OptiX OSN 8800 can be interconnected to the SDH equipment. When you configure an SDH service for the OptiX OSN 8800, you can configure the SDH service on a per-NE basis. In this way, you can specify the timeslot and route for the service on each NE. 9.1 SDH Service Configuration Process This topic describes the process of configuring SDH services. The process consists of deploying a network, configuring the source NE, configuring the sink NE, configuring a pass-through NE, and verifying services. 9.2 SDH Service Overhead This topic describes the SDH overheads, including J0, J1, and C2, that the OptiX OSN 8800 supports. 9.3 Configuring Services on the Non-Protection Ring Configure the protection subnet and the services on the non-protection ring separately. It is recommended that you configure the protection subnet before configuring services on the nonprotection ring. 9.4 Configuring 1+1 Linear MSP Services In the case of 1+1 linear MSP, the source NE dual-feeds service signals to the working and protection lines. In normal conditions, the sink NE selectively receives the services from the working line. When the working line is faulty, the sink NE selectively receives the services from the protection line. 9.5 Configuring the Two-Fiber Bidirectional MSP Ring Services To configure the two-fiber bidirectional MSP services, you need to create the MSP subnet protection and MSP services. There is no requirement for the sequence of creating the MSP subnet protection and MSP services. 9.6 Configuring the SNCP Tangent Ring Services With respect to the physical topology, the SNCP tangent ring is similar to the MSP tangent ring. It can protect services on the two SNCP rings when one fiber between any adjacent stations on each ring is cut. For service configuration of the SNCP tangent ring, you should focus on the tangent node. Each bidirectional service that passes by the tangent node must be configured with four pairs of protection groups.
9.7 Parameter
Issue 02 (2011-10-31)
235
9.1 SDH Service Configuration Process

This topic describes the process of configuring SDH services. The process consists of deploying a network, configuring the source NE, configuring the sink NE, configuring a pass-through NE, and verifying services. Figure 9-1 shows the process of configuring SDH services. Figure 9-1 SDH service configuration process
Required Optional Deploy a network Configure the source NE Configure the sink NE Configure passthrough NEs Maintenance for SDH services Verify services
Create and configure NEs
Querying the NE Software Version
Querying the NE Software Version
Querying the NE Software Version Create SDH services
Change SDH services
Test SDH services
Create fibers
Configure the communication
Querying the Capacity of Lower Order CrossConnections
Querying the Capacity of Lower Order CrossConnections
Delete SDH services
Set the NE time
Create SDH services Create SNCP services
Create SDH services Create SNCP services
Configure clocks
Configure the orderwire Configure the protection
NOTE
l In the landscape orientation of the configuration flow chart, there are six main phases of SDH service configuration process. They are deploying a network, configuring the source NE, configuring the sink NE, configuring a pass-through NE, maintenance for SDH services, and verifying services. l The portrait orientation of the flow chart shows the relationships between operation tasks in each phase.
9.2 SDH Service Overhead

This topic describes the SDH overheads, including J0, J1, and C2, that the OptiX OSN 8800 supports.
Issue 02 (2011-10-31)
236
9.2.1 Trace Byte

Trace bytes are used to trace the connection status between the receive end and transmit end. The trace bytes can be used to detect and solve problems in advance to prevent transmitted services from being affected. This decreases the network restoration time to a great extent.
J0 Byte
The J0 byte is located at line 1 and column (6N+1) in a STM-N frame. The J0 byte is the regenerator section trace byte. The J0 byte is continuously to carry an access point identifier of a regenerator section, according to which the receive end verifies the continuous connection to the intended transmit end.
J1 Byte
The J1 byte is the first byte in a virtual container (VC) and its location is indicated by the relevant pointer. The J1 byte is the higher order path trace byte. The J1 byte is used to repetitively transmit the access point identifier of a higher order path (HO APId) so that the receive end of the path can verify its continuous connection to the intended transmit end. The J1 byte can be used to detect and solve problems in advance to prevent transmitted services from being affected. This decreases the network restoration time to a great extent.
9.2.2 Signal Label Byte

This topic describes the locations and functions of the signal label bytes C2 in SDH overheads.
C2 Byte
The C2 byte is the third byte in a VC. C2 is the signal label byte, which is used to indicate the multiplexing structure of VC frames and the payload property. The sent C2 byte must match the received C2 byte. If C2 mismatch occurs, an HP_SLM alarm is generated in the corresponding VC4 path at the local end.
9.3 Configuring Services on the Non-Protection Ring

Configure the protection subnet and the services on the non-protection ring separately. It is recommended that you configure the protection subnet before configuring services on the nonprotection ring.

You can configure a non-protection ring if the services on the ring do not need to be protected. In this case, all the timeslots on the ring can carry services. Figure 9-2 shows a non-protection ring that consists of four NEs. NE1, NE2, NE3 and NE4 are the OptiX OSN 8800. In this example, the source NE NE1 and the sink NE NE3 use the SLO16 boards to add or drop services, and use the SLQ64 boards to transmit SDH services. NE2 and NE4 use the SLQ64 boards to pass through the SDH services.
Figure 9-2 Networking diagram of a non-protection
18-SLO16 17-SLQ64
West
East
East 01-SLQ64 17-SLQ64 West NE2
NE1 Two-fiber bidirectional non-protection ring NE3 East West 01-SLQ64 NE4 17-SLQ64
18-SLO16 17-SLQ64
: OptiX OSN 8800
9.3.2 Signal Flow and Timeslot Allocation

To configure services on the non-protection ring, you need to plan the traffic direction and timeslot allocation for the services on the non-protection ring. Figure 9-3 shows the signal flow and timeslot allocation. In this example, five STM-1 services are added to or dropped from the source NE NE1 and the sink NE NE3, and the STM-1 services pass through the intermediate NE NE2.
Issue 02 (2011-10-31)
238
Figure 9-3 Signal flow and timeslot allocation of the services on the non-protection ring
NE1: 5xSTM-1 VC4-1:1-5 17-SLQ64 18-SLO16
NE2: 01-SLQ64 17-SLQ64 VC4-1:1-5 Pass-through service
NE1
NE2
Two-fiber bidirectional non-protection ring
NE4
NE3
NE3: VC4-1:1-5 5xSTM-1

: Traffic direction : Line board
17-SLQ64 18-SLO16

Configuration of the services on the non-protection ring is not related to the configuration of the protection subnet. To configure the services on the non-protection ring, configure the SDH services on the source and sink NEs and the pass-through services on the intermediate NEs if the protection subnet is already created.
Prerequisite
The physical topology of the network must be created. The NEs, boards, and fibers must be created on the U2000. The created protection subnet must be consistent with the actual network topology.


Step 1 Configure an SDH service for the source NE NE1. 1. 2. In the NE Explorer, select NE1 and choose Configuration > SDH Service Configuration from the Function Tree. Click Create in the lower-right pane and the Create SDH Service dialog box is displayed. Set the required parameters, and then click OK. Click Close in the Operation Result dialog box that is displayed. Parameter Value in This Example VC4 Bidirectiona l 18N4SLO16-1 (SDH-1) Description
Level Direction
In this example, STM-1 services are configured. Hence, Level of the STM-1 services is set to VC4. In this example, the services are transmitted and received over the same path. That is, the services are Bidirectional services. In this example, the SLO16 board in slot 18 of NE1 is configured as the source board. In this example, five STM-1 services are configured between NE1-NE3. Hence, the source VC4 is not configured. In this example, five STM-1 services are configured between NE1-NE3. Hence, the source timeslot range is configured as 1-5. In this example, the SLQ64 board in slot 17 of NE1 is configured as the sink board. In this example, five STM-1 services are configured between NE1-NE3. Hence, the sink VC4 is not configured. In this example, five STM-1 services are configured between NE1-NE3. Hence, the sink timeslot range is configured as 1-5. -
Source Slot
Source VC4
Source Timeslot Range (e.g. 1,3-6) Sink Slot
1-5
17N4SLQ64-1 (SDH-1) -
Sink VC4
Sink Timeslot Range (e.g. 1,3-6) Activate Immediately
1-5
Yes
Step 2 Configure an SDH service for the sink NE3. See Step Step 1 to configure the SDH service on NE3. Set the following parameters.
Issue 02 (2011-10-31)
240
Parameter
Value in This Example VC4 Bidirectional
Description
Level Direction
In this example, STM-1 services are configured. Hence, Level of the STM-1 services is set to VC4. In this example, the services are transmitted and received over the same path. That is, the services are Bidirectional services. In this example, the SLO16 board in slot 18 of NE3 is configured as the source board. In this example, five STM-1 services are configured between NE1-NE3. Hence, the source VC4 is not configured. In this example, five STM-1 services are configured between NE1-NE3. Hence, the source timeslot range is configured as 1-5. In this example, the SLQ64 board in slot 17 of NE3 is configured as the sink board. In this example, five STM-1 services are configured between NE1-NE3. Hence, the sink VC4 is not configured. In this example, five STM-1 services are configured between NE1-NE3. Hence, the sink timeslot range is configured as 1-5. -
Source Slot
18N4SLO16-1 (SDH-1) -
Source VC4
1-5
17N4SLQ64-1 (SDH-1) 1-5
Sink VC4 Sink Timeslot Range (e.g. 1,3-6) Activate Immediately
Yes
Step 3 Configure pass-through services on the intermediate NE NE2. 1. 2. Select NE2 from the NE Explorer, and then choose Configuration > SDH Service Configuration from the Function Tree. Click Create on the lower-right pane to display the Create SDH Service dialog box. Set the parameters that are required, and then click OK. Click Close in the Operation Result dialog box that is displayed. Parameter Value in This Example VC4 Description
Level
In this example, STM-1 services are configured. Hence, Level of the STM-1 services is set to VC4.
Issue 02 (2011-10-31)
241
Parameter
Value in This Example Bidirectiona l 01N4SLQ64-1 (SDH-1) -
Description
Direction
In this example, the services are transmitted and received over the same path. That is, the services are Bidirectional services. In this example, the SLQ64 board in slot 01 of NE2 is configured as the source board. In this example, five STM-1 services are configured between NE1-NE3. Hence, the source VC4 is not configured. In this example, five STM-1 services are configured between NE1-NE3. Hence, the source timeslot range is configured as 1-5. In this example, the SLQ64 board in slot 17 of NE2 is configured as the sink board. In this example, five STM-1 services are configured between NE1-NE3. Hence, the sink VC4 is not configured. In this example, five STM-1 services are configured between NE1-NE3. Hence, the sink timeslot range is configured as 1-5. -
Source Slot
Source VC4
1-5
17N4SLQ64-1 (SDH-1) -
Sink VC4
1-5
Yes
Step 4 Check whether the services are configured correctly. For details, see Verifying the Correctness of the Service Configuration. Step 5 Enable the performance monitoring function of the NEs. For details, see Setting Performance Monitoring Parameters of an NE. Step 6 Back up the configuration data of the NEs. Select a proper one from the following second methods depending on the actual situation. Option Description
When the system control and communication Backing Up the NE Database to the SCC board is not configured with the CF card Board. When the system control and communication Manually Backing Up the NE Database to a board is configured with the CF card CF Card. ----End
9.4 Configuring 1+1 Linear MSP Services

In the case of 1+1 linear MSP, the source NE dual-feeds service signals to the working and protection lines. In normal conditions, the sink NE selectively receives the services from the working line. When the working line is faulty, the sink NE selectively receives the services from the protection line.

This topic describes the configuration of 1+1 linear MSP. The OptiX OSN 8800 is used as only the intermediate NE that transmits an SDH service. The OptiX OSN 3500 adds or drops the SDH service. In Figure 9-4, NE1, NE2, NE5, and NE6 use the OptiX OSN 3500, and the intermediate NEs NE3 and NE4 use the OptiX OSN 8800. In this example, the OptiX OSN 3500 adds or drops the SDH service, and the OptiX OSN 8800 only transmits the SDH service instead of adding or dropping the SDH service. NE1, NE2, NE5, and NE6 use the PQ1 boards as the tributary boards that add or drop the SDH service, and use the SL16 boards as the line boards that transmit the SDH service. The intermediate NEs NE3 and NE4 use the SLO16 boards as the line boards that dual-feed or selectively receive the SDH service, and use the SLQ64 boards as the line boards that transmit the SDH service. Figure 9-4 Networking diagram of the 1+1 linear MSP
Tributary board Line board 2-PQ1 7-SL16 Tributary board Line board 2-PQ1 7-SL16
NE1
NE6
NE2 Tributary board Line board
NE3 Line board 7-SLO16 Line board 8-SLQ64 Line board 12-SLQ64 2-PQ1 7-SL16
NE4 Line board 7-SLO16 Line board 8-SLQ64 Line board 12-SLQ64
NE5 Tributary board Line board
2-PQ1 7-SL16
: OptiX OSN 8800
: OptiX OSN 3500

You can configure the service added to the source NE and dropped to the sink NE if the 1+1 linear MSP is already created. Figure 9-5 shows the service signal flow and timeslot allocation between NE1 and NE6.
The service flow from NE1 to NE6 is as follows: NE1NE3NE4NE6. A service is added to the source NE NE1, cross-connected from the tributary board PQ1 to the line board SL16, and then transmitted to the intermediate NE3. The line board SLO16 dual-feeds the service to the line board SLQ64 through the working and protection lines. The two services are received by the line board SLQ64 on the intermediate NE4, and the line board SLO16 selects one of the two services and then transmits the service to the sink NE6. The service is dropped to NE6, and cross-connected from the line board SL16 to the tributary board PQ1.
The services between NE1 and NE6 use the first to fourth VC12 timeslots (VC4-1:1-4 (VC12)) in the first VC4 on the SDH link between NE1 and NE6. There are totally four E1 services. The service flow from NE2 to NE5 is as follows: NE2NE3NE4NE5. A service is added to the source NE NE2, cross-connected from the tributary board PQ1 to the line board SL16, and then transmitted to the intermediate NE3. The line board SLO16 dual-feeds the service to the line board SLQ64 through the working and protection lines. The two services are received by the line board SLQ64 on the intermediate NE4, and the line board SLO16 selects one of the two services and then transmits the service to the sink NE5. The service is dropped to NE5, and cross-connected from the line board SL16 to the tributary board PQ1.
Figure 9-5 shows the service signal flow and timeslot allocation between NE2 and NE5. l
l l l
The services between NE2 and NE3 occupy the first to fourth VC12 timeslots (VC4-1:1-4 (VC12)) in the first VC4 on the SDH link. There are totally four E1 services. The services between NE3 and NE4 occupy the fifth to eighth VC12 timeslots (VC4-1:5-8 (VC12)) in the first VC4 on the SDH link. There are totally four E1 services. The services between NE4 and NE5 occupy the first to fourth VC12 timeslots (VC4-1:1-4 (VC12)) in the first VC4 on the SDH link. There are totally four E1 services.
Issue 02 (2011-10-31)
244
Figure 9-5 Signal flow and timeslot allocation of the 1+1 linear MSP service
Tributary board Line board 4xE1 services are added/ dropped NE1 NE2 4xE1 services are added/ dropped VC4-1:1-4(VC12) Tributary board Line board 2-PQ1 7-SL16 NE3 VC4-1:5-8(VC12) Line board Line board Line board 7-SLO16 8-SLQ64 12-SLQ64 NE4 VC4-1:5-8(VC12) Line board Line board Line board 7-SLO16 8-SLQ64 12-SLQ64 2-PQ1 7-SL16 Tributary board Line board 2-PQ1 7-SL16 4xE1 services are added/ dropped NE6 NE5 4xE1 services are added/ dropped VC4-1:1-4(VC12) Tributary board Line board 2-PQ1 7-SL16
VC4-1:1-4(VC12) VC4-1:1-4(VC12) VC4-1:1-4(VC12)
VC4-1:1-4(VC12)
: Line Board : Traffic direction of the working path path
: Tributary board : Traffic direction of the protection

This topic describes how to configure the 1+1 linear MSP services.
Prerequisite
The physical topology of the network must be created. The NEs, boards, and fibers must be created on the U2000. The created protection subnet must be consistent with the actual network topology.


Step 1 Configure an SDH service for the source NE NE1. 1. 2. In the NE Explorer, select NE1 and choose Configuration > SDH Service Configuration from the Function Tree. Click Create in the lower-right pane and the Create SDH Service dialog box is displayed. Set the required parameters, and then click OK. Click Close in the Operation Result dialog box that is displayed.
Issue 02 (2011-10-31)
245
Parameter
Value in This Example VC12 Bidirectiona l
Description
Level Direction
In this example, E1 services are configured. Hence, Level of the E1 services is set to VC12. In this example, the services are transmitted and received over the same path. That is, the services are bidirectional services. Hence, Direction of the services is set to Bidirectional. In this example, the PQ1 board in slot 2 is configured as the source tributary board for the bidirectional services. The total capacity of the services is 4xE1 according to the plan. Hence, Source Timeslot Range (e.g. 1, 3-6) is set to 1-4 In this example, the SL16 board in slot 7 is configured as the sink line board. In this example, the services require four VC12s. As a result, Sink VC4 is set to VC4-1, because a VC4 contains 63 VC12s. The total capacity of the services is 4xE1 according to the plan. Hence, Sink Timeslot Range (e.g. 1, 3-6) is set to 1-4. -
Source Slot Source VC4 Source Timeslot Range (e.g. 1,3-6) Sink Slot Sink VC4
2-PQ1 1-4
7-N1SL16-1 (SDH-1) VC4-1
1-4
Yes
Step 2 Configure another SDH service for the source NE NE2. See Step Step 1 to configure the SDH service on NE2. Set the following parameters. Parameter Value in This Example VC12 Bidirectional Description
Level Direction
In this example, E1 services are configured. Hence, Level of the E1 services is set to VC12. In this example, the services are transmitted and received over the same path. That is, the services are bidirectional services. Hence, Direction of the services is set to Bidirectional. In this example, the PQ1 board in slot 2 is configured as the source tributary board for the bidirectional services.
Source Slot
2-PQ1
Issue 02 (2011-10-31)
246
Parameter
Value in This Example 1-4
Description
Source VC4 Source Timeslot Range (e.g. 1,3-6) Sink Slot Sink VC4
The total capacity of the services is 4xE1 according to the plan. Hence, Source Timeslot Range (e.g. 1, 3-6) is set to 1-4 In this example, the SL16 board in slot 7 is configured as the sink line board. In this example, the services require four VC12s. As a result, Sink VC4 is set to VC4-1, because a VC4 contains 63 VC12s. The total capacity of the services is 4xE1 according to the plan. Hence, Sink Timeslot Range (e.g. 1, 3-6) is set to 1-4. -
7-N1SL16-1 (SDH-1) VC4-1
1-4
Yes
Step 3 Configure an SDH service for the sink NE NE6. See Step Step 1 to configure the SDH service on NE6. Set the following parameters. Parameter Value in This Example VC12 Bidirectional Description
Level Direction
In this example, E1 services are configured. Hence, Level of the E1 services is set to VC12. In this example, the services are transmitted and received over the same path. That is, the services are bidirectional services. Hence, Direction of the services is set to Bidirectional. In this example, the PQ1 board in slot 2 is configured as the source tributary board for the bidirectional services. The total capacity of the services is 4xE1 according to the plan. Hence, Source Timeslot Range (e.g. 1, 3-6) is set to 1-4 In this example, the SL16 board in slot 7 is configured as the sink line board.
Source Slot Source VC4 Source Timeslot Range (e.g. 1,3-6) Sink Slot
2-PQ1 1-4
7-N1SL16-1 (SDH-1)
Issue 02 (2011-10-31)
247
Parameter
Value in This Example VC4-1
Description
Sink VC4
In this example, the services require four VC12s. As a result, Sink VC4 is set to VC4-1, because a VC4 contains 63 VC12s. The total capacity of the services is 4xE1 according to the plan. Hence, Sink Timeslot Range (e.g. 1, 3-6) is set to 1-4. -
1-4
Yes
Step 4 Configure another SDH service for the sink NE NE5. See Step Step 1 to configure the SDH service on NE5. Set the following parameters. Parameter Value in This Example VC12 Bidirectional Description
Level Direction
In this example, E1 services are configured. Hence, Level of the E1 services is set to VC12. In this example, the services are transmitted and received over the same path. That is, the services are bidirectional services. Hence, Direction of the services is set to Bidirectional. In this example, the PQ1 board in slot 2 is configured as the source tributary board for the bidirectional services. The total capacity of the services is 4xE1 according to the plan. Hence, Source Timeslot Range (e.g. 1, 3-6) is set to 1-4 In this example, the SL16 board in slot 7 is configured as the sink line board. In this example, the services require four VC12s. As a result, Sink VC4 is set to VC4-1, because a VC4 contains 63 VC12s. The total capacity of the services is 4xE1 according to the plan. Hence, Sink Timeslot Range (e.g. 1, 3-6) is set to 1-4. -
Source Slot Source VC4 Source Timeslot Range (e.g. 1,3-6) Sink Slot Sink VC4
2-PQ1 1-4
7-N1SL16-1 (SDH-1) VC4-1
1-4
Yes
Issue 02 (2011-10-31)
248
Step 5 Configure an SDH service for the intermediate NE NE3. 1. 2. In the NE Explorer, select NE3 and choose Configuration > SDH Service Configuration from the Function Tree. Click Create in the lower-right pane and the Create SDH Service dialog box is displayed. Set the required parameters, and then click OK. Click Close in the Operation Result dialog box that is displayed. Parameter Value in This Example VC12 Bidirectiona l Description
Level Direction
In this example, E1 services are configured. Hence, Level of the E1 services is set to VC12. In this example, the services are transmitted and received over the same path. That is, the services are bidirectional services. Hence, Direction of the services is set to Bidirectional. In this example, the SLO16 board in slot 7 is configured as the source line board. In this example, the services require four VC12s. As a result, Source VC4 is set to VC4-1, because a VC4 contains 63 VC12s. The total capacity of the services is 4xE1 according to the plan. Hence, Source Timeslot Range (e.g. 1, 3-6) is set to 1-4 In this example, the SLQ64 board in slot 8 is configured as the sink line board. In this example, the services require four VC12s. As a result, Sink VC4 is set to VC4-1, because a VC4 contains 63 VC12s. The total capacity of the services is 4xE1 according to the plan. Hence, Sink Timeslot Range (e.g. 1, 3-6) is set to 1-4. -
Source Slot Source VC4
7-N4SLO16 (SDH-1) VC4-1
1-4
8N4SLQ64-1 (SDH-1) VC4-1
Sink VC4
1-4
Yes
Step 6 Configure another SDH service for the intermediate NE NE3. See Step Step 5 to configure the SDH service on NE3. Set the following parameters.
Issue 02 (2011-10-31)
249
Parameter
Value in This Example VC12 Bidirectional
Description
Level Direction
In this example, E1 services are configured. Hence, Level of the E1 services is set to VC12. In this example, the services are transmitted and received over the same path. That is, the services are bidirectional services. Hence, Direction of the services is set to Bidirectional. In this example, the SLO16 board in slot 7 is configured as the source line board. In this example, the services require four VC12s. As a result, Source VC4 is set to VC4-1, because a VC4 contains 63 VC12s. The total capacity of the services is 4xE1 according to the plan. Hence, Source Timeslot Range (e.g. 1, 3-6) is set to 1-4 In this example, the SLQ64 board in slot 8 is configured as the sink line board. In this example, the services require four VC12s. As a result, Sink VC4 is set to VC4-1, because a VC4 contains 63 VC12s. The total capacity of the services is 4xE1 according to the plan. Hence, Sink Timeslot Range (e.g. 1, 3-6) is set to 5-8. -
Source Slot Source VC4
7-N4SLO16 (SDH-2) VC4-1
1-4
12N4SLQ64-1 (SDH-1) VC4-1
Sink VC4
5-8
Yes
Step 7 Configure an SDH service for the intermediate NE NE4. See Step Step 5 to configure the SDH service on NE4. Set the following parameters. Parameter Value in This Example VC12 Bidirectional Description
Level Direction
In this example, E1 services are configured. Hence, Level of the E1 services is set to VC12. In this example, the services are transmitted and received over the same path. That is, the services are bidirectional services. Hence, Direction of the services is set to Bidirectional.
Issue 02 (2011-10-31)
250
Parameter
Value in This Example 8N4SLQ64-1 (SDH-1) VC4-1
Description
Source Slot
In this example, the SLQ64 board in slot 8 is configured as the source line board. In this example, the services require four VC12s. As a result, Source VC4 is set to VC4-1, because a VC4 contains 63 VC12s. The total capacity of the services is 4xE1 according to the plan. Hence, Source Timeslot Range (e.g. 1, 3-6) is set to 1-4 In this example, the SLO16 board in slot 7 is configured as the sink line board. In this example, the services require four VC12s. As a result, Sink VC4 is set to VC4-1, because a VC4 contains 63 VC12s. The total capacity of the services is 4xE1 according to the plan. Hence, Sink Timeslot Range (e.g. 1, 3-6) is set to 1-4. -
Source VC4
Source Timeslot Range (e.g. 1,3-6) Sink Slot Sink VC4
1-4
7-N4SLO16 (SDH-1) VC4-1
1-4
Yes
Step 8 Configure another SDH service for the intermediate NE NE4. See Step Step 5 to configure the SDH service on NE4. Set the following parameters. Parameter Value in This Example VC12 Bidirectional Description
Level Direction
In this example, E1 services are configured. Hence, Level of the E1 services is set to VC12. In this example, the services are transmitted and received over the same path. That is, the services are bidirectional services. Hence, Direction of the services is set to Bidirectional. In this example, the SLQ64 board in slot 8 is configured as the source line board. In this example, the services require four VC12s. As a result, Source VC4 is set to VC4-1, because a VC4 contains 63 VC12s.
Source Slot
12N4SLQ64-1 (SDH-1) VC4-1
Source VC4
Issue 02 (2011-10-31)
251
Parameter
Description
Source Timeslot Range (e.g. 1,3-6) Sink Slot Sink VC4
The total capacity of the services is 4xE1 according to the plan. Hence, Source Timeslot Range (e.g. 1, 3-6) is set to 1-4 In this example, the SLO16 board in slot 7 is configured as the sink line board. In this example, the services require four VC12s. As a result, Sink VC4 is set to VC4-1, because a VC4 contains 63 VC12s. The total capacity of the services is 4xE1 according to the plan. Hence, Sink Timeslot Range (e.g. 1, 3-6) is set to 5-8. -
7-N4SLO16 (SDH-2) VC4-1
5-8
Yes
9.5 Configuring the Two-Fiber Bidirectional MSP Ring Services

To configure the two-fiber bidirectional MSP services, you need to create the MSP subnet protection and MSP services. There is no requirement for the sequence of creating the MSP subnet protection and MSP services.
Issue 02 (2011-10-31)
252

In the network construction, you should create and name NEs in sequence according to the certain direction, which helps you facilitate the planning of the service flow and service configuration. In the networking diagram shown in Figure 9-6, a two-fiber bidirectional MSP ring that consists of four OptiX OSN 8800 NEs. The OptiX OSN 3500 NEs at the source and sink ends are used to add or drop services. In this example, the source NE NE5 and the sink NE NE6 use the PQ1 boards as the tributary boards that add or drop services, and use the SL16 boards as the line boards that transmit SDH services. NE2 and NE4 on the ring use the SLO16 boards to receive the services sent from the OptiX OSN 3500 or to transmit the services to the OptiX OSN 3500, and use the SLQ64 boards to transmit the SDH services. NE1 and NE3 on the ring uses the SLQ64 board to transparently transmit the SDH services. Figure 9-6 Networking of two-fiber bidirectional MSP ring
12-SLQ64 8-SLQ64 12-SLQ64 8-SLQ64 7-SLO16 NE2 NE5 Tributary board: 2-PQ1 Line board: 7-SL16 12-SLQ64 8-SLQ64 NE1 Two-fiber bidirectional NE4 MSP ring NE3 NE6 Tributary board: 2-PQ1 Line board: 7-SL16 12-SLQ64 8-SLQ64 7-SLO16
: OptiX OSN 8800
: OptiX OSN 3500

If you have created an MSP protection subnet, you can configure a service on a two-fiber bidirectional MSP ring as follows: The source NE adds a service, an NE accesses the service to the ring network, the intermediate NE passes through the service, an NE transmits the service out of the ring network, and then the sink NE drops the service. The service on a ring network has more than one route from the source NE to the sink NE. You need not configure all routes in actual situations. Hence, it is important that you plan and configure the flow of service signals and timeslot allocation properly before you configure a service. Figure 9-7 shows the signal flow and timeslot allocation of a service. In this example, NE5 adds a service, NE2 accesses the service to the ring network, NE1 passes through the service, NE4 transmits the service out of the network, and NE6 drops the service. There are totally five E1 services.
Figure 9-7 Signal flow and timeslot allocation

12-SLQ64 8-SLQ64 VC4-1:1-5(VC12) 12-SLQ64 8-SLQ64 VC4-1:1-5(VC12) 7-SLO16 NE1 12-SLQ64 8-SLQ64 7-SLO16 VC4-1:1-5(VC12)

NE5 NE2 VC4-1:1-5(VC12)
5xE1 services are added/dropped
Two-fiber bidirectional MSP ring NE4 VC4-1:1-5(VC12)
5xE1 services are added/dropped
NE6 Tributary board: 2-PQ1 Line board: 7-SL16
Tributary board: 2-PQ1 Line board: 7-SL16

NE3 12-SLQ64 8-SLQ64
VC4-1:1-5(VC12)
: Traffic direction
: Line board
: Tributary board

The configuration of the two-fiber bidirectional MSP service is independent of creation of its MSP protection subnet. In the case that the protection subnet is created, you need to respectively configure SDH services from the tributary board to the line board on the source NE and the destination NE, and configure the pass-through service on the intermediate NE.
Prerequisite
The physical network topology must be created. NEs, boards, and fibers must be successfully created on the U2000. The created protection subnet must be consistent with the actual topology.


Step 1 Configure an SDH service for the source NE NE5. 1. 2. In the NE Explorer, select NE5 and choose Configuration > SDH Service Configuration from the Function Tree. Click Create in the lower-right pane and the Create SDH Service dialog box is displayed. Set the required parameters, and then click OK. Click Close in the Operation Result dialog box that is displayed.
Issue 02 (2011-10-31)
254
Parameter
Value Description
Level Direction
In this example, E1 services are added and dropped. Hence, Level of the E1 services is set to VC12. In this example, the services are transmitted and received over the same path. That is, the services are bidirectional services. Hence, Direction of the services is set to Bidirectional. In the planning of this example, the PQ1 housed in slot 2 serves as the source tributary board. Different source boards can be selected according to actual situations. In the planning of this example, the total service volume is 5xE1. The service level is VC12, and thus the 5xVC12 need be set. In the planning of this example, the SL16 housed in slot 7 serves as the sink line board. Different sink boards can be selected according to actual situations. In this example, the service requires 5xVC12. One VC4 timeslot contains 63xVC12. Hence, only the first VC4 timeslot need be set. In the planning of this example, the total service volume is 5xE1. The service level is VC12, and thus the 5xVC12 need be set. -
Source Slot
2-PQ1
Source VC4 Source Timeslot Range (e.g. 1,3-6) Sink Slot
1-5
7-N1SL16-1 (SDH-1) VC4-1
Sink VC4
1-5
Yes
Step 2 Configure an SDH service for the sink NE NE6. See Step Step 1 to configure the SDH service on NE6. Set the following parameters. Parameter Value in This Example VC12 Bidirectional Value Description
Level Direction
In this example, E1 services are added and dropped. Hence, Level of the E1 services is set to VC12. In this example, the services are transmitted and received over the same path. That is, the services are bidirectional services. Hence, Direction of the services is set to Bidirectional.
Issue 02 (2011-10-31)
255
Parameter
Value in This Example 2-PQ1
Value Description
Source Slot
In the planning of this example, the PQ1 housed in slot 2 serves as the source tributary board. Different sink boards can be selected according to actual situations. In the planning of this example, the total service volume is 5xE1. The service level is VC12, and thus the 5xVC12 need be set. In the planning of this example, the SL16 housed in slot 7 serves as the sink line board. Different source boards can be selected according to actual situations. In this example, the service requires 5xVC12. One VC4 timeslot contains 63xVC12. Hence, only the first VC4 timeslot need be set. In the planning of this example, the total service volume is 5xE1. The service level is VC12, and thus the 5xVC12 need be set. -
Source VC4 Source Timeslot Range (e.g. 1,3-6) Sink Slot
1-5
7-N1SL16-1 (SDH-1) VC4-1
Sink VC4
1-5
Yes
Step 3 Configure the SDH service for NE2 to access the SDH service to the ring network. 1. 2. In the NE Explorer, select NE2 and choose Configuration > SDH Service Configuration from the Function Tree. Click Create in the lower-right pane and the Create SDH Service dialog box is displayed. Set the required parameters, and then click OK. Click Close in the Operation Result dialog box that is displayed. Parameter Value in This Example VC12 Bidirectiona l Value Description
Level Direction
In this example, E1 services are added and dropped. The corresponding service level is set to VC12. In this example, the services are transmitted and received over the same path. That is, the services are bidirectional services. Hence, Direction of the services is set to Bidirectional. In the planning of this example, the SLO16 housed in slot 7 serves as the source board. Different source boards can be selected according to actual situations.
Source Slot
7N4SLO16-1 (SDH-1)
Issue 02 (2011-10-31)
256
Parameter
Value Description
Source VC4
In this example, the service requires 5xVC12. One VC4 timeslot contains 63xVC12. Hence, only the first VC4 timeslot need be set. In the planning of this example, the total service volume is 5xE1. The service level is VC12, and thus the 5xVC12 need be set. In the planning of this example, the SLQ64 housed in slot 8 serves as the sink board. Different sink boards can be selected according to actual situations. In this example, the service requires 5xVC12. One VC4 timeslot contains 63xVC12. Hence, only the first VC4 timeslot need be set. In the planning of this example, the total service volume is 5xE1. The service level is VC12, and thus the 5xVC12 need be set. -
1-5
8N4SLQ64-1 (SDH-1) VC4-1
Sink VC4
1-5
Yes
Step 4 Configure the SDH service for NE4 to transmit the SDH service out of the ring network. See Step Step 3 to configure the SDH service on NE4. Set the following parameters. Parameter Value in This Example VC12 Bidirectional Value Description
Level Direction
In this example, E1 services are added and dropped. The corresponding service level is set to VC12. In this example, the services are transmitted and received over the same path. That is, the services are bidirectional services. Hence, Direction of the services is set to Bidirectional. In the planning of this example, the SLQ64 housed in slot 8 serves as the source board. Different source boards can be selected according to actual situations. In this example, the service requires 5xVC12. One VC4 timeslot contains 63xVC12. Hence, only the first VC4 timeslot need be set.
Source Slot
8N4SLQ64-1 (SDH-1) VC4-1
Source VC4
Issue 02 (2011-10-31)
257
Parameter
Value Description
In the planning of this example, the total service volume is 5xE1. The service level is VC12, and thus the 5xVC12 need be set. In the planning of this example, the SLO16 housed in slot 7 serves as the sink board. Different sink boards can be selected according to actual situations. In this example, the service requires 5xVC12. One VC4 timeslot contains 63xVC12. Hence, only the first VC4 timeslot need be set. In the planning of this example, the total service volume is 5xE1. The service level is VC12, and thus the 5xVC12 need be set. -
7N4SLO16-1 (SDH-1) VC4-1
Sink VC4
1-5
Yes
Step 5 Configure the pass-through service for NE1. 1. 2. In the NE Explorer, select NE1 and choose Configuration > SDH Service Configuration from the Function Tree. Click Create in the lower-right pane and the Create SDH Service dialog box is displayed. Set the required parameters, and then click OK. Click Close in the Operation Result dialog box that is displayed. Parameter Value in This Example VC12 Bidirectiona l Value Description
Level Direction
In this example, E1 services are added and dropped. The corresponding service level is set to VC12. In this example, the services are transmitted and received over the same path. That is, the services are bidirectional services. Hence, Direction of the services is set to Bidirectional. In the planning of this example, the SLQ64 housed in slot 12 serves as the source board. Different source boards can be selected according to actual situations. In this example, the service requires 5xVC12. One VC4 timeslot contains 63xVC12. Hence, only the first VC4 timeslot need be set.
Source Slot
12N4SLQ64-1 (SDH-1) VC4-1
Source VC4
Issue 02 (2011-10-31)
258
Parameter
Value Description
In the planning of this example, the total service volume is 5xE1. The service level is VC12, and thus the 5xVC12 need be set. In the planning of this example, the SLQ64 housed in slot 8 serves as the sink board. Different sink boards can be selected according to actual situations. In this example, the service requires 5xVC12. One VC4 timeslot contains 63xVC12. Hence, only the first VC4 timeslot need be set. In the planning of this example, the total service volume is 5xE1. The service level is VC12, and thus the 5xVC12 need be set. -
8N4SLQ64-1 (SDH-1) VC4-1
Sink VC4
1-5
Yes
9.6 Configuring the SNCP Tangent Ring Services

With respect to the physical topology, the SNCP tangent ring is similar to the MSP tangent ring. It can protect services on the two SNCP rings when one fiber between any adjacent stations on each ring is cut. For service configuration of the SNCP tangent ring, you should focus on the tangent node. Each bidirectional service that passes by the tangent node must be configured with four pairs of protection groups.

The SNCP tangent ring is similar to the MSP tangent ring in terms of physical networking topology. The difference is that you need to configure only one pair of bidirectional services in the tangent point for the MSP ring. For the SNCP ring, however, you need to configure four protection groups for each pair of bidirectional services. In the networking diagram shown in Figure 9-8, two SNCP tangent rings consist of six OptiX OSN 3500 NEs and an OptiX OSN 8800 NE. The OptiX OSN 8800 NE functions as the tangent NE, namely, NE3. The source NE NE1 and the sink NE NE6 use the PQ1 boards as the tributary boards that add or drop services. Figure 9-8 SNCP tangent ring networking
Tributary board: 2-PQ1 Line board: 11-SL16 Line board: 8-SL16
Line board: 11-SL16 Line board: 8-SL16
NE1
NE2
SNCP Ring1
NE3
NE4
Line board: 7-SLO16 Line board: 8-SLO16 Line board: 12-SLO16 Line board: 13-SLO16
NE5
SNCP Ring2
NE7
NE6
Tributary board: 2-PQ1 Line board: 8-SL16 Line board: 11-SL16
: OptiX OSN 8800
: OptiX OSN 3500
NOTE
This example illustrates a network that consists of the OptiX OSN 3500 and OptiX OSN 8800. In the case of a network that consists of the OptiX OSN 8800 and other MSTP equipment, the configuration method is the same. The difference lies in the slots where boards are inserted. For the slot information, see the Hardware Description of the relevant product.
Issue 02 (2011-10-31)
260
9.6.2 Service Signal Flow and Timeslot Allocation

The service in the SNCP tangent ring is not transmitted in a fixed direction. The service flow direction depends on the configuration of the working path and the protection path on each NE where the SNCP protection group is configured. When configuring the SNCP protection group on the tangent NE, you need to configure four SNCP protection groups for each bidirectional service in the tangent point. The service timeslot allocation in the SNCP tangent ring is same as the service timeslot allocation on a single SNCP ring. Figure 9-9 shows the service signal flow and timeslot allocation. The service can be transmitted in the MSP tangent ring in different directions and routes. In this example, the service in the ring is transmitted to the ring network from NE1 and then is dropped on the sink NE (NE6). on tangent NE (NE3), four SNCP protection groups need to be configured. The service flow direction is NE1-NE2-NE3-NE5-NE6 or NE1-NE2-NE3-NE7-NE6. There are five E1 services on the ring. Figure 9-9 Signal flow and timeslot allocation
NE1: 5xE1 SNCP protection group service source protection source 8-SL16 service sink 2-PQ1
protection group1 11-SL16 VC4-1:1-5 (VC12) 8 11 VC4-1:1-5 (VC12)
NE1
NE2 and NE4 : SDH service service source 11-SL16 service sink 8-SL16
11 VC4-1:1-5 (VC12) Service pass-through 8 NE2 SNCP Ring1 NE4
8 11 NE3: 12 NE3 SNCP 8
VC12
VC4-1:1-5 (VC12) Service pass-through
SNCP protection group
service source
protection source 7-SLO16 7-SLO16 8-SLO16 8-SLO16
service sink 12-SLO16 8-SLO16 7-SLO16 13-SLO16
protection group1 13-SLO16 VC4-1:1-5 (VC12) VC4-1:1-5 (VC12) protection group2 13-SLO16 protection group3 12-SLO16 7 13 protection group4 12-SLO16
11 VC4-1:1-5 (VC12) Service pass-through NE5 8 SNCP Ring2 NE7
8 VC4-1:1-5 (VC12) Service pass-through 11
11
NE6
VC4-1:1-5 (VC12)
VC4-1:1-5 (VC12) NE6: 5 x E1 SNCP protection group service source protection source 8-SL16 service sink 2-PQ1
working service route protection service route
Line board Tributary board
protection group1 11-SL16
Issue 02 (2011-10-31)
261

For non-tangent nodes in the SNCP tangent rings, the service configuration is the same as the service configuration in a single ring network. On tangent nodes, you need to configure four SNCP protection groups for a bidirectional service.
Prerequisite
The physical network topology must be created. NEs, boards, and fibers must be successfully created on the U2000.


Step 1 Configure an SNCP-protected SDH service for NE1. 1. 2. In the NE Explorer, select NE1 and choose Configuration > SDH Service Configuration from the Function Tree. Click Create SNCP Service in the lower-right pane and the Create SNCP Service dialog box is displayed. Set the required parameters, and then click OK. Click Close in the Operation Result dialog box that is displayed. Parameter Value in This Example SNCP VC12 Bidirectiona l Value Description
Service Type Level Direction
In this example, this parameter is set to the default value, that is, SNCP. In this example, the service in the ring is the E1 service. The corresponding service level is set to VC12. In this example, the received and transmitted services pass through the same route, and thus the service is bidirectional. The service direction is set to Bidirectional. This parameter indicates the processing policies after the faulty line is recovered, that is, revertive or nonrevertive. During the service configuration, the revertive mode is set to Revertive. In the planning of this example, the SL16 housed in slot 11 serves as the source board of the working service. Different source boards of the working service can be selected according to actual situations.
Revertive Mode
Revertive
Source Slot of the Working Service
11N1SL16-1 (SDH-1)
Issue 02 (2011-10-31)
262
Parameter
Value Description
Source Timeslot Range of the Working Service Source Slot of the Protection Service Source Timeslot Range of the Protection Service Sink Slot
In the planning of this example, the total service volume is 5xE1. The service level is VC12, and thus 5xVC12 need be set.
8-N1SL16-1 (SDH-1)
In the planning of this example, the SL16 housed in slot 8 serves as the source board of the protection service. Different source boards of the protection service can be selected according to actual situations. In the planning of this example, the total service volume is 5xE1. The service level is VC12, and thus 5xVC12 need be set.
1-5
2-PQ1
In the planning of this example, the PQ1 housed in slot 2 serves as the sink tributary board. Different sink boards can be selected according to actual situations. In the planning of this example, the total service volume is 5xE1. The service level is VC12, and thus 5xVC12 need be set.
Sink Timeslot Range of the Working Service Activate Immediately 3. Click OK.
1-5
Yes
Step 2 The procedure of configuring a service for NE6 is similar to the procedure for NE1. Hence, configure an SDH service for NE6 by referring to the service configuration process of NE1 and the NE6 service planning described in Figure 9-9. Step 3 Configure the pass-through service on NE2. 1. 2. 3. In the NE Explorer, select NE2 and choose Configuration > SDH Service Configuration from the Function Tree. In the NE Explorer, select NE2 and choose Configuration > Cross Connection Configuration from the Function Tree. Click Create in the lower-right pane and the Create SDH Service dialog box is displayed. Set the required parameters, and then click OK. Click Close in the Operation Result dialog box that is displayed.
Issue 02 (2011-10-31)
263
Parameter
Value Description
Level Direction
In this example, the service in the ring is the E1 service. The corresponding service level is set to VC12. In this example, the received and transmitted services pass through the same route, and thus the service is bidirectional. The service direction is set to Bidirectional. In the planning of this example, the SL16 housed in slot 11 serves as the source line board. Different source boards can be selected according to actual situations. In this example, the service requires 5xVC12. One VC4 timeslot contains 63xVC12. Hence, only the first VC4 timeslot need be set. In the planning of this example, the total service volume is 5xE1. The service level is VC12, and thus 5xVC12 need be set. In the planning of this example, the SL16 housed in slot 8 serves as the sink board. Different sink boards can be selected according to actual situations. In this example, the service requires 5xVC12. One VC4 timeslot contains 63xVC12. Hence, only the first VC4 timeslot need be set. In the planning of this example, the total service volume is 5xE1. The service level is VC12, and thus 5xVC12 need be set. -
Source Slot
11N1SL16-1 (SDH-1) VC4-1
Source VC4
1-5
8-N1SL16-1 (SDH-1) VC4-1
Sink VC4
1-5
Yes
Step 4 In this example, NE4, NE5, and NE7 are pass-through NEs. The configuration method and parameter setting are the same as those of NE2. Refer to the configuration of NE2 to configure pass-though SDH service of NE4, NE5 and NE7 Step 5 Configure the SDH service on NE3 (tangent NE).
NOTE
According to the configuration principle of the SNCP tangent rings, you need to configure four SNCP protection groups for each bidirectional service. The configuration combination of protection groups is not fixed. You can configure the protection group according to actual requirements. The following configuration is considered as a reference.
1.
In the NE Explorer, select NE3 and choose Configuration > SDH Service Configuration from the Function Tree.
Issue 02 (2011-10-31)
2. 3.
In the NE Explorer, select NE3 and choose Configuration > Cross Connection Configuration from the Function Tree. Click Create SNCP Service in the lower-right pane and the Create SNCP Service dialog box is displayed. Set the required parameters, and then click OK. Click Close in the Operation Result dialog box that is displayed. Parameter Value in This Example SNCP VC12 Revertive Value Description
Service Type Level Revertive Mode
In this example, this parameter is set to the default value, that is, SNCP. In this example, the service in the ring is the E1 service. The corresponding service level is set to VC12. This parameter indicates the processing policies after the faulty line is recovered, that is, revertive or nonrevertive. During the service configuration, the revertive mode is set to Revertive. In this example, the received and transmitted services pass through the same route, and thus the service is bidirectional. The service direction is set to Bidirectional. In this example, only one protection switching mode is available, and thus the hold-off time does not need to be set. During the service configuration, the hold-off time is set to 0. In normal cases, this parameter is set to the default value, that is, 600. In the planning of this example, the SLO16 housed in slot 13 serves as the source board of the working service. Different source boards of the working service can be selected according to actual situations. In the planning of this example, the port 1 of SLO16 housed in slot 13 serves as the source port of the working service. The service source uses the timeslots of VC4-1.
Direction
Bidirectiona l
Hold-off Time (100ms) WTR Time (s) Source Board of the Working Service Source Port of the Working Service Source VC4 of the Working Service Source Timeslot Range of the Working Service
600 13N4SLO16
VC4-1
1-5
In the planning of this example, the total service volume is 5xE1. The service level is VC12, and thus the 5xVC12 need be set.
Issue 02 (2011-10-31)
265
Parameter
Value in This Example 7-N4SLO16
Value Description
Source Board of the Protection Service Source Port of the Protection Service Source VC4 of the Protection Service Source Timeslot Range of the Protection Service Sink Board
In the planning of this example, the SLO16 housed in slot 7 serves as the source board of the protection service. Different source boards of the protection service can be selected according to actual situations. In the planning of this example, the port 1 of SLO16 housed in slot 7 serves as the source port of the protection service. The service source uses the timeslots of VC4-1.
VC4-1
1-5
In the planning of this example, the total service volume is 5xE1. The service level is VC12, and thus the 5xVC12 need be set.
12N4SLO16 1 VC4-1 1-5
In the planning of this example, the SLO16 housed in slot 12 serves as the sink board. Different sink boards can be selected according to actual situations. In the planning of this example, the port 1 of SLO16 housed in slot 12 serves as the sink port. The service source uses the timeslots of VC4-1. In the planning of this example, the total service volume is 5xE1. The service level is VC12, and thus the 5xVC12 need be set. -
Sink Port Sink VC4 Sink Timeslot Range (e.g. 1,3-6) Activate Immediately
Yes
Step 6 Enable the performance monitoring of the NE. For the operation steps, see Setting Performance Monitoring Parameters of an NE. Step 7 To back up configuration data of the NE, you can take the following second methods as references: Option Description
When the system control and communication Backing Up the NE Database to the SCC board is not configured with the CF card Board.
Issue 02 (2011-10-31)
266
Option
Description
When the system control and communication Manually Backing Up the NE Database to a board is configured with the CF card CF Card. ----End
9.7 Parameter
9.7.1 SDH Service Configuration
In this user interface, you can configure services for stations, such as services at VC4, VC3 and VC12 levels. In addition, you can configure SNCP services and other services. You can query, delete, print, and bind/unbind services. You can also customize columns to display important parameters.
Parameters
Field Level Direction Value VC12, VC3, VC4, VC4-4C, VC4-16C, VC4-64C Bidirectional, Unidirectional Description Specifies the level of the newly created service. The service received and transmitted through the same route is called bidirectional service, while the service received and transmitted through different routes is called unidirectional service. Specifies the service source (sink) slot.
Source (Sink) Slot
For example: Shelf ID (subrack)-Slot ID-Board Name-Optical Port No. (name) For example: VC4-1
Source (Sink) VC4
Selects the source (sink) VC4. This parameter is unavailable if a tributary board is selected for Source (Sink) Slot.
Issue 02 (2011-10-31)
267
Field Source (Sink) Timeslot Range (for example: 1,3-6)
Value For example: 1 to 63
Description Sets the specific timeslot or timeslot range of the service. The format of inputting multiple consecutive timeslots: start timeslot number - end timeslot number. The format of inputting multiple inconsecutive timeslots: ts1, ts2.... Two formats can be used together. The range can be different for different levels of services or different boards.
Checked, Unchecked
If this option is checked, activate the service immediately.
9.7.2 SNCP Service Control

In this user interface, you can query and modify attributes and status of SNCP service.
Parameters
Field Service Type Source Value SNCP For example: Shelf ID (subrack)-Slot ID-Board Name-Optical Port No. (name) For example: Shelf ID (subrack)-Slot ID-Board Name-Optical Port No. (name) VC12, VC3, VC4, VC4-4C, VC4-16C, VC4-64C Description Displays the service protection type. Displays the service source timeslot of the service.
Sink
Displays the service sink timeslot of the service.
Level
Displays the service level.
Issue 02 (2011-10-31)
268
Field Current Status
Value Normal, Lockout, Forced Switching, Forced Switching to Working, Forced Switching to Protection, SF Switching, SD Switching, Manual Switching, Manual Switching to Working, Manual Switching to Protection, Automatic Switching, WTR, DNR, Unknown Revertive, NonRevertive
Description Displays the current switching status of the protection group.
Revertive Mode
Displays the revertive mode. Whether the working service is switched back from the protection service after it returns normal. Sets the wait-to-restore time. Refer to the period of time starting when it is detected that the working service returns to normal and ending when the working service is switched back after the protection switching. If the revertive mode is nonrevertive, skip this step. Sets a period of time which starts when the system detects signal degrade and ends when service switching occurs, so as to avoid duplicate switching when the service status is unstable. Sets 100 milliseconds as the unit time for switching. 5 indicates that the hold-off time is 500 milliseconds. Sets the startup conditions that trigger service protection switching. Displays the working status of the working or the protection service in a protection group. Displays and configures the group status of the service. Displays the group type.
WTR Time (s)
300 to 720
Hold-off Time (100ms)
0 to 100, in the unit of 100 milliseconds
Initiation Condition Switching Condition Trail Status
TIM, EXC, SD, UNEQ, SLM, BIPOVER, NULL Default: NULL Normal, SF, SD, Unknown For example: Null For example: Null
Service Grouping Group Type
Issue 02 (2011-10-31)
269
Field Active Channel
Value For example: Working Channel, Protection Channel, Unknown For example: NE350NE351-VC12-0001
Description Displays what the active protection group selectively receives: the working or the protection service. Displays the trail name.
Trail Name
9.7.3 VC4 Path Overhead

You can query and set overhead bytes of the VC4 path in this user interface.
Parameters
Field Object Value For example: NE351-3ADL4-2(SDH-2)-VC4:1 For example: NE56-4-SD1-1 (SDH-2)-1 J1 to be Sent ([Mode] Content) For example: [16 Bytes] Huawei SBS Sets the higher-order path overhead byte J1 to be sent. [Mode] indicates whether the overhead byte is of the single-byte mode, 16-byte mode or 64-byte mode. Object: VC4 path It is applicable to SDH line boards. The default value is usually used, but in the case of Huawei equipment interconnecting with thirdparty's equipment, you need to set the same value as J1 to be received at the opposite end. Description Displays the name of the operation object.
Issue 02 (2011-10-31)
270
Field J1 to be Received ([Mode] Content)
Value For example: [16 Bytes] Huawei SBS
Description Sets the higher-order path overhead byte J1 to be received. [Mode] indicates whether the overhead byte is of the single-byte mode, 16byte mode or 64-byte mode. Object: VC4 path It is applicable to SDH line boards. The default value is usually used, but in the case of Huawei equipment interconnecting with thirdparty's equipment, you need to set the same value as J1 to be sent of the opposite end.
J1 Received ([Mode] Content)
For example: [16 Bytes] Huawei SBS
Queries the higher-order path overhead byte J1 received. The NE reports an alarm if the byte is different from the J1 to be received. [Mode] indicates whether the overhead byte is of the single-byte mode, 16-byte mode or 64-byte mode.
Issue 02 (2011-10-31)
271
Field C2 to be Sent
Value (0x00)Unequipped, (0x01) Reserved, (0x02)TUG Structure, (0x03)Locked TUn, (0x04)34M/45M into C-3, (0x05)Experimental Mapping, (0x12)140M into C-4, (0x13)ATM Mapping, (0x14)MAN DQDB Mapping, (0x15)FDDI Mapping, (0x16)HDLC/PPP Mapping, (0x17)Reserved for Special Purpose, (0x18) HDLC/LAPS Mapping, (0x19)Reserved for Special Purpose, (0x1A)10G Ethernet Frames, (0x1B)GFP Mapping, (0xCF)Reserved, (0xFE)O.181 Test Signal, (0xFF)VC-AIS (0x00)Unequipped, (0x01) Reserved, (0x02)TUG Structure, (0x03)Locke TUn, (0x04)34M/45M into C-3, (0x05)Experimental, (0x12) 140M into C-4 asynchronously, (0x13)ATM Mapping, (0x14)MAN DQDB Mapping, (0x15) FDDI Mapping, (0x16) HDLC/PPP Mapping, (0x17) Reserved for Special Purpose, (0x18)HDLC/ LAPS Mapping, (0x19) Reserved for Special Purpose, (0x1A)10G Ethernet Frame, (0x1B)GFP Mapping, (0xCF)Reserved, (0xFE)O.181 Test Signal, (0xFF)VC-AIS
Description Sets the signal label byte C2 to be sent. Object: VC4 path It is applicable to SDH line boards. The default value is usually used, but when accessing signals of nonTUG structure (for example, ATM, FDDI), you need to set the C2 to be sent as required.
Issue 02 (2011-10-31)
272
Field C2 to be Received
Value (0x00)Unequipped, (0x01) Reserved, (0x02)TUG Structure, (0x03)Locked TUn, (0x04)34M/45M into C-3, (0x05)Experimental Mapping, (0x12)140M into C-4, (0x13)ATM Mapping, (0x14)MAN DQDB Mapping, (0x15)FDDI Mapping, (0x16)HDLC/PPP Mapping, (0x17)Reserved for Special Purpose, (0x18) HDLC/LAPS Mapping, (0x19)Reserved for Special Purpose, (0x1A)10G Ethernet Frames, (0x1B)GFP Mapping, (0xCF)Reserved, (0xFE)O.181 Test Signal, (0xFF)VC-AIS (0x00)Unequipped, (0x01) Reserved, (0x02)TUG Structure, (0x03)Locke TUn, (0x04)34M/45M into C-3, (0x05)Experimental, (0x12) 140M into C-4 asynchronously, (0x13)ATM Mapping, (0x14)MAN DQDB Mapping, (0x15) FDDI Mapping, (0x16) HDLC/PPP Mapping, (0x17) Reserved for Special Purpose, (0x18)HDLC/ LAPS Mapping, (0x19) Reserved for Special Purpose, (0x1A)10G Ethernet Frame, (0x1B)GFP Mapping, (0xCF)Reserved, (0xFE)O.181 Test Signal, (0xFF)VC-AIS
Description Sets the signal label byte C2 to be received. Object: VC4 path It is applicable to the SDH line board. The default is usually used, but when accessing signals of nonTUG structure (for example, ATM, FDDI), you need to set the C2 to be received as required.
C2 Received
For example: (0x00) Unequipped
Queries the signal label byte C2 received. Reports an alarm if it is different from the C2 to be received. Displays VC4 overhead termination.
VC4 Overhead Termination
Auto, Termination, PassThrough
Issue 02 (2011-10-31)
273
Field Byte Mode
Value Single Byte Mode, 16-Byte Mode(the first byte is created automatically), 64-Byte Mode(Synchronization Bit 0x0D,0x0A), 64-Byte Mode (Without Synchronization Bit), Disable Mode
Description Sets byte mode for the overhead byte.
Issue 02 (2011-10-31)
274
10 Configuring Ethernet Services
10
About This Chapter
Configuring Ethernet Services
This chapter describes how to configure Ethernet services. The flexible grooming of Ethernet services is implemented by configuring Ethernet services and electrical cross-connections. 10.1 Ethernet Service Types The WDM equipment supports the following Ethernet services: Ethernet private line (EPL), Ethernet virtual private line (EVPL), Ethernet private local area network (EPLAN) services, and Ethernet virtual private local area network (EVPLAN) services. 10.2 Basic Concepts Before you configure Ethernet boards with services, you need to learn the basic concepts of configuring the Ethernet service. 10.3 Configuration Process of Ethernet Services This section describes the configuration process of Ethernet services using figures. 10.4 Configuring Ethernet Services in an OTN System This section describes how to configure Ethernet services in an OTN system. 10.5 Configuring Ethernet Services in an OCS System This section describes how to configure Ethernet services in an OCS system. 10.6 Configuration Example: Configuring EPL Services The EPL service provides 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. 10.7 Configuration Example: Configuring EVPL (QinQ) Services on a WDM Network EVPL (QinQ) services realize the nesting of VLAN. With the increase of network users, the existing number of VLAN IDs fails to meet the requirement of users. After EVPL (QinQ) services are configured, however, users can be identified through multiple layers of VLAN IDs. In this case, VLAN extension is achieved. 10.8 Configuration Example: Configuring EPLAN Services (IEEE 802.1d Bridge) on a WDM Network The EPLAN service (IEEE 802.1d bridge) provides an LAN solution for multipoint-tomultipoint convergence. This service applies in cases where user-side data communication
equipment connected to the transmission network does not support VLANs or where the VLAN planning is kept secret from the network operator. 10.9 Configuration Example: Configuring EVPLAN Services (IEEE 802.1q Bridge) on a WDM Network The EVPLAN service (IEEE 802.1q bridge) provides an LAN solution for multipoint-tomultipoint convergence. This service applies in cases where user-side data communication equipment connected to the transmission network does not support VLANs or where the VLAN planning is open to the network operator. 10.10 Configuration Example: Configuring EVPLAN Services (IEEE 802.1 ad Bridge) on a WDM Network The QinQ technology provides a cheap and easy solution for Layer 2 virtual private networks (VPNs). The IEEE 802.1ad bridge uses the QinQ technology to provide the VPN solution, thus facilitating the identifying, differentiating and grooming EVPLAN services. 10.11 Configuration Example: Configuring EVPL and EVPLAN Services (IEEE 802.1q Bridge) on a WDM Network Based on different VLANs, EVPL and EVPLAN services can be accessed through a same port, which is applicable to the scenario where the EVPL and EVPLAN users share the same port. 10.12 Configuration Example: Configuring EPL Services on a SDH Network EPL services provide the point-to-point Ethernet transparent transmission solution where the bandwidth is occupied exclusively. EPL services are applicable when the communication equipment that is used to access the client-side data in the transmission network does not support VLAN or when the VLAN planning cannot be disclosed to the network operator. 10.13 Configuration Example: Configuring EVPL (QinQ) Services on a SDH Network The EVPL (QinQ) service provides an Ethernet private line solution. The services are applicable where the services of multiple users that have the same VLAN ID are accessed into a transmission network and need to be transmitted on the same VCTRUNK. In the case of EVPL (QinQ) services, a layer of S-VLAN tag is added on the network side to isolate the services of different users from each other. 10.14 Configuration Example: Configuring PORT-Shared EVPL (VLAN) Services on a SDH Network The PORT-shared EVPL (VLAN) service is applicable when the services of multiple users, which are received from the same external port on the Ethernet board at a station, need to be transmitted on different VCTRUNKs to another station or to another external port of the station. 10.15 Configuration Example: Configuring VCTRUNK-Shared EVPL Services on a SDH Network When the services of multiple users that do not carry VLAN tags are accessed into a transmission network and are transmitted on the same VCTRUNK, the VCTRUNK-shared EVPL (VLAN) service is used to isolate the services of different users by adding VLAN tags. In this manner, the bandwidth is shared on the SDH side. 10.16 Configuration Example: Configuring EPLAN Services (IEEE 802.1d Bridge) on a SDH Network The EPLAN service (IEEE 802.1d bridge) provides a LAN solution for multipoint-to-multipoint convergence. This service is applicable where the user-side data communication equipment connected to the transmission network does not support VLAN tags or where the VLAN planning cannot be disclosed to the network operator. 10.17 Configuration Example: Configuring EVPLAN Services (IEEE 802.1q Bridge) on a SDH Network The EVPLAN service (IEEE 802.1q bridge) provides a LAN solution for multipoint-tomultipoint convergence. This service is applicable where the user-side data communication
equipment, which is connected to the transmission network, does not support VLAN tags or where the VLAN planning cannot be disclosed to the network operator. 10.18 Configuration Example: Configuring EVPLAN Services (IEEE 802.1ad Bridge) on a SDH Network The QinQ technology provides an economical and easy solution for Layer 2 virtual private networks (VPNs). The IEEE 802.1ad bridge uses the QinQ technology to provide the VPN solution, thus facilitating the identifying, differentiating, and grooming of EVPLAN services. 10.19 Configuration Example: Configuring EVPL and EVPLAN Services (IEEE 802.1q Bridge) on a SDH Network The EGSH board supports the EVPL and EVPLAN services (IEEE 802.1q bridge) on a same port. Based on different VLANs, EVPL and EVPLAN services can be accessed through a same port, which is applicable to the scenario where the EVPL and EVPLAN users share the same port. 10.20 Parameters
Issue 02 (2011-10-31)
277
10.1 Ethernet Service Types

The WDM equipment supports the following Ethernet services: Ethernet private line (EPL), Ethernet virtual private line (EVPL), Ethernet private local area network (EPLAN) services, and Ethernet virtual private local area network (EVPLAN) services.
NOTE
When configuring Ethernet services between the client-side ports of the boards, the ALS function of the client side interfaces should be set to Disable.
10.1.1 Ethernet Private Line Service

Ethernet private line 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 does not need to share the bandwidth with the services of the other users, as shown in Figure 10-1. Hence, 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 10-1 EPL services
EVPL Services
For EVPL services, services of different users share the bandwidth. Therefore, the VLAN/QinQ scheme needs to be used for differentiating the services 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. EVPL services are classified into two types, depending on whether the PORT or VCTRUNK is shared. There are two types of EVPL services: l l PORT-shared EVPL services 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 10-2, 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 this station through different VCTRUNKs. Figure 10-2 PORT-shared EVPL services
VCTRUNK-shared EVPL services As shown in Figure 10-3, the services of different users are isolated by using the VLAN/QinQ scheme. Hence, the services of different users can be transmitted in the same VCTRUNK. l VLAN tag-based convergence and distribution of EVPL services Figure 10-3 VLAN tag-based convergence and distribution of EVPL services
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.
10.1.2 Ethernet LAN Service

Huawei OSN equipment supports Ethernet private local area network (EPLAN) and Ethernet virtual private local area network (EVPLAN) services.
Issue 02 (2011-10-31)
279
EPLAN Services
Currently, Ethernet LAN services mainly refer to Ethernet private LAN (EPLAN) services. Based on the Layer 2 switch function, The EPLAN realizes transmission of the accessed data based on 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 need not share the bandwidth. That is, in the case of EPLAN 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. There is more than one node in the EPLAN services, Hence, the nodes need to learn the MAC addresses and forward data according to MAC addresses. Therefore, Layer 2 switching is involved. See Figure 10-4. Figure 10-4 EPLAN services
NM
NE3
NE2 VB1
VCTRUNK1 PORT3
NE4
VB1
VCTRUNK1 PORT3
F2 NE1 F3
VB1
VCTRUNK1 VCTRUNK2 PORT3
F1
NE2 VCTRUNK NE1 PORT VB1

VCTRUNK1 VCTRUNK1
PORT
PORT3
10M
VCTRUNK
F2
VB1 NE4 VCTRUNK

VCTRUNK1
F1
PORT3
10M VCTRUNK2
PORT
PORT3
10M
F3
WDM
VB1
VB Service Mount of VB Cross-conection
As shown in Figure 10-4, three branches of user F need to communicate with each other. On NE1, the IEEE 802.1d bridge is established to achieve 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 broadcast within the domain of the IEEE 802.1d bridge according to the destination MAC addresses. To avoid broadcast storm, the EPLAN services cannot be set as a ring. If the EPLAN services are set as a ring, the rapid spanning tree protocol (RSTP) or Multiple Spanning Tree Protocol (MSTP) must be started in the network.
EVPLAN Services
EVPLAN services of different users need to share the bandwidth. Hence, 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. As shown in Figure 10-5, 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 achieve EVPLAN services. IEEE 802.1q bridge: 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. Figure 10-5 EVPLAN services (IEEE 802.1q bridge)
NM
NE3
H2
PORT2 PORT1 G2 H1 VCTRUNK
NE2 NE1
NE4
PORT2 H3 PORT1 G3
PORT6
PORT5
G1
IEEE 802.1q bridge VLAN 200 VCTRUNK VCTRUNK 1 2 PORT6
IEEE 802.1q bridge VLAN 100 VCTRUNK VCTRUNK 1 2 PORT5
As shown in Figure 10-6, 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. 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 l
This bridge does not check the contents of the VLAN tags that are in the packets, and performs Layer 2 switching according to the destination MAC addresses of the packets. This 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 S-VLAN IDs of the packets.
Figure 10-6 EVPLAN services (IEEE 802.1ad bridge)
NM Service C-VLAN 10 GE 20 FE PORT1 User M GE 8 11 NE2
NE3 Service C-VLAN GE 10 FE 20 NE4 NE1 8 11 FE VCTRUNK PORT1 User N
IEEE 802.1ad bridge S-VLAN 100 VCTRUNK VCTRUNK 1 2 PORT7
IEEE 802.1ad bridge S-VLAN 200 VCTRUNK VCTRUNK 1 2 PORT8
10.2 Basic Concepts

Before you configure Ethernet boards with services, you need to learn the basic concepts of configuring the Ethernet service.
10.2.1 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. That is, tagged packets contain VLAN IDs and untagged packets do not contain VLAN IDs. An Ethernet port has the following three types, which are Tag aware, Access and Hybrid. See Table 10-1 for details on how an Ethernet board processes tagged and untagged packets at the ingress.
Issue 02 (2011-10-31)
282
Table 10-1 Processing policy at ingress Port Type Tag aware Access Hybrid Tagged Packet Transparently transmitted Discarded Transparently transmitted Untagged Packet Discarded Added with the default VLAN tag Added with the default VLAN tag
See Table 10-2 for details on how an Ethernet board processes tagged and untagged packets at the egress. Table 10-2 Processing policy at egress Port Type Tag aware Access Hybrid Tagged Packet Transparently transmitted The VLAN tag is removed 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 Untagged Packet -
As shown in Table 10-1 and Table 10-2, 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 ingress port to Access and set the egress port to Tag aware. If the user-side equipment sends the Tag message, set the ingress port to Tag aware and set the egress port to Tag aware.
10.2.2 VLAN Group

This section describes the application scenarios of the VLAN group.
VLAN Group
The U2000 and its managed NG WDM equipment organize certain consecutively accessed VLAN services in a group (usually service demands of the same type) to form a VLAN group. U2000 creates services, manages the QoS flow, and performs Ethernet OAM operations according to the initial VLAN ID so that the other VLAN services in the VLAN group have the same configuration.
Issue 02 (2011-10-31)
283
Application Scenarios of the VLAN Group

Currently, the digital subscriber line access multiplexer (DSLAM) does not support the QinQ function. The broadband remote access server (BRAS), however, requires that two layers of VLAN tags should be verified. Based on this, the VLAN grouping function provides the broadband bearer solution from the DSLAM to the BRAS. Currently, the NG WDM equipment supports the following three service scenarios: l Convergence from multiple GE services to one 10GE service. The BRAS has the 10GE access port. The GE service of the DSLAM is converged to the 10GE port of the BRAS/ PE through the NG WDM VLAN group. Convergence from multiple GE services to one GE service. The BRAS increases the number of access ports. The WDM equipment implements GE transparent transmission or GE convergence from the DSLAM to the BRAS. Private line from GE services to GE services. In the metropolitan enterprise private lines, point-to-point service transparent transmission is required. In this case, a typical transmission channel is adopted. That is, services are transmitted over the 10GE optical line by using the WDM equipment. This is realized as follows: GE services are accessed on the client side of the WDM equipment, and then the GE services are multiplexed to the 10GE line for transmission through the VLAN group.
10.2.3 QinQ
The QinQ technology is the basis for implementing EVPL services. QinQ technology achieves VLAN nesting. With the increase of network users, the current number of VLAN IDs fail to meet the network requirement. With the QinQ technology, users can be identified through multiple layers of VLAN IDs. In this case, the VLAN is extended. The VLAN is a LAN technology developed along with the Ethernet switch technology. As the Ethernet technology is deployed largely in the networks of carriers, which are the metropolitan area networks, implementing the 802.1Q VLAN to isolate and identifying users is limited to a great extent. The VLAN tag domain that is defined in the IEEE 802.1Q has 12 bits, which can represent 4K VLANs only. This cannot meet the requirements for identifying a large number of users in metropolitan area networks. In order to increase the number of VLANs, the QinQ technology is developed. The QinQ technology is realized by adding a layer of 802.1Q tags to 802.1Q packets. Thus, 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. See Table 10-3. Table 10-3 EVPL services based on QinQ Operation Add S-VLAN
Data C-VLAN Data C-VLAN S-VLAN
Illustration
Issue 02 (2011-10-31)
284
Operation Strip S-VLAN
Illustration
Data
C-VLAN
S-VLAN
Data
C-VLAN
Transparently Transmit CVLAN
Data
C-VLAN
Data
C-VLAN
Transparently Transmit SVLAN
Data
S-VLAN
Data
S-VLAN
Transparently Transmit SVLAN and CVLAN
Data
C-VLAN S-VLAN
Data
C-VLAN S-VLAN
Translate SVLAN
Data
S-VLAN1
Data
S-VLAN2
NOTE
l The "Strip S-VLAN" is valid only for unidirectional services. l The LEM24 and LEX4 boards do not support "Add S-VLAN and C-VLAN" and "Strip S-VLAN and CVLAN".
10.2.4 MAC Address Filtering

MAC address filtering is an OTN broadband transmission solution. MAC address filtering is enabled for Ethernet data boards to alleviate router load. Figure 10-7 describes the principle and function of MAC address filtering. 1. 2. Station 2: Sets the MAC address of the opposite BRAS1. Station 3: Dual feeds services. The dual-fed services carry the MAC address of the destination BRAS1 and respectively reach stations 1 and 2.
Issue 02 (2011-10-31)
3.
Station 2: Analyzes whether the MAC address of the destination router is included in the MAC addresses set in the opposite BRAS1 of station 2. l Included: Indicates that BRAS2 is not the destination BRAS of the service and the transmission of the service stops at station 2. l Excluded: Indicates that BRAS2 is the destination BRAS of the service and the service is transmitted to BRAS2.
Figure 10-7 Principle and function of MAC address filtering

BRAS1
Station 1 Filter MAC address on the standby node
BRAS2
Station 2
TBE L4G
TBE L4G
L2
L4G
Station 3
Working Service Protection Service
BRAS
Broadband Remote Access Server
10.2.5 IGMP Snooping

The Internet group management protocol (IGMP) Snooping technology is used to enhance the multicast management capability of Layer 2 switching equipment. This technology applies to data service boards that support Layer 2 switching. Based on the interception of Layer 3 IGMP packets, the Layer 2 multicast function is created and maintained, to prevent multicast packets from being broadcast in the Layer 2 equipment.
Overview
l Restriction on the User Access: Illegal users are prevented from using multicast services by configuring the attributes of the multicast strategy, static multicast group, static router port and unknown multicast service forwarding. As shown in Figure 10-9, the multicast group strategy is configured on the equipment. In this way, the range of the group addresses that can be accessed by users through the access control list (ACL) is set. Thus, the multicast packets that can be received by the user host can be controlled. Quick Response to the Link Change: When the topology of the network where the equipment resides changes, the switching equipment should set up new forwarding table items in minutes after receiving the subsequent multicast query packet. As a result, the
Issue 02 (2011-10-31)
multicast services are interrupted for a long time. The IGMP Snooping informs the router of the change in the response spanning tree topology and then quickly transmits the query packets. In this way, the switching equipment in the downstream can learn the multicast information quickly and decrease the service interruption time.
Basic Concepts
1. Enabling the IGMP Snooping Protocol l If the IGMP Snooping protocol is enabled, the equipment begins to perform the learning and aging of the router port and multicast group. Then, the multicast services are multicast in corresponding multicast groups. l If the IGMP Snooping protocol is disabled, the equipment stops learning and aging of the router port and multicast group, and deletes all the learned dynamic multicast groups. 2. Router Port The router port refers to the port that faces the multicast router. The Ethernet data board of the equipment regards the port that receives the IGMP query packets as the router port. Router ports are classified into two types: l Dynamic router ports: They receive the IGMP query packets. These ports are decided on the basis of the packets transmitted between routers and hosts. Moreover, they are dynamically maintained. Each of this port can enable a router port aging timer. When the timer times out, this router port is invalid and the multicast group that relies on the router port is deleted. l Static router ports: They are specified with configuration commands, and are not aged.
NOTE
Both the L4G and TBE boards do not support the static router ports.
3.
Member Port The multicast member port refers to the port that faces the host of the member. The Layer 2 equipment forwards the multicast service packets to these ports. The multicast group member ports, referred to as member ports for short, are classified into the following two types: l Dynamic member ports, which can receive the IGMP report packets. These ports are decided on the basis of the packets transmitted between routers and hosts. Moreover, they are dynamically maintained. Each dynamic member port is aged after reaching the maximum non-response times. l Static member ports, which are specified by users by using configuration commands, cannot be aged.
Basic Principle
As a multicast constraint mechanism of the Layer 2 Ethernet switch, the IGMP Snooping runs at the data link layer, to manage and control multicast groups. When the Layer 2 Ethernet switch receives an IGMP packet between the host and router, the IGMP Snooping analyzes the information carried by the packet. l l When monitoring an IGMP response packet sent by the host, the switch adds the host into the corresponding multicast table. When monitoring an IGMP departure packet sent by the host, the switch deletes the multicast table item corresponding to the host.
Issue 02 (2011-10-31)
By monitoring IGMP packets continuously, the switch creates and maintains the MAC multicast address table at Layer 2, and forwards multicast packets sent by the router according to the MAC multicast address table. If the IGMP Snooping does not run, multicast packets are broadcast at Layer 2. When the IGMP Snooping runs, the packets are multicast instead of broadcast at Layer 2. See Figure 10-8. Figure 10-8 IGMP Snooping
Multicast management router
Multicast service source
IGMP Snooping-supported NGWDM equipment
Host (Non-multicast member)
Host Host Host (Multicast member) (Multicast member) (Non-multicast member)
Physical connection Flow direction of the ulticast service
Compliant Standard and Protocol: The IGMP complies with RFC 4541, Considerations for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping Switches.
Application
The IGMP Snooping enhances the resource utilization through multicast forwarding, and the network security by restricting the user access. The advantages of the application of the IGMP Snooping are as follows: l l l The network bandwidth can be saved. Signals are forwarded based on the VLAN. Hence, the information security is enhanced. Quick response is made to the link fault. Hence, the reliability is enhanced.
Figure 10-9 shows how to configure the IGMP Snooping function. After reaching the equipment, the multicast packets are distributed from the port of the host where group members exist in the downstream.
Figure 10-9 IGMP Snooping application
Internet /Intranet Source
OTN/OCS
OTN/OCS
Host 1
Host 2
Host3
Host 4
Host 5
Group member
Group member
Group member
Multicast packets
10.2.6 STP/RSTP/MSTP
Generally, the topology for the Layer 2 switching network involves the loop. This may result in the broadcast storm and MAC bridge table flapping. The STP/RSTP protocol is used to trim a bridged LAN to a single spanning tree based on the logical topology. Thus, the broadcast storm can be avoided. MSTP is compatible with the STP and RSTP, and it also fixes the defects of the STP and RSTP. The MSTP fixes the defects of the STP and RSTP. The convergence rate of the MSTP is fast. In addition, traffic of different VLANs passes through corresponding trails, which provides a well load balancing mechanism.
Basic Principle
STP applies to a redundant network. Based on a certain algorithm, the STP is used to block redundant trails so that a loop network can be trimmed as a tree network. In this way, the reproduction and endless cycling of packets in the loop network are avoided. Besides, a connected network without redundant trails can be formed in the case of the link failure. RSTP is an improvement of the STP. The RSTP not only supports all the functions of the STP, but also shortens the delay of generating the network topology structure and ensures the connectivity of the network. STP is based on this basic principle. That is, bridge protocol data units (BPDUs) are transmitted between bridges to decide the network topology structure. The STP blocks redundant links to prevent possible loops in the bridged network, and activates the redundant backup links to restore
the network connectivity when the working trail fails. BPDUs of STP are classified into two types: l l Configuration BPDU (CBPDU) BPDU for topology change notice (TCN)
RSTP is based on STP. RSTP makes, however, detailed modifications and supplements to STP. Different from STP, RSTP shortens the time delay at the ports from congestion to forwarding, rapidly restores the network connectivity, and provides better services if no temporary loops are caused. The protocol packets transmitted between the bridges using RSTP are rapid spanning tree protocol data units (namely, RST PDUs).
NOTE
l OptiX NG WDM the Ethernet data boards support both STP and RSTP. By default, they support RSTP. l Only the LEX4/LEM24 boards support MSTP.
Status Migration for Ports

The STP ports are of either the Enabled or Disabled status. The Enabled status is further classified into the following statuses: Blocking, Listening, Learning and Forwarding. According to the forwarding and learning situation of the port, RSTP sorts Disabled, Blocking and Listening to Discarding. For this reason, there are altogether three statuses: Learning, Forwarding and Discarding. Figure 10-10 shows the status migration of an STP port. Figure 10-10 Status migration of STP ports
Disabled Listening
Disabled
Blocking
Learning
Disabled
Enabled
Forwarding Disabled
Disabled: The port in the Disabled status is not involved in the topology and does not forward any packets. Any sub-status of the Enabled status can migrate to this status. The Disabled status must migrate to the Blocking status to enter the Enabled status. The STP cannot control this status because the port in the Disabled status is not involved in the topology. This status can only be controlled by the management.
Issue 02 (2011-10-31)
l l
Blocking: The port in the Blocking status is involved in the topology, and does not forward any packets. Moreover, it does not learn the MAC addresses. Listening: The port in the Listening status is involved in the topology. It can forward BPDUs and discard service packets. It does not, however, learn the MAC addresses. The Listening status is a temporary status when a topology is being created or transformed. Learning: The port in the Learning status is involved in the topology. It can forward BPDUs and discard service packets. Moreover, it learns the MAC addresses of the service packets to make ready for forwarding these packets. The Learning status is a temporary status when a topology is being created or transformed. Forwarding: The port in forwarding status is involved in the topology. It can forward the service packets and BPDUs.
Migrate some ports into the Forwarding or Blocking status by controlling the port status. If a loop exists, at least one port is blocked to release the loop. This is the ultimate goal of the STP algorithm. For the STP, the convergence time is relatively long and the ports play unclear roles. In this case, the RSTP is widely used and is compatible with the STP. In comparison with the STP, the RSTP shows the following improvements. l By configuration, The definition of the role of a port is clearer and there are following four types of port: Root port, Designated port, Replacing port, Backup port.
NOTE
RSTP can configure an edge port to help the topology-independent port to rapidly forward service packets.
l l l
A more active handshake mechanism is applied to decrease the port status to the following types: Forwarding, Learning, and Discarding. The Discarding status in the RSTP maps with the Listening, Blocking, and Disabled status in the STP. Fast convergence.
Improvement of the MSTP

The MSTP fixes the defects of the STP and RSTP. The convergence rate of the MSTP is fast. In addition, traffic of different VLANs passes through corresponding trails, which provides a well load balancing mechanism. The MSTP divides a switching network into different regions, each of which is called an MST region. Within each region, there are multiple spanning trees, which are independent from each other. Each spanning tree is a multiple spanning tree instance (MSTI). The MSTP sets the VLAN mapping table, which specifies the mapping relation between VLAN and MSTI. The network shown in Figure 1 can be considered as an MST region when MSTP is used. Thus, Figure 10-11 shows the result. It is computed that two spanning trees are generated for VLAN 2 and VLAN 3 respectively. l l MSTI 1 takes Switch B as the root switch to forward packets of VLAN 2. MSTI 2 takes Switch F as the root switch to forward packets of VLAN 3.
In this way, all VLAN packets can be properly forwarded. In addition, different VLAN packets are forwarded through different paths. Thus, the load is balanced.
Figure 10-11 MSTI in an MST region

Host A Switch A Switch B Host B
VLAN 3 Switch C VLAN 2 VLAN 3 VLAN 3 VLAN 2
VLAN 2 Switch D
Host C
Switch E
Switch F
Host D
Switch A
Switch B (Root)
Switch A
Switch B
VLAN 2 Switch C VLAN 2 VLAN 3 VLAN 2 Switch D
VLAN 3 Switch C VLAN 2 VLAN 3 VLAN 3
VLAN 2 Switch D
Switch E
Switch F
Switch E MSTI 2 -> VLAN 3
Switch F (Root)
MSTI 1 -> VLAN 2
10.3 Configuration Process of Ethernet Services

This section describes the configuration process of Ethernet services using figures.
10.3.1 EPL Service Configuration Process

This section describes the EPL service configuration process that mainly consists of deploying a network, configuring source NEs, configuring sink NEs, configuring pass-through NEs, and verifying services. Figure 10-12 shows the process for configuring EPL services.
Issue 02 (2011-10-31)
292
Figure 10-12 EPL service configuration process

Required Optional
Deploy a Network
Configure source NE
Configure sink NE
Configure pass-through NE
Verify service
Creating and Configuring NEs
Setting External Ports Attributes of Ethernet Boards
Setting External Ports Attributes of Ethernet Boards
Creating CrossConnection Between Line and Line Boards
Test the Ethernet Services
Creating Fibers Setting Internal Ports Attributes of Ethernet Boards Setting Internal Ports Attributes of Ethernet Boards
Checking the Connectivity of Ethernet Service Checking the Connectivity of Ethernet Port
Configuring Communication
Setting the NE Time
Creating CrossConnection Between Ethernet and Line Boards
Creating CrossConnection Between Ethernet and Line Boards
Configuring Clocks
Creating EPL Services
Creating EPL Services
Configuring Orderwire
Configuring Protection
NOTE
l In the landscape orientation of the configuration flow chart by using U2000, there are five main phases of EPL service configuration process. They are deploying a network, configuring source NEs, configuring sink NEs, configuring pass-through NEs, and verifying services. l The portrait orientation of the flow chart shows the relationships between operation tasks in each phase.
10.3.2 EVPL (QinQ) Service Configuration Process

This section describes the EVPL (QinQ) service configuration process that mainly consists of deploying a network, configuring the source NEs, configuring the sink NEs, configuring passthrough NEs, and verifying services. Figure 10-13 shows the process for configuring EVPL (QinQ) services.
Issue 02 (2011-10-31)
293
Figure 10-13 EVPL (QinQ) service configuration process

Required Optional
Deploying a Network
Configure source NE
Configure sink NE
Configure pass-through NE
Verify service
Enable NE Performance Monitoring
Back up NE Configuration Data
Creating and Configuring NEs
Setting External Ports Attributes of Ethernet Boards Setting Internal Ports Attributes of Ethernet Boards Creating CrossConnection Between Ethernet and Line Boards Creating EVPL(QinQ) Services
Creating Fibers
Setting External Ports Attributes of Ethernet Boards Setting Internal Ports Attributes of Ethernet Boards Creating CrossConnection Between Ethernet and Line Boards Creating EVPL(QinQ) Services
Creating CrossConnection Between Line and Line Boards
Test the Ethernet Services
Setting Performance Monitoring Parameters of an NE
Backing Up the NE Database to the SCC Board
Configuring Ethernet Service OAM Configuring the Ethernet Port OAM
Automatically Backing Up the NE Database to a CF Card Manually Backing Up the NE Database to a CF Card
Configuring Communication
Setting the NE Time Configuring Clocks Configuring Orderwire Configuring Protection
NOTE
l In the landscape orientation of the configuration flow chart by using U2000, there are five main phases of EVPL (QinQ) service configuration process. They are deploying a network, configure source NE, configure sink NE, configure pass-through NE and verify service. l The portrait orientation of the flow chart shows the relationships between operation tasks in each phase.
10.3.3 EPLAN Service Configuration Process

This section describes the EPLAN service configuration process that mainly consists of deploying a network, configuring source NEs, configuring sink NEs, configuring pass-through NEs, and verifying services. Figure 10-14 shows the process for configuring EPLAN services.
Issue 02 (2011-10-31)
294
Figure 10-14 EPLAN service configuration process

Required Optional Configure source NE Configure sink NE Configure pass-through NE
Enable NE Performance Monitoring
Deploying a Network
Verify service
Back up NE Configuration Data
Creating and Configuring NEs Creating Fibers Configuring Communicati on Setting the NE Time
Setting External Ports Attributes of Ethernet Boards Setting Internal Ports Attributes of Ethernet Boards
Setting External Ports Attributes of Ethernet Boards Setting Internal Ports Attributes of Ethernet Boards
Configuring CrossConnection Between Line and Line Boards
Test the Ethernet Services Checking the Connectivity of Ethernet Service Checking the Connectivity of Ethernet Port
Setting Performance Monitoring Parameters of an NE
Backing Up the NE Database to the SCC Board
Automatically Backing Up the NE Database to a CF Card Manually Backing Up the NE Database to a CF Card
Configuring Clocks Configuring Orderwire Configuring Protection
Creating CrossConnection Between Ethernet and Line Boards Creating EPLAN Services
Creating CrossConnection Between Ethernet and Line Boards Creating EPLAN Services
Creating VLAN
Creating VLAN
Configuring QOS
Configuring QOS
NOTE
l In the landscape orientation of the configuration flow chart by using U2000, there are five main phases of EPLAN service configuration process. They are deploying a network, configure source NE, configure sink NE, configure pass-through NE and verify service. l The portrait orientation of the flow chart shows the relationships between operation tasks in each phase.
10.4 Configuring Ethernet Services in an OTN System

This section describes how to configure Ethernet services in an OTN system.
10.4.1 Creating Cross-Connections on an Ethernet Board

Before the client Ethernet services are transmitted to the WDM side, appropriate crossconnections must be created on the U2000.
Prerequisite
You must be an NM user with "NE operator" authority or higher. Applicable to the LEM24, LEX4, TBE, L4G board. When you configure cross-connections, make sure that the source optical channel is the same as the sink optical channel.


Step 1 In the NE Explorer, click an NE and choose Configuration > WDM Service Management from the Function Tree. Step 2 Click the WDM Cross-Connection Configuration tab. Step 3 Click New and then the Create Cross-Connection Service dialog box is displayed. Step 4 Configure the parameters for the cross-connection and click OK. For details of the parameters, see 2.8.1 WDM Cross-Connection Configuration.
Step 5 Click Query. Confirm that the query results are the same as the values that are set. ----End
Procedure on the Web LCT

Step 1 In the NE Explorer, click an NE and choose Configuration > Electrical Cross-Connection Service Management from the Function Tree. Step 2 Click the Electrical Cross-Connection Configuration tab.
Step 3 Click New and then the Create Cross-Connection Service dialog box is displayed. Step 4 Configure the parameters for the cross-connection and click OK.
Step 5 Click Query. Confirm that the query results are the same as the values that are set. ----End
10.4.2 Creating EPL Services

You can configure EPL services for a single NE.
Prerequisite
You must be an NM user with "NE operator" authority or higher. The port attribute must be configured for the Ethernet board. The cross-connections must be configured for the Ethernet boards. Applicable to the TBE and L4G board of the OptiX OSN 6800 and OptiX OSN 3800. Applicable to the LEX4 and LEM24 board of the OptiX OSN 6800 and OptiX OSN 8800.

The configuration of service parameters on both ends of an Ethernet service must be the same. The following are the three types of EPL services that can be configured on the NMS. l l l EPL services between PORT and VCTRUNK ports. EPL services between VCTRUNK and VCTRUNK ports. EPL services between PORT and PORT ports.
Issue 02 (2011-10-31)
297

NOTE
l For the above three types of services, if the source VLAN ID and sink VLAN ID are different, this VLAN is a switched VLAN. To configure VLAN SNCP at the receive end of services, the source VLAN ID and sink VLAN ID must be the same. l For the port description and configuration rules of each board, refer to the Hardware Description of the corresponding equipment.

Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Step 2 Click the EPL Service tab. Click New and the Create Ethernet Line Service dialog box is displayed. Step 3 Select EPL from the Service Type drop-down list. Step 4 Configure the information related to the EPL service, such as Direction, Source Port, Sink Port, etc.
NOTE
l You can set Direction to unidirectional or bidirectional. l In Port Attributes, you can set Port Enabled and TAG for a port in the Create Ethernet Line Service dialog box, or in Ethernet Interface. l In Port Attributes, certain parameters can be modified. If port attributes are already set, however, retain the default values.
Step 5 Click Apply or OK. The created EPL service is displayed in the window. Step 6 Optional: If the VLAN SNCP is required at the receive end of services, after creating Ethernet services at the transmit end, double-click the OAM Enabled field corresponding to the Ethernet services and set it to Enabled.

NOTE
When creating the VLAN SNCP protection on the TBE board, you can choose not to enable the OAM function because a large volume of service data may be transmitted in consideration of bandwidth usage
----End
10.4.3 Creating EPLAN Services

Based on the Ethernet data layer 2 switch function, EPLAN services allow the accessed data to be transported to its destination media access control (MAC) address. This section describes the method to set the EPLAN service.
Prerequisite
You must be an NM user with "NE operator" authority or higher. The port attributes must be set for the Ethernet board. The electrical cross-connect services between the TBE board and the line board must be created. Applicable to the TBE, L4G board of the OptiX OSN 6800 and OptiX OSN 3800. Applicable to the LEX4, LEM24 board of the OptiX OSN 6800 and OptiX OSN 8800. Each TBE, L4G LEM24 and LEX4 board support one virtual bridge (VB).

One VB can be created in each Ethernet board in the system. Inside VBs, the MAC address learning function is used to complete the forwarding of Ethernet data. The MAC address table is updated periodically based on the address learning result.
Precaution
NOTE
Setting the parameters of a port affect the service of the board. Before setting the parameters of a port, configure State of the port as OOS at the Ethernet Interface. After setting the parameters, restore State of the port to IS.

Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Click the Service Mount tab. Step 2 Click New and the Create Ethernet LAN Service dialog box is displayed. Step 3 Complete the information of the EPLAN service. Enter a VB Name, and select VB Type and Bridge Switch Mode. Step 4 Click Configure Mount... in the Create Ethernet LAN Service dialog box. The Service Mount Configuration dialog box is displayed. Select a port in the Available Mounted Ports pane and click
Issue 02 (2011-10-31)
.
CAUTION
Modifying the ports that are mounted to the bridge may interrupt the service.
Step 5 Click OK to return to Create Ethernet LAN Service.
Issue 02 (2011-10-31)
300
Step 6 Click OK. Step 7 Select the Service Mount tab, and then click Query. The created EPLAN service is displayed.
NOTE
After you create an EPLAN service, if you want to set the Hub/Spoke attribute of a VB port, 1. Click Query in the Service Mount panel to query the parameters value. 2. Double-click Hub/Spoke and select an option from the drop-down list. Services are interoperable between Hub ports or between a Hub port and a Spoke port, but are isolated between Spoke ports.
----End
10.4.4 Creating VLANs Filtering

You can create VLANs to divide services in a virtual bridge (VB). The PORT port and the VCTRUNK port that have different VLANs are isolated and do not transmit services to each other.
Prerequisite
You must be an NM user with "NE operator" authority or higher. The port must be mounted to a VB. Make sure that you set Bridge Switch Mode to IVL/Ingress Filter Enable. Only in this way, you can create VLANs.


Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Select a service and click the VLAN Filtering tab. Step 2 Select the service and click New, the Create VLAN dialog box is displayed. Enter a VLAN ID, select an Available forwarding port, and then click .
Step 3 Click OK. Step 4 Click Query. Confirm that the query results are the same as the values that are set. Step 5 Create other VLAN Filtering according to the requirements. ----End
10.4.5 Creating VLAN Unicast

You can configure VLAN unicast, to allow a packet whose destination address is the specified MAC address, to be forwarded through the specified port in the specified VLAN. If the VB swapping mode is SVL/Ingress Filter Disable, the packets are forwarded through the specified port in the entire VB.
Prerequisite
You must be an NM user with "NE operator" authority or higher. The VLAN must be created.

Precaution
NOTE
Issue 02 (2011-10-31)
302

Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Click the VLAN Unicast tab. Step 2 Click New and the Create VLAN Unicast dialog box is displayed. Set VLAN ID, MAC Address, and Physical Port.
NOTE
The first byte of the MAC Address of VLAN unicast must be even. For the configuration of related parameters, see 10.20.10 Parameters: Ethernet LAN Service.
Step 3 Click OK. Step 4 Click Query. Confirm that the query results are the same as the values that are set. ----End
10.4.6 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
You are an NMS user with "Operator Group" authority or higher. Applicable to the TBE board of the OptiX OSN 6800 and OptiX OSN 3800. Applicable to the LEX4 and LEM24 boards of the OptiX OSN 6800 and OptiX OSN 8800. Applicable to the EGSH board of the OptiX OSN 8800.

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.

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.
Step 3 Click OK and then click Apply. ----End
10.4.7 Creating EVPL (QinQ) Services

When the services of multiple users that have the same C-VLAN ID are accessed on the same station and need to be transmitted on the same VCTRUNK, a layer of S-VLAN tag is added to isolate the services of different users from each other.
Prerequisite
You must be an NM user with "NE operator" authority or higher. The port attribute must be configured for the Ethernet board. The cross-connections must be configured for the Ethernet boards. Applicable to the TBE, L4G and ECOM board of the OptiX OSN 6800 and OptiX OSN 3800. Applicable to the LEX4 and LEM24 board of the OptiX OSN 6800 and OptiX OSN 8800.

EVPL (QinQ) services is the Ethernet service packets that are added with an S-VLAN tag or CVLAN tag. In this way, the extension of VLAN ID is realized.

Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Click the EPL Service tab. Step 2 Select the Display QinQ Shared Service check box in the lower right corner. Step 3 Click New and the Create Ethernet Line Service dialog box is displayed.
Step 4 Select EVPL(QinQ) from the Service Type drop-down list. Step 5 Configure the information related to the EVPL (QinQ) service, such as Direction, Source Port, Sink Port, etc.
NOTE
l You can only set Direction to unidirectional. l In Port Attributes, certain parameters can be modified. If port attributes are already set, however, use the default values. l In Port Attributes, you can set TAG for a port in Ethernet Interface.
Step 6 Click Apply or OK. The created EVPL service is displayed in the window. Step 7 Optional: To create VLAN SNCP at the receive end of services, after creating Ethernet services at the transmit end, double-click the field of OAM Enabled and set the value to Enabled. Step 8 Select the Ethernet Line Service tab, and then click Query. The created EVPL (QinQ) service is displayed.
NOTE
To transmit a large volume of service data, you do not need to set OAM Enabled during the creation of VLAN SNCP on the TBE board in consideration of bandwidth usage.
----End
10.5 Configuring Ethernet Services in an OCS System

This section describes how to configure Ethernet services in an OCS system.
10.5.1 Creating Cross-Connections Between an Ethernet Board and a Line Board

The cross-connections between an Ethernet board and a line board carry Ethernet services. Hence, you need to create cross-connections between the Ethernet board and the line board prior to creating Ethernet services.
Prerequisite
You must be an NM user with "NE operator" authority or higher. The EGSH and OCS line board must be installed.


Step 1 In the NE Explorer, select the NE and choose Configuration > SDH Service Configuration from the Function Tree.
NOTE
If the Web LCT is used, the navigation path is as follows: In the NE Explorer, select the NE and choose Configuration > Cross-Connection Configuration from the Function Tree.
Step 2 Click Create and the Create SDH Service dialog box is displayed. Step 3 Create a cross connection between Ethernet and line boards by entering the values of the attribute in the dialog box. For details of the parameters, see 9.7.1 SDH Service Configuration.
NOTE
l In the case of the EGSH board, Level can be set to only VC3 or VC4. l The service level and timeslot of the cross-connection created must be consistent with the level and timeslot of the bound path of the Ethernet interface.
Issue 02 (2011-10-31)
306
Step 4 Click OK.

NOTE
When the operation is performed on the U2000, the Operation Result dialog box is displayed, indicating that the operation is successful. Then, click Close.
----End
10.5.2 Creating EPL Services

You can create an EPL service on a per-NE basis.
Prerequisite
You are an NMS user with "Operator Group" authority or higher. Applies to the EGSH board.


Step 1 In the NE Explorer, select the EGSH board and choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Step 2 Click New. Step 3 In the Create Ethernet Line Service dialog box displayed, configure the relevant information about the EPL service.
NOTE
l If an appropriate path is not available in the Bound Path field, click Configuration to bind new paths. l To configure the VLAN ID, you can set the same or different VLAN IDs for both the source and the sink ports.
Step 4 Click OK. ----End

10.5.3 Creating EPLAN Services

You can create an EPLAN service on a per-NE basis.
Prerequisite
You must be an NM user with "NE operator" authority or higher. The port attributes and bound paths must be set for the Ethernet board. Applies to the EGSH board.


Step 1 In the NE Explorer, click the Ethernet board and choose Configuration > Ethernet Service > Ethernet LAN Service. Step 2 Click New. The Create Ethernet LAN Service dialog box is displayed. Step 3 Set the parameters of the bridge. Step 4 Configure service mounting relationships. Option Configure the services that are mounted to the IEEE 802.1d or IEEE 802.1q bridge. Configure the services that are mounted to the IEEE 802.1ad bridge. Description Go to Step 5. Go to Step 6.
Step 5 Optional: Configure the services that are mounted to the IEEE 802.1d or IEEE 802.1q bridge.
CAUTION
Modifying the ports that are mounted to the bridge may interrupt the service. 1. 2. 3. 4. Click Configure Mount. Select Available Mounted Ports and click Click OK. .
Optional: Repeat Step 5.2 and select other ports to be mounted.
Step 6 Optional: Configure the services that are mounted to the IEEE 802.1ad bridge. 1. Click Configure Mount.
Issue 02 (2011-10-31)
308
2.
Set the parameters for configuring mounted services.
3. 4. 5.
Click Add Mount Port. Repeat Step 6.2 to Step 6.3 to add the other mount ports. Click OK.
Step 7 Click Configuration to configure the VC paths that are bound with the internal ports. Step 8 Click OK and then click Close in the Operation Result dialog box.
NOTE
After you create an EPLAN service, if you want to set the Hub/Spoke attribute of a VB port, double-click Hub/Spoke and select an option from the drop-down list. Services are interoperable between Hub ports or between a Hub port and a Spoke port, but are isolated between Spoke ports.
----End
10.5.4 Creating VLANs Filtering

You can create VLANs to divide services in a virtual bridge (VB). The PORT port and the VCTRUNK port that have different VLANs are isolated and do not transmit services to each other.
Prerequisite
You must be an NM user with "NE operator" authority or higher. The port must be mounted to a VB. Make sure that you set Bridge Switch Mode to IVL/Ingress Filter Enable. Only in this way, you can create VLANs.


Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Select a service and click the VLAN Filtering tab. Step 2 Select the service and click New, the Create VLAN dialog box is displayed. Enter a VLAN ID, select an Available forwarding port, and then click .
Step 3 Click OK. Step 4 Click Query. Confirm that the query results are the same as the values that are set. Step 5 Create other VLAN Filtering according to the requirements. ----End
10.5.5 Creating VLAN Unicast

You can configure VLAN unicast, to allow a packet whose destination address is the specified MAC address, to be forwarded through the specified port in the specified VLAN. If the VB swapping mode is SVL/Ingress Filter Disable, the packets are forwarded through the specified port in the entire VB.
Prerequisite
You must be an NM user with "NE operator" authority or higher. The VLAN must be created.

Precaution
NOTE
Issue 02 (2011-10-31)
310

Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Click the VLAN Unicast tab. Step 2 Click New and the Create VLAN Unicast dialog box is displayed. Set VLAN ID, MAC Address, and Physical Port.
NOTE
The first byte of the MAC Address of VLAN unicast must be even. For the configuration of related parameters, see 10.20.10 Parameters: Ethernet LAN Service.
Step 3 Click OK. Step 4 Click Query. Confirm that the query results are the same as the values that are set. ----End
10.5.6 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
You are an NMS user with "Operator Group" authority or higher. Applicable to the TBE board of the OptiX OSN 6800 and OptiX OSN 3800. Applicable to the LEX4 and LEM24 boards of the OptiX OSN 6800 and OptiX OSN 8800. Applicable to the EGSH board of the OptiX OSN 8800.

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.

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.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The port attribute must be configured for the Ethernet board. The cross-connections must be configured for the Ethernet boards. Applicable to the TBE, L4G and ECOM board of the OptiX OSN 6800 and OptiX OSN 3800. Applicable to the LEX4 and LEM24 board of the OptiX OSN 6800 and OptiX OSN 8800.

EVPL (QinQ) services is the Ethernet service packets that are added with an S-VLAN tag or CVLAN tag. In this way, the extension of VLAN ID is realized.

Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Click the EPL Service tab. Step 2 Select the Display QinQ Shared Service check box in the lower right corner. Step 3 Click New and the Create Ethernet Line Service dialog box is displayed.
Step 4 Select EVPL(QinQ) from the Service Type drop-down list. Step 5 Configure the information related to the EVPL (QinQ) service, such as Direction, Source Port, Sink Port, etc.
NOTE
l You can only set Direction to unidirectional. l In Port Attributes, certain parameters can be modified. If port attributes are already set, however, use the default values. l In Port Attributes, you can set TAG for a port in Ethernet Interface.
Step 6 Click Apply or OK. The created EVPL service is displayed in the window. Step 7 Optional: To create VLAN SNCP at the receive end of services, after creating Ethernet services at the transmit end, double-click the field of OAM Enabled and set the value to Enabled. Step 8 Select the Ethernet Line Service tab, and then click Query. The created EVPL (QinQ) service is displayed.
NOTE
To transmit a large volume of service data, you do not need to set OAM Enabled during the creation of VLAN SNCP on the TBE board in consideration of bandwidth usage.
----End

Prerequisite
You must be an NM user with "NE operator" authority or higher. Applicable to the EGSH board of the OptiX OSN 8800.


Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Click New. Step 2 Select the Display QinQ Shared Service check box in the lower right corner. Step 3 Click New and the Create Ethernet Line Service dialog box is displayed. Step 4 Complete the information of the EVPL (QinQ) service.
NOTE
If an appropriate path is not available in the Bound Path field, click Configuration to bind new paths.
Issue 02 (2011-10-31)
314
Step 5 Click OK. ----End
10.6 Configuration Example: Configuring EPL Services

The EPL service provides 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.

This section describes the Ethernet service configuration in a ring network.
Service Requirement
See Figure 10-15. The optical NEs (ONEs) A, B, C and D form a ring network. All the ONEs function as OADM stations.
There is Ethernet communication between User1 and User2. In addition, a bidirectional EPL service exists between stations A and C and passes through station B. The working mode of the bidirectional EPL service is set to auto-negotiation and the bidirectional EPL service does not support the VLAN function. Figure 10-15 Networking diagram for configuring EPL services
User1 NM
IU 3 LEM24
IU 3 LEM24
B C
D IU 3 LEM24
IU 3 LEM24
NG WDM Equipment
User2

In this example, each station is configured with one LEM24 board.
10.6.2 Service Signal Flow and Wavelength Allocation

Ethernet services are received from an external port, encapsulated through an internal port, and transparently transmitted on the WDM network. In this way, the node communicates with the remote node. Figure 10-16 shows the signal flow of the bidirectional EPL services between stations A and C.
Issue 02 (2011-10-31)
316
Figure 10-16 Service signal flow of the bidirectional EPL service

ONE C
PORT5 PORT6 PORT7 PORT28 AP1 AP2 AP3 AP4 2(IN2/OUT2)-1 (VCTrunck 2)
LEM24
1(IN1/OUT1)-1 (VCTrunck 1)
ONE B
1(IN1/OUT1)-1 (VCTrunck 1) 2(IN2/OUT2)-1 (VCTrunck 2)
LEM24
ONE A
AP1 AP2 AP3 AP4 PORT5 PORT6 PORT7 PORT28
LEM24
:Client-side signals
:WDM-side working service
:Working service direction
Figure 10-17 shows the wavelength allocation. Figure 10-17 Wavelength allocation diagram
Wavelength(nm)/ Frequency(THz) A B C D
1560.61/ 192.10
Working channel
Table 10-4 Parameters of external ports on the Ethernet boards Parameter Board Port Port Enabled Working Mode Maximum Frame Length A 3-LEM24 PORT7 Enabled Auto-Negotiation 1522 C 3-LEM24 PORT7 Enabled Auto-Negotiation 1522
Table 10-5 Parameters of internal ports on the Ethernet boards Parameter Board Port A 3-LEM24 VCTRUNK1 C 3-LEM24 VCTRUNK1
Issue 02 (2011-10-31)
317
Table 10-6 Parameters of the EPL services Parameter Board Service Type Direction Source Port Source C-VLAN (e.g. 1,3-6) Sink Port Sink C-VLAN (e.g. 1,3-6) EPL Service of A 3-LEM24 EPL Bidirectional VCTRUNK1 PORT7 EPL Service of B 3-LEM24 EPL Bidirectional VCTRUNK1 VCTRUNK2 EPL Service of C 3-LEM24 EPL Bidirectional PORT7 VCTRUNK1 -

This section describes how to configure an EPL service through an example in which station C transmits the EPL service to station A. The case that station A transmits the EPL service to station C is similar, and thus is not described in this section.
Prerequisite
You must read and understand the contents of Configuration Process of the EPL Service.


Step 1 Configure the EPL service that User2 occupies at station C. 1. Configure the attributes of the external port that User2 occupies. a. In the NE Explorer, select the LEM24 board in slot 3 and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Then, select External Port. Click the Basic Attributes tab. After setting the parameter on this tab page, click Apply. For details on parameter settings, see 10.20.1 Parameters: Basic Attributes (External Port). Parameter Port Enabled Value PORT7: Enabled Description The EPL service of User2 occupies the external port PORT7, and the enabling status of PORT7 is set to Enabled.
b.
Issue 02 (2011-10-31)
318
Parameter Working Mode
Value PORT7: AutoNegotiation
Description The access equipment of the EPL service of User2 supports autonegotiation, and the working mode of PORT7 is set to Auto-Negotiation. In general, the default value 1522 is used. The MAC loopback setting is used for fault diagnosis. When configuring a service, set this parameter to NonLoopback. The PHY loopback setting is used for fault diagnosis. When configuring a service, set this parameter to NonLoopback.
Maximum Frame Length MAC Loopback
PORT7: 1522 PORT7: NonLoopback
PHY Loopback
PORT7: NonLoopback
c. d.
Click the Flow Control tab. The default value of the parameter is recommended. Click the TAG Attributes tab. After setting the parameter on this tab page, click Apply. For details on parameter settings, see 10.20.6 Parameters: TAG Attributes. Parameter TAG Value PORT7: Access Description The access equipment of the service of User2 does not support the VLAN function. The transmitted data does not contain the VLAN ID. In this case, the TAG identifier of PORT7 is set to Access. The EPL service of User2 occupies the PORT and VCTRUNK interfaces exclusively, and the service does not need to be separated by using a VLAN ID. In this case, you do not need to configure the VLAN ID but retain the default value. The VLAN ID is not required, and thus VLAN priority is also not required. In this case, retain the default value, namely 0.
Default VLAN ID
PORT7: 1
VLAN Priority
PORT7: 0
e.
Click the Network Attributes tab. After setting the parameter on this tab page, click Apply. For details on parameter settings, see 10.20.7 Parameters: Network Attributes.
Issue 02 (2011-10-31)
319
Parameter Port
Value PORT7: UNI
Description If the port is a UNI port, the port processes the 802.1Q tag header. The port attributes include Tag Aware, Access, and Hybrid.
2.
Configure the attribute of the internal port that User2 occupies. a. In the NE Explorer, select the LEM24 board in slot 3 and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Then, select Internal Port. Click the Network Attributes tab. After setting the parameter on this tab page, click Apply. For details on parameter settings, see 10.20.7 Parameters: Network Attributes. Parameter Port Value VCTRUNK1: UNI Description If the port is a UNI port, the port processes the 802.1Q tag header. The port attributes include Tag Aware, Access, and Hybrid.
b.
c.
Click the TAG Attributes tab. After setting the parameter on this tab page, click Apply. For details on parameter settings, see 10.20.6 Parameters: TAG Attributes. Parameter TAG Value VCTRUNK1: Tag Aware Description For the internal port, you do not need to configure the tag header but retain the default value, namely Tag Aware.
3.
Configure the EPL service of User2 at station C. a. In the NE Explorer, select the LEM24 board in slot 3 and then choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Click the EPL Service tab. Click New at the bottom of the window. The Create Ethernet Line Service dialog box is displayed. Enter the attributes of the Ethernet private line service in the dialog box. For details on parameter settings, see 10.20.8 Parameters: Ethernet Line Service.
b. c.
Issue 02 (2011-10-31)
320
Parameter Service Type Direction Source Port Source C-VLAN (e.g. 1,3-6) Sink Port Sink C-VLAN (e.g.1, 3-6)
Value EPL Bidirectional PORT7 VCTRUNK1 -
Description The service type of User2 is EPL. The service of User2 is a bidirectional service. Indicates the name of the source port. Keep this item empty. Indicates the name of the sink port. Keep this item empty.
d.
Click OK, and the created Ethernet private line service is displayed on the interface.
Step 2 Configure pass-through EPL services at station B. 1. Configure the attributes of the external port at station B. a. In the NE Explorer, select the LEM24 board in slot 3 and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Then, select Internal Port. Click the Network Attributes tab. After setting the parameter on this tab page, click Apply. For details on parameter settings, see 10.20.7 Parameters: Network Attributes. Parameter Port Value VCTRUNK1: UNI VCTRUNK2: UNI Description If the port is a UNI port, the port processes the 802.1Q tag header. The port attributes include Tag Aware, Access, and Hybrid.
321
b.
Issue 02 (2011-10-31)
c.
Click the TAG Attributes tab. After setting the parameter on this tab page, click Apply. For details on parameter settings, see 10.20.6 Parameters: TAG Attributes. Parameter TAG Value VCTRUNK1: Tag Aware VCTRUNK2: Tag Aware Description For the internal port, you do not need to configure the tag header but retain the default value, namely Tag Aware.
2.
Configure the EPL service at station B. a. In the NE Explorer, select the LEM24 board in slot 3 and then choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Click the EPL Service tab. Click New on the lower right of the window. The Create Ethernet Line Service dialog box is displayed. Enter the attributes of the Ethernet private line service in the dialog box. For details on parameter settings, see 10.20.8 Parameters: Ethernet Line Service.
b. c.
Parameter Service Type Direction Source Port Source S-VLAN (e.g.1, 3-6) Sink Port
Value EPL Bidirectional VCTRUNK1 VCTRUNK2
Description The service type is EPL. The service is a bidirectional service. Indicates the name of the source port. Keep this item empty. Indicates the name of the source port.
Issue 02 (2011-10-31)
322
Parameter Sink S-VLAN (e.g.1, 3-6)
Value -
Description Keep this item empty.
d.
Click OK, and the created EPL service is displayed on the interface.
Step 3 Configure the EPL service that User1 occupies at station A. Configure the EPL service at station A by referring to step 1. Step 4 Verify the service configurations of User2 and User1. For the verification procedure, see Testing Ethernet Service Channels in the Commissioning Guide.
NOTE
The external ports on the Ethernet boards at the source and sink ends of the accessed Ethernet service must be set to Access, and the default VLAN ID must be set to the same value.
Step 5 Enable the performance monitoring function for the NEs. For the operation procedures, see Setting Performance Monitoring Parameters of an NE in the Commissioning Guide. Step 6 Back up the configuration data on the NEs. Two methods are available for the backup.
NOTE
Only the U2000 supports backing up the configuration data of NEs.
Option The SCC board is not configured with any CF card The SCC board is configured with a CF card
Description See Backing Up the NE Database to the SCC Board in the Commissioning Guide See Manually Backing Up the NE Database to a CF Card in the Commissioning Guide
----End
10.7 Configuration Example: Configuring EVPL (QinQ) Services on a WDM Network

EVPL (QinQ) services realize the nesting of VLAN. With the increase of network users, the existing number of VLAN IDs fails to meet the requirement of users. After EVPL (QinQ) services are configured, however, users can be identified through multiple layers of VLAN IDs. In this case, VLAN extension is achieved.

This section describes the Ethernet service configuration in a ring network.
Service Requirement
See Figure 10-18. The optical NEs (ONEs) A, B, and C form a ring network, and all the ONEs are OADM stations.
There is Ethernet communication between User1 and User2. In addition, a bidirectional EVPL (QinQ) service exists between stations A and B. The working mode of the bidirectional EVPL (QinQ) service is set to auto-negotiation. Figure 10-18 Networking diagram for configuring EVPL(QinQ) service
IU 3 NM
LEM24
C
IU 3 LEM24 IU 3 LEM24
A
User 1
B
User 2
NG WDM Equipment

In this example, each station is configured with one LEM24 board.
10.7.2 Service Signal Flow and Wavelength Allocation

Ethernet services are received from an external port, encapsulated through an internal port, and transparently transmitted on the WDM network. In this way, the node communicates with the remote node. Figure 10-19 shows the signal flow of the bidirectional EVPL (QinQ) services between stations A and B. Figure 10-19 Service signal flow of EVPL (QinQ) service
ONE A
PORT5 PORT6 PORT7 PORT28 AP1 AP2 AP3 AP4 2(IN2/OUT2)-1 2(IN2/OUT2)-1 1(IN1/OUT1)-1 1(IN1/OUT1)-1
ONE B
AP1 AP2 AP3 AP4 PORT5 PORT6 PORT7 PORT28
LEM24
LEM24
:Client-side signals :WDM-side working service :Working service direction
Issue 02 (2011-10-31)
324
Wavelength(nm)/ Frequency(THz) A B C
1560.61/ 192.10
Working channel
Table 10-7 Parameters of external ports on the Ethernet boards Parameters Board Port Port Enabled Working Mode Maximum Frame Length A 3-LEM24 PORT7 Enabled Auto-Negotiation 1522 B 3-LEM24 PORT7 Enabled Auto-Negotiation 1522
Table 10-8 Parameters of internal ports on the Ethernet boards Parameter Board Port A 3-LEM24 VCTRUNK1 B 3-LEM24 VCTRUNK1
Table 10-9 Parameters of the EVPL (QinQ) service Parameter Service Type Direction Operation Type Source Port
Issue 02 (2011-10-31)
EVPL (QinQ) Service of A EVPL (QinQ) Bidirectional Add S-VLAN PORT7

EVPL (QinQ) Service of B EVPL (QinQ) Bidirectional Strip S-VLAN VCTRUNK1

325
Parameter Sink Port Sink S-VLAN
EVPL (QinQ) Service of A VCTRUNK1 1
EVPL (QinQ) Service of B PORT7 1

This section describes how to configure an EVPL (QinQ) service through an example in which station A transmits the EVPL (QinQ) service to station B. The case that station B transmits the EVPL (QinQ) service to station A is similar, and thus is not described in this section.
Prerequisite
You must read and understand the contents of Configuration Process of the EVPL (QinQ) Service.


Step 1 Configure the EVPL (QinQ) service that User1 occupies at station A. 1. Configure the attributes of the external port that User1 occupies. l In the NE Explorer, select the LEM24 board in slot 3 and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Then, select External Port. l Click the Basic Attributes tab. After setting the parameter on this tab page, click Apply. For details on parameter settings, see Description of the Basic Attributes Parameter (External Port). Parameter Port Enabled Value PORT7: Enabled Description The EVPL (QinQ) service of User1 occupies the external port PORT7, and the enabling status of PORT7 is set to Enabled. The access equipment of the EVPL (QinQ) service of User1 supports autonegotiation, and the working mode of PORT7 is set to Auto-Negotiation. In general, the default value 1522 is used.
Working Mode
PORT7: AutoNegotiation
Maximum Frame Length
PORT7: 1522
l Click the Flow Control tab. The default value of the parameter is recommended. For the default value of the parameter, see Description of the Flow Control Parameter (External Port).
l Click the TAG Attributes tab. After setting the parameter on this tab page, click Apply. For the default value of the parameter, see Description of the TAG Attributes Parameter. Parameter Port Value PORT7: C-Aware Description In the case of C-Aware, the port does not process the TAG attribute of 802.1Q. It determines that the data packet carries C-VLAN tag and processes the data packet based on the C-VLAN tag.
2.
Configure the attribute of the internal port that User1 occupies. l In the NE Explorer, select the LEM24 board in slot 3 and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Then, select Internal Port. l Click the Network Attributes tab. After setting the parameter on this tab page, click Apply. For details on parameter settings, see Description of the Network Attributes Parameter. Parameter Port Value VCTRUNK1: SAware Description In the case of S-Aware, the port does not process the TAG attribute of 802.1Q. It determines that the data packet carries S-VLAN tag and processes the data packet based on the S-VLAN tag.
l Click the TAG Attributes tab. After setting the parameter on this tab page, click Apply. For details on parameter settings, see Description of the TAG Attributes Parameter. Parameter TAG Value VCTRUNK1: Tag Aware Description For the internal port, you do not need to configure the tag header but retain the default value, namely Tag Aware.
3.
Configure the EVPL (QinQ) service of User1 at station A. l In the NE Explorer, select the LEM24 board in slot 3 and then choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Click the EPL Service tab. l Select Display QinQ Shared Service check box in the lower right corner. l Click New on the lower right of the window. The Create Ethernet Line Service dialog box is displayed. l Enter the attributes of the Ethernet private line service in the dialog box.
Issue 02 (2011-10-31)
327
Parameter Service Type Direction Operation Type Source Port Sink Port Sink S-VLAN (e.g.1, 3-6)
Value EVPL (QinQ) Bidirectional Add S-VLAN PORT7 VCTRUNK1 1
Description The service type of User1 is EVPL (QinQ). The service of User1 is a bidirectional service. Add the label of S-VLAN. Indicates the name of the source port. Indicates the name of the sink port. Select the S-VLAN.
l Click OK, and the created EVPL (QinQ) service is displayed on the interface. Step 2 Configure the EVPL (QinQ) service that User2 occupies at station B. Configure the EVPL (QinQ) service at station B by referring to step 1. Step 3 Verify the service configurations of User2 and User1. For the verification procedure, see Testing Ethernet Service Channels in the Commissioning Guide. Step 4 Enable the performance monitoring function for the NEs. For the operation procedures, see Setting Performance Monitoring Parameters of an NE in the Commissioning Guide. Step 5 Back up the configuration data on the NEs. Two methods are available for the backup.
Issue 02 (2011-10-31)
328
----End
10.8 Configuration Example: Configuring EPLAN Services (IEEE 802.1d Bridge) on a WDM Network
The EPLAN service (IEEE 802.1d bridge) provides an LAN solution for multipoint-tomultipoint convergence. This service applies in cases where user-side data communication equipment connected to the transmission network does not support VLANs or where the VLAN planning is kept secret from the network operator.

The convergence node needs to exchange Ethernet services with two access nodes at Layer 2. The two access nodes need not communicate with each other.
Service Requirement
On the network as shown in Figure 10-21, the service requirements are as follows: l l Three branches (F1, F2, and F3) of user F are located at NE1, NE2, and NE4. F1 needs to communicate with F2 and F3. The Ethernet equipment of user F provides Ethernet optical ports that work in autonegotiation mode and support VLANs. VLAN IDs and the number of VLANs, however, are unknown and may be changed.
NOTE
The application scenarios whether one branch needs to communicate with other branches are as follows: l Branches F2 and F3 need to communicate with each other. l Branches F2 and F3 do not need to communicate with each other. If branches F2 and F3 need to communicate with each other, skip Step 2.
Issue 02 (2011-10-31)
329
Figure 10-21 Networking diagram for configuring EPLAN services (IEEE 802.1d bridge)
NM
IU 3
LEM24
IU 3
LEM24
NE 3 NE 2 NE 4 NE 1
IU 3
LEM24
F2
F3
IU 3
LEM24 VB VCTRUNK1 VCTRUNK2 PORT7 F1
NG WDM equipment VCTRUNCK

In this example, the convergence node NE1 is configured with one LEM24 boards that supports the IEEE 802.1d bridge, thus implementing EPLAN services wherein user VLANs are not limited. The access nodes NE2 and NE4 are configured with one LEM24 board each. The EPL services are configured to be transparently transmitted from NE2 and NE4 to NE1.
10.8.2 Service Signals Flow and Wavelength Allocation

The Ethernet services of the convergence node are received from an external port, forwarded to an internal port through Layer 2 switching, encapsulated, and transparently transmitted on the WDM network. In this manner, the node communicates with a remote node. Figure 10-22 shows the signal flow of the EPLAN services (IEEE 802.1d bridge) and the timeslot allocation to the EPLAN services (IEEE 802.1d bridge).
Issue 02 (2011-10-31)
330
Figure 10-22 Service signal flow of the EPLAN service

LEM24
1(IN1/OUT1)-1
(VCTRUNCK 1)
ONE 2
AP1 PORT5 PORT6 PORT7 PORT28
ONE 1
PORT5 PORT6 PORT7 PORT8 PORT28 VB
LEM24
1(IN1/OUT1)-1
(VCTRUNCK 1) (VCTRUNCK 2)
2(IN2/OUT2)-1
(VCTRUNCK 2)
2(IN2/OUT2)-1
LEM24
1(IN1/OUT1)-1
(VCTRUNCK 1)
ONE 4
AP1 PORT5 PORT6 PORT7 PORT28
:Client-side signals :WDM-side working service :Working service direction
(VCTRUNCK 2)
2(IN2/OUT2)-1
Wavelength(nm)/ Frequency(THz) 1560.61/192.10 1559.79/192.20
NE1
NE2
NE3
NE4
Working channel
Table 10-10 Parameters of external ports on the Ethernet boards Parameter Board Port Port Enabled Working Mode Maximum Frame Length Entry Detection TAG Port Type NE2 1-LEM24 PORT7 Enabled Auto-Negotiation 1522 NE1 3-LEM24 PORT7 Enabled Auto-Negotiation 1522 Enabled Tag Aware UNI NE4 1-LEM24 PORT7 Enabled Auto-Negotiation 1522 -
Issue 02 (2011-10-31)
331
Table 10-11 Parameters of internal ports on the Ethernet boards Parameter Board Port NE2 1-LEM24 VCTRUNK1 NE1 3-LEM24 VCTRUNK1 NE4 1-LEM24 VCTRUNK1
Table 10-12 Parameters of the EPLAN services (IEEE 802.1d bridge) Parameter VB Name VB Type Bridge Switch Mode Bridge Learning Mode Ingress Filter VB Mount Port Hub/Spoke PORT7 VCTRUNK1 VCTRUNK2 EPLAN Service of NE1 VB 802.1d SVL/Ingress Filter Disable SVL Disabled PORT7, VCTRUNK1, VCTRUNK2 Hub Spoke Spoke

At the convergence node NE1, you need to create an EPLAN service (IEEE 802.1d bridge). At the access nodes NE2 and NE4, you need to configure only transparently transmitted EPL services.
Prerequisite
You must read and understand the contents of Configuration Process of the EPLAN Service.


Step 1 Configure EPLAN services for users F1, F2, and F3 on NE1. 1.
Issue 02 (2011-10-31)
Set the attributes of the external port used by the service of user F1.
l In the NE Explorer, select the LEM24 board in slot 3 and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. l Select External Port. l Click the Basic Attributes tab. After setting the parameter on this tab page, click Apply. For details on parameter settings, see Description of the Basic Attributes Parameter (External Port). Parameter Port Enabled Working Mode Value PORT7: Enabled PORT7: AutoNegotiation Description Set PORT7 to Enabled. If the Ethernet service access equipment of user F1 supports the autonegotiation function, set the working mode of PORT7 to Auto-Negotiation. Generally, this parameter is set to 1522 by default. The loopback setting is used for fault diagnosis. When configuring a service, set this parameter to Non-Loopback. The loopback setting is used for fault diagnosis. When configuring a service, set this parameter to Non-Loopback.
Maximum Frame Length MAC Loopback
PORT7: 1522 PORT7: NonLoopback PORT7: NonLoopback
PHY Loopback
l Click the Flow Control tab. The default value of the parameter is recommended. For the default value of the parameter, see Description of the Flow Control Parameter (External Port). l Click the TAG Attributes tab. After setting the parameter on this tab page, click Apply. For details on parameter settings, see Description of the TAG Attributes Parameter. Parameter Entry Detection Value PORT7: Enabled Description If the packets of user F1 carry VLAN tags, you need to enable the entry detection function to detect the VLAN tags of packets. In this case, set this parameter to Enabled. If the service access equipment of user F1 supports VLAN and if the transmitted data frames carry VLAN tags, set these parameters to Tag Aware for PORT7 and PORT8. If TAG is set to Tag Aware, it is unnecessary to set Default VLAN ID. If TAG is set to Tag Aware, it is unnecessary to set VLAN Priority.
TAG
PORT7: Tag Aware
Default VLAN ID VLAN Priority
Issue 02 (2011-10-31)
333
l Click the Network Attributes tab. After setting the parameter on this tab page, click Apply. For details on parameter settings, see Description of the Network Attributes Parameter. Parameter Port Type Value PORT7: UNI Description A UNI port is connected to the equipment on the user side because it is provided by the service provider. This port processes the packets with TAG attributes specified in IEEE 802.1q. In addition, this port identifies and processes the VLAN information of the received packets according to the supported Tag Aware, Access, or Hybrid attribute.
2.
Configure the attribute of the internal port that F1 occupies. l In the NE Explorer, select the LEM24 board in slot 3 and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. l Select Internal Port. l Click the Network Attributes tab. After setting the parameter on this tab page, click Apply. For details on parameter settings, see Description of the Network Attributes Parameter. Parameter Port Value VCTRUNK1: UNI Description If the port is a UNI port, the port processes the 802.1Q tag header. The port attributes include Tag Aware, Access, and Hybrid.
l Click the TAG Attributes tab. After setting the parameter on this tab page, click Apply. For details on parameter settings, see Description of the TAG Attributes Parameter. Parameter Entry Detection Value VCTRUNK1: Enabled Description If the data frames of users F2 and F3 carry VLAN tags, you need to enable the entry detection function to detect the VLAN tags of packets. In this case, set this parameter to Enabled. For the internal port, you do not need to configure the tag header but retain the default value, namely Tag Aware.
TAG
VCTRUNK1: Tag Aware
3.
Create a bridge for the LEM24 board on NE1. l In the NE Explorer, select the LEM24 board and then choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree.
Issue 02 (2011-10-31)
334
l Click New. l Set the parameters in the Create Ethernet LAN Service dialog box that is displayed. For details on parameter settings, see 10.20.10 Parameters: Ethernet LAN Service. Parameter Value in This Example VB Description
VB Name
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. The IEEE 802.1d MAC bridge learns and forwards the packets according to 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 isolated. When the bridge adopts the SVL learning mode, all the VLANs share the same MAC address table. That is, the bridge learns and forwards the packets according to 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. -
VB Type
802.1d
Bridge Switch Mode
SVL/Ingress Filter Disable
Bridge Learning Mode Ingress Filter MAC Address Selflearning
SVL
Disabled Enabled
The IEEE 802.1d MAC bridge does not detect the VLAN tags of the received packets. -
l Click Configure Mountnt.... l In Available Mounted Ports, select PORT7, VCTRUNK1 and VCTRUNK2. Then, click . l Click OK. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. l In the Create Ethernet LAN Service dialog box that is displayed, click OK. 4. Change the Hub/Spoke attribute of the ports mounted to the bridge.
NOTE
If normal communication is required between user F2 and user F3, go to Step 2.
Issue 02 (2011-10-31)
335
l Select the created bridge and click the Service Mount tab. l Change the Hub/Spoke attribute of the port mounted to the bridge. After setting the parameters, click Apply. Parameter Hub/Spoke Value PORT7: Hub VCTRUNK2: Spoke VCTRUNK1: Spoke Description If user F1 needs to communicate with users F2 and F3 respectively, set PORT7 that accesses the services of user F1 to Hub. A port of the Hub attribute can communicate with a port of the Spoke or Hub attribute. If user F2 does not need to communicate with user F3, set the VCTRUNK1 and VCTRUNK2 that receive the services of users F2 and F3 to Spoke. Ports of the Spoke attribute cannot communicate with each other.
Step 2 Configure EPL services on NE2 and NE4.

NOTE
The Ethernet services on NE2 and NE4 are EPL services transparently transmitted from point to point. Complete the configuration based on the planned parameters by referring to the operations described in 10.6 Configuration Example: Configuring EPL Services
Step 3 Verify the correctness of the service configuration. For the verification procedure, see Testing Ethernet Service Channels in the Commissioning Guide.
NOTE
NOTE
After the test, change the modified parameter values to the values specified in the service configuration.
Step 4 Enable the performance monitoring function for the NEs. For the operation procedures, see Setting Performance Monitoring Parameters of an NE in the Commissioning Guide. Step 5 Back up the configuration data on the NEs. Two methods are available for the backup. Option The SCC board is not configured with any CF card The SCC board is configured with a CF card Description See Backing Up the NE Database to the SCC Board in the Commissioning Guide See Manually Backing Up the NE Database to a CF Card in the Commissioning Guide
----End
Issue 02 (2011-10-31)
336
10.9 Configuration Example: Configuring EVPLAN Services (IEEE 802.1q Bridge) on a WDM Network
The EVPLAN service (IEEE 802.1q bridge) provides an LAN solution for multipoint-tomultipoint convergence. This service applies in cases where user-side data communication equipment connected to the transmission network does not support VLANs or where the VLAN planning is open to the network operator.

The convergence node needs to exchange Ethernet services with two access nodes at Layer 2. LAN services of the two users (H and G) need to be isolated.
Service Requirement
On the network as shown in Figure 10-24, the service requirements are as follows: l l l l Three branches (G1, G2, and G3) of user G are located at NE1, NE2, and NE4 respectively. G2 and G3 do not need to communicate with each other. Three branches (H1, H2, and H3) of user H are located at NE1, NE2, and NE4 respectively. The service of user G needs to be isolated from the service of user H. The Ethernet equipment of user G and user H provides Ethernet electrical ports that work mode in auto-negotiation mode and do not support VLANs.
Figure 10-24 Networking diagram for configuring EVPLAN services (IEEE 802.1q bridge)
IU 3 NM
LEM24
NE 3
IU 3 LEM24
IU 3
LEM24
NE 2
H2 G2 H1 VB2 VLAN 200 VCTRUNK1 PORT8 NG WDM equipment VCTRUNK2 IU 3
NE 4 NE 1
G3 G1 LEM24 VB1 VLAN 100 VCTRUNK1 POR7 VCTRUNCK VCTRUNK2 H3
Issue 02 (2011-10-31)
337

In this example, the convergence node NE 1 is configured with one LEM24 board that supports the IEEE 802.1q bridge to implement EVPLAN services in which user data is isolated. The access nodes NE2 and NE4 are configured with an LEM24 board respectively. EVPL services are configured to implement transparent transmission from NE2 and NE4 to NE1.
10.9.2 Service Signals Flow

The Ethernet services of the convergence node are received from an external port and tagged with the corresponding VLAN IDs. After the services are forwarded to an internal port through Layer 2 switching, the VLAN IDs are stripped and then the services are transparently transmitted in the WDM network. In this way, the node communicates with a remote node. Figure 10-25 shows the signal flow of the EPLAN services (IEEE 802.1q bridge) and the timeslot allocation to the EPLAN services (IEEE 802.1q bridge). Figure 10-25 Service signal flow of the EPLAN service
LEM24
ONE 4
AP1 PORT7 PORT8
ONE 1
PORT7
VB1
LEM24
1(IN1/OUT1)-1
(VCTRUNCK1)
1(IN1/OUT1)-1
(VCTRUNCK1)
PORT8
VB2
2(IN2/OUT2)-1
(VCTRUNCK2)
LEM24
(VCTRUNCK2)
ONE 2
AP2 PORT7 PORT8
2(IN2/OUT2)-1
:Client-side signals :WDM-side working service
:Working service of H :Working service of G
Table 10-13 Parameters of external ports on the Ethernet boards Paramete r Board Port NE1 3-LEM24 PORT7 PORT8 Port Enabled Working Mode Enabled AutoNegotiatio n Enabled AutoNegotiatio n Enabled Auto-Negotiation Enabled Auto-Negotiation PORT8 NE2 3-LEM24 PORT7 PORT8 NE4 3-LEM24 PORT7 PORT8
Issue 02 (2011-10-31)
338
Paramete r Maximum Frame Length TAG Entry Detection Default VLAN ID VLAN Priority Port Type
NE1 1522 1522
NE2 1522 1522
NE4 1522 1522
Access Enabled 100 0 UNI
Table 10-14 Parameters of internal ports on the Ethernet boards Parameter Board Port TAG Entry Detection Default VLAN ID VLAN Priority Port Type NE1 3-LEM24 VCTRUNK1 Access Enabled 100 0 UNI VCTRUNK2 Access Enabled 200 0 UNI NE2 3-LEM24 VCTRUNK1 Enabled UNI NE4 3-LEM24 VCTRUNK1 Enabled UNI
Table 10-15 Parameters of the EPLAN services (IEEE 802.1q bridge) Parameter VB Name VB Type Bridge Switch Mode Bridge Learning Mode Ingress Filter EPLAN Service of NE1 VB 802.1q IVL/Ingress Filter Enable IVL Enabled
Issue 02 (2011-10-31)
339
Parameter VB Mount Port VLAN Filtering
EPLAN Service of NE1 PORT7, PORT8, VCTRUNK1, VCTRUNK2 VLAN Filtering VLAN ID Forwarding Physical Port VLAN filter table 1 100 PORT7, VCTRUNK1, VCTRUNK2 Hub Hub Spoke Spoke VLAN filter table 2 200 PORT8, VCTRUNK1, VCTRUNK2
Hub/Spoke
PORT7 PORT8 VCTRUNK1 VCTRUNK2

At the convergence node NE1, you need to create an EPLAN service (IEEE 802.1q bridge) and a VLAN filtering table. The access nodes NE2 and NE4 need to be configured with EVPL services only.
Prerequisite


Step 1 Configure the EVPLAN services for user G1, user G2, user G3, user H1, user H2, and user H3 on NE1. 1. Configure the attributes of the external ports used by the services of user G1 and user H1. l In the NE Explorer, select the LEM24 board and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. l Select External Port. l Click the Basic Attributes tab. After setting the parameters, click Apply. Click Close in the Operation Result dialog box that is displayed.
Issue 02 (2011-10-31)
340
Parame ter Enabled / Disable d Workin g Mode
Value in This Example PORT7: Enabled PORT8: Enabled
Description In this example, PORT7 and PORT8 carry the services and Enabled/Disabled is set to Enabled for PORT7 and PORT8. In this example, the Ethernet service access equipment of user G1 and user H1 supports the auto-negotiation mode. Hence, Working Mode is set to Auto-Negotiation for PORT7 and PORT8. Generally, this parameter adopts the default value 1522.
PORT7: AutoNegotiation PORT8: AutoNegotiation
Maximu m Frame Length MAC Loopba ck PHY Loopba ck
PORT7: 1522 PORT8: 1522
PORT7: Non-Loopback PORT8: Non-Loopback PORT7: Non-Loopback PORT8: Non-Loopback
The MAC loopback setting is used for fault diagnosis. In this example, MAC Loopback is set to Non-Loopback. The PHY loopback setting is used for fault diagnosis. In this example, PHY Loopback is set to Non-Loopback.
l Click the Flow Control tab. The parameters in the Flow Control tab page adopt the default values. For details on parameter settings, see 10.20.7 Parameters: Network Attributes l Click the TAG Attributes tab. After setting the parameters, click Apply. Then, click Close in the Operation Result dialog box that is displayed. Parame ter TAG Value in This Example PORT7: Access PORT8: Access Description The access equipment of user G1 and user H1 does not support VLAN tags. Hence, the Ethernet access equipment transmits only the packets without the VLAN tags. In this example, TAG is set to Access for PORT7 and PORT8. According to the plan, the VLAN ID is set to 100 on the transmission network side for the Ethernet services between user G1, user G2, and user G3. The VLAN ID is set to 200 on the transmission network side for the EVPLAN services between user H1, user H2, and user H3. In this manner, the services of different users are isolated. This parameter adopts the default value.
Default VLAN ID
PORT7: 100 PORT8: 200
VLAN Priority
Issue 02 (2011-10-31)
341
Parame ter Entry Detectio n
Description The services of user G1 and user H1 are EVPLAN services. Hence, the entry detection function must be enabled to check whether the packets carry VLAN tags. In this example, Entry Detection is set to Enabled.
l Click the Network Attributes tab. After setting the parameters, click Apply. Then, click Close in the Operation Result dialog box that is displayed. Parame ter Port Type Value in This Example PORT7: UNI PORT8: UNI Description UNI indicates the user-network interface, namely, the interface of the service provider located near the user side. The UNI interface processes the tag attribute of IEEE 802.1qcompliant packets. That is, the UNI interface processes and identifies the VLAN information of the accessed user packets, according to the supported tag flags, namely Tag Aware, Access, and Hybrid.
l Click the Advanced Attributes tab. The parameters in the Advanced Attributes tab page adopt the default values. For details on parameter settings, see 10.20.4 Parameters: Advanced Attributes (External Port). 2. Set the attributes of the internal ports used by the services of user G2, user G3, user H2, and user H3 on NE1. l Select Internal Port. l Click the TAG Attributes tab. After setting the parameters, click Apply. Then, click Close in the Operation Result dialog box that is displayed. For details on parameter settings, see Description of the TAG Attributes Parameter. Parame ter TAG Value in This Example VCTRUNK1: Access VCTRUNK2: Access Description The service access equipment of user G2, user G3, user H2, and user H3 supports VLAN tags and the transmitted data frames do not carry VLAN tags. In this example, TAG is set to Access for VCTRUNK1VCTRUNK4.
Issue 02 (2011-10-31)
342
Value in This Example VCTRUNK1: Enabled VCTRUNK2: Enabled
Description The services of user G2, user G3, user H2, and user H3 are EVPLAN services. Hence, the entry detection function must be enabled to check whether the packets carry VLAN tags. In this example, Entry Detection is set to Enabled.
l Click the Network Attributes tab. After setting the parameters, click Apply. Then, click Close in the Operation Result dialog box that is displayed. For details on parameter settings, see Description of the Network Attributes Parameter. Parame ter Port Type Value in This Example VCTRUNK1: UNI VCTRUNK2: UNI Description UNI indicates the user-network interface, namely, the interface of the service provider located near the user side. The UNI interface processes the tag attribute of IEEE 802.1qcompliant packets. That is, the UNI interface processes and identifies the VLAN information of the accessed user packets, according to the supported tag flags, namely Tag Aware, Access, and Hybrid.
l Click the Advanced Attributes tab. The parameters in the Advanced Attributes tab page adopt the default values. For details on parameter settings, see Description of the Advanced Attributes Parameter (External Port). 3. Create a bridge for the LEM24 board on NE1. l In the NE Explorer, select the LEM24 board and then choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. l Click New. l Set the parameters in the Create Ethernet LAN Service dialog box that is displayed. Parameter Value in This Example VB1 Description
VB Name
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. 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.
343
VB Type
802.1q
Issue 02 (2011-10-31)
Parameter
Value in This Example IVL/Ingress Filter Enable
Description
Bridge Switch Mode
When Bridge Learning Mode is set to IVL, 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. -
IVL
Enabled Enabled
l Click Configure Mount. l In Available Mounted Ports, select PORT7, PORT8, VCTRUNK1 and VCTRUNK2. Then, click . l Click OK. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. l In the Create Ethernet LAN Service dialog box that is displayed, click OK. 4. Create a VLAN filtering table. l Select the created bridge and click the VLAN Filtering tab. l Click New. l Create the VLAN filtering table for user G1, user G2, and user G3 in the Create VLAN dialog box that is displayed. Parameter Value in This Example 100 Description
VLAN ID
According to the plan, the VLAN ID is set to 100 on the transmission network side for the EVPLAN services between user G1, user G2, and user G3.
l In Available Forwarding Ports, select PORT7, VCTRUNK1 and VCTRUNK2. Click . Then, click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. l Create the VLAN filtering table for user H1, user H2, and user H3.
Issue 02 (2011-10-31)
344
Parameter
Value in This Example 200
Description
VLAN ID
According to the plan, the VLAN ID is set to 200 on the transmission network side for the EVPLAN services between user H1, user H2, and user H3.
l In Available Forwarding Ports, select PORT8, VCTRUNK1 and VCTRUNK2. Click . Then, click OK. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. 5. Change the Hub/Spoke attribute of the port that is mounted to the bridge.
NOTE
If normal communication is required between user G2 and user G3, go to Step 2.
l Select the created bridge and click the Service Mount tab. l Change the Hub/Spoke attribute of the port that is mounted to the bridge. After setting the parameters, click Apply. The Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. Parameter Hub/Spoke Value in This Example PORT7: Hub VCTRUNK1: Spoke VCTRUNK2: Spoke PORT8: Hub Description If user G2 need not communicate with user G3, set VCTRUNK1 and VCTRUNK2 that access the services of user G2 and user G3 to Spoke. Ports of the Spoke attribute cannot communicate with each other. A port of the Hub attribute can communicate with a port of the Spoke or Hub attribute.
Step 2 Configure EVPL services on NE2 and NE4.

NOTE
The Ethernet services on NE2 and NE4 are EVPL services. Complete the configuration based on the planned parameters by referring to the operations described in 10.7 Configuration Example: Configuring EVPL (QinQ) Services on a WDM Network
NOTE
Step 4 Enable the performance monitoring function for the NEs. For the operation procedures, see Setting Performance Monitoring Parameters of an NE in the Commissioning Guide. Step 5 Back up the configuration data on the NEs. Two methods are available for the backup.
Issue 02 (2011-10-31)
345
----End
10.10 Configuration Example: Configuring EVPLAN Services (IEEE 802.1 ad Bridge) on a WDM Network
The QinQ technology provides a cheap and easy solution for Layer 2 virtual private networks (VPNs). The IEEE 802.1ad bridge uses the QinQ technology to provide the VPN solution, thus facilitating the identifying, differentiating and grooming EVPLAN services.

A network operator requires that the GE and FE services sent to the transmission network be uniformly labeled and groomed at the convergence node.
Service Requirement
On the network as shown in Figure 10-26, the service requirements are as follows: l l l l The GE services of user M and user N are sent to the transmission network at NE2 and NE4 respectively and to the GE server at the convergence node NE1. The FE services of user M and user N are sent to the transmission network at NE2 and NE4 respectively and to the FE server at the convergence node NE1. The GE services need to be isolated from the FE services. User M does not need to communicate with user N. The data communication equipment of user M and user N provides Ethernet electrical ports that work in auto-negotiation mode and support VLANs. C-VLAN ID of the GE services: 10 C-VLAN ID of the FE services: 20
NOTE
The application senarios whether user M needs to communicate with user N are as follows: l User M needs to communicate with user N. l User M does not need to communicate with user N.
Requirement of the operator requires that all services received from the user side should be uniformly labeled and groomed through planned S-VLANs. l l
Issue 02 (2011-10-31)
S-VLAN ID of the GE services: 100 S-VLAN ID of the FE services: 200

Figure 10-26 Networking diagram for configuring EVPLAN services (IEEE 802.1ad bridge)
IU 3 NM
Service GE FE C-VLAN 10 20
LEM24
Service GE C-VLAN 10 20
NE3 NE2 NE4 NE1
FE
IU 3
LEM24
IU 3
LEM24
User M
User N
GE VB1 VLAN 100 VCTRUNK1 PORT7 NG WDM equipment VCTRUNCK VCTRUNK2 IU 3 LEM24
FE VB2 VLAN 200 VCTRUNK1 PORT8 VCTRUNK2

In this example, the convergence node NE1 is configured with one LEM24 board that supports the IEEE 802.1ad bridge, thus implementing the EVPLAN services in which GE data is isolated from FE data. l The GE services tagged with C-VLAN ID 10 from NE2 and NE4 respectively are further tagged with S-VLAN ID 100 when they arrive at the IEEE 802.1ad bridge of NE1 the services are forwarded to the NE1 through Layer 2 switching. The FE services tagged with C-VLAN ID 20 from NE2 and NE4 respectively are further tagged with S-VLAN ID 200 when they arrive at the IEEE 802.1ad bridge of NE1 the services are forwarded to the NE1 through Layer 2 switching.
The access nodes NE2 and NE4 are configured with one LEM24 board each. The EPL services are configured to be transparently transmitted from NE2 and NE4 to NE1.
10.10.2 Service Signals Flow and Wavelength Allocation

The services of user M and user N are transmitted from the access nodes NE2 and NE4 respectively to the convergence node NE1 through the Ethernet transparent transmission boards. GE and FE services carrying different C-VLANs are tagged with different S-VLANs. Service data is isolated and exchanged at Layer 2 through S-VLAN filtering. Figure 10-27 shows the signal flow of the EVPLAN services (IEEE 802.1ad bridge) and the timeslot allocation to the EVPLAN services (IEEE 802.1 ad bridge).
Figure 10-27 Service signal flow of the EPLAN service

LEM24
ONE 4
AP1 PORT7 PORT8
ONE 1
PORT7
SVLAN 100 SVLAN 200 VB1
LEM24
1(IN1/OUT1)-1
(VCTRUNCK1)
1(IN1/OUT1)-1
(VCTRUNCK1)
User M
PORT8
2(IN2/OUT2)-1
(VCTRUNCK2)
LEM24
(VCTRUNCK1)
ONE 2
AP2 PORT7 PORT8
1(IN1/OUT1)-1
User N
:Client-side signals :WDM-side working service
:Working service of GE :Working service of FE
Table 10-16 Parameters of external ports on the Ethernet boards Parameter Board Port Port Enabled Working Mode Maximum Frame Length Port Type NE1 3-LEM24 PORT7 Enabled AutoNegotiation 1522 C-Aware PORT8 Enabled AutoNegotiation 1522 C-Aware NE2 3-LEM24 PORT7 Enabled AutoNegotiation 1522 NE4 3-LEM24 PORT7 Enabled AutoNegotiation 1522 -
Table 10-17 Parameters of internal ports on the Ethernet boards Parameter Board Port Port Type NE1 3-LEM24 VCTRUNK1 C-Aware VCTRUNK2 C-Aware NE2 3-LEM24 VCTRUNK1 NE4 3-LEM24 VCTRUNK1 -
Table 10-18 Parameters of the EPLAN services (IEEE 802.1ad bridge) Parameter VB Name VB Type
Issue 02 (2011-10-31)
EPLAN Service of NE1 VB1 802.1ad

Parameter Bridge Switch Mode Bridge Learning Mode Ingress Filter Operation Type VB Port Mount Port C-VLAN S-VLAN VLAN Filterin g VLAN Filtering VLAN ID Forwarding Physical Port Hub/ Spoke PORT7 PORT8 VCTRUNK1 VCTRUNK2
EPLAN Service of NE1 IVL/Ingress Filter Enable IVL Enabled Add S-VLAN base for Port and C-VLAN 1 PORT7 10 100 2 PORT8 20 200 3 VCTRUNK1 10 100 20 200 4 VCTRUNK2 10 100 20 200
VLAN filter table 1 100 PORT7, VCTRUNK1, VCTRUNK2 Hub Hub Spoke Spoke
VLAN filter table 2 200 PORT8, VCTRUNK1, VCTRUNK2

An EVPLAN service (IEEE 802.1ad bridge) and the corresponding S-VLAN filtering table need to be created for the convergence node NE1. The access nodes NE2 and NE4 need to be configured with EPL transparent transmission services only.
Prerequisite

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 l l l Adding the S-VLAN tag based on the port Adding the S-VLAN tag based on the port and C-VLAN Performing port mounting based on the port Performing port mounting based on the port and the S-VLAN
This topic describes the four operation types when Bridge Switch Mode of the IEEE 802.1ad bridge is set to IVL/Ingree Filter Enabled. 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. 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 relationship 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 CAware 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.
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. 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 l The port is contained in the S-VLAN filtering table that is created by the user. 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 is mounted based on the port, the S-VLAN ID is considered to contain all the legal SVLAN IDs.

Step 1 Configure EVPLAN services on NE1. 1.
Issue 02 (2011-10-31)
Configure the attributes of the external ports.

l In the NE Explorer, select the LEM24 board in slot 3 and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Then, select External Port. l Click the Basic Attributes tab. After setting the parameter on this tab page, click Apply. For details on parameter settings, see Description of the Basic Attributes Parameter (External Port). Parameter Port Enabled Value PORT7: Enabled PORT8: Enabled Working Mode PORT7: AutoNegotiation PORT8: AutoNegotiation Maximum Frame Length MAC Loopback PORT7: 1522 PORT8: 1522 PORT7: NonLoopback PORT8: NonLoopback PHY Loopback PORT7: NonLoopback PORT8: NonLoopback Description Set PORT7 and PORT8 that carry the service to Enabled. The GE server and FE server support the auto-negotiation function. This parameter is set to Auto-Negotiation for PORT7 and PORT8. In general, the default value 1522 is used. The loopback setting is used for fault diagnosis. When configuring a service, set this parameter to Non-Loopback
The loopback setting is used for fault diagnosis. When configuring a service, set this parameter to Non-Loopback.
l Click the Flow Control tab. The default value of the parameter is recommended. For the default value of the parameter, see Description of the Flow Control Parameter (External Port). l Click the Network Attributes tab. After setting the parameter on this tab page, click Apply. For details on parameter settings, see Description of the Network Attributes Parameter.
Issue 02 (2011-10-31)
351
Parameter Port Type
Value PORT7: C-Aware PORT8: C-Aware
Description The C-Aware or S-Aware attribute must be selected for the port when you configure the IEEE 802.1ad bridge. The C-Aware port connects to the port in the client network, identifies and processes the packets that contain CVLAN tags (namely, client tags). The S-Aware port connects to the port on the network side, identifies and processes the packets that contain SVLAN tags (namely, service tags of the network operator). It is unnecessary to set the parameters on the TAG Attributes tab. If the port type
l It is unnecessary to set the parameters on the TAG Attributes tab. If the port type is set to C-Aware or S-Aware, the parameters on the TAG Attributes are meaningless. 2. Set the attributes of the internal ports used by the service between user M and user N. l In the NE Explorer, select the LEM24 board in slot 3 and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Then, select Internal Port. l Click the Network Attributes tab. After setting the parameter on this tab page, click Apply. For details on parameter settings, see Description of the Network Attributes Parameter. Parameter Port Type Value VCTRUNK1: SAware VCTRUNK2: SAware Description When you configure the IEEE 802.1ad bridge, set the port to C-Aware or SAware. The C-Aware port is connected to the UNI port, identifies, and processes the packets with the CVLAN tags. The S-Aware port is connected to the network-side port, identifies, and processes the packets with the S-VLAN tags.
l It is unnecessary to set the parameters on the TAG Attributes tab. If the port type is set to C-Aware or S-Aware, the parameters on the TAG Attributes are meaningless. 3. Create a bridge for the LEM24 board on NE1. l In the NE Explorer, select the LEM24 board in slot 3 and then choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Click the Service Mount tab. l Click New on the lower right of the window. The Create Ethernet LAN Service dialog box is displayed. l Enter the attributes of the Ethernet LAN service in the dialog box. For details on parameter settings, see Description of the EPLAN Service Parameter.
Parameter VB Name
Value VB1
Description 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. 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. An IEEE 802.1ad bridge checks the content of VLAN tags of the received packets. The bridge performs Layer 2 switching based on the destination MAC addresses and the S-VLAN IDs of the packets. -
VB Type
802.1ad
Bridge Switch Mode
IVL/Ingress Filter Enable
Bridge Learning Mode Ingress Filter
IVL Enabled
l Click Configure Mount, the Service Mount Configuration dialog box is displayed. l Select the mount ports in the dialog box. Attr ibu te Ope ratio n Typ e VB Port Mo unt Port CVL AN Attribute Value
Adding S-VLAN tags based on Port and C-VLAN
1 POR T7 10
2 PORT8
3 VCTRUNK1
4 VCTRUNK2
20
10
20
10
20
Issue 02 (2011-10-31)
353
Attr ibu te SVL AN
Attribute Value
100
200
100
200
100
200
l Click OK, and the service mount is displayed on the interface. l Click OK, and the created EPLAN service is displayed on the interface. 4. Create a VLAN filtering table. l Select the created bridge and click the VLAN Filtering Table tab. l Click New. l Create the VLAN filtering table of the GE service. Parameter VLAN ID Value 100 Description According to the plan, the S-VLAN ID is 100 for the GE service.
l In Available Forwarding Ports, select PORT7, VCTRUNK1, and VCTRUNK2. Click . Then click Apply. l Create the VLAN filtering table of the FE service. Parameter VLAN ID Value 200 Description According to the plan, the S-VLAN ID is 200 for the FE service.
l In Available Forwarding Ports, select PORT8, VCTRUNK1, and VCTRUNK2. Click . Then click Apply. 5. Change the Hub/Spoke attribute of the ports mounted to the bridge.
NOTE
If normal communication is required between user M and user N, go to Step 2.
l Select the created bridge and click the Service Mount tab. l Change the Hub/Spoke attribute of the port mounted to the bridge.
Issue 02 (2011-10-31)
354
Parameter Hub/Spoke
Value PORT7: Hub PORT8: Hub VCTRUNK1: Spoke VCTRUNK2: Spoke
Description Users M and N do not need to communicate with each other. In this case, set VCTRUNK1 and VCTRUNK2 that access the services of users M and N to the Spoke attribute. Ports of the Spoke attribute cannot communicate with each other. A port of the Hub attribute can communicate with a port of the Spoke or Hub attribute.
Step 2 Configure EPL services on NE2 and NE4.

NOTE
The Ethernet services on NE2 and NE4 are EPL services transparently transmitted from point to point. Complete the configuration based on the planned parameters by referring to the operations described in 10.6 Configuration Example: Configuring EPL Services
NOTE
Step 4 Enable the performance monitoring function for the NEs. For the operation procedures, see Setting Performance Monitoring Parameters of an NE in the Commissioning Guide. Step 5 Back up the configuration data on the NEs. Two methods are available for the backup. Option The SCC board is not configured with any CF card The SCC board is configured with a CF card Description See Backing Up the NE Database to the SCC Board in the Commissioning Guide See Manually Backing Up the NE Database to a CF Card in the Commissioning Guide
----End
10.11 Configuration Example: Configuring EVPL and EVPLAN Services (IEEE 802.1q Bridge) on a WDM Network
Based on different VLANs, EVPL and EVPLAN services can be accessed through a same port, which is applicable to the scenario where the EVPL and EVPLAN users share the same port.

Based on different VLANs, EVPL and EVPLAN services can be accessed through a same port.
Service Requirement
On the network as shown in Figure 10-28, the service requirements are as follows: l l l l l l l The same Ethernet port receives services from A1 and B1. Two branches of user A are located at NE1 and NE2. Three branches (B1, B2, and B3) of user B are located at NE1, NE2, and NE3 respectively. B2 and B3 do not need to communicate with each other. The service of user A needs to be isolated from the service of user B. The Ethernet equipment of user A and user B provides Ethernet optical ports that work mode in auto-negotiation mode. VLAN ID of the A1 and A2 services: 100 VLAN ID of the B1, B2 and B3 services: 200
Figure 10-28 Networking diagram for configuring EVPL and EPLAN services (IEEE 802.1q bridge)
B2 PORT7 A2 IU3 LEM24 PORT8
IU3
LEM24
NE2
NE3
PORT7 B3
NE1
IU3 LEM24
NG WDM equipment VCTRUNCK
A1
B1 VB1 VLAN 200 VCTRUNK1 VCTRUNK2 PORT7

In this example, the convergence node NE1 is configured with one LEM24 board that supports the IEEE 802.1q bridge. The access nodes NE2 and NE4 are configured with one LEM24 board each. The EPL and EVPL services are configured to be transmitted from NE2 and NE4 to NE1.
10.11.2 Service Signals Flow

The Ethernet services of the convergence node are received from an external port and tagged with the corresponding VLAN IDs. After the services are forwarded to an internal port through
Layer 2 switching, the VLAN IDs are stripped and then the services are transparently transmitted in the SDH network. In this way, the node communicates with a remote node. Figure 10-29 shows the signal flow of the EVPL and EVPLAN services (IEEE 802.1q bridge). Figure 10-29 Service signal flow of the EVPL and EVPLAN services (IEEE 802.1q bridge)
ONE 1
VLAN 100 EVPL
LEM24 LEM24
1(IN1/OUT1)-1
(VCTRUNCK 1) (VCTRUNCK 1)
ONE 2
User A2 PORT7 PORT8 User B2
1(IN1/OUT1)-1
User A1 PORT7 User B1

VLAN 200
2(IN2/OUT2)-1
(VCTRUNCK 2)
LEM24
(VCTRUNCK 1)
ONE 3
EPL
1(IN1/OUT1)-1
User B3 PORT7
:Client-side working service :WDM-side working service
:Working service direction
Table 10-19 Parameters of external ports on the Ethernet boards Parameter Board Port Port Enabled Working Mode Maximum Frame Length TAG Entry Detection Default VLAN ID Port Type NE1 LEM24 PORT7 Enabled AutoNegotiation 1522 Tag Aware Enabled 0 UNI NE2 LEM24 PORT7 Enabled AutoNegotiation 1522 Disabled UNI PORT8 Enabled AutoNegotiation 1522 Disabled UNI NE3 LEM24 PORT8 Enabled AutoNegotiation 1522 Disabled UNI
Table 10-20 Parameters of internal ports on the Ethernet boards Parameter Board Port TAG
Issue 02 (2011-10-31)
NE1 LEM24 VCTRUNK1 Access VCTRUNK2 Access
NE2 LEM24 VCTRUNK1 -
NE3 LEM24 VCTRUNK1 357
Parameter Entry Detection Default VLAN ID Port Type
NE1 Enabled 100 UNI Enabled 200 UNI
NE2 Disabled UNI
NE3 Disabled UNI
Table 10-21 Parameters of the EVPL services Parameter Board Service Type Service Direction Source Port Source C-VLAN(e.g.1, 3-6) Sink Port Sink C-VLAN(e.g.1, 3-6) EVPL Service of NE1 EGSH EVPL Bidirectional PORT7 100 VCTRUNK1 100
Table 10-22 Parameters of the EVPLAN (IEEE 802.1q bridge) services Parameter VB Name VB Type Bridge Switch Mode Bridge Learning Mode Ingress Filter VB Mount Port VLAN Filtering VLAN Filtering VLAN ID Forwarding Physical Port Hub/Spoke PORT7 VCTRUNK1 EPLAN Service of NE1 VB1 802.1q IVL/Ingress Filter Enable IVL Enabled PORT7, VCTRUNK1, VCTRUNK2 VLAN filtering table 1 200 PORT7, VCTRUNK1, VCTRUNK2 HUB Spoke
Issue 02 (2011-10-31)
358
Parameter VCTRUNK2
EPLAN Service of NE1 Spoke

This section describes how to configure an EPLAN service through an example in which station B transmits the EPLAN service to station D. The case that station D transmits the EPLAN service to station B is similar, and thus is not described in this section.
Prerequisite
You must read and understand the contents of Configuration Process of the EVPL Service and Configuration Process of the EVPLAN Service.


Step 1 Configure the EVPL services form user A1 to user A2 on NE1. For the operation procedures, see 10.7 Configuration Example: Configuring EVPL (QinQ) Services on a WDM Network. Step 2 Configure the EVPLAN services of user B1 and user B3. For the operation procedures, see 10.9 Configuration Example: Configuring EVPLAN Services (IEEE 802.1q Bridge) on a WDM Network. Step 3 Configure the EVPL services on NE2. For the operation procedures, see 10.7 Configuration Example: Configuring EVPL (QinQ) Services on a WDM Network. Step 4 Configure the EPL services on NE3. For the operation procedures, see 10.6 Configuration Example: Configuring EPL Services. Step 5 Verify the service configurations. For the verification procedure, see Testing Ethernet Service Channels in the Commissioning Guide. Step 6 Enable the performance monitoring function for the NEs. For the operation procedures, see Setting Performance Monitoring Parameters of an NE in the Commissioning Guide. Step 7 Back up the configuration data on the NEs. Two methods are available for the backup. Option The SCC board is not configured with any CF card The SCC board is configured with a CF card Description See Backing Up the NE Database to the SCC Board in the Commissioning Guide See Manually Backing Up the NE Database to a CF Card in the Commissioning Guide
----End
10.12 Configuration Example: Configuring EPL Services on a SDH Network

EPL services provide the point-to-point Ethernet transparent transmission solution where the bandwidth is occupied exclusively. EPL services are applicable when the communication equipment that is used to access the client-side data in the transmission network does not support VLAN or when the VLAN planning cannot be disclosed to the network operator.

The completely isolated data services of two users at a station must be transported to another station.
Service Requirement
On the network shown in Figure 10-30, the service requirements are as follows: l l l l The two branches of user A that are located at NE1 and NE3 need to communicate with each other over Ethernet. A 100 Mbit/s bandwidth is required. The two branches of user B that are located at NE1 and NE3 need to communicate with each other over Ethernet. A 200 Mbit/s bandwidth is required. The services of user A must be isolated from the services of user B. The Ethernet equipment of user A and user B provides 1000 Mbit/s Ethernet electrical interfaces that work in 1000M full-duplex mode and do not support VLAN tags.
Issue 02 (2011-10-31)
360
Figure 10-30 Networking diagram of the EPL services

User A2 User B2
PORT1
PORT2
Line Board Ethernet Board

1 17 NE3
1-SLQ64 4-EGSH
Line Board Line Board
1-SLQ64 17-SLQ64
1
NE2
NE4
17
NE1

PORT1 PORT2
17-SLQ64 4-EGSH
User A1
User B1
VCTRUNK
OptiX OSN 8800

Ethernet services are received from an external port, encapsulated through an internal port, and mapped into the SDH network for transparent transmission. In this manner, the node communicates with a remote node. The signal flow of the EPL services and the timeslot allocation to the EPL services are shown in Figure 10-31. Figure 10-31 Signal flow and timeslot allocation (Ethernet switching board)
NE1 EGSH
PORT1 User A1 PORT2 User B1 VCTRUNK1 VC4--xv:VC4-1 VCTRUNK2 VC4--xv:VC4-2 VC4--xv:VC4-3 VC4:VC4-2 VC4:VC4-3 VC4:VC4-1
NE2
NE3 EGSH
VCTRUNK1 VC4--xv:VC4-1 VCTRUNK2 VC4--xv:VC4-2 VC4--xv:VC4-3
PORT1 User A2 PORT2 User B2
SDH
Issue 02 (2011-10-31)
361
The EPL services of user A: Occupy the first VC-4 (VC4:VC4-1) on the SDH link between NE1 and NE3 and pass through NE2. Are added and dropped by using the first VC-4 (VC4-xv:VC4-1) on the EGSH board of NE1 and the first VC-4 (VC4-xv:VC4-1) on the EGSH board of NE3.
The EPL services of user B: Occupy the second and third VC-4s (VC4:VC4-2 and VC4:VC4-3) on the SDH link between NE1 and NE3 and pass through NE2. Are added and dropped by using the second and third VC-4s (VC4-xv:VC4-2 and VC4xv:VC4-3) on the EGSH board of NE1 and the second and third VC-4s (VC4-xv:VC4-2 and VC4-xv:VC4-3) on the EGSH board of NE3.
Table 10-23 Parameters of the external ports of the Ethernet boards Parameter Board Port Enabled/ Disabled Working Mode Maximum Frame Length Entry Detection Port Type NE1 EGSH PORT1 Enabled 1000M Full Duplex 1522 Disabled UNI PORT2 Enabled 1000M Full Duplex 1522 Disabled UNI NE3 EGSH PORT1 Enabled 1000M Full Duplex 1522 Disabled UNI PORT2 Enabled 1000M Full Duplex 1522 Disabled UNI
Table 10-24 Parameters of the internal ports of the Ethernet boards Parameter Board Internal Port Mapping Protocol Bound Path NE1 EGSH VCTRUNK1 GFP VC4xv:VC4-1 Disabled UNI VCTRUNK2 GFP VC4-xv:VC4-2 and VC4xv:VC4-3 Disabled UNI NE3 EGSH VCTRUNK1 GFP VC4xv:VC4-1 Disabled UNI VCTRUNK2 GFP VC4-xv:VC4-2, VC4-xv:VC4-3 Disabled UNI
Entry Detection Port Type
Issue 02 (2011-10-31)
362
Table 10-25 Parameters of the EPL services Parameter Board Service Type Service Direction Source Port Source C-VLAN(e.g.1, 3-6) Sink Port Sink C-VLAN(e.g.1, 3-6) EPL Services of User A EGSH EPL Bidirectional PORT1 Null VCTRUNK1 Null PORT2 Null VCTRUNK2 Null EPL Services of User B

During the configuration of EPL services on Ethernet switching boards, you need to configure Ethernet private line services. This topic describes the process of configuring Ethernet private line services for Ethernet switching boards.
Prerequisite
The Creating a Network task must be complete. You must be familiar with 10.3.1 EPL Service Configuration Process.


Step 1 Configure the EPL services for user A1 and user B1 on NE1. 1. Configure the attributes of the external ports (PORT1 and PORT2 of the EGSH board) used by the services of user A1 and user B1. l In the NE Explorer, select the EGSH and then choose Communication > Ethernet Interface Management > Ethernet Interface from the Function Tree. l Select External Port. l Click the Basic Attributes tab. After setting the parameters, click Apply. Then, the Operation Result dialog box is displayed. Click Close. Parame ter Enabled / Disable d
Issue 02 (2011-10-31)
Description PORT1 is used by the service of user A1. PORT2 is used by the service of user B1. In this example, Enabled/Disabled is set to Enabled for PORT1 and PORT2.
363
Parame ter Workin g Mode
Value in This Example PORT1: 1000M FullDuplex PORT2: 1000M FullDuplex
Description In this example, the Ethernet service access equipment of user A1 and user B1 supports the 1000M full-duplex mode. Hence, Working Mode is set to 1000M FullDuplex for PORT1 and PORT2. Generally, this parameter adopts the default value 1522.
PORT1: 1522 PORT2: 1522
l Click the Flow Control tab. The parameters in the Flow Control tab page adopt the default values. l Click the TAG Attributes tab. After setting the parameters, click Apply. Then, the Operation Result dialog box is displayed. Click Close. Parame ter Entry Detectio n Value in This Example PORT1: Disabled PORT2: Disabled Description The services of user A1 and user B1 are EPL transparent transmission services. Hence, you need not enable the entry detection function to check the VLAN tags of the packets. In this example, Entry Detection needs to be set to Disabled. When Entry Detection is set to Disabled, the parameters of TAG, Default VLAN ID, and VLAN Priority are invalid.
l Click the Network Attributes tab. After setting the parameters, click Apply. Then, the Operation Result dialog box is displayed. Click Close. Parame ter Port Type Value in This Example PORT1: UNI PORT2: UNI Description The UNI interface processes the tag attribute of IEEE 802.1q-compliant packets. That is, the UNI interface processes and identifies the VLAN information of the accessed user packets, according to the supported tag flag, namely, Tag Aware, Access, and Hybrid.
Issue 02 (2011-10-31)
364
l Click the Advanced Attributes tab. The parameters in the Advanced Attributes tab page adopt the default values. 2. Configure the attributes of the internal ports (VCTRUNK1 and VCTRUNK2 of the EGSH board) used by the services of user A1 and user B1. l Select Internal Port. l Click the TAG Attributes tab. After setting the parameters, click Apply. Then, the Operation Result dialog box is displayed. Click Close. Parame ter Entry Detectio n Value in This Example VCTRUNK1: Disabled VCTRUNK2: Disabled Description The services of user A1 and user B1 are EPL transparent transmission services. Hence, you need not enable the entry detection function to check the VLAN tags of the packets. In this example, Entry Detection needs to be set to Disabled. When Entry Detection is set to Disabled, the parameters of TAG, Default VLAN ID, and VLAN Priority are invalid. Hence, it is recommended that this parameter adopts the default value.
l Click the Network Attributes tab. After setting the parameters, click Apply. Then, the Operation Result dialog box is displayed. Click Close. Parame ter Port Type Value in This Example PORT1: UNI PORT2: UNI Description The UNI interface processes the tag attribute of IEEE 802.1q-compliant packets. That is, the UNI interface processes and identifies the VLAN information of the accessed user packets, according to the supported tag flag, namely, Tag Aware, Access, and Hybrid.
l Click the Encapsulation/Mapping tab. After setting the parameters, click Apply. Then, the Operation Result dialog box is displayed. Click Close. Parame ter Mappin g Protocol Value in This Example VCTRUNK1: GFP VCTRUNK2: GFP Description In this example, the EGSH board is used. This parameter adopts the default value GFP. Mapping Protocol of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value.
Issue 02 (2011-10-31)
365
Parame ter Scrambl e
Value in This Example VCTRUNK1: Scrambling mode[X43 +1] VCTRUNK2: Scrambling mode[X43 +1]
Description In this example, this parameter adopts the default value Scrambling mode[X43+1]. Scramble of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value. In this example, this parameter adopts the default value FCS32. Check Field Length of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value. When Mapping Protocol is set to GFP, FCS Calculated Bit Sequence is set to Big endian. FCS Calculated Bit Sequence of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value. When Mapping Protocol is set to GFP, this parameter is valid and adopts the default value No. Extension Header Option of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value.
Check Field Length
VCTRUNK1: FCS32 VCTRUNK2: FCS32
FCS Calculat ed Bit Sequenc e Extensi on Header Option
VCTRUNK1: Big endian VCTRUNK2: Big endian
VCTRUNK1: No VCTRUNK2: No
l This operation is optional. Click the LCAS tab. After setting the parameters, click Apply. Then, the Operation Result dialog box is displayed. Click Close. Parame ter Enablin g LCAS LCAS Mode Value in This Example VCTRUNK1: Enabled VCTRUNK2: Enabled VCTRUNK1: Huawei Mode VCTRUNK2: Huawei Mode HO Time (ms) WTR Time (s) VCTRUNK1: 2000 VCTRUNK2: 2000 Description In this example, the LCAS function is enabled. In this example, this parameter adopts the default value Huawei Mode. When Huawei equipment is used at both ends, LCAS Mode of the equipment at both ends is set to Huawei Mode. In this example, this parameter adopts the default value 2000. This parameter can also be set according to the requirement of the user. In this example, this parameter adopts the default value 300. This parameter can also be set according to the requirement of the user.
VCTRUNK1: 300 VCTRUNK2: 300
Issue 02 (2011-10-31)
366
Parame ter TSD
Value in This Example VCTRUNK1: Disabled VCTRUNK2: Disabled
Description In this example, the TSD function is disabled. The LCAS does not check the B3 bit error or BIP status of the VCTRUNK members.
l Click the Bound Path tab. Click the Configuration button. Set the following parameters in the Bound Path Configuration dialog box that is displayed. Click and click Apply. Click Yes in the Hint dialog box that is displayed. Click Close in the Operation dialog box that is displayed. User Parameter Value in This Example VCTRUN K VC4-xv Description
User A1 user A2
Configurabl e Ports Avail able Boun d Paths Lev el Ser vice Dir ecti on Ava ilab le Res our ces
VCTRUNK1 is used by the service between user A1 and user A2. The service between user A1 and user A2 uses a 100 Mbit/s bandwidth. Hence, one VC-4 needs to be bound. The service between user A1 and user A2 is a bidirectional service.
Bidirectio nal
VC4-1
User B1 user B2
Configurabl e Ports Avail able Boun d Paths Lev el Ser vice Dir ecti on
VCTRUN K VC4-xv
VCTRUNK2 is used by the service between user B1 and user B2. The service between user B1 and user B2 uses a 200 Mbit/s bandwidth. Hence, two VC-4s need to be bound. The service between user B1 and user B2 is a bidirectional service.
Bidirectio nal
Issue 02 (2011-10-31)
367
User
Parameter
Value in This Example VC4-2, VC4-3
Description
Ava ilab le Res our ces
The service between user B1 and user B2 uses a 200 Mbit/s bandwidth. Hence, two VC-4s needs to be bound.
l Click the Advanced Attributes tab. The parameters in the Advanced Attributes tab page adopt the default values. 3. Configure the Ethernet private line services for user A1 and user B1. l In the NE Explorer, select the EGSH and then choose Communication > Ethernet Service > Ethernet Line Service from the Function Tree. Click . l Click New on the lower-right pane to display the Create Ethernet Line Service dialog box. Set the following parameters, and then click OK. The Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. User Parameter Value in This Example EPL Bidirection al PORT1 Description
User A1
Service Type Service Direction Source Port
The service of user A1 is an EPL service. The service of user A1 is a bidirectional service. When creating the bidirectional Ethernet service from a PORT to a VCTRUNK, it is recommended that you use a specific PORT as the source port. In this example, the service of user A1 occupies PORT1. In this example, the EPL service does not carry the VLAN tag. When creating the bidirectional Ethernet service from a PORT to a VCTRUNK, it is recommended that you use a specific VCTRUNK as the sink port. In this example, the service of user A1 occupies VCTRUNK1. In this example, the EPL service does not carry the VLAN tag. The service of user B1 is an EPL service.
Source CVLAN (e.g. 1, 3-6) Sink Port
Null
VCTRUN K1
Sink CVLAN (e.g. 1, 3-6) User B1 Service Type
Null
EPL
Issue 02 (2011-10-31)
368
User
Parameter
Value in This Example Bidirection al PORT2
Description
Service Direction Source Port
The service of user B1 is a bidirectional service. When creating the bidirectional Ethernet service from a PORT to a VCTRUNK, it is recommended that you use a specific PORT as the source port. In this example, the service of user B1 occupies PORT2. In this example, the EPL service does not carry the VLAN tag. When creating the bidirectional Ethernet service from a PORT to a VCTRUNK, it is recommended that you use a specific VCTRUNK as the sink port. In this example, the service of user B1 occupies VCTRUNK2. In this example, the EPL service does not carry the VLAN tag.
Null
VCTRUN K2
Sink CVLAN (e.g. 1, 3-6) 4.
Null
Configure the cross-connections from the Ethernet services to the SDH links for user A1 and user B1. l In the NE Explorer, select NE1 and then choose Configuration > SDH Service Configuration from the Function Tree. Click . l Click Create on the lower-right pane to display the Create SDH Service dialog box. Set the parameters that are required, and then click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. User Paramete r Level Value in This Example VC4 Description
User A1
The timeslot bound with the service of user A1 is at the VC-4 level. The service level must be consistent with the level of the path bound with the VCTRUNK. The service of user A1 is a bidirectional service. When you create a bidirectional SDH service from an Ethernet board to a line board, it is recommended that you set the slot of the Ethernet board as the source slot.
Direction
Bidirectiona l
Source Slot 4-EGSH-1 (SDH-1)
Issue 02 (2011-10-31)
369
User
Paramete r Source Timeslot Range (e.g. 1,3-6)
Description
The value range of the source VC-4 timeslots is consistent with the value of Available Resources, which is set for the paths bound with VCTRUNK1. In this example, the value of Available Resources is VC4-1. When you create a bidirectional SDH service from an Ethernet board to a line board, it is recommended that you set the slot of the line board as the sink slot. The value range of the sink timeslots can be the same as or different from the value range of the source timeslots. The number of sink timeslots, however, must be consistent with the number of source timeslots. -
Sink Slot
17SLQ64-1 (SDH-1) 1
Sink Timeslot Range (e.g. 1,3-6)
Activate Immediatel y User B1 Level
Yes
VC4
The timeslot bound with the service of user B1 is at the VC-4 level. The service level must be consistent with the level of the path bound with the VCTRUNK. The service of user B1 is a bidirectional service. When you create a bidirectional SDH service from an Ethernet board to a line board, it is recommended that you set the slot of the Ethernet board as the source slot. The value range of the source VC-4 timeslots is consistent with the value of Available Resources, which is set for the paths bound with VCTRUNK1. In this example, the values of Available Resources are VC4-2 and VC4-3. When you create a bidirectional SDH service from an Ethernet board to a line board, it is recommended that you set the slot of the line board as the sink slot.
Direction
Bidirectiona l
Source Timeslot Range (e.g. 1,3-6)
2-3
Sink Slot
17SLQ64-1 (SDH-1)
Issue 02 (2011-10-31)
370
User
Paramete r Sink Timeslot Range (e.g. 1,3-6) Activate Immediatel y
Description
The value range of the sink timeslot can be the same as or different from the value range of the source timeslot. The number of source timeslots must be, however, the same as the number of sink timeslots. -
Yes
Step 2 Configure the pass-through services for user A1 and user B1 on NE2. 1. 2. 3. Click . Select NE2 in the dialog box that is displayed. Then, click OK. .
In the NE Explorer, select NE2 and then choose Configuration > SDH Service Configuration from the Function Tree. Click Click Create on the lower-right pane to display the Create SDH Service dialog box. Set the parameters that are required, and then click OK. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. Parameter Value in This Example VC4 Bidirectional 1-SLQ64-1 (SDH-1) 1-3 Description
Level Direction Source Slot
The SDH service of NE1, which passes through NE2, is at the VC-4 level. The SDH service from NE1 to NE2 is a bidirectional service. The service signals are transmitted from 1-SLQ64-1 (SDH-1) to 17-SLQ64-1(SDH-1). In this example, Source Slot is set to 1-SLQ64-1(SDH-1). The service between user A1 and user B1 occupies three VC-4s.
17-SLQ64-1 (SDH-1) 1-3
The service signals are transmitted from 1-SLQ64-1 (SDH-1) to 17-SLQ64-1(SDH-1). In this example, Sink Slot is set to 17-SLQ64-1(SDH-1). The service between user A1 and user B1 occupies three VC-4s.
Issue 02 (2011-10-31)
371
Parameter
Value in This Example Yes
Description
Activate Immediatel y
Step 3 Configure the EPL services for user A2 and user B2 on NE3. Refer to Step 1 and configure the EPL services for user A2 and user B2. Step 4 Check whether the service between user A1 and user A2 and the service between user B1 and user B2 are correct. For the operation procedure, see Testing Ethernet Service Paths. Step 5 Enable the performance monitoring function of the NEs. For details, see Setting Performance Monitoring Parameters of an NE. Step 6 Back up the configuration data of the NEs. Second methods are available for the backup. Option Description
The SCC board is not configured with any Backing Up the NE Database to the SCC Board CF card. The SCC board is configured with a CF card. ----End Manually Backing Up the NE Database to a CF Card
10.13 Configuration Example: Configuring EVPL (QinQ) Services on a SDH Network

The EVPL (QinQ) service provides an Ethernet private line solution. The services are applicable where the services of multiple users that have the same VLAN ID are accessed into a transmission network and need to be transmitted on the same VCTRUNK. In the case of EVPL (QinQ) services, a layer of S-VLAN tag is added on the network side to isolate the services of different users from each other.

When the services of multiple users that have the same VLAN ID are accessed on the same station and need to be transmitted on the same VCTRUNK, a layer of S-VLAN tag is added to isolate the services of different users from each other.
Service Requirement
On the network as shown in Figure 10-32, the service requirements are as follows: l Two branches of user J are located at NE1 and NE2, and need to communicate with each other.
Issue 02 (2011-10-31)
l l
Two branches of user K are located at NE1 and NE2, and need to communicate with each other. The services of user J need to be isolated from the services of user K. The traffic of user J and the traffic of user K, however, occupy a 200 Mbit/s bandwidth during different time periods. The Ethernet equipment of user J and user K provides 1000 Mbit/s Ethernet optical ports that work in 1000M full-duplex mode. The services of all the users have the same VLAN ID of 100 and are accessed into the transmission network.
Figure 10-32 Networking diagram of the EVPL (QinQ) services
1-SLQ64 4-EGSH NE2 1
NE3
PORT1 VLAN 100 User J2 PORT2 VLAN 100
NE4
NE1 17 PORT2 VLAN 100 User K1 PORT1 VLAN 100
User K2 Line Board Ethernet Board 17-SLQ64 4-EGSH
User J1 VCTRUNK OptiX OSN 8800

In this example, NE1 and NE2 are each configured with one EGSH board, which is an Ethernet switching board supporting the QinQ function. Two layers of VLAN tags are added to isolate the services of different users from each other. l When the data of user J is accessed into the transmission network, the S-VLAN tags are added to the data. When the data is transmitted out of the transmission network, the SVLAN tags are stripped. When the data of user K is accessed into the transmission network, the S-VLAN tags are added to the data. When the data is transmitted out of the transmission network, the SVLAN tags are stripped.
Issue 02 (2011-10-31)

The services of multiple users that have the same VLAN ID are accessed through different external ports of the Ethernet board on the source node. After different S-VLAN tags are added to the services, the services are transmitted on the same VCTRUNK. In this manner, the services of different users are isolated from each other. After the services arrive at the sink node, the SVLAN tags are stripped. Figure 10-33 shows the signal flow of the EVPL (QinQ) services and the timeslot allocation to the EVPL (QinQ) services. Figure 10-33 Signal Flow and Timeslot Allocation
NE1:EGSH
User J1 VLAN 100 User K1 VLAN 100 PORT1 PORT2 EVPL2 EVPL1
VCTRUNK1 VC4-xv:VC4-1 VC4-xv:VC4-2 VC4:VC4-1 VC4:VC4-2 VCTRUNK1 VC4-xv:VC4-1 VC4-xv:VC4-2
NE2:EGSH
EVPL1 PORT1 User J2 VLAN 100 PORT2 EVPL2 User K2 VLAN 100
SDH
PORT Strip S-VLAN Label
C-VLAN(100) C-VLAN(100) User J1 User K1
VCTRUNK Add S-VLAN Label Strip S-VLAN Label

C-VLAN(100) C-VLAN(100) User J1 User K1
S-VLAN(10) S-VLAN(20)
C-VLAN(100) C-VLAN(100)
User J1 User K1
l l
The EVPL services of user J and user K that share VCTRUNK1 occupy the first VC-4 (VC4:VC4-1) and second VC-4 (VC4:VC4-2) on the SDH link between NE1 and NE2. The EVPL services of user J and user K are added and dropped by using the first VC-4 (VC4-xv:VC4-1) and second VC-4 (VC4-xv:VC4-2) on the EGSH board of NE1 and the first VC-4 (VC4-xv:VC4-1) and second VC-4 (VC4-xv:VC4-2) on the EGSH board of NE2.
Table 10-26 Parameters of the external ports of the Ethernet boards Parameter Board Port Enabled/ Disabled Working Mode Maximum Frame Length Port Type NE1 EGSH PORT1 Enabled 1000M FullDuplex 1522 C-Aware PORT2 Enabled 1000M FullDuplex 1522 C-Aware NE2 EGSH PORT1 Enabled 1000M FullDuplex 1522 C-Aware PORT2 Enabled 1000M FullDuplex 1522 C-Aware
Issue 02 (2011-10-31)
374
Table 10-27 Parameters of the internal ports of the Ethernet boards Parameter Board Port Mapping Protocol Port Type Bound Path NE1 EGSH VCTRUNK1 GFP S-Aware VC4-xv:VC4-1, VC4xv:VC4-2 NE2 EGSH VCTRUNK1 GFP S-Aware VC4-xv:VC4-1, VC4xv:VC4-2
Table 10-28 Parameters of the EVPL (QinQ) services Parameter NE1 EVPL1 PORT1 VCTRUNK1 Board Service Type Service Direction Operation Type Source Port Source CVLAN(e.g.1, 3-6) Source SVLAN Sink Port Sink C-VLAN (e.g.1, 3-6) Sink S-VLAN C-VLAN Priority S-VLAN Priority EGSH EVPL(QinQ) Bidirectional Add S-VLAN PORT1 100 PORT2 100 EVPL2 PORT2 VCTRUNK1 NE2 EVPL1 PORT1 VCTRUNK1 EGSH EVPL(QinQ) Bidirectional Add S-VLAN PORT1 100 PORT2 100 EVPL2 PORT2 VCTRUNK1
VCTRUNK1 100 10 AUTO AUTO
Issue 02 (2011-10-31)
375

The Ethernet switching boards supporting the QinQ function need to be installed at the source and sink nodes and need to be configured with the EVPL services of different users. Different S-VLAN tags are added to the services of different users that have the same C-VLAN ID and are accessed through different ports on the Ethernet switching boards. In this manner, the services of different users are isolated from each other and are transmitted on the same VCTRUNK.
Prerequisite
The Creating a Network task must be complete. You must be familiar with EVPL (QinQ) Service Configuration Process.
Procedure
Step 1 Configure the EVPL services for user J1 and user K1 on NE1. 1. Configure the attributes of the external ports (PORT1 and PORT2 of the EGSH board) used by the services of user J1 and user K1. l In the NE Explorer, select the EGSH board and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. l Select External Port. l Click the Basic Attributes tab. After setting the parameters, click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. Parame ter Enabled / Disable d Workin g Mode Value in This Example PORT1: Enabled PORT2: Enabled Description PORT1 is used by the service of user J1. PORT2 is used by the service of user K1. In this example, Enabled/Disabled is set to Enabled for PORT1 and PORT2. In this example, the Ethernet service access equipment of user J1 and user K1 supports the 1000M full-duplex mode. Hence, Working Mode is set to 1000M FullDuplex for PORT1 and PORT2. Generally, this parameter adopts the default value 1522.
PORT1: 1000M FullDuplex PORT2: 1000M FullDuplex
PORT1: 1522 PORT2: 1522
Issue 02 (2011-10-31)
376
l Click the Flow Control tab. The parameters in the Flow Control tab page adopt the default values. l Click the Network Attributes tab. After setting the parameters, click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. Parameter Port Type Value in This Example PORT1: C-Aware PORT2: C-Aware Description The C-Aware port is used for connecting to the client network, and identifies and processes the packets that carry C-VLAN tags.
l When Port Type is set to C-Aware or S-Aware, the parameters in the TAG Attributes tab page are invalid. Hence, The parameters in the TAG Attributes tab page need not be set. l Click the Advanced Attributes tab. The parameters in the Advanced Attributes tab page adopt the default values. 2. Set the attributes of the internal port (VCTRUNK1 on the EGSH board) used by the service between user J1 and user J2 and the service between K1 and user K2. l Select Internal Port. l Click the Network Attributes tab. After setting the parameters, click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. Parame ter Port Type Value in This Example VCTRUNK1: S-Aware Description The S-Aware port is used for connecting to the supplier network, and identifies and processes the packets that carry S-VLAN tags.
l Click the Encapsulation/Mapping tab. After setting the parameters, click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. Parame ter Mappin g Protocol Scrambl e Value in This Example VCTRUNK1: GFP Description Mapping Protocol of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value. In this example, this parameter adopts the default value Scrambling mode[X43+1]. Scramble of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value.
377
VCTRUNK1: Scrambling mode[X43 +1]
Issue 02 (2011-10-31)
Parame ter Check Field Length
Value in This Example VCTRUNK1: FCS32
Description In this example, this parameter adopts the default value FCS32. Check Field Length of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value. When Mapping Protocol is set to GFP, FCS Calculated Bit Sequence is set to Big endian. FCS Calculated Bit Sequence of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value. When Mapping Protocol is set to GFP, this parameter is valid and adopts the default value No. Extension Header Option of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value.
VCTRUNK1: Big endian
VCTRUNK1: No
l This operation is optional. Click the LCAS tab. After setting the parameters, click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. Parame ter Enablin g LCAS LCAS Mode Value in This Example VCTRUNK1: Enabled VCTRUNK1: Huawei Mode Description In this example, the LCAS function is enabled. In this example, this parameter adopts the default value Huawei Mode. When Huawei equipment is used at both ends, LCAS Mode of the equipment at both ends is set to Huawei Mode. In this example, this parameter adopts the default value 2000. This parameter can also be set according to the requirement of the user. In this example, this parameter adopts the default value 300. This parameter can also be set according to the requirement of the user. In this example, the TSD function is disabled. The LCAS does not check the B3 bit error or BIP status of the VCTRUNK members.
HO Time (ms) WTR Time(s) TSD
VCTRUNK1: 2000
VCTRUNK1: 300
VCTRUNK1: Disabled
Issue 02 (2011-10-31)
378
l Click the Bound Path tab. Click the Configuration button. Set the parameters in the Bound Path Configuration dialog box that is displayed. Click and then click Apply. Click Yes in the Hint dialog box that is displayed. Click Close in the Operation Result dialog box that is displayed. User Paramete r Configurab le Ports Ava ilabl e Bou nd Path s Lev el Value in This Example VCTRUN K1 VC4-xv Description
User J1 user J2 User K1 user K2
VCTRUNK1 is used by the service between user J1 and user J2 and the service between user K1 and user K2. The service between user J1 and user J2 and the service between user K1 and user K2 share a 200 Mbit/s bandwidth. Hence, two VC-4s need to be bound. The service between user J1 and user J2 and the service between user K1 and user K2 are bidirectional services.
Ser vice Dir ecti on Ava ilab le Res our ces
Bidirection al
VC4-1, VC4-2
In this example, the first and second VC-4s of the EGSH board are bound.
l When Port Type is set to C-Aware or S-Aware, the parameters in the TAG Attributes tab page are invalid. Hence, The parameters in the TAG Attributes tab page need not be set. l Click the Advanced Attributes tab. The parameters in the Advanced Attributes tab page adopt the default values. 3. Configure the Ethernet private line services between user J1 and user J2 and between user K1 and user K2. l In the NE Explorer, select the EGSH board and then choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. l Select Display QinQ Shared Service on the lower-right pane. Then, click New. l Set the parameters in the Create Ethernet Line Service dialog box that is displayed. Click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. User Parameter Value in This Example EVPL (QinQ) Description
User J1 user J2
Issue 02 (2011-10-31)
Service Type
The service between user J1 and user J2 is an EVPL (QinQ) service.
379
User
Parameter
Value in This Example Bidirectio nal Add SVLAN
Description
Service Direction Operation Type
The service between user J1 and user J2 is a bidirectional service. The service between user J1 and user J2 and the service between user K1 and user K2 carry the same C-VLAN tag. Hence, a layer of S-VLAN tag needs to be added to isolate the services of different users. When creating the bidirectional Ethernet service from a PORT to a VCTRUNK, it is recommended that you use a specific PORT as the source port. In this example, PORT1 is the external port used by the service between user J1 and user J2. The Ethernet service of user J1 carries the CVLAN ID of 100. The data packets that are accessed into the external port carry the C-VLAN tags but do not carry the S-VLAN tags. When creating the bidirectional Ethernet service from a PORT to a VCTRUNK, it is recommended that you use a specific VCTRUNK as the sink port. In this example, VCTRUNK1 is the internal port used by the service between user J1 and user J2. The Ethernet service of user J2 carries the CVLAN ID of 100. According to the plan, the S-VLAN ID of 10 needs to be added to the service between user J1 and user J2. In this example, this parameter adopts the default value. In this example, this parameter adopts the default value. The service between user K1 and user K2 is a bidirectional service.
Source Port
PORT1
Source CVLAN(e.g. 1, 3-6) Source SVLAN Sink Port
100
VCTRUN K1
Sink CVLAN(e.g. 1, 3-6) Sink SVLAN C-VLAN Priority S-VLAN Priority User K1 user K2 Service Direction
100
10
AUTO AUTO Bidirectio nal
Issue 02 (2011-10-31)
380
User
Parameter
Value in This Example Add SVLAN
Description
Operation Type
The service between user J1 and user J2 and the service between user K1 and user K2 carry the same C-VLAN tag. Hence, a layer of S-VLAN tag needs to be added to isolate the services of different users. When creating the bidirectional Ethernet service from a PORT to a VCTRUNK, it is recommended that you use a specific PORT as the source port. In this example, PORT2 is the external port used by the service between user K1 and user K2. The Ethernet service of user K1 carries the C-VLAN ID of 100. The data packets that are accessed into the external port carry the C-VLAN tags but do not carry the S-VLAN tags. When creating the bidirectional Ethernet service from a PORT to a VCTRUNK, it is recommended that you use a specific VCTRUNK as the sink port. In this example, VCTRUNK1 is the internal port used by the service between user K1 and user K2. The Ethernet service of user K2 carries the C-VLAN ID of 100. According to the plan, the S-VLAN ID of 20 needs to be added to the service between user K1 and user K2. In this example, this parameter adopts the default value. In this example, this parameter adopts the default value.
Source Port
PORT2
Source CVLAN(e.g. 1, 3-6) Source SVLAN Sink Port
100
VCTRUN K1
Sink CVLAN(e.g. 1, 3-6) Sink SVLAN C-VLAN Priority S-VLAN Priority
100
20
AUTO AUTO
4.
Configure the cross-connections from the Ethernet services to the SDH links for user J1 and user K1. l In the NE Explorer, select NE1 and then choose Configuration > SDH Service Configuration from the Function Tree. Click . l Click Create on the lower-right pane to display the Create SDH Service dialog box. Set the parameters that are required. Click Apply. Then, the Operation Result is displayed, indicating that the operation is successful. Click Close.
Issue 02 (2011-10-31)
381
User
Paramete r Level
Value in This Example VC4
Description
The timeslots bound with the service between user J1 and user J2 and the service between user K1 and user K2 are at the VC-4 level. The service level must be consistent with the level of the paths bound with the VCTRUNK. The service between user J1 and user J2 and the service between user K1 and user K2 are bidirectional services. When you create a bidirectional SDH service from an Ethernet board to a line board, it is recommended that you set the slot of the Ethernet board as the source slot. The value range of the source timeslots is consistent with the value of Available Resources, which is set for the paths bound with VCTRUNK1. In this example, the values of Available Resources are VC4-1 and VC4-2. When you create a bidirectional SDH service from an Ethernet board to a line board, it is recommended that you set the slot of the line board as the sink slot. The value range of the sink timeslots can be the same as or different from the value range of the source timeslots. The number of sink timeslots, however, must be consistent with the number of source timeslots. -
Direction
Bidirectiona l
Source Timeslot Range(e.g. 1,3-6)
1-2
Sink Slot
17SLQ64-1 (SDH-1) 1-2
Sink Timeslot Range(e.g. 1,3-6)
Yes
Step 2 Configure the EVPL service of NE2. Refer to Step 1 and configure the EVPL service of NE2. The procedures and parameters for configuring the EVPL service of NE2 are the same as the procedures and parameters for configuring the EVPL service of NE1. Step 3 Check whether the services between NE1 and NE2 are configured correctly. For the operation procedures, see Testing Ethernet Service Paths. l Before testing the service connectivity between user J1 and user J2, set TAG to Access and Default VLAN ID to 100 for PORT1 on the EGSH board.
l Before testing the service connectivity between user K1 and user K2, set TAG to Access and Default VLAN ID to 100 for PORT2 on the EGSH board.
NOTE
After the test, change the parameter values back to the values specified in the service configuration.
Step 4 Enable the performance monitoring function of the NEs. For details, see Setting Performance Monitoring Parameters of an NE. Step 5 Back up the configuration data of the NEs. Three methods are available for the backup. Option Description
10.14 Configuration Example: Configuring PORT-Shared EVPL (VLAN) Services on a SDH Network
The PORT-shared EVPL (VLAN) service is applicable when the services of multiple users, which are received from the same external port on the Ethernet board at a station, need to be transmitted on different VCTRUNKs to another station or to another external port of the station.

The services of multiple users, which are received from the same external port on an Ethernet board of a station, need to be transmitted to different stations on different VCTRUNKs.
Service Requirement
On the network shown in Figure 10-34, the service requirements are as follows: l The headquarters C1 of user C is located at NE1. Two branches (C2 and C3) of user C are located at NE2 and NE4. The services between C1 and C2 are transmitted in the VLAN of which the VLAN ID is 100. The services between C1 and C3 are transmitted in the VLAN of which the VLAN ID is 200. The services of C2 are isolated from the services of C3. The services of C2 and C3 require a 100 Mbit/s bandwidth respectively. The Ethernet equipment of C1, C2, and C3 provides 1000 Mbit/s Ethernet optical ports that work in 1000M full-duplex mode. The Ethernet equipment of C1 supports VLAN tags, but the Ethernet equipment of C2 and C3 does not support VLAN tags. The VLAN ID used by the Ethernet services between C1 and C2 is 100. The VLAN ID used by the Ethernet services between C1 and C3 is 200.
l l
Issue 02 (2011-10-31)
383
Figure 10-34 Networking diagram for configuring PORT-shared EVPL (VLAN) services
T2000 Line Board 1-JL64 Ethernet Board 15-EGT6 NE2 PORT1 User C2 1 NE1 17 PORT1 1 Line Board 17-SLQ64 Line Board 1-SLQ64 Ethernet Board 4-EGSH NE3 Line Board Ethernet Board NE4 17 17-JL64 15-EGT6
PORT1
User C3
User C1 VLAN 100 VLAN 200 VCTRUNK
OptiX OSN 8800
OptiX OSN 3500

In this example, NE1 is configured with an EGSH board. VLAN IDs are used to isolate the data of different users that are received from the same port. NE2 and NE4 are configured with an EGT6 board each. The EPL services are configured to implement service transparent transmission from NE2 and NE4 to NE1.
NOTE
The Ethernet boards are classified into the Ethernet transparent transmission boards and Ethernet switching boards, based on the type of the accessed services. The Ethernet transparent transmission boards support only EPL services whereas the Ethernet switching boards support EPL services, EVPL services, and Layer 2 switching. Hence, Ethernet switching boards are used more widely than Ethernet transparent transmission boards.

The Ethernet services wherein different VLAN IDs are used to isolate the data of different users, are received from the same external port of NE1, encapsulated through an internal port, and then transparently transmitted on the SDH network. In this manner, the node communicates with a remote node. Figure 10-35 shows the signal flow of the PORT-shared EVPL (VLAN) services and the timeslot allocation to the PORT-shared EVPL (VLAN) services.

NE2:EGT6 NE1:EGSH
EVPL1 EVPL2
VCTRUNK1 VC4-xv:VC4-1 VCTRUNK2 VC4-xv:VC4-2
VC 4
4:VC VC4
VCTRUNK1 VC4-xv:VC4-1
EPL
PORT1 User C2
PORT1 User C1
:VC 4-1
NE4:EGT6
EPL
PORT1 User C3
SDH
The EVPL service from C1 to C2: Occupies the first VC-4 (VC4:VC4-1) on the SDH link between NE1 and NE2. Is added and dropped by using the first VC-4 (VC4-xv:VC4-1) on the EGSH board of NE1 and the first VC-4 (VC4-xv:VC4-1) on the EGT6 board of NE2.
The EVPL service from C1 to C3: Occupies the first VC-4 (VC4:VC4-1) on the SDH link between NE1 and NE4. Is added and dropped by using the second VC-4 (VC4-xv:VC4-2) on the EGSH board of NE1 and the first VC-4 (VC4-xv:VC4-1) on the EGT6 board of NE4.
Table 10-29 Parameters of the external ports of the Ethernet boards Parameter Board Port Enabled/Disabled Working Mode Maximum Frame Length TAG Entry Detection Port Type NE1 EGSH PORT1 Enabled 1000M Full-Duplex 1522 Tag Aware Enabled UNI NE2 EGT6 PORT1 Enabled 1000M Full-Duplex 1522 NE4 EGT6 PORT1 Enabled 1000M Full-Duplex 1522 -
Table 10-30 Parameters of the internal ports of the Ethernet boards Parameter Board
Issue 02 (2011-10-31)
NE1 EGSH
NE2 EGT6
NE4 EGT6
385
Parameter Port Mapping Protocol TAG Entry Detection Default VLAN ID VLAN Priority Bound Path Port Type
NE1 VCTRUNK1 GFP Access Enabled 100 0 VC4-xv:VC4-1 UNI VCTRUNK2 GFP Access Enabled 200 0 VC4-xv:VC4-2 UNI
NE2 VCTRUNK1 GFP VC4-xv:VC4-1 -
Table 10-31 Parameters of the PORT-shared EVPL (VLAN) services Parameter NE1 EVPL1 (PORT1 VCTRUNK1) Board Service Type Service Direction Source Port Source C-VLAN(e.g.1, 3-6) Sink Port Sink C-VLAN(e.g.1, 3-6) EGSH EVPL Bidirectional PORT1 100 VCTRUNK1 100 PORT1 200 VCTRUNK2 200 EVPL2 (PORT1 VCTRUNK2)

Ethernet switching boards are required for creating EVPL services of different VLAN IDs on NE1. In this manner, the data of different users, which are received from the same external port, can be differentiated. Ethernet transparent transmission boards are required for creating EPL transparent transmission services on NE2 and NE4.
Prerequisite
The Creating a Network task must be complete. You must be familiar with 10.3.2 EVPL (QinQ) Service Configuration Process.


Step 1 Configure the EVPL services for user C1 on NE1. 1. Configure the attributes of the external port (PORT1 of the EGSH board) used by the service of user C1. l In the NE Explorer, select the EGSH and then choose Communication > Ethernet Interface Management > Ethernet Interface from the Function Tree. l Select External Port. l Click the Basic Attributes tab. After setting the parameters, click Apply. Then, the Operation Result dialog box is displayed. Click Close. Parame ter Enabled / Disable d Workin g Mode Value in This Example PORT1: Enabled Description The service of user C1 occupies PORT1. In this example, Enabled/Disabled is set to Enabled. The Ethernet service access equipment of user C1 supports the 1000M full-duplex mode. In this example, Working Mode is set to Auto-Negotiation. Generally, this parameter adopts the default value 1522.
PORT1: 1000M FullDuplex
PORT1: 1522
PORT1: Non-Loopback
PORT1: Non-Loopback
l Click the Flow Control tab. The parameters in the Flow Control tab page adopt the default values. l Click the TAG Attributes tab. After setting the parameters, click Apply. Then, the Operation Result dialog box is displayed. Click Close.
Issue 02 (2011-10-31)
387
Parame ter TAG
Value in This Example PORT1: Tag Aware
Description When the port is set to Tag Aware, all data frames transmitted and received at the port must carry VLAN tags. In this example, TAG is set to Tag Aware. When TAG is set to Tag Aware, you need not set Default VLAN ID. When TAG is set to Tag Aware, you need not set VLAN Priority. The services of user C1 is EVPL services. Hence, the entry detection function must be enabled to check whether the data frames carry VLAN tags. In this manner, the user data frames with different VLAN tags can be distinguished at one port. In this example, Entry Detection of PORT1 is set to Enabled.
Default VLAN ID VLAN Priority Entry Detectio n
PORT1: Enabled
l Click the Network Attributes tab. After setting the parameters, click Apply. Then, the Operation Result dialog box is displayed. Click Close. Parame ter Port Type Value in This Example PORT1: UNI Description UNI indicates the user-network interface, namely, the interface of the service provider located near the user side. The UNI interface processes the tag attribute of IEEE 802.1qcompliant packets. That is, the UNI interface processes and identifies the VLAN information of the accessed user packets, according to the supported tag flags, namely Tag Aware, Access, and Hybrid.
l Click the Advanced Attributes tab. The parameters in the Advanced Attributes tab page adopt the default values. 2. Set the attributes of the internal ports (VCTRUNK1 and VCTRUNK2 of the EGSH board) used by the services between user C1 and user C2 and between user C1 and user C3. l Select Internal Port. l Click the TAG Attributes tab. After setting the parameters, click Apply. Then, the Operation Result dialog box is displayed. Click Close.
Issue 02 (2011-10-31)
388
Parame ter TAG
Value in This Example VCTRUNK1: Access VCTRUNK2: Access
Description This parameter is set to Access if the Ethernet equipment of user C2 and user C3 does not support VLAN tags and if the transmitted packets do not carry VLAN tags. According to the plan, the VLAN ID is set to 100 on the transmission network side for the Ethernet services between user C1 and user C2. The VLAN ID is set to 200 on the transmission network side for the Ethernet services between user C1 and user C3.
Default VLAN ID
VLAN Priority Entry Detectio n
VCTRUNK1: 0 VCTRUNK2: 0 VCTRUNK1: Enabled VCTRUNK2: Enabled
In this example, this parameter adopts the default value. The services of user C1, user C2 and user C3 are EVPL services. Hence, the entry detection function must be enabled to check whether the received packets carry VLAN tags.
l Click the Network Attributes tab. After setting the parameters, click Apply. Then, the Operation Result dialog box is displayed. Click Close. Parame ter Port Type Value in This Example VCTRUNK1: UNI VCTRUNK2: UNI Description UNI indicates the user-network interface, namely, the interface of the service provider located near the user side. The UNI interface processes the tag attribute of IEEE 802.1qcompliant packets. That is, the UNI interface processes and identifies the VLAN information of the accessed user packets, according to the supported tag flags, namely Tag Aware, Access, and Hybrid.
l Click the Encapsulation/Mapping tab. After setting the parameters, click Apply. Then, the Operation Result dialog box is displayed. Click Close. Parame ter Mappin g Protocol Value in This Example VCTRUNK1: GFP VCTRUNK2: GFP Description Mapping Protocol of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value.
Issue 02 (2011-10-31)
389
Parame ter Scrambl e
Value in This Example VCTRUNK1: Scrambling mode[X43 +1] VCTRUNK2: Scrambling mode[X43 +1]
Description In this example, this parameter adopts the default value Scrambling mode[X43+1]. Scramble of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value. In this example, this parameter adopts the default value FCS32. Check Field Length of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value. When Mapping Protocol is set to GFP, FCS Calculated Bit Sequence is set to Big endian. FCS Calculated Bit Sequence of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value. When Mapping Protocol is set to GFP, this parameter is valid and adopts the default value No. Extension Header Option of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value.
Check Field Length
l This operation is optional. Click the LCAS tab. After setting the parameters, click Apply. Then, the Operation Result dialog box is displayed. Click Close. Parame ter Enablin g LCAS LCAS Mode Value in This Example VCTRUNK1: Enabled VCTRUNK2: Enabled VCTRUNK1: Huawei Mode VCTRUNK2: Huawei Mode HO Time (ms) WTR Time (s) VCTRUNK1: 2000 VCTRUNK2: 2000 Description In this example, the LCAS function is enabled. In this example, this parameter adopts the default value Huawei Mode. When Huawei equipment is used at both ends, LCAS Mode of the equipment at both ends is set to Huawei Mode. In this example, this parameter adopts the default value 2000. This parameter can also be set according to the requirement of the user. In this example, this parameter adopts the default value 300. This parameter can also be set according to the requirement of the user.
Issue 02 (2011-10-31)
390
Parame ter TSD
Value in This Example VCTRUNK1: Disabled VCTRUNK2: Disabled
Description In this example, the TSD function is disabled. The LCAS does not check the B3 bit error or BIP status of the VCTRUNK members.
l Click the Bound Path tab. Click the Configuration button. Set the following parameters in the Bound Path Configuration dialog box that is displayed. Click and click Apply. Click Yes in the Hint dialog box that is displayed. Click Close in the Operation Result dialog box that is displayed. User Parameter Value in This Example VCTRUN K1 VC4-xv Description
User C1 user C2
Configurabl e Ports Availa ble Bound Paths Le vel Se rvi ce Di rec tio n Av ail abl e Re so ur ce s
As shown in Figure 10-35, VCTRUNK1 is used by the service between user C1 and user C2. The service between user C1 and user C2 uses a 100 Mbit/s bandwidth. Hence, one VC-4 needs to be bound. The service between user C1 and user C2 is a bidirectional service.
Bidirection al
VC4-1
In this example, Available Resources is set to VC4-1.
User C1 user C3
Configurabl e Ports Availa ble Bound Paths Le vel
VCTRUN K2 VC4-xv
As shown in Figure 10-35, VCTRUNK2 is used by the service between user C1 and user C3. The service between user C1 and user C3 uses a 100 Mbit/s bandwidth. Hence, one VC-4 needs to be bound.
Issue 02 (2011-10-31)
391
User
Parameter
Value in This Example Bidirection al
Description
Se rvi ce Di rec tio n Av ail abl e Re so ur ce s
The service between user C1 and user C3 is a bidirectional service.
VC4-2
l Click the Advanced Attributes tab. The parameters in the Advanced Attributes tab page adopt the default values. 3. Configure the Ethernet private line services between user C1 and user C2 and between user C1 and user C3. l In the NE Explorer, select the EGSH board and then choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Click . l Click New on the lower-right pane to display the Create Ethernet Line Service dialog box. Set the following parameters, and then click OK. The Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. User Parameter Value in This Example EPL Bidirection al PORT1 Description
User C1 user C2
Service Type Service Direction Source Port
The service between user C1 and C2 is a pointto-point Ethernet private line service. The service between user C1 and user C2 is a bidirectional service. When creating the bidirectional Ethernet service from a PORT to a VCTRUNK, it is recommended that you use a specific PORT as the source port. PORT1 is the external port used by the service between user C1 and user C2. According to the plan, the VLAN ID is set to 100 for the Ethernet service between user C1 and user C2.
392
Source CVLAN (e.g. 1, 3-6)

Issue 02 (2011-10-31)
100
User
Parameter
Value in This Example VCTRUN K1
Description
Sink Port
When creating the bidirectional Ethernet service from a PORT to a VCTRUNK, it is recommended that you use a specific VCTRUNK as the sink port. VCTRUNK1 is the internal port used by the service between user C1 and user C2. According to the plan, the VLAN ID is set to 100 for the Ethernet service between user C1 and user C2. The service between user C1 and user C3 is a point-to-point Ethernet private line service. The service between user C1 and user C3 is a bidirectional service. When creating the bidirectional Ethernet service from a PORT to a VCTRUNK, it is recommended that you use a specific PORT as the source port. PORT1 is the external port used by the service between user C1 and user C3. According to the plan, the VLAN ID is set to 200 for the Ethernet service between user C1 and user C3. When creating the bidirectional Ethernet service from a PORT to a VCTRUNK, it is recommended that you use a specific VCTRUNK as the sink port. VCTRUNK2 is the internal port used by the service between user C1 and user C2. According to the plan, the VLAN ID is set to 200 for the Ethernet service between user C1 and user C3.
Sink CVLAN (e.g. 1, 3-6) User C1 user C3 Service Type Service Direction Source Port
100
EPL Bidirection al PORT1
200
VCTRUN K2
Sink CVLAN (e.g. 1, 3-6) 4.
200
Configure the cross-connections from Ethernet services (between user C1 and user C2 and between user C1 and user C3) to the SDH links. l In the NE Explorer, select NE1 and then choose Configuration > SDH Service Configuration from the Function Tree. Click . l Click Create on the lower-right pane to display the Create SDH Service dialog box. Set the parameters that are required. Click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close.
Issue 02 (2011-10-31)
393
User
Paramete r Level
Value in This Example VC4
Description
User C1 user C2
The timeslots bound with the service between user C1 and user C2 is at the VC-4 level. The service level must be consistent with the level of the paths bound with the VCTRUNK. The service between user C1 and user C2 is a bidirectional service. When you create a bidirectional SDH service from an Ethernet board to a line board, it is recommended that you set the slot of the Ethernet board as the source slot. The value range of the source timeslots is consistent with the value of Available Resources, which is set for the paths bound with VCTRUNK1. In this example, the value of Available Resources is VC4-1. When you create a bidirectional SDH service from an Ethernet board to a line board, it is recommended that you set the slot of the line board as the sink slot. The value range of the sink timeslots can be the same as or different from the value range of the source timeslots. The number of sink timeslots, however, must be consistent with the number of source timeslots. -
Direction
Bidirectiona l
17SLQ64-1 (SDH-1) 1
Activate Immediatel y User C1 user C3 Level
Yes
VC4
The timeslot bound with the service between user C1 and user C3 is at the VC-4 level. The service level must be consistent with the level of the paths bound with the VCTRUNK. The service between user C1 and user C3 is a bidirectional service. When you create a bidirectional SDH service from an Ethernet board to a line board, it is recommended that you set the slot of the Ethernet board as the source slot.
Direction
Bidirectiona l
Issue 02 (2011-10-31)
394
User
Paramete r Source Timeslot Range (e.g. 1,3-6) Sink Slot
Description
The value range of the source timeslots is consistent with the value of Available Resources, which is set for the paths bound with VCTRUNK2. In this example, the value of Available Resources is VC4-2. When you create a bidirectional SDH service from an Ethernet board to a line board, it is recommended that you set the slot of the line board as the sink slot. The value range of the sink timeslots can be the same as or different from the value range of the source timeslots. The number of sink timeslots, however, must be consistent with the number of source timeslots. -
1-SLQ64-1 (SDH-1)
Yes
Step 2 Configure the EPL services of NE2 and NE4.

NOTE
The Ethernet services of NE2 and NE4 are point-to-point transparent transmission EPL services. See Configuration Guide (on a SDH Network) to set the parameters.
Step 3 Check whether the services are configured correctly. For the operation procedures, see Testing Ethernet Service Paths. l Before testing the service connectivity between headquarters C1 and branch C2, set TAG to Access and Default VLAN ID to 100 for PORT1 on the EGSH board. l Before testing the service connectivity between headquarters C1 and branch C3, set TAG to Access and Default VLAN ID to 200 for PORT1 on the EGSH board.
NOTE
Step 4 Enable the performance monitoring function of the NEs. For details, see Setting Performance Monitoring Parameters of an NE. Step 5 Back up the configuration data of the NEs. Second methods are available for the backup. Option Description
The SCC board is not configured with any Backing Up the NE Database to the SCC Board CF card. The SCC board is configured with a CF card. ----End
Manually Backing Up the NE Database to a CF Card
10.15 Configuration Example: Configuring VCTRUNKShared EVPL Services on a SDH Network

When the services of multiple users that do not carry VLAN tags are accessed into a transmission network and are transmitted on the same VCTRUNK, the VCTRUNK-shared EVPL (VLAN) service is used to isolate the services of different users by adding VLAN tags. In this manner, the bandwidth is shared on the SDH side.

The services of multiple Ethernet users are accessed on the same station, transmitted on the same VCTRUNK, and isolated by using different VLAN IDs. In this manner, the bandwidth is shared on the SDH side.
Service Requirement
On the network as shown in Figure 10-36, the service requirements are as follows: l l l Two branches of user D are located at NE1 and NE2, and need to communicate with each other. Two branches of user E are located at NE1 and NE2, and need to communicate with each other. The services of user D need to be isolated from the services of user E. The traffic of user D and the traffic of user E, however, occupy a 100 Mbit/s bandwidth during different time period. The Ethernet equipment of user D and user E provides 1000 Mbit/s Ethernet optical ports that work in 1000M full-duplex mode and do not support VLAN tags.
Issue 02 (2011-10-31)
396
Figure 10-36 Networking diagram for configuring VCTRUNK-shared EVPL (VLAN) services
1-SLQ64 4-EGSH
NE3 NE4 NE1 17
PORT1 User D2 PORT2 1
NE2
User E2
PORT1
PORT2
User E1
User D1
Line Board 17-SLQ64 Ethernet Board 4-EGSH
VCTRUNK
OptiX OSN 8800

In this example, NE1 and NE2 are each configured with an EGSH board. Different VLAN IDs are used to isolate the data of different users transmitted on the same VCTRUNK. l When the data of user D is accessed into the transmission network, the VLAN ID of 100 is added to the data. When the data is transmitted out of the transmission network, the VLAN tag is stripped. When the data of user E is accessed into the transmission network, the VLAN ID of 200 is added to the data. When the data is transmitted out of the transmission network, the VLAN tag is stripped.

The services of multiple users are received from different external ports on an Ethernet board, tagged with different VLAN IDs, and then transmitted on the same VCTRUNK. In this manner, the services of different users are isolated from each other. After the data arrives at the sink node, the VLAN tags are stripped. Figure 10-37 shows the signal flow of the VCTRUNK-shared EVPL (VLAN) services and the timeslot allocation to the VCTRUNK-shared EVPL (VLAN) services.
Issue 02 (2011-10-31)
397

NE1:EGSH
PORT1 User D1 PORT2 User E1 EVPL1
VCTRUNK1
NE2:EGSH
EVPL1
VCTRUNK1 VC4:VC4-1 VC4-xv:VC4-1 VC4-xv:VC4-1
PORT1 User D2 PORT2 User E2
EVPL2
EVPL2
SDH
l l
The EVPL services of user D and user E that share VCTRUNK1 occupy the first VC-4 (VC4:VC4-1) on the SDH link between NE1 and NE2. The EVPL services are added and dropped by using the first VC-4 (VC4-xv:VC4-1) on the EGSH board of NE1 and the first VC-4 (VC4-xv:VC4-1) on the EGSH board of NE2.
Table 10-32 Parameters of the external ports of the Ethernet boards Parameter Board Port Enabled/ Disabled Working Mode Maximum Frame Length TAG Entry Detection Default VLAN ID VLAN Priority Port Type NE1 EGSH PORT1 Enabled 1000M FullDuplex 1522 Access Enabled 100 0 UNI PORT2 Enabled 1000M FullDuplex 1522 Access Enabled 200 0 UNI NE2 EGSH PORT1 Enabled 1000M FullDuplex 1522 Access Enabled 100 0 UNI PORT2 Enabled 1000M FullDuplex 1522 Access Enabled 200 0 UNI
Table 10-33 Parameters of the internal ports of the Ethernet boards Parameter Board Port Mapping Protocol NE1 EGSH VCTRUNK1 GFP NE2 EGSH VCTRUNK1 GFP
Issue 02 (2011-10-31)
398
Parameter TAG Entry Detection Bound Path Port Type
NE1 Tag Aware Enabled VC4-xv:VC4-1 UNI
NE2 Tag Aware Enabled VC4-xv:VC4-1 UNI
Table 10-34 Parameters of the VCTRUNK-shared EVPL (VLAN) services Parameter NE1 EVPL1 PORT1 VCTRUNK1 Board Service Type Service Direction Source Port Source CVLAN(e.g.1, 3-6) Sink Port Sink C-VLAN (e.g.1, 3-6) EGSH EVPL Bidirectional PORT1 100 PORT2 200 EVPL2 PORT2 VCTRUNK1 NE2 EVPL1 PORT1 VCTRUNK1 EGSH EVPL Bidirectional PORT1 100 PORT2 200 EVPL2 PORT2 VCTRUNK1
VCTRUNK1 100
VCTRUNK1 200
VCTRUNK1 100
VCTRUNK1 200

The Ethernet switching boards supporting the QinQ function need to be installed at the source and sink nodes and need to be configured with the EVPL services of different users. Different S-VLAN tags are added to the services of different users that have the same C-VLAN ID and are accessed through different ports on the Ethernet switching boards. In this manner, the services of different users are isolated from each other and are transmitted on the same VCTRUNK.
Prerequisite
The Creating a Network task must be complete. You must be familiar with 10.3.2 EVPL (QinQ) Service Configuration Process.


Step 1 Configure the EVPL services for user J1 and user K1 on NE1. 1. Configure the attributes of the external ports (PORT1 and PORT2 of the EGSH board) used by the services of user J1 and user K1. l In the NE Explorer, select the EGSH board and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. l Select External Port. l Click the Basic Attributes tab. After setting the parameters, click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. Parame ter Enabled / Disable d Workin g Mode Value in This Example PORT1: Enabled PORT2: Enabled Description PORT1 is used by the service of user J1. PORT2 is used by the service of user K1. In this example, Enabled/Disabled is set to Enabled for PORT1 and PORT2. In this example, the Ethernet service access equipment of user J1 and user K1 supports the 1000M full-duplex mode. Hence, Working Mode is set to 1000M FullDuplex for PORT1 and PORT2. Generally, this parameter adopts the default value 1522.
PORT1: 1522 PORT2: 1522
l Click the Flow Control tab. The parameters in the Flow Control tab page adopt the default values. l Click the Network Attributes tab. After setting the parameters, click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. Parameter Port Type Value in This Example PORT1: C-Aware PORT2: C-Aware Description The C-Aware port is used for connecting to the client network, and identifies and processes the packets that carry C-VLAN tags.
Issue 02 (2011-10-31)
400
l When Port Type is set to C-Aware or S-Aware, the parameters in the TAG Attributes tab page are invalid. Hence, the parameters in the TAG Attributes tab page do not need to be set. l Click the Advanced Attributes tab. The parameters in the Advanced Attributes tab page adopt the default values. 2. Set the attributes of the internal port (VCTRUNK1 on the EGSH board) used by the service between user J1 and user J2 and the service between K1 and user K2. l Select Internal Port. l Click the Network Attributes tab. After setting the parameters, click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. Parame ter Port Type Value in This Example VCTRUNK1: S-Aware Description The S-Aware port is used for connecting to the supplier network, and identifies and processes the packets that carry S-VLAN tags.
l Click the Encapsulation/Mapping tab. After setting the parameters, click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. Parame ter Mappin g Protocol Scrambl e Value in This Example VCTRUNK1: GFP Description Mapping Protocol of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value. In this example, this parameter adopts the default value Scrambling mode[X43+1]. Scramble of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value. In this example, this parameter adopts the default value FCS32. Check Field Length of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value. When Mapping Protocol is set to GFP, FCS Calculated Bit Sequence is set to Big endian. FCS Calculated Bit Sequence of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value.
VCTRUNK1: Scrambling mode[X43 +1]
Check Field Length
VCTRUNK1: FCS32
FCS Calculat ed Bit Sequenc e
VCTRUNK1: Big endian
Issue 02 (2011-10-31)
401
Parame ter Extensi on Header Option
Value in This Example VCTRUNK1: No
Description When Mapping Protocol is set to GFP, this parameter is valid and adopts the default value No. Extension Header Option of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value.
l This operation is optional. Click the LCAS tab. After setting the parameters, click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. Parame ter Enablin g LCAS LCAS Mode Value in This Example VCTRUNK1: Enabled VCTRUNK1: Huawei Mode Description In this example, the LCAS function is enabled. In this example, this parameter adopts the default value Huawei Mode. When Huawei equipment is used at both ends, LCAS Mode of the equipment at both ends is set to Huawei Mode. In this example, this parameter adopts the default value 2000. This parameter can also be set according to the requirement of the user. In this example, this parameter adopts the default value 300. This parameter can also be set according to the requirement of the user. In this example, the TSD function is disabled. The LCAS does not check the B3 bit error or BIP status of the VCTRUNK members.
HO Time (ms) WTR Time(s) TSD
VCTRUNK1: 2000
VCTRUNK1: 300
VCTRUNK1: Disabled
l Click the Bound Path tab. Click the Configuration button. Set the parameters in the Bound Path Configuration dialog box that is displayed. Click and then click Apply. Click Yes in the Hint dialog box that is displayed. Click Close in the Operation Result dialog box that is displayed. User Paramete r Configurab le Ports Value in This Example VCTRUN K1 Description
User J1 user J2
VCTRUNK1 is used by the service between user J1 and user J2 and the service between user K1 and user K2.
Issue 02 (2011-10-31)
402
User
Paramete r Ava ilabl e Bou nd Path s Lev el
Value in This Example VC4-xv
Description
User K1 user K2
The service between user J1 and user J2 and the service between user K1 and user K2 share a 200 Mbit/s bandwidth. Hence, two VC-4s need to be bound. The service between user J1 and user J2 and the service between user K1 and user K2 are bidirectional services.
Ser vice Dir ecti on Ava ilab le Res our ces
Bidirection al
VC4-1, VC4-2
In this example, the first and second VC-4s of the EGSH board are bound.
l When Port Type is set to C-Aware or S-Aware, the parameters in the TAG Attributes tab page are invalid. Hence, the parameters in the TAG Attributes tab page do not need to be set. l Click the Advanced Attributes tab. The parameters in the Advanced Attributes tab page adopt the default values. 3. Configure the Ethernet private line services between user J1 and user J2 and between user K1 and user K2. l In the NE Explorer, select the EGSH board and then choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. l Select Display QinQ Shared Service on the lower-right pane. Then, click New. l Set the parameters in the Create Ethernet LAN Service dialog box that is displayed. Click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. User Parameter Value in This Example EVPL (QinQ) Bidirectio nal Add SVLAN Description
User J1 user J2
Service Type Service Direction Operation Type
The service between user J1 and user J2 is an EVPL (QinQ) service. The service between user J1 and user J2 is a bidirectional service. The service between user J1 and user J2 and the service between user K1 and user K2 carry the same C-VLAN tag. Hence, a layer of S-VLAN tag needs to be added to isolate the services of different users.
Issue 02 (2011-10-31)
403
User
Parameter
Value in This Example PORT1
Description
Source Port
When creating the bidirectional Ethernet service from a PORT to a VCTRUNK, it is recommended that you use a specific PORT as the source port. In this example, PORT1 is the external port used by the service between user J1 and user J2. The Ethernet service of user J1 carries the CVLAN ID of 100. The data packets that are accessed into the external port carry the C-VLAN tags but do not carry the S-VLAN tags. When creating the bidirectional Ethernet service from a PORT to a VCTRUNK, it is recommended that you use a specific VCTRUNK as the sink port. In this example, VCTRUNK1 is the internal port used by the service between user J1 and user J2. The Ethernet service of user J2 carries the CVLAN ID of 100. According to the plan, the S-VLAN ID of 10 needs to be added to the service between user J1 and user J2. In this example, this parameter adopts the default value. In this example, this parameter adopts the default value. The service between user K1 and user K2 is a bidirectional service. The service between user J1 and user J2 and the service between user K1 and user K2 carry the same C-VLAN tag. Hence, a layer of S-VLAN tag needs to be added to isolate the services of different users. When creating the bidirectional Ethernet service from a PORT to a VCTRUNK, it is recommended that you use a specific PORT as the source port. In this example, PORT2 is the external port used by the service between user K1 and user K2.
Source CVLAN (e.g. 1, 3-6) Source SVLAN Sink Port
100
VCTRUN K1
Sink CVLAN (e.g. 1, 3-6) Sink SVLAN C-VLAN Priority S-VLAN Priority User K1 user K2 Service Direction Operation Type
100
10
AUTO AUTO Bidirectio nal Add SVLAN
Source Port
PORT2
Issue 02 (2011-10-31)
404
User
Parameter
Description
Source CVLAN (e.g. 1, 3-6) Source SVLAN Sink Port
The Ethernet service of user K1 carries the C-VLAN ID of 100. The data packets that are accessed into the external port carry the C-VLAN tags but do not carry the S-VLAN tags. When creating the bidirectional Ethernet service from a PORT to a VCTRUNK, it is recommended that you use a specific VCTRUNK as the sink port. In this example, VCTRUNK1 is the internal port used by the service between user K1 and user K2. The Ethernet service of user K2 carries the C-VLAN ID of 100. According to the plan, the S-VLAN ID of 20 needs to be added to the service between user K1 and user K2. In this example, this parameter adopts the default value. In this example, this parameter adopts the default value.
VCTRUN K1
Sink CVLAN (e.g. 1, 3-6) Sink SVLAN C-VLAN Priority S-VLAN Priority 4.
100
20
AUTO AUTO
Configure the cross-connections from the Ethernet services to the SDH links for user J1 and user K1. l In the NE Explorer, select NE1 and then choose Configuration > SDH Service Configuration from the Function Tree. Click . l Click Create on the lower-right pane to display the Create SDH Service dialog box. Set the parameters that are required. Click Apply. Then, the Operation Result is displayed, indicating that the operation is successful. Click Close. User Paramete r Level Value in This Example VC4 Description
The timeslots bound with the service between user J1 and user J2 and the service between user K1 and user K2 are at the VC-4 level. The service level must be consistent with the level of the paths bound with the VCTRUNK.
Issue 02 (2011-10-31)
405
User
Paramete r Direction
Value in This Example Bidirectiona l
Description
The service between user J1 and user J2 and the service between user K1 and user K2 are bidirectional services. When you create a bidirectional SDH service from an Ethernet board to a line board, it is recommended that you set the slot of the Ethernet board as the source slot. The value range of the source timeslots is consistent with the value of Available Resources, which is set for the paths bound with VCTRUNK1. In this example, the values of Available Resources are VC4-1 and VC4-2. When you create a bidirectional SDH service from an Ethernet board to a line board, it is recommended that you set the slot of the line board as the sink slot. The value range of the sink timeslots can be the same as or different from the value range of the source timeslots. The number of sink timeslots, however, must be consistent with the number of source timeslots. -
Source Timeslot Range (e.g. 1,3-6)
1-2
Sink Slot
17SLQ64-1 (SDH-1) 1-2
Yes
Step 2 Configure the EVPL service of NE2. Refer to Step 1 and configure the EVPL service of NE2. The procedures and parameters for configuring the EVPL service of NE2 are the same as the procedures and parameters for configuring the EVPL service of NE1. Step 3 Check whether the services between NE1 and NE2 are configured correctly. For the operation procedures, see Testing Ethernet Service Paths. l Before testing the service connectivity between user J1 and user J2, set TAG to Access and Default VLAN ID to 100 for PORT1 on the EGSH board. l Before testing the service connectivity between user K1 and user K2, set TAG to Access and Default VLAN ID to 100 for PORT2 on the EGSH board.
NOTE
Step 4 Enable the performance monitoring function of the NEs. For details, see Setting Performance Monitoring Parameters of an NE.
Step 5 Back up the configuration data of the NEs. Second methods are available for the backup. Option Description
10.16 Configuration Example: Configuring EPLAN Services (IEEE 802.1d Bridge) on a SDH Network
The EPLAN service (IEEE 802.1d bridge) provides a LAN solution for multipoint-to-multipoint convergence. This service is applicable where the user-side data communication equipment connected to the transmission network does not support VLAN tags or where the VLAN planning cannot be disclosed to the network operator.

The convergence node needs to exchange Ethernet services with two access nodes at Layer 2. The two access nodes need not communicate with each other.
Service Requirement
On the network as shown in Figure 10-38, the service requirements are as follows: l Three branches (F1, F2, and F3) of user F are located at NE1, NE2, and NE4. F1 needs to communicate with F2 and F3, and requires a 100 Mbit/s bandwidth for communication with each branch. The Ethernet equipment of user F provides 1000 Mbit/s Ethernet optical ports that work in 1000M full-duplex mode and support VLAN tags. The VLAN IDs and the number of VLANs, however, are unknown and may be changed.
NOTE
The application scenarios where one branch needs to communicate with other branches are as follows: l Branches F2 and F3 need to communicate with each other. l Branches F2 and F3 need not communicate with each other. If branches F2 and F3 need to communicate with each other, skip Step 1.4.
Issue 02 (2011-10-31)
407
Figure 10-38 Networking diagram for configuring EPLAN services (IEEE 802.1d bridge)
NE3
1-SL64 15-EGT2 NE2 PORT1 F2 VB PORT1 PORT1 VCTRUNK 2 F1 1 17 NE1 1 NE4 17
Line Board 17-SL64 Ethernet Board 15-EGT2
PORT1
VCTRUNK 1
F3 Line Board 1-SLQ64 Line Board 17-SLQ64 Ethernet Board 4-EGSH VCTRUNK
OptiX OSN 8800
OptiX OSN 3500

In this example, the convergence node NE1 is configured with an EGSH board that supports the IEEE 802.1d bridge, thus implementing EPLAN services wherein user VLANs are not limited. The access nodes NE2 and NE4 are configured with a EGT2 board each. The EPL services are configured to be transparently transmitted from NE2 and NE4 to NE1.

The Ethernet services of the convergence node are received from an external port, forwarded to an internal port through Layer 2 switching, encapsulated, and transparently transmitted on the SDH network. In this manner, the node communicates with a remote node. Figure 10-39 shows the signal flow of the EPLAN services (IEEE 802.1d bridge) and the timeslot allocation to the EPLAN services (IEEE 802.1d bridge).
Issue 02 (2011-10-31)
408
Figure 10-39 Signal flow of and timeslot allocation

NE2:EGT2 NE1:EGSH
VCTRUNK1
VC C 4:V 4-1
PORT1
User F2
PORT1 User F1
VC4-xv:VC4-1 VCTRUNK2 VC4-xv:VC4-2
VB1
V C4 :VC 4-
NE4:EGT2
1
PORT1
User F3
SDH
The Ethernet LAN services of user F occupy the first VC-4 (VC4:VC4-1) on the SDH link between NE1 and NE2 and the first VC-4 (VC4:VC4-1) on the SDH link between NE1 and NE4. The Ethernet LAN services between NE1 and NE2 are added and dropped by using the first VC-4 (VC4-xv:VC4-1) on the EGSH board of NE1 and the first VC-4 (VC4xv:VC4-1) on the EGT2 board of NE2. The Ethernet LAN services between NE1 and NE4 are added and dropped by using the second VC-4 (VC4-xv:VC4-2) on the EGSH board of NE1 and the first VC-4 (VC4xv:VC4-1) on the EGT2 board of NE4.
Table 10-35 Parameters of the external ports of the Ethernet boards Parameter Board Port Enabled/Disabled Working Mode Maximum Frame Length Entry Detection TAG Port Type NE1 EGSH PORT1 Enabled 1000M Full-Duplex 1522 Enabled Tag Aware UNI NE2 EGT2 PORT1 Enabled 1000M Full-Duplex 1522 NE4 EGT2 PORT1 Enabled 1000M Full-Duplex 1522 -
Table 10-36 Parameters of the internal ports of the Ethernet boards Parameter Board
Issue 02 (2011-10-31)
NE1 EGSH
NE2 EGT2
NE4 EGT2
409
Parameter Port Mapping Protocol Entry Detection TAG Bound Path Port Type
NE1 VCTRUNK1 GFP Enabled Tag Aware VC4-xv:VC4-1 UNI VCTRUNK2 GFP Enabled Tag Aware VC4-xv:VC4-2 UNI
Table 10-37 Parameters of Ethernet LAN services (IEEE 802.1d bridge) Parameter Board VB Name Bridge Type Bridge Switch Mode Bridge Learning Mode Ingress Filter VB Mount Port Hub/Spoke PORT1 VCTRUNK1 VCTRUNK2 Ethernet LAN Service of NE1 EGSH VB1 IEEE 802.1d SVL/Ingress Filter Disable SVL Disabled PORT1, VCTRUNK1, VCTRUNK2 Hub Spoke Spoke

At the convergence node NE1, you need to create an EPLAN service (IEEE 802.1d bridge). At the access nodes NE2 and NE4, you need to configure only transparent transmission EPL services.
Prerequisite
The Creating a Network task must be complete. You must be familiar with EPLAN Service Configuration Process.
Issue 02 (2011-10-31)
410
Procedure
Step 1 Configure the EPLAN services for user F1, user F2, and user F3 on NE1. 1. Configure the attributes of the external port (PORT1 of the EGSH board) used by the service of user F1. l In the NE Explorer, select the EGSH board and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. l Select External Port. l Click the Basic Attributes tab. After setting the parameters, click Apply. Then, click Close in the Operation Result dialog box that is displayed. Parame ter Enabled / Disable d Workin g Mode Value in This Example PORT1: Enabled Description In this example, PORT1 carries the services and Enabled/Disabled is set to Enabled for PORT1. The Ethernet service access equipment of user F1 supports the 1000M full-duplex mode. In this example, Working Mode is set to Auto-Negotiation. Generally, this parameter adopts the default value 1522.
PORT1: 1000M FullDuplex
PORT1: 1522
PORT1: Non-Loopback
PORT1: Non-Loopback
l Click the Flow Control tab. The parameters in the Flow Control tab page adopt the default values. l Click the TAG Attributes tab. After setting the parameters, click Apply. Then, click Close in the Operation Result dialog box that is displayed. Parame ter TAG Value in This Example PORT1: Tag Aware Description The service access equipment of user F1 supports VLAN tags and the transmitted data frames carry VLAN tags. In this example, TAG is set to Tag Aware for PORT1. When TAG is set to Tag Aware, you need not set Default VLAN ID.
Default VLAN ID
Issue 02 (2011-10-31)
411
Parame ter VLAN Priority Entry Detectio n
Value in This Example PORT1: Enabled
Description When TAG is set to Tag Aware, you need not set VLAN Priority. The services of user F1 is EPLAN services. Hence, the entry detection function must be enabled to check whether the packets carry VLAN tags. In this example, Entry Detection is set to Enabled.
l Click the Network Attributes tab. After setting the parameters, click Apply. Then, click Close in the Operation Result dialog box that is displayed. Parame ter Port Type Value in This Example PORT1: UNI Description UNI indicates the user-network interface, namely, the interface of the service provider located near the user side. The UNI interface processes the tag attribute of IEEE 802.1qcompliant packets. That is, the UNI interface processes and identifies the VLAN information of the accessed user packets, according to the supported tag flags, namely Tag Aware, Access, and Hybrid.
l Click the Advanced Attributes tab. The parameters in the Advanced Attributes tab page adopt the default values. 2. Set the attributes of the internal ports (VCTRUNK1 and VCTRUNK2 of the EGSH board) used by the services of user F2 and user F3 on NE1. l Select Internal Port. l Click the TAG Attributes tab. After setting the parameters, click Apply. Then, click Close in the Operation Result dialog box that is displayed. Parame ter TAG Value in This Example VCTRUNK1: Tag Aware VCTRUNK2: Tag Aware Description The service access equipment of user F2 and user F3 supports VLAN tags and the transmitted data frames carry VLAN tags. In this example, TAG is set to Tag Aware for VCTRUNK1 and VCTRUNK2. When TAG is set to Tag Aware, you need not set Default VLAN ID. When TAG is set to Tag Aware, you need not set VLAN Priority.
Default VLAN ID VLAN Priority
Issue 02 (2011-10-31)
412
Value in This Example VCTRUNK1: Enabled VCTRUNK2: Enabled
Description The services of user F2 and user F3 are EPLAN services. Hence, the entry detection function must be enabled to check whether the packets carry VLAN tags. In this example, Entry Detection is set to Enabled.
l Click the Network Attributes tab. After setting the parameters, click Apply. Then, click Close in the Operation Result dialog box that is displayed. Parame ter Port Type Value in This Example VCTRUNK1: UNI VCTRUNK2: UNI Description UNI indicates the user-network interface, namely, the interface of the service provider located near the user side. The UNI interface processes the tag attribute of IEEE 802.1qcompliant packets. That is, the UNI interface processes and identifies the VLAN information of the accessed user packets, according to the supported tag flags, namely Tag Aware, Access, and Hybrid.
l Click the Encapsulation/Mapping tab. After setting the parameters, click Apply. Then, click Close in the Operation Result dialog box that is displayed. Parame ter Mappin g Protocol Value in This Example VCTRUNK1: GFP VCTRUNK2: GFP Description In this example, the EGSH board is used. This parameter adopts the default value GFP. Mapping Protocol of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value. In this example, this parameter adopts the default value Scrambling mode[X43+1]. Scramble of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value. In this example, this parameter adopts the default value FCS32. Check Field Length of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value.
Scrambl e
VCTRUNK1: Scrambling mode[X43 +1] VCTRUNK2: Scrambling mode[X43 +1]
Check Field Length
Issue 02 (2011-10-31)
413
Parame ter FCS Calculat ed Bit Sequenc e Extensi on Header Option
Value in This Example VCTRUNK1: Big endian VCTRUNK2: Big endian
Description When Mapping Protocol is set to GFP, FCS Calculated Bit Sequence is set to Big endian. FCS Calculated Bit Sequence of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value. When Mapping Protocol is set to GFP, this parameter is valid and adopts the default value No. Extension Header Option of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value.
l This operation is optional. Click the LCAS tab. After setting the parameters, click Apply. Then, click Close in the Operation Result dialog box that is displayed. Parame ter Enablin g LCAS LCAS Mode Value in This Example VCTRUNK1: Enabled VCTRUNK2: Enabled VCTRUNK1: Huawei Mode VCTRUNK2: Huawei Mode HO Time (ms) WTR Time(s) TSD VCTRUNK1: 2000 VCTRUNK2: 2000 Description In this example, the LCAS function is enabled. In this example, this parameter adopts the default value Huawei Mode. When Huawei equipment is used at both ends, LCAS Mode of the equipment at both ends is set to Huawei Mode. In this example, this parameter adopts the default value 2000. This parameter can also be set according to the requirement of the user. In this example, this parameter adopts the default value 300. This parameter can also be set according to the requirement of the user. In this example, the TSD function is disabled. The LCAS does not check the B3 bit error or BIP status of the VCTRUNK members.
VCTRUNK1: 300 VCTRUNK2: 300 VCTRUNK1: Disabled VCTRUNK2: Disabled
l Click the Bound Path tab. Click the Configuration button. Set the following parameters in the Bound Path Configuration dialog box that is displayed. Click and then click Apply. Click Yes in the Hint dialog box that is displayed. Click Close in the Operation Result dialog box that is displayed.
Issue 02 (2011-10-31)
414
User
Parameter
Value in This Example VCTRUN K1 VC4-xv
Description
User F2
Configurabl e Ports Avail able Boun d Paths Lev el Ser vic e Dir ecti on Av aila ble Res our ces
VCTRUNK1 of the EGSH board is used by the service of user F2. The service of user F2 uses a 100 Mbit/s bandwidth. Hence, one VC-4 needs to be bound. The service of user F2 is a bidirectional service.
Bidirectio nal
VC4-1
User F3
Configurabl e Ports Avail able Boun d Paths Lev el Ser vic e Dir ecti on Av aila ble Res our ces
VCTRUN K2 VC4-xv
VCTRUNK2 of the EGSH board is used by the service of user F3. The service of user F3 uses a 100 Mbit/s bandwidth. Hence, one VC-4 needs to be bound. The service of user F3 is a bidirectional service.
Bidirectio nal
VC4-2
l Click the Advanced Attributes tab. The parameters in the Advanced Attributes tab page adopt the default values. 3. Create a bridge for the EGSH board on NE1. l In the NE Explorer, select the EGSH board and then choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. l Click New.
Issue 02 (2011-10-31)
415
l Set the parameters in the Create Ethernet LAN Service dialog box that is displayed. Click Apply. Then, the Operation Result dialog box is displayed. Click Close. Parameter Value in This Example VB1 Description
VB Name
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. The IEEE 802.1d MAC bridge learns and forwards the packets according to 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 need not be isolated. When the bridge adopts the SVL learning mode, all the VLANs share the same MAC address table. That is, the bridge learns and forwards the packets according to the MAC addresses 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. -
VB Type
802.1d
Bridge Switch Mode
SVL/Ingress Filter Disable
Bridge Learning Mode Ingress Filter MAC Address Self-learning
SVL
Disabled Enabled
The IEEE 802.1d MAC bridge does not detect the VLAN tags of the received packets. When MAC Address Self-learning is set to Enabled, the bridge can learn the MAC address.
l Click Configure Mount. l Select PORT1, VCTRUNK1, and VCTRUNK2 in the Service Mount Configuration dialog box that is displayed. Then, click l Click OK. l In the Create Ethernet LAN Service dialog box that is displayed, click OK. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. 4. Change the Hub/Spoke attribute of the port that is mounted to the bridge.
NOTE
If normal communication is required between user F2 and user F3, proceed to Step 1.5.
Issue 02 (2011-10-31)
416
l Select the created bridge and click the Service Mount tab. l Change the Hub/Spoke attribute of the port that is mounted to the bridge. After setting the parameters, click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. Parameter Value in This Example PORT1: Hub VCTRUNK 1: Spoke VCTRUNK 2: Spoke Description
Hub/Spoke
If user F1 needs to communicate with user F2 and user F3, Hub/Spoke of PORT1 that accesses the services of user F1 is set to Hub. A port of the Hub attribute can communicate with a port of the Spoke or Hub attribute. If user F2 need not communicate with user F3, set the two VCTRUNKs that access the services of users F2 and F3 to Spoke. Ports of the Spoke attribute cannot communicate with each other.
5.
Configure the cross-connections from the Ethernet services to the SDH links for user F2 and user F3. l In the NE Explorer, select NE1 and then choose Configuration > SDH Service Configuration from the Function Tree. Click . l Click Create on the lower-right pane to display the Create SDH Service dialog box. Set the parameters that are required. Click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. User Paramete r Level Value in This Example VC4 Description
User F2
The timeslot bound with the service of user F2 is at the VC-4 level. The service level must be consistent with the level of the paths bound with the VCTRUNK. The service of user F2 is a bidirectional service. When you create a bidirectional SDH service from an Ethernet board to a line board, it is recommended that you set the slot of the Ethernet board as the source slot. The value range of the source timeslots is consistent with the value of Available Resources, which is set for the paths bound with VCTRUNK1. In this example, the value of Available Resources is VC4-1.
Direction Source Slot
Bidirectiona l 4-EGSH-1 (SDH-1)
Issue 02 (2011-10-31)
417
User
Paramete r Sink Slot
Value in This Example 17SLQ64-1 (SDH-1) 1
Description
When you create a bidirectional SDH service from an Ethernet board to a line board, it is recommended that you set the slot of the line board as the sink slot. The value range of the sink timeslots can be the same as or different from the value range of the source timeslots. The number of sink timeslots, however, must be consistent with the number of source timeslots. -
Sink Timeslot Range(e.g. 1,3-6) Activate Immediate ly User F3 Level
Yes
VC4
The timeslot bound with the service of user F3 is at the VC-4 level. The service level must be consistent with the level of the paths bound with the VCTRUNK. The service of user F3 is a bidirectional service. When you create a bidirectional SDH service from an Ethernet board to a line board, it is recommended that you set the slot of the Ethernet board as the source slot. The value range of the source timeslots is consistent with the value of Available Resources, which is set for the paths bound with VCTRUNK2. In this example, the value of Available Resources is VC4-2. When you create a bidirectional SDH service from an Ethernet board to a line board, it is recommended that you set the slot of the line board as the sink slot. The value range of the sink timeslot can be the same as or different from the value range of the source timeslot. The number of source timeslots, however, must be the same as the number of source timeslots. -
Direction Source Slot
Bidirectiona l 4-EGSH-1 (SDH-1)
Source Timeslot Range(e.g. 1,3-6) Sink Slot
1-SLQ64-1 (SDH-1)
Sink Timeslot Range(e.g. 1,3-6) Activate Immediate ly
Yes
Issue 02 (2011-10-31)
418

NOTE
The Ethernet services of NE2 and NE4 are point-to-point transparent transmission EPL services. See Configuration Guide(on a SDH Network) to set the parameters.
Step 3 Check whether the services are configured correctly. For the operation procedures, see Testing Ethernet Service Paths. l Before testing the service connectivity between headquarters F1 and branch F2, set TAG to Access and Default VLAN ID to 1 for PORT1 and VCTRUNK1 of the EGSH board. l Before testing the service connectivity between headquarters F1 and branch F3, set TAG to Access and Default VLAN ID to 1 for PORT1 and VCTRUNK2 of the EGSH board.
NOTE
10.17 Configuration Example: Configuring EVPLAN Services (IEEE 802.1q Bridge) on a SDH Network
The EVPLAN service (IEEE 802.1q bridge) provides a LAN solution for multipoint-tomultipoint convergence. This service is applicable where the user-side data communication equipment, which is connected to the transmission network, does not support VLAN tags or where the VLAN planning cannot be disclosed to the network operator.

The convergence node needs to exchange Ethernet services with two access nodes at Layer 2. LAN services of two users need to be isolated.
Service Requirement
On the network as shown in Figure 10-40, the service requirements are as follows: l l l
Issue 02 (2011-10-31)
Three branches (G1, G2, and G3) of user G are located at NE1, NE2, and NE4 respectively. A 100 Mbit/s bandwidth is required. G2 and G3 need not communicate with each other. Three branches (H1, H2, and H3) of user H are located at NE1, NE2, and NE4 respectively. A 100 Mbit/s bandwidth is required. The services of user G must be isolated from the services of user H.
The Ethernet equipment of user G and user H provides 1000 Mbit/s Ethernet optical ports that work in 1000M full-duplex mode and do not support VLAN tags.
Figure 10-40 Networking diagram for configuring EVPLAN services (IEEE 802.1q bridge)
T2000 Line Board 1-JL64 Ethernet Board 15-EGT6 H2 PORT2 PORT1 G2 H1 17 PORT2 1 NE2
NE3
Line Board 17-JL64 Ethernet Board 15-EGT6 NE4 NE1 17 1 PORT1 PORT2 H3 PORT1 G3 G1
Line Board 1-SLQ64 Line Board 17-SLQ64 Ethernet Board 4-EGSH
VB1 VLAN 200 VCTRUNK3 PORT2
VCTRUNK4 VCTRUNK1
VB1 VLAN 100 VCTRUNK2 PORT1 VCTRUNK
OptiX OSN 8800
OptiX OSN 3500

In this example, the convergence node NE1 is configured with an EGSH board that supports the IEEE 802.1q bridge, thus implementing EVPLAN services wherein services of different users are isolated from each other. The access nodes NE2 and NE4 are configured with a EGT6 board each. The EPL services are configured to be transparently transmitted from NE2 and NE4 to NE1.
NOTE
The Ethernet boards are classified into the Ethernet transparent transmission boards and Ethernet switching boards, based on the type of the accessed services. The Ethernet transparent transmission boards support only EPL services whereas the Ethernet switching boards support EPL services, EVPL services, and Layer 2 switching. Hence, Ethernet switching boards are used more widely than Ethernet transparent transmission boards.
Issue 02 (2011-10-31)
420

The Ethernet services of the convergence node are received from an external port and tagged with the corresponding VLAN IDs. After the services are forwarded to an internal port through Layer 2 switching, the VLAN tags are stripped and then the services are transparently transmitted on the SDH network. In this manner, the node communicates with a remote node. Figure 10-41 shows the signal flow of the EVPLAN services (IEEE 802.1q bridge) and the timeslot allocation to the EVPLAN services (IEEE 802.1q bridge). Figure 10-41 Signal flow of and timeslot allocation
NE2:EGT6
VCTRUNK1
NE1:EGSH
VLAN 100
PORT1 User G1 VCTRUNK1 VC4-xv:VC4-1 VCTRUNK2 VC4-xv:VC4-2
VC 4:V
-1 C4
PORT1 User G2 PORT2 User H2
VC 4: VC
VC
2 4-
VLAN 200
PORT2 User H1
VCTRUNK3 VC4-xv:VC4-3 VCTRUNK4 VC4-xv:VC4-4

VC
4: VC
41
NE4:EGT6
VCTRUNK1
4:V C
4-2
VB1
SDH
PORT Strip VLAN Label
Data(User G) Data(User H)
VCTRUNK Add VLAN Label Strip VLAN Label

VLAN(100) VLAN(200)
The Ethernet LAN services of user G: Occupy the first VC-4 (VC4:VC4-1) on the SDH link between NE1 and NE2 and the first VC-4 (VC4:VC4-1) on the SDH link between NE1 and NE4. Are added and dropped by using the first VC-4 (VC4-xv:VC4-1) on the EGSH board of NE1 and the first VC-4 (VC4-xv:VC4-1) on the EGT6 board of NE2. Are added and dropped by using the second VC-4 (VC4-xv:VC4-2) on the EGSH board of NE1 and the first VC-4 (VC4-xv:VC4-1) on the EGT6 board of NE4.
The Ethernet LAN services of user H: Occupy the second VC-4 (VC4:VC4-2) on the SDH link between NE1 and NE2 and the second VC-4 (VC4:VC4-3) on the SDH link between NE1 and NE4. Are added and dropped by using the third VC-4 (VC4-xv:VC4-3) on the EGSH board of NE1 and the second VC-4 (VC4-xv:VC4-2) on the EGT6 board of NE2. Are added and dropped by using the fourth VC-4 (VC4-xv:VC4-4) on the EGSH board of NE1 and the second VC-4 (VC4-xv:VC4-2) on the EGT6 board of NE4.
Issue 02 (2011-10-31)
421
Table 10-38 Parameters of the external ports of the Ethernet boards Paramete r Board Port Enabled/ Disabled Working Mode Maximum Frame Length TAG Entry Detection Default VLAN ID VLAN Priority Port Type NE1 EGSH PORT1 Enabled 1000M FullDuplex 1522 PORT2 Enabled 1000M FullDuplex 1522 NE2 EGT6 PORT1 Enabled 1000M FullDuplex 1522 PORT2 Enabled 1000M FullDuplex 1522 NE4 EGT6 PORT1 Enabled 1000M FullDuplex 1522 PORT2 Enabled 1000M FullDuplex 1522
Table 10-39 Parameters of the internal ports of the Ethernet boards Param eter Board Port Mappin g Protoco l TAG Entry Detecti on NE1 EGSH VCTR UNK1 GFP VCTR UNK2 GFP VCTR UNK3 GFP VCTR UNK4 GFP NE2 EGT6 VCTR UNK1 GFP VCTR UNK2 GFP NE3 EGT6 VCTR UNK1 GFP VCTR UNK2 GFP
Access Enable d
Access Enable d
Access Enable d
Access Enable d
Issue 02 (2011-10-31)
422
Param eter Default VLAN ID VLAN Priority Bound Path Port Type
NE1 100 100 200 200
NE2 -
NE3 -
0 VC4xv:VC4 -1 UNI
0 VC4xv:VC4 -2 UNI
0 VC4xv:VC4 -3 UNI
0 VC4xv:VC4 -4 UNI
VC4xv:VC4 -1 -
VC4xv:VC4 -2 -
VC4xv:VC4 -1 -
VC4xv:VC4 -2 -
Table 10-40 Parameters of Ethernet LAN services (IEEE 802.1q bridge) Parameter Board VB Name Bridge Type Bridge Switch Mode Bridge Learning Mode Ingress Filter VB Mount Port VLAN Filtering VLAN Filtering VLAN ID Ethernet LAN Service of NE1 EGSH VB1 IEEE 802.1q IVL/Ingress Filter Enable IVL Enabled PORT1, PORT2, VCTRUNK1, VCTRUNK2, VCTRUNK3, VCTRUNK4 VLAN filtering table 1 100 VLAN filtering table 2 200 PORT2, VCTRUNK3, VCTRUNK4
Forwarding PORT1, VCTRUNK1, Physical Port VCTRUNK2 Hub/Spoke PORT1 PORT2 VCTRUNK 1 VCTRUNK 2 VCTRUNK 3 Hub Hub Spoke Spoke Hub
Issue 02 (2011-10-31)
423
Parameter VCTRUNK 4
Ethernet LAN Service of NE1 Hub

At the convergence node NE1, you need to create an EVPLAN service (IEEE 802.1q bridge) and a VLAN filtering table. At the access nodes NE2 and NE4, you need to configure transparent transmission EPL services only.
Prerequisite
The Creating a Network task must be complete. You must be familiar with 10.3.3 EPLAN Service Configuration Process.


Step 1 Configure the EVPLAN services for user G1, user G2, user G3, user H1, user H2, and user H3 on NE1. 1. Configure the attributes of the external ports (PORT1 and PORT2 of the EGSH board) used by the services of user G1 and user H1. l In the NE Explorer, select the EGSH board and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. l Select External Port. l Click the Basic Attributes tab. After setting the parameters, click Apply. Click Close in the Operation Result dialog box that is displayed. Parame ter Enabled / Disable d Workin g Mode Value in This Example PORT1: Enabled PORT2: Enabled Description In this example, PORT1 carries the services and Enabled/Disabled is set to Enabled for PORT1 and PORT2. In this example, the Ethernet service access equipment of user G1 and user H1 supports the 1000M full-duplex mode. Hence, Working Mode is set to 1000M FullDuplex for PORT1 and PORT2.
Issue 02 (2011-10-31)
424
Parame ter Maximu m Frame Length MAC Loopba ck PHY Loopba ck
Value in This Example PORT1: 1522 PORT2: 1522
Description Generally, this parameter adopts the default value 1522.
l Click the Flow Control tab. The parameters in the Flow Control tab page adopt the default values. l Click the TAG Attributes tab. After setting the parameters, click Apply. Then, click Close in the Operation Result dialog box that is displayed. Parame ter TAG Value in This Example PORT1: Access PORT2: Access Description The access equipment of user G1 and user H1 does not support VLAN tags. Hence, the Ethernet access equipment transmits only the packets without the VLAN tags. In this example, TAG is set to Access for PORT1 and PORT2. According to the plan, the VLAN ID is set to 100 on the transmission network side for the Ethernet services between user G1, user G2, and user G3. The VLAN ID is set to 200 on the transmission network side for the EVPLAN services between user H1, user H2, and user H3. In this manner, the services of different users are isolated. This parameter adopts the default value. The services of user G1 and user H1 are EVPLAN services. Hence, the entry detection function must be enabled to check whether the packets carry VLAN tags. In this example, Entry Detection is set to Enabled.
Default VLAN ID
PORT1: 100 PORT2: 200
VLAN Priority Entry Detectio n
PORT1: Enabled PORT2: Enabled
l Click the Network Attributes tab. After setting the parameters, click Apply. Then, click Close in the Operation Result dialog box that is displayed.
Issue 02 (2011-10-31)
425
Parame ter Port Type
Value in This Example PORT1: UNI PORT2: UNI
Description UNI indicates the user-network interface, namely, the interface of the service provider located near the user side. The UNI interface processes the tag attribute of IEEE 802.1qcompliant packets. That is, the UNI interface processes and identifies the VLAN information of the accessed user packets, according to the supported tag flags, namely Tag Aware, Access, and Hybrid.
l Click the Advanced Attributes tab. The parameters in the Advanced Attributes tab page adopt the default values. 2. Set the attributes of the internal ports (VCTRUNK1, VCTRUNK2, VCTRUNK3, and VCTRUNK4 of the EGSH board) used by the services of user G2, user G3, user H2, and user H3 on NE1. l Select Internal Port. l Click the TAG Attributes tab. After setting the parameters, click Apply. Then, click Close in the Operation Result dialog box that is displayed. Parame ter TAG Value in This Example VCTRUNK1: Access VCTRUNK2: Access VCTRUNK3: Access VCTRUNK4: Access Default VLAN ID VCTRUNK1: 100 VCTRUNK2: 100 VCTRUNK3: 200 VCTRUNK4: 200 Description The service access equipment of user G2, user G3, user H2, and user H3 supports VLAN tags and the transmitted data frames do not carry VLAN tags. In this example, TAG is set to Access for VCTRUNK1VCTRUNK4. According to the plan, the VLAN ID is set to 100 on the transmission network side for the EVPLAN services between user G1, user G2, and user G3. The VLAN ID is set to 200 on the transmission network side for the EVPLAN services between user H1, user H2, and user H3. In this manner, the services of different users are isolated. This parameter adopts the default value.
VLAN Priority
VCTRUNK1: 0 VCTRUNK2: 0 VCTRUNK3: 0 VCTRUNK4: 0
Issue 02 (2011-10-31)
426
Value in This Example VCTRUNK1: Enabled VCTRUNK2: Enabled VCTRUNK3: Enabled VCTRUNK4: Enabled
Description The services of user G2, user G3, user H2, and user H3 are EVPLAN services. Hence, the entry detection function must be enabled to check whether the packets carry VLAN tags. In this example, Entry Detection is set to Enabled.
l Click the Network Attributes tab. After setting the parameters, click Apply. Then, click Close in the Operation Result dialog box that is displayed. Parame ter Port Type Value in This Example VCTRUNK1: UNI VCTRUNK2: UNI VCTRUNK3: UNI VCTRUNK4: UNI Description UNI indicates the user-network interface, namely, the interface of the service provider located near the user side. The UNI interface processes the tag attribute of IEEE 802.1qcompliant packets. That is, the UNI interface processes and identifies the VLAN information of the accessed user packets, according to the supported tag flags, namely Tag Aware, Access, and Hybrid.
l Click the Encapsulation/Mapping tab. After setting the parameters, click Apply. Then, click Close in the Operation Result dialog box that is displayed. Parame ter Mappin g Protocol Value in This Example VCTRUNK1: GFP VCTRUNK2: GFP VCTRUNK3: GFP VCTRUNK4: GFP Scrambl e VCTRUNK1: Scrambling mode[X43 +1] VCTRUNK2: Scrambling mode[X43 +1] VCTRUNK3: Scrambling mode[X43 +1] VCTRUNK4: Scrambling mode[X43 +1]
Description In this example, the EGSH board is used. This parameter adopts the default value GFP. Mapping Protocol of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value. In this example, this parameter adopts the default value Scrambling mode[X43+1]. Scramble of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value.
Parame ter Check Field Length
Value in This Example VCTRUNK1: FCS32 VCTRUNK2: FCS32 VCTRUNK3: FCS32 VCTRUNK4: FCS32
Description In this example, this parameter adopts the default value FCS32. Check Field Length of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value. When Mapping Protocol is set to GFP, FCS Calculated Bit Sequence is set to Big endian. FCS Calculated Bit Sequence of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value. When Mapping Protocol is set to GFP, this parameter is valid and adopts the default value No. Extension Header Option of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value.
VCTRUNK1: Big endian VCTRUNK2: Big endian VCTRUNK3: Big endian VCTRUNK4: Big endian VCTRUNK1: No VCTRUNK2: No VCTRUNK3: No VCTRUNK4: No
l This operation is optional. Click the LCAS tab. After setting the parameters, click Apply. Then, click Close in the Operation Result dialog box that is displayed. Parame ter Enablin g LCAS Value in This Example VCTRUNK1: Enabled VCTRUNK2: Enabled VCTRUNK3: Enabled VCTRUNK4: Enabled LCAS Mode VCTRUNK1: Huawei Mode VCTRUNK2: Huawei Mode VCTRUNK3: Huawei Mode VCTRUNK4: Huawei Mode HO Time (ms) VCTRUNK1: 2000 VCTRUNK2: 2000 VCTRUNK3: 2000 VCTRUNK4: 2000 In this example, this parameter adopts the default value 2000. This parameter can also be set according to the requirement of the user. In this example, this parameter adopts the default value Huawei Mode. When Huawei equipment is used at both ends, LCAS Mode of the equipment at both ends is set to Huawei Mode. Description In this example, the LCAS function is enabled.
Issue 02 (2011-10-31)
428
Parame ter WTR Time(s)
Value in This Example VCTRUNK1: 300 VCTRUNK2: 300 VCTRUNK3: 300 VCTRUNK4: 300
Description In this example, this parameter adopts the default value 300. This parameter can also be set according to the requirement of the user.
TSD
VCTRUNK1: Disabled VCTRUNK2: Disabled VCTRUNK3: Disabled VCTRUNK4: Disabled
In this example, the TSD function is disabled. The LCAS does not check the B3 bit error or BIP status of the VCTRUNK members.
l Click the Bound Path tab. Click the Configuration button. Set the following parameters in the Bound Path Configuration dialog box that is displayed. Click and then click Apply. Click Yes in the Hint dialog box that is displayed. Click Close in the Operation Result dialog box that is displayed. User Parameter Value in This Example VCTRUN K1 VC4-xv Description
User G2
Configurabl e Ports Avai lable Bou nd Path s Lev el Ser vice Dire ctio n Ava ilabl e Res ourc es
As shown in Figure 10-41, VCTRUNK1 of the EGSH board is used by the service of user G2. The service of user G2 uses a 100 Mbit/s bandwidth. Hence, one VC-4 needs to be bound. The service of user G2 is a bidirectional service.
Bidirection al
VC4-1
User G3
Configurabl e Ports Avai lable Bou nd Lev el
VCTRUN K2 VC4-xv
As shown in Figure 10-41, VCTRUNK2 of the EGSH board is used by the service of user G3. The service of user G3 uses a 100 Mbit/s bandwidth. Hence, one VC-4 needs to be bound.
Issue 02 (2011-10-31)
429
User
Parameter
Value in This Example Bidirection al
Description
Path s
Ser vice Dire ctio n Ava ilabl e Res ourc es
The service of user G3 is a bidirectional service.
VC4-2
User H2
Configurabl e Ports Avai lable Bou nd Path s Lev el Ser vice Dire ctio n Ava ilabl e Res ourc es
VCTRUN K3 VC4-xv
As shown in Figure 10-41, VCTRUNK3 of the EGSH board is used by the service of user H2. The service of user H2 uses a 100 Mbit/s bandwidth. Hence, one VC-4 needs to be bound. The service of user H2 is a bidirectional service.
Bidirection al
VC4-3
User H3
Configurabl e Ports Avai lable Bou nd Path s Lev el Ser vice Dire ctio n
VCTRUN K4 VC4-xv
As shown in Figure 10-41, VCTRUNK4 of the EGSH board is used by the service of user H3. The service of user H3 uses a 100 Mbit/s bandwidth. Hence, one VC-4 needs to be bound. The service of user H3 is a bidirectional service.
Bidirection al
Issue 02 (2011-10-31)
430
User
Parameter
Description
Ava ilabl e Res ourc es
l Click the Advanced Attributes tab. The parameters in the Advanced Attributes tab page adopt the default values. 3. Create a bridge for the EGSH board on NE1. l In the NE Explorer, select the EGSH board and then choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. l Click New. l Set the parameters in the Create Ethernet LAN Service dialog box that is displayed. Parameter Value in This Example VB1 Description
VB Name
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. 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. When Bridge Learning Mode is set to IVL, 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. -
VB Type
802.1q
Bridge Switch Mode
IVL
Enabled Enabled
l Click Configure Mount.

l In Available Mounted Ports, select PORT1, PORT2, VCTRUNK1, VCTRUNK2, VCTRUNK3, and VCTRUNK4. Then, click . l Click OK. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. ClickClose. l In the Create Ethernet LAN Service dialog box that is displayed, click OK. 4. Create a VLAN filtering table. l Select the created bridge and click the VLAN Filtering tab. l Click New. l Create the VLAN filtering table for user G1, user G2, and user G3 in the Create VLAN dialog box that is displayed. Parameter Value in This Example 100 Description
VLAN ID
According to the plan, the VLAN ID is set to 100 on the transmission network side for the EVPLAN services between user G1, user G2, and user G3.
l In Available Forwarding Ports, select PORT1, VCTRUNK1, and VCTRUNK2. Click . Then, click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. ClickClose. l Create the VLAN filtering table for user H1, user H2, and user H3. Parameter Value in This Example 200 Description
VLAN ID
According to the plan, the VLAN ID is set to 200 on the transmission network side for the EVPLAN services between user H1, user H2, and user H3.
l In Available Forwarding Ports, select PORT2, VCTRUNK3, and VCTRUNK4. Click . Then, click OK. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. 5. Change the Hub/Spoke attribute of the port that is mounted to the bridge. l Select the created bridge and click the Service Mount tab. l Change the Hub/Spoke attribute of the port that is mounted to the bridge. After setting the parameters, click Apply. The Operation Result dialog box is displayed, indicating that the operation is successful. ClickClose.
Issue 02 (2011-10-31)
432
Parameter Hub/Spoke
Value in This Example PORT1: Hub VCTRUNK1: Spoke VCTRUNK2: Spoke PORT2: Hub VCTRUNK3: Hub VCTRUNK4: Hub
Description If user G2 need not communicate with user G3, set VCTRUNK1 and VCTRUNK2 that access the services of user G2 and user G3 to Spoke. Ports of the Spoke attribute cannot communicate with each other. A port of the Hub attribute can communicate with a port of the Spoke or Hub attribute.
6.
Configure the cross-connections from the Ethernet services to the SDH links for user G2, user G3, user H2, and user H3. l In the NE Explorer, select NE1 and then choose Configuration > SDH Service Configuration from the Function Tree. Click . l Click Create on the lower-right pane to display the Create SDH Service dialog box. Set the parameters that are required. Click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. User Paramete r Level Value in This Example VC4 Description
User G2
The timeslot bound with the service of user G2 is at the VC-4 level. The service level must be consistent with the level of the paths bound with the VCTRUNK. The service of user G2 is a bidirectional service. When you create a bidirectional SDH service from an Ethernet board to a line board, it is recommended that you set the slot of the Ethernet board as the source slot. The value range of the source timeslots is consistent with the value of Available Resources, which is set for the paths bound with VCTRUNK1. In this example, the value of Available Resources is VC4-1. When you create a bidirectional SDH service from an Ethernet board to a line board, it is recommended that you set the slot of the line board as the sink slot.
Direction
Bidirectiona l
17SLQ64-1 (SDH-1)
Issue 02 (2011-10-31)
433
User
Paramete r Sink Timeslot Range(e.g. 1,3-6)
Description
The value range of the sink timeslots can be the same as or different from the value range of the source timeslots. The number of sink timeslots, however, must be consistent with the number of source timeslots. -
Activate Immediatel y User G3 Level
Yes
VC4
The timeslot bound with the service of user G3 is at the VC-4 level. The service level must be consistent with the level of the paths bound with the VCTRUNK. The service of user G3 is a bidirectional service. When you create a bidirectional SDH service from an Ethernet board to a line board, it is recommended that you set the slot of the Ethernet board as the source slot. The value range of the source timeslots is consistent with the value of Available Resources, which is set for the paths bound with VCTRUNK2. In this example, the value of Available Resources is VC4-2. When you create a bidirectional SDH service from an Ethernet board to a line board, it is recommended that you set the slot of the line board as the sink slot. The value range of the sink timeslot can be the same as or different from the value range of the source timeslot. The number of source timeslots, however, must be the same as the number of sink timeslots. -
Direction
Bidirectiona l
1-SLQ64-1 (SDH-1)
Sink Timeslot Range(e.g. 1,3-6) Activate Immediatel y User H2 Level
Yes
VC4
The timeslot bound with the service of user H2 is at the VC-12 level. The service level must be consistent with the level of the paths bound with the VCTRUNK.
Issue 02 (2011-10-31)
434
User
Paramete r Direction
Value in This Example Bidirectiona l
Description
The service of user H2 is a bidirectional service. When you create a bidirectional SDH service from an Ethernet board to a line board, it is recommended that you set the slot of the Ethernet board as the source slot. The value range of the source timeslots is consistent with the value of Available Resources, which is set for the paths bound with VCTRUNK3. In this example, the value of Available Resources is VC4-3. When you create a bidirectional SDH service from an Ethernet board to a line board, it is recommended that you set the slot of the line board as the sink slot. The value range of the sink timeslot can be the same as or different from the value range of the source timeslot. The number of source timeslots, however, must be the same as the number of source timeslots. -
171SLQ64-1 (SDH-1) 2
Sink Timeslot Range(e.g. 1,3-6) Activate Immediatel y User H3 Level
Yes
VC4
The timeslot bound with the service of user H3 is at the VC-12 level. The service level must be consistent with the level of the paths bound with the VCTRUNK. The service of user H3 is a bidirectional service. When you create a bidirectional SDH service from an Ethernet board to a line board, it is recommended that you set the slot of the Ethernet board as the source slot. The value range of the source timeslots is consistent with the value of Available Resources, which is set for the paths bound with VCTRUNK4. In this example, the value of Available Resources is VC4-4.
Direction
Bidirectiona l
Issue 02 (2011-10-31)
435
User
Paramete r Sink Slot
Value in This Example 1-SLQ64-1 (SDH-1)
Description
When you create a bidirectional SDH service from an Ethernet board to a line board, it is recommended that you set the slot of the line board as the sink slot. The value range of the sink timeslot can be the same as or different from the value range of the source timeslot. The number of source timeslots, however, must be the same as the number of source timeslots. -
Sink Timeslot Range(e.g. 1,3-6) Activate Immediatel y
Yes

NOTE
Step 3 Check whether the services are configured correctly. For the operation procedures, see Testing Ethernet Service Paths. Step 4 Enable the performance monitoring function of the NEs. For details, see Setting Performance Monitoring Parameters of an NE. Step 5 Back up the configuration data of the NEs. Second methods are available for the backup. Option Description
10.18 Configuration Example: Configuring EVPLAN Services (IEEE 802.1ad Bridge) on a SDH Network
The QinQ technology provides an economical and easy solution for Layer 2 virtual private networks (VPNs). The IEEE 802.1ad bridge uses the QinQ technology to provide the VPN solution, thus facilitating the identifying, differentiating, and grooming of EVPLAN services.

A network operator requires that the voice over IP (VoIP) and high speed Internet (HSI) services sent to the transmission network be uniformly labeled and groomed at the convergence node.
Service Requirement
As shown in Figure 10-42, the transmission network is required to transmit the VoIP and HSI services. The service requirements are as follows: l The VoIP services of user M and user N are accessed into the transmission network at NE2 and NE4 respectively and into the VoIP server at the convergence node NE1. A 100 Mbit/ s bandwidth is required. The HSI services of user M and user N are accessed into the transmission network at NE2 and NE4 respectively and into the HSI server at the convergence node NE1. A 150 Mbit/ s bandwidth is required. The VoIP services need to be isolated from the HSI services. The data communication equipment of user M and user N provides 1000 Mbit/s Ethernet optical ports that work in 1000M full-duplex mode and support VLAN tags. C-VLAN ID of the VoIP services: 10 C-VLAN ID of the HSI services: 20
NOTE
l l
The application scenarios where one branch needs to communicate with other branches are as follows: l User M needs to communicate with user N. l User M need not communicate with user N. If user M and user N need to communicate with each other, skip 10.18.3 Configuration Process.
The operator requires that all services received from the user side should be uniformly labeled and groomed through planned S-VLANs. l l S-VLAN ID of the VoIP services: 100 S-VLAN ID of the HSI services: 200
Issue 02 (2011-10-31)
437
Figure 10-42 Networking diagram for configuring EVPLAN services (IEEE 802.1ad bridge)
NE3
Line Board 1-SL64 Ethernet Board 15-EGT2 User M PORT1 1 VoIP 17 NE2 NE1 1 NE4 17 HSI
Line Board 17-SL64 Ethernet Board 15-EGT2 PORT1 User N
Service C-VLAN 10 VoIP 20 HSI
Service C-VLAN VoIP 10 HSI 20
PORT1 PORT2 Line Board 1-SLQ64 Line Board u 17-SLQ64 Ethernet Board 4-EGSH
VB1 VCTRUNK1
S-VLAN 100 PORT1
VB1
VCTRUNK2 VCTRUNK1
S-VLAN 200 VCTRUNK2 PORT2 VCTRUNK OptiX OSN 8800
OptiX OSN 3500

In this example, the convergence node NE1 is configured with an EGSH board that supports the IEEE 802.1ad bridge, thus implementing the EVPLAN services in which VoIP data is isolated from HSI data. l The VoIP services tagged with the C-VLAN ID of 10 from NE2 and NE4 are further tagged with the S-VLAN ID of 100 when they arrive at the IEEE 802.1ad bridge of NE1. Then, the services are forwarded to the VoIP server through Layer 2 switching. The HSI services tagged with the C-VLAN ID of 20 from NE2 and NE4 are further tagged with the S-VLAN ID of 200 when they arrive at the IEEE 802.1ad bridge of NE1. Then, the services are forwarded to the HSI server through Layer 2 switching.
The access nodes NE2 and NE4 are configured with a EGT2 board each. The EPL services are configured to be transparently transmitted from NE2 and NE4 to NE1.

The services of user M and user N are transmitted from the access nodes NE2 and NE4 respectively to the convergence node NE1 through the Ethernet transparent transmission boards. The VoIP and HSI services carrying different C-VLAN IDs are tagged with different S-VLAN IDs. The service data is isolated and exchanged at Layer 2 through S-VLAN filtering.
Figure 10-43 shows the signal flow of the EVPLAN services (IEEE 802.1ad bridge) and the timeslot allocation to the EVPLAN services (IEEE 802.1ad bridge). Figure 10-43 Signal flow of and timeslot allocation
NE1:EGSH
SVLAN 100
VoIP Server PORT1 VCTRUNK1 VC4-xv:VC4-1 VC4-xv:VC4-2
-1 :VC4 VC4 C4-2 :V VC4
NE2:EGT2
VCTRUNK1 VC4-xv:VC4-1 VC4-xv:VC4-2
PORT1 User M
SVLAN 200
HSI Server PORT2
VC4:V VC4:V C4-1 C4-2
NE4:EGT2
PORT1 User N
VB1
SDH
PORT Strip S-VLAN Label

Data(VoIP) Data(HSI)
VCTRUNK Add S-VLAN Label Strip S-VLAN Label

S-VLAN(100) C-VLAN(10) S-VLAN(200) C-VLAN(20)
The EVPLAN services of user M: Occupy the first VC-4 (VC4:VC4-1) and second VC-4 (VC4:VC4-2) on the SDH link between NE1 and NE2. Are added and dropped by using the first VC-4 (VC4-xv:VC4-1) and second VC-4 (VC4-xv:VC4-2) on the EGSH board of NE1 and the first VC-4 (VC4-xv:VC4-1) and second VC-4 (VC4-xv:VC4-2) on the EGT2 board of NE2.
The EVPLAN services of user N: Occupy the third VC-4 (VC4:VC4-3) and fourth VC-4 (VC4:VC4-4) on the SDH link between NE1 and NE4. Are added and dropped by using the third VC-4 (VC4-xv:VC4-3) and fourth VC-4 (VC4-xv:VC4-4) on the EGSH board of NE1 and the first VC-4 (VC4-xv:VC4-1) and second VC-4 (VC4-xv:VC4-2) on the EGT2 board of NE4.
Table 10-41 Parameters of the external ports of the Ethernet boards Parameter Board Port Enabled/ Disabled Working Mode Maximum Frame Length
Issue 02 (2011-10-31)
NE1 EGSH PORT1 Enabled 1000M FullDuplex 1522 PORT2 Enabled 1000M FullDuplex 1522
NE2 EGT2 PORT1 Enabled 1000M FullDuplex 1522
NE4 EGT2 PORT1 Enabled 1000M FullDuplex 1522
439
Parameter Port Type
NE1 C-Aware C-Aware
NE2 -
NE4 -
Table 10-42 Parameters of the internal ports of the Ethernet boards Parameter Board Port Mapping Protocol Port Type Bound Path NE1 EGSH VCTRUNK1 GFP C-Aware VC4-xv:VC4-1, VC4-xv:VC4-2 VCTRUNK2 GFP C-Aware VC4-xv:VC4-3, VC4-xv:VC4-4 NE2 EGT2 VCTRUNK1 GFP VC4-xv:VC4-1, VC4-xv:VC4-2 NE3 EGT2 VCTRUNK1 GFP VC4-xv:VC4-1, VC4-xv:VC4-2
Table 10-43 Parameters of Ethernet LAN services (IEEE 802.1ad bridge) Parameter Board VB Name Bridge Type Bridge Switch Mode Bridge Learning Mode Ingress Filter Operation Type VB Port Mount Port C-VLAN S-VLAN VLAN Filterin g VLAN Filtering VLAN ID Ethernet LAN Service of NE1 EGSH VB1 802.1ad IVL/Ingress Filter Enable IVL Enabled Add S-VLAN base for Port and C-VLAN 1 PORT1 10 100 2 PORT2 20 200 3 VCTRUNK1 10 100 20 200 4 VCTRUNK2 10 100 20 200
VLAN filtering table 1 100
VLAN filtering table 2 200 PORT2, VCTRUNK1, VCTRUNK2
Forwarding PORT1, VCTRUNK1, Physical Port VCTRUNK2
Issue 02 (2011-10-31)
440
Parameter Hub/ Spoke PORT1 PORT2 VCTRUNK 1 VCTRUNK 2
Ethernet LAN Service of NE1 Hub Hub Spoke Spoke

At the convergence node NE1, you need to create an EVPLAN service (IEEE 802.1ad bridge) and an S-VLAN filtering table. At the access nodes NE2 and NE4, you need to configure transparent transmission EPL services only.
Prerequisite
The Creating a Network task must be complete.
The IEEE 802.1ad provider 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 tags. The IEEE 802.1ad provider bridge supports the following operation types: l l l l Adding the S-VLAN tag based on the port Adding the S-VLAN tag based on the port and C-VLAN Performing port mounting based on the port Performing port mounting based on the port and the S-VLAN
This topic describes the four operation types when Bridge Switch Mode of the IEEE 802.1ad provider bridge is set to IVL/Ingress Filter Enabled. l Adding the S-VLAN based on the port: The packets that enter the C-Aware port are added with the preset S-VLAN tags, and are forwarded in the bridge according to the S-VLAN filtering table. Before the packets leave the C-Aware port, the S-VLAN tags are stripped. Adding the S-VLAN tag based on the port and C-VLAN: The 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 relation between the C-VLAN tags and the S-VLAN tags of the packets. If the mapping relation 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 CAware port, the S-VLAN tags are stripped.
Issue 02 (2011-10-31)
441

NOTE
l A C-Aware port supports different C-VLAN tags being mapped into different S-VLAN tags, but does not support the same C-VLAN tag being mapping into multiple S-VLAN tags.
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. 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 l The port must be contained in the S-VLAN filtering table that is created by the user. 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-Aware 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-Aware port, the S-VLAN ID corresponding to the port is the S-VLAN ID that is set when the user mounts the port to the bridge. If the S-Aware port is mounted based on the port, the S-VLAN ID is considered to contain all the legal S-VLAN IDs.
Procedure
Step 1 Configure the EVPLAN service of NE1. 1. Set the attributes of the external ports (PORT1 and PORT2 of the EGSH board) used by the VoIP server and HSI server. l In the NE Explorer, select the EGSH board and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. l Select External Port. l Click the Basic Attributes tab. After setting the parameters, click Apply. Then, the Operation Result dialog box is displayed. Click Close. Parame ter Enabled / Disable d Workin g Mode Value in This Example PORT1: Enabled PORT2: Enabled Description In this example, PORT1 and PORT2 transmit the services and Enabled/Disabled is set to Enabled for PORT1 and PORT2. In this example, the VoIP server and HSI server support the 1000M full-duplex mode. Hence, Working Mode is set to 1000M FullDuplex for PORT1 and PORT2.
Issue 02 (2011-10-31)
442
Parame ter Maximu m Frame Length MAC Loopba ck PHY Loopba ck
Value in This Example PORT1: 1522 PORT2: 1522
Description Generally, this parameter adopts the default value 1522.
l Click the Flow Control tab. The parameters in the Flow Control tab page adopt the default values. l Click the Network Attributes tab. After setting the parameters, click Apply. Then, the Operation Result dialog box is displayed. Click Close. Parameter Port Type Value in This Example PORT1: C-Aware PORT2: C-Aware Description The C-Aware or S-Aware attribute must be selected for the port when you configure the IEEE 802.1ad bridge. The C-Aware port connects to the port on the client network, identifies and processes the packets that contain C-VLAN tags (namely, client tags). The S-Aware port connects to the port on the network side, identifies and processes the packets that contain S-VLAN tags (namely, service tags of the network operator).
l When Port Type is set to C-Aware or S-Aware, the parameters in the TAG Attributes tab page are invalid. Hence, The parameters in the TAG Attributes tab page need not be set. l Click the Advanced Attributes tab. The parameters in the Advanced Attributes tab page adopt the default values. 2. Set the attributes of the internal ports (VCTRUNK1 and VCTRUNK2 of the EGSH board) used by the services of user M and user N on NE1. l Select Internal Port. l Click the Network Attributes tab. After setting the parameters, click Apply. Then, the Operation Result dialog box is displayed. Click Close.
Issue 02 (2011-10-31)
443
Parame ter Port Type
Value in This Example VCTRUNK1: C-Aware VCTRUNK2: C-Aware
Description The C-Aware or S-Aware attribute must be selected for the port when you configure the IEEE 802.1ad bridge. The C-Aware port is connected to the network port of the user equipment, and identifies and processes the packets that carry the C-VLAN tags. The Saware port is used for connecting to the supplier network, and identifies and processes the packets that carry the S-VLAN tags.
l When Port Type is set to C-Aware or S-Aware, the parameters in the TAG Attributes tab page are invalid. Hence, The parameters in the TAG Attributes tab page need not be set. l Click the Encapsulation/Mapping tab. After setting the parameters, click Apply. Then, the Operation Result dialog box is displayed. Click Close. Parame ter Mappin g Protocol Value in This Example VCTRUNK1: GFP VCTRUNK2: GFP Description In this example, the EGSH board is used. This parameter adopts the default value GFP. Mapping Protocol of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value. In this example, this parameter adopts the default value Scrambling mode[X43+1]. Scramble of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value. In this example, this parameter adopts the default value FCS32. Check Field Length of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value. When Mapping Protocol is set to GFP, FCS Calculated Bit Sequence is set to Big endian. FCS Calculated Bit Sequence of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value.
Scrambl e
VCTRUNK1: Scrambling mode[X43 +1] VCTRUNK2: Scrambling mode[X43 +1]
Check Field Length
FCS Calculat ed Bit Sequenc e
Issue 02 (2011-10-31)
444
Parame ter Extensi on Header Option
Value in This Example VCTRUNK1: No VCTRUNK2: No
Description When Mapping Protocol is set to GFP, this parameter is valid and adopts the default value No. Extension Header Option of the VCTRUNKs on the Ethernet boards of the interconnected equipment at both ends must be set to the same value.
l This operation is optional. Click the LCAS tab. After setting the parameters, click Apply. Then, the Operation Result dialog box is displayed. Click Close. Parame ter Enablin g LCAS LCAS Mode Value in This Example VCTRUNK1: Enabled VCTRUNK2: Enabled VCTRUNK1: Huawei Mode VCTRUNK2: Huawei Mode HO Time (ms) WTR Time(s) TSD VCTRUNK1: 2000 VCTRUNK2: 2000 Description In this example, the LCAS function is enabled. In this example, this parameter adopts the default value Huawei Mode. When Huawei equipment is used at both ends, LCAS Mode of the equipment at both ends is set to Huawei Mode. In this example, this parameter adopts the default value 2000. This parameter can also be set according to the requirement of the user. In this example, this parameter adopts the default value 300. This parameter can also be set according to the requirement of the user. In this example, the TSD function is disabled. The LCAS does not check the B3 bit error or BIP status of the VCTRUNK members.
VCTRUNK1: 300 VCTRUNK2: 300 VCTRUNK1: Disabled VCTRUNK2: Disabled
l Click the Bound Path tab. Click the Configuration button. Set the parameters in the and then click Bound Path Configuration dialog box that is displayed. Click Apply. Click Yes in the Hint dialog box that is displayed. Click Close in the Operation Result that is displayed. User Parameter Value in This Example VCTRUN K1 Description
User M
Configurabl e Ports
VCTRUNK1 of the EGSH board is used by the service of user M.
Issue 02 (2011-10-31)
445
User
Parameter
Value in This Example VC4-xv
Description
Avail able Boun d Paths
Lev el Serv ice Dire ctio n Ava ilabl e Res ourc es
The service of user M uses a 200 Mbit/s bandwidth. Hence, two VC-4s need to be bound. The service of user M is a bidirectional service.
Bidirectio nal
VC4-1, VC4-2
User N
Configurabl e Ports Avail able Boun d Paths Lev el Serv ice Dire ctio n Ava ilabl e Res ourc es
VCTRUN K2 VC4-xv
VCTRUNK2 of the EGSH board is used by the service of user N. The service of user N uses a 200 Mbit/s bandwidth. Hence, two VC-4s need to be bound. The service of user N is a bidirectional service.
Bidirectio nal
VC4-3, VC4-4
l Click the Advanced Attributes tab. The parameters in the Advanced Attributes tab page adopt the default values. 3. Create a bridge for the EGSH board on NE1. l In the NE Explorer, select the EGSH board and then choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. l Click New. l Set the parameters in the Create Ethernet LAN Service dialog box that is displayed.
Issue 02 (2011-10-31)
446
Parameter
Value in This Example VB1
Description
VB Name
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. 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 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 S-VLAN IDs of the packets. -
VB Type
802.1ad
Bridge Switch Mode
IVL
Enabled Enabled
l Click Configure Mount. l Set the parameters in the Service Mount Configuration dialog box that is displayed. Click Add Mount Port and then click OK. Click Close in the Operation Result dialog box. Parameter Operation Type VB Port Mount Port C-VLAN S-VLAN Value in This Example Adding the S-VLAN tag based on the port and C-VLAN 1 PORT1 10 100 2 PORT2 20 200 3 VCTRUNK1 10 100 20 200 4 VCTRUNK2 10 100 20 200
The other parameters take the default values. l Click OK.
Issue 02 (2011-10-31)
447
l In the Create Ethernet LAN Service dialog box that is displayed, click OK. Click Close in the Operation Result dialog box that is displayed. 4. Create a VLAN filtering table. l Select the created bridge and click the VLAN Filtering tab. l Click New. l Create the VLAN filtering table of the VoIP service. Parameter Value in This Example 100 Description
VLAN ID
According to the plan, the VoIP service uses the SVLAN ID of 100.
l In Available Forwarding Ports, select PORT1, VCTRUNK1, and VCTRUNK2. Click . Then, click Apply. Click Close in the Operation Result that is displayed. l Create the VLAN filtering table of the HSI service. Parameter Value in This Example 200 Description
VLAN ID
According to the plan, the HSI service uses the SVLAN ID of 200.
l In Available Forwarding Ports, select PORT2, VCTRUNK1, and VCTRUNK2. Click . Then, click OK. Click Close in the Operation Result dialog box that is displayed. 5. Change the Hub/Spoke attribute of the port that is mounted to the bridge.
NOTE
If normal communication is required between user M and user N, proceed to Step 1.6.
l Select the created bridge and click the Service Mount tab. l Change the Hub/Spoke attribute of the port that is mounted to the bridge. Parameter Hub/Spoke Value in This Example PORT1: Hub PORT2: Hub VCTRUNK1: Spoke VCTRUNK2: Spoke Description User M and user N need not communicate with each other. In this case, set VCTRUNK1 and VCTRUNK2 that access the services of user M and user N to the Spoke attribute. Ports of the Spoke attribute cannot communicate with each other. A port of the Hub attribute can communicate with a port of the Spoke or Hub attribute.
6.
Configure the cross-connections from the Ethernet services to the SDH links for user M and user N.
Issue 02 (2011-10-31)
l In the NE Explorer, select NE1 and then choose Configuration > SDH Service Configuration from the Function Tree. Click . l Click Create on the lower-right pane to display the Create SDH Service dialog box. Set the parameters that are required. Click Apply. Then, click Close in the Operation Result dialog box that is displayed. User Paramete r Level Value in This Example VC4 Description
User M
The timeslot bound with the service of user M is at the VC-12 level. The service level must be consistent with the level of the paths bound with the VCTRUNK. The service of user M is a bidirectional service. When you create a bidirectional SDH service from an Ethernet board to a line board, it is recommended that you set the slot of the Ethernet board as the source slot. The value range of the source timeslots is consistent with the value of Available Resources, which is set for the paths bound with VCTRUNK1. In this example, the values of Available Resources are VC4-1 and VC4-2. When you create a bidirectional SDH service from an Ethernet board to a line board, it is recommended that you set the slot of the line board as the sink slot. The value range of the sink timeslots can be the same as or different from the value range of the source timeslots. The number of sink timeslots, however, must be consistent with the number of source timeslots. -
Direction
Bidirectiona l
1-2
Sink Slot
17SLQ64-1 (SDH-1) 1-2
Sink Timeslot Range(e.g. 1,3-6)
Activate Immediatel y User N Level
Yes
VC4
The timeslot bound with the service of user N is at the VC-12 level. The service level must be consistent with the level of the paths bound with the VCTRUNK. The service of user N is a bidirectional service.
Direction
Bidirectiona l
Issue 02 (2011-10-31)
449
User
Paramete r
Value in This Example
Description
When you create a bidirectional SDH service from an Ethernet board to a line board, it is recommended that you set the slot of the Ethernet board as the source slot. The value range of the source timeslots is consistent with the value of Available Resources, which is set for the paths bound with VCTRUNK2. In this example, the values of Available Resources are VC4-3 and VC4-4. When you create a bidirectional SDH service from an Ethernet board to a line board, it is recommended that you set the slot of the line board as the sink slot. The value range of the sink timeslot can be the same as or different from the value range of the source timeslot. The number of source timeslots, however, must be the same as the number of source timeslots. -
3-4
Sink Slot
1-SLQ64-1 (SDH-1)
Sink Timeslot Range(e.g. 1,3-6) Activate Immediatel y
1-2
Yes

NOTE
The Ethernet services of NE2 and NE4 are point-to-point transparent transmission EPL services. See Configuration Guide(on a SDH Network) to set the parameters.
Issue 02 (2011-10-31)
450
10.19 Configuration Example: Configuring EVPL and EVPLAN Services (IEEE 802.1q Bridge) on a SDH Network
The EGSH board supports the EVPL and EVPLAN services (IEEE 802.1q bridge) on a same port. Based on different VLANs, EVPL and EVPLAN services can be accessed through a same port, which is applicable to the scenario where the EVPL and EVPLAN users share the same port.

Based on different VLANs, EVPL and EVPLAN services can be accessed through a same port.
Service Requirement
On the network as shown Figure 10-44, the service requirements are as follows: l Three branches (G1, G2, and G3) of user G are located at NE1, NE2, and NE4 respectively. The branches need to form a LAN and share a 100 Mbit/s bandwidth. G2 and G3 need not communicate with each other. Two branches of user H are located at NE1 and NE2, and need to communicate with each other. The services of user G must be isolated from the services of user H. The Ethernet equipment of user G and user H provides 1000 Mbit/s Ethernet optical ports that work in 1000M full-duplex mode and do not support VLAN tags.
l l l
Issue 02 (2011-10-31)
451
Figure 10-44 Networking diagram for configuring EVPL and EVPLAN services
T2000 Line Board 1-JL64 Ethernet Board 15-EGT6 H2 PORT2 PORT1 G2 H1 17 PORT2 1 NE2
NE3
Line Board 17-JL64 Ethernet Board 15-EGT6 NE4 NE1 17 G3 1 PORT1 G1 PORT1
Line Board 1-SLQ64 Line Board 17-SLQ64 Ethernet Board 4-EGSH
VB1 VLAN 200 VCTRUNK3 PORT2 VCTRUNK4 VCTRUNK
OptiX OSN 8800
OptiX OSN 3500

In this example, the convergence node NE1 is configured with an EGSH board that supports the IEEE 802.1q, the access nodes NE2 and NE4 are configured with a EGT6 board each. When the data of user G is accessed into the transmission network, services of different users are isolated from each other by EGSH board on NE1. The EPL services are configured to be transparently transmitted from NE2 and NE4 to NE1 when the NE2 and NE4 are used as access nodes. When the data of user H is accessed into the transmission network, the VLAN ID of 200 is added to the data. When the data is transmitted out of the transmission network, the VLAN tag is stripped.

When the data of user E is accessed into the transmission network, the Ethernet services of the convergence node are received from an external port and tagged with the corresponding VLAN IDs. After the services are forwarded to an internal port through Layer 2 switching, the VLAN tags are stripped and then the services are transparently transmitted on the SDH network. In this manner, the node communicates with a remote node. The Ethernet services of user H are received
from the external port on an Ethernet board, tagged with different VLAN IDs, and then transmitted on the same VCTRUNK. In this manner, the services of different users are isolated from each other. After the data arrives at the sink node, the VLAN tags are stripped. Figure 10-45 shows the signal flow of the EVPL and EVPLAN Services (IEEE 802.1ad Bridge) and the timeslot allocation to the EVPL and EVPLAN Services (IEEE 802.1ad Bridge). Figure 10-45 Signal flow of and timeslot allocation
NE2:EGT6
VCTRUNK1
NE1:EGSH
VLAN 100
PORT1 User G1 VCTRUNK1 VC4-xv :VC4-1 VCTRUNK2 VC4-xv :VC4-2 PORT2 User H1
VC
VC 4:V C
4-1
VC4-xv :VC4-1 VCTRUNK2
VC
VC 4:
4-
VC4-xv :VC4-2
VCTRUNK3 VC4-xv :VC4-3
4:V C4 -1
NE4:EGT6
VCTRUNK1
VB1
VC4-xv :VC4-1
PORT1 User G3
SDH
PORT Strip VLAN Label
VCTRUNK Strip VLAN Label

Add VLAN Label

VLAN(100) VLAN(200) Data(User G) Data(User H)
The Ethernet LAN services of user G: Occupy the first VC-4 (VC4:VC4-1) on the SDH link between NE1 and NE2 and the first VC-4 (VC4:VC4-1) on the SDH link between NE1 and NE4. Are added and dropped by using the first VC-4 (VC4-xv:VC4-1) on the EGSH board of NE1 and the first VC-4 (VC4-xv:VC4-1) on the EGT6 board of NE2. Are added and dropped by using the second VC-4 (VC4-xv:VC4-2) on the EGSH board of NE1 and the first VC-4 (VC4-xv:VC4-1) on the EGT6 board of NE4.
The Ethernet services of user H Occupy the second VC-4 (VC4:VC4-2) on the SDH link between NE1 and NE2. Are added and dropped by using the third VC-4 (VC4-xv:VC4-3) on the EGSH board of NE1 and the second VC-4 (VC4-xv:VC4-2) on the EGT6 board of NE2.
Table 10-44 Parameters of the external ports of the Ethernet boards Parameter Board Port Enabled/ Disabled
Issue 02 (2011-10-31)
NE1 EGSH PORT1 Enabled PORT2 Enabled
NE2 EGT6 PORT1 Enabled PORT2 Enabled
NE4 EGT6 PORT1 Enabled
453
Parameter Working Mode Maximum Frame Length TAG Entry Detection Default VLAN ID VLAN Priority Port Type
NE1 1000M FullDuplex 1522 1000M FullDuplex 1522
NE2 1000M FullDuplex 1522 1000M FullDuplex 1522
NE4 1000M FullDuplex 1522
Table 10-45 Parameters of the internal ports of the Ethernet boards Paramete r Board Port Mapping Protocol TAG Entry Detection Default VLAN ID VLAN Priority Bound Path Port Type NE1 EGSH VCTRUN K1 GFP Access Enabled 100 0 VC4xv:VC4-1 UNI VCTRUN K2 GFP Access Enabled 100 0 VC4xv:VC4-2 UNI VCTRUN K3 GFP Tag aware Enabled 200 0 VC4xv:VC4-3 UNI NE2 EGT6 VCTRUN K1 GFP VC4xv:VC4-1 VCTRUN K2 GFP VC4xv:VC4-2 NE3 EGT6 VCTRUN K1 GFP VC4xv:VC4-1 -
Issue 02 (2011-10-31)
454
Table 10-46 Parameters of Ethernet LAN services (IEEE 802.1q bridge) Parameter Board VB Name Bridge Type Bridge Switch Mode Bridge Learning Mode Ingress Filter VB Mount Port VLAN Filtering VLAN Filtering VLAN ID Forwarding Physical Port Hub/Spoke PORT1 PORT2 VCTRUNK1 VCTRUNK2 VCTRUNK3 VCTRUNK4 Ethernet LAN Service of NE1 EGSH VB1 IEEE 802.1q IVL/Ingress Filter Enable IVL Enabled PORT1, VCTRUNK1, VCTRUNK2 VLAN filtering table 1 100 PORT1, VCTRUNK1, VCTRUNK2 Hub Hub Spoke Spoke Hub Hub
Table 10-47 Parameters of the VCTRUNK-shared EVPL (VLAN) services Parameter NE1 EVPL PORT1VCTRUNK1 Board Service Type Service Direction Source Port Source C-VLAN(e.g.1, 3-6) Sink Port Sink C-VLAN(e.g.1, 3-6) EGSH EVPL Bidirectional PORT1 200 VCRTUNK1 200
Issue 02 (2011-10-31)
455

For the Ethernet service of user G, at convergence node NE1, the EVPLAN service (IEEE 802.1q bridge) and VLAN filtering table should be created. Access nodes NE2 and NE4 should be configured with the EPL transparent services. After user H transmits services to the Ethernet, the service data is added with different VLAN tags and thus different user data is isolated but transmitted over the same VCTRUNK.
Prerequisite
The Creating a Network task must be complete. You must be familiar with 10.3.2 EVPL (QinQ) Service Configuration Process and 10.3.3 EPLAN Service Configuration Process.


Step 1 Configure the EVPLAN services for user G1, user G2 and user G3 on NE1. For the operation procedures, see 10.17.3 Configuration Process. Step 2 Configure the EPL services of NE2 and NE4.
NOTE
Step 3 Configure the EVPL services for user H1 and user H2 on NE1. For the operation procedures, see 10.15.3 Configuration Process. Step 4 Check whether the services are configured correctly. For the operation procedures, see Testing Ethernet Service Paths. Step 5 Enable the performance monitoring function of the NEs. For details, see Setting Performance Monitoring Parameters of an NE. Step 6 Back up the configuration data of the NEs. Second methods are available for the backup. Option Description
10.20 Parameters
10.20.1 Parameters: Basic Attributes (External Port)

In this user interface, you can query and set basic attributes of a MAC port.
Parameters
Field Port Value PORTn Description Displays all PORT ports an Ethernet board can use. A PORT port numbered n. Port Enabled Disabled, Enabled Default: Disabled Enabled: the port is used and its services will be processed. Disabled: services at the port will not be processed. So, you need to enable the ports that will be used during configuring services. Working modes of the Ethernet port. The AutoNegotiation mode is recommended, because it can automatically find out the best working mode to combine a port and its interconnected port and thus is convenient for maintenance. Be careful to configure the same working mode for the port and its interconnected port. Otherwise, service will fail. Max. Frame Length Values of parameters vary with different boards and products. Max. Frame Length (Ethernet Port Attribute) parameter specifies the maximum transmission unit (MTU). For the NG WDM equipment, the range is from 1518 to 9600. Click A.2 Max. Frame Length for more information. Port physical parameters Displays the value that is queried. Displays the actual working status of the PORT port.
Working Mode
For example: AutoNegotiation
Issue 02 (2011-10-31)
457
Field MAC Loopback
Value Non-Loopback, Inloop, Outloop Default: Non-Loopback
Description The MAC Loopback parameter specifies the MAC loopback state at an Ethernet port. With this parameter, users can test whether equipment runs normally by creating a looped path at the MAC layer and then sending and receiving signals over the path. The PHY Loopback parameter specifies the PHY loopback state at an Ethernet port. With this parameter, users can test whether equipment runs normally by creating a looped path at the PHY layer and then sending and receiving signals over the path. Displays in hexadecimals. Displays the physical type of port. Displays the logic type of port.
PHY Loopback
Non-Loopback, Inloop, Outloop Default: Non-Loopback
QinQ Type Area Physical Type Logic Type
0x0600 - 0xFFFF Reported value by query SDH-OPPORT, SDHEPORT
10.20.2 Parameters: Basic Attributes (Internal Port)

In this user interface, you can query or set basic attributes of an internal port, including port, port enabling and port physical parameters.
Parameters
Field Port Enabled/Disabled Port Physical Parameters QinQ Type Area Value VCTRUNKn, RPRn Enabled, Disabled Displays the value that is queried. For example: 33024 Description Displays the VCTRUNK or RPR port number. Sets this parameter for the RPR port of the ER4 board. This value can be queried only. Sets the QinQ type of the port.
Issue 02 (2011-10-31)
458
10.20.3 Parameters: Flow Control (External Port)

In this user interface, you can enable and disable the auto-negotiation or non-auto-negotiation flow control mode for an external port.
Parameters
Field Port Value PORTn Description Displays all PORT ports an Ethernet board can use. A port numbered n. Non-Autonegotiation Flow Control Mode Disabled, Enable Symmetric Flow Control, Send Only, Receive Only Default: Disable Values of parameters vary with different boards and products. Non-Autonegotiation Flow Control Mode is selected when a port works in nonautonegotiation mode. Autonegotiation Flow Control Mode is selected when a port works in autonegotiation mode.
Autonegotiation Flow Control Mode
10.20.4 Parameters: Advanced Attributes (External Port)

In this user interface, you can set and query advanced attributes for an external port.
Parameters
Field Port Value PORTn Description Displays the PORT port. The letter n indicates the port number. Enables or disables broadcast packet suppression. When the broadcast packet suppression function is enabled, if the broadcast packet occupies a bandwidth that exceeds the overall bandwidth of the port x the suppression threshold, the broadcast packet is suppressed.
Enabling Broadcast Packet Suppression Broadcast Packet Suppression Threshold
Disabled, Enabled Default: Disabled 10% to 100%
Issue 02 (2011-10-31)
459
Field Loop Detection
Value Disabled, Enabled Default: Disabled
Description Sets whether to enable loop detection, which is used to check whether a loop exists at the port. Sets whether to enable shutdown of a loop port, which is used to set blocking for a loop port.
Loop Port Shutdown
Enabled, Disabled
10.20.5 Parameters: Advanced Attributes (Internal Port)

In this user interface, you can set and query advanced attributes for an internal port.
Parameters
Field Port Value VCTRUNKn Description Displays the VCTRUNK port. The letter n indicates the port number. The Loop Detection parameter specifies the function of reporting the selfloop alarms after one of the following loopback cases is detected. The Loop Port Shutdown parameter is set to disable the self-loop port after a selfloop port is detected if the loop port shutdown function is enabled. After the self-loop port is shut down, the selfloop port only transmits or receives the self-loop detection packets rather than any other packets. If the port is not a self-loop port, it starts to work again.
Loop Detection
Enabled, Disabled Default: Disabled
Loop Port Shutdown
Enabled, Disabled Default: Enabled
10.20.6 Parameters: TAG Attributes

In this user interface, you can query and set the TAG attribute for a PORT port or a VCTRUNK port.
Parameters
Field Port TAG Value PORTn or VCTRUNKn Tag Aware, Access, Hybrid Default: Tag Aware Description PORT port or VCTRUNK port. "n" is the port number. The tag is used for setting which type of data packets can be processed. Set this parameter to Tag Aware to enable the port to transparently transmit packets that have the VLAN ID (tag). If packets do not have the VLAN ID (untag), the packets are discarded. Default VLAN ID and VLAN priority cannot be edited. Set this parameter to Access to enable the port to add the default VLAN ID to packets that do not have the VLAN ID (untag). If the packets have the VLAN ID (tag), the packets are discarded. Set this parameter to Hybrid to enable the port to add the default VLAN ID to the packets that do not have the VLAN ID (untag). If the packets have the VLAN ID (tag), the packets are transparently transmitted. The tag attribute is effective only when the network attribute of the port is PE or UNI.
NOTE The tag attribute does not apply to C-Aware and S-Aware ports.
Default VLAN ID
1-4095 Default: 1
The Default VLAN ID parameter specifies a default VLAN ID for a port that transmits untagged packets.
NOTE When the tag attribute is Tag Aware, the default VLAN cannot be set. When the tag attribute is Access or Hybrid, the default VLAN can be set.
Issue 02 (2011-10-31)
461
Field VLAN Priority
Value 0-7 Default: 0
Description The VLAN Priority parameter specifies the priority of the default VLAN ID of a port.
NOTE When the tag attribute is Tag Aware, the VLAN priority cannot be set. When the tag attribute is Access or Hybrid, the VLAN priority can be set.
Entry Detection
The Entry Detection parameter determines whether a port detects packets by tag identifier.
10.20.7 Parameters: Network Attributes

In this user interface, you can set port attributes.
Parameters
Field Port Port Attribute Value PORTn or VCTRUNKn Values of parameters vary with different boards and products. Description A PORT or VCTRUNK port numbered n. The Port Attribute (Ethernet Port) parameter specifies the position of a port in the network. Different port attributes support different packets.
10.20.8 Parameters: Ethernet Line Service

In this user interface, you can create or query the source and sink routes of an Ethernet leased line, and set port attributes and path binding.
Issue 02 (2011-10-31)
462
Parameters
Table 10-48 Ethernet Service Parameters Field Service Type Value Values of parameters vary with different boards and products. Unidirectional, Bidirectional Default: Bidirectional Description Displays the service type.
Direction
Displays the transmit direction of the service. The bidirectional service refers to two services, one of which is transmitted from the source port to the sink port and the other one of which is transmitted from the sink port to the source port. The unidirectional service refers to a service transmitted from the source port to the sink port.
Operation Type
Values of parameters vary with different boards and products. Add S-VLAN, Add S-VLAN and C-VLAN, Strip SVLAN, Strip S-VLAN and C-VLAN, Transparently transmit S-VLAN, Translate S-VLAN, Transparently transmit C-VLAN, Add S-VLAN, Transparently transmit S-VLAN, Translate S-VLAN, Transparently transmit C-VLAN, Translate C-VLAN
Sets the operation type for the EVPL(QinQ) services. l Add S-VLAN: Adds STAG based on the PORT route. l Add S-VLAN and CVLAN: Adds S-TAG and C-TAG based on the PORT route. l Transparently transmit SVLAN: Transmits the User TAG transparently. l Transparently transmit CVLAN: Transmits the CTAG transparently. l Translate S-VLAN: Exchanges S-TAG based on the PORT route. l Strip S-VLAN: Strip STAG. l Strip S-VLAN and CVLAN: Strip S-TAG and C-TAG.
Source Port
PORTn, VCTRUNKn Default: PORT3
Displays the name of the source port.
Issue 02 (2011-10-31)
463
Field Source VLAN
Value 1-4095
Description Sets VLAN ID of the source port. Applies to EPL services. Sets C-VLAN of the source port. C-VLAN is the client VLAN ID. Applies to EVPL(QinQ) services.
Source C-VLAN
1-4095
Source S-VLAN
1-4095, NULL Default: NULL
Sets S-VLAN of the source port. S-VLAN is the service VLAN ID. Applies to EVPL(QinQ) services.
Sink Port
PORTn, VCTRUNKn For example: PORT3
Displays the name of the sink port. Sets VLAN ID of the sink port. Applies to EPL services. Sets C-VLAN of the sink port. C-VLAN is the client VLAN ID. Applies to EVPL(QinQ) services.
Sink VLAN
1-4095
Sink C-VLAN
1-4095
Sink S-VLAN
1-4095, NULL Default: NULL
Sets S-VLAN of the sink port. S-VLAN is the service VLAN ID. Applies to EVPL(QinQ) services.
C-VLAN Priority
AUTO, Priority0, Priority1, Priority2, Priority3, Priority4, Priority5, Priority6, Priority7 AUTO, Priority0, Priority1, Priority2, Priority3, Priority4, Priority5, Priority6, Priority7
Sets the priority of C-VLAN.
S-VLAN Priority
Sets the priority of S-VLAN.
Issue 02 (2011-10-31)
464
Field OAM Enable
Value Enabled, Disabled Default: Disabled
Description Enable OAM Protocol parameter specified whether the end-to-end OAM protocol (namely, the IEEE 802.3ah protocol) is enabled at a port. l Enabled indicates that the IEEE 802.3ah protocol is enabled and the end-toend Ethernet OAM function is available. l Disabled indicates that the IEEE 802.3ah protocol is disabled and the end-to-end Ethernet OAM function is unavailable.
Port Port Type
For example: PORT3 UNI, C-Aware, S-Aware (for boards that support QinQ) Default: UNI
Displays the name of a port. Sets the network attributes for a port. If the port is of the UNI type, the port processes the tag attributes in 802.1Q and the port has the Tag, Access, and Hybrid attributes. If the port is of the C-Aware type, the port does not process the tag attributes in 802.1Q. It determines that the data packet carries the CVLAN tag and processes only the data packet that has the C-VLAN tag. If the port is of the S-Aware type, the port does not process the tag attributes in 802.1Q. It determines that the data packet carries the SVLAN tag and processes only the data packet that has the S-VLAN tag.
Port Enabled
Enables or disables a port. Enabled: This port can access services. Disabled: This port cannot access services.
Issue 02 (2011-10-31)
465
Field TAG
Value Tag Aware, Access, Hybrid Default: Tag Aware
Description TAG is used to set the type of the processed messages. The tag aware port only processes the messages with a tag, and those messages without a tag are discarded. However, the Access port is quite the contrary. The hybrid port processes the two types of messages. It adds a tag to the messages without a tag according to the VLAN ID of this port.
10.20.9 Parameters: VLAN Group

In this user interface, you can configure a VLAN group. You can assign services that have consecutive CVLANs into a VLAN group. In this way, you configure the VLAN group as a whole in the same way as you configure a single VLAN.
Parameters
Field Board Port Initial VLAN Value For example: 4-TBE For example: PORT3 For example: 1 Description Displays the name of a board. Choose the port of the VLAN group. Sets and displays the initial VLAN. The value of Initial VLAN ranges from 1 to 4095. The calculation formula is as follows: Initial VLAN = p x (2^n), where n = 0, 1,..., 12, and p is an integer ranging from 1 to 2^m. m + n< = 12. Displays the VLAN ID of last the VLAN.
Last VLAN
For example: 1
Issue 02 (2011-10-31)
466
Field VLAN Group Member Count
Value For example: 1
Description Sets and displays the number of members in a VLAN group. l The calculation formula of VLAN Group Member CountVLAN depends on the value of Initial VLAN. When Initial VLAN = 1, VLAN Group Member Count = 2^n - 1. When Initial VLAN has another value, VLAN Group Member Count = 2^n, where n is equal to the n in the formula of Initial VLAN. l The maximum number of VLAN groups is equal to the number of links on a board.
10.20.10 Parameters: Ethernet LAN Service

In this user interface, you can create and query Ethernet LAN services, and configure the forwarding filter table.
Parameters
Field Board VB ID Value For example: NE501-4-TBE For example: 1 Description Displays the name of the board. Allocated automatically when an Ethernet LAN service is created. Indicates the name of the VB. Sets the type of a bridge. Selects the bridge switch mode.
VB Name Bridge Type Bridge Switch Mode
A maximum of 16 English letters or numerals For example: 802.1q IVL/Ingress Filter Enable, SVL/Ingress Filter Disable Default: IVL/Ingress Filter Enable
Issue 02 (2011-10-31)
467
Field Bridge Learning Mode
Value Values of default with different bridge mode. For details, click the links in the Description column.
Description Bridge Learning Mode (Ethernet LAN Service) indicates how the bridge learns the MAC address. Bridge Learning Mode is classified into the shared VLAN learning and independent VLAN learning modes. The shared VLAN learning mode indicates learning and forwarding based on the MAC address. The independent VLAN learning mode indicates learning and forwarding based on the VLAN and MAC address. Displays the status of an ingress filter. Enabled: Checks the validity of a VLAN ID on the basis of bridge. If the ingress receives a packet that does not belong to the VLAN associated to the port on the bridge, the ingress discards the packet. Disabled: Does not check the validity of a VLAN ID. All packets that need to enter the bridge are valid.
Ingress Filter
Enabled, Disabled
MAC Address Self-learning
Enables or disables MAC address learning. Enabled: MAC addresses are learned. Disabled: MAC addresses are statically configured.
Active
Active, Inactive
Displays the activation status of a VB.
Table 10-49 Service Mount Field VB Port Value For example: 1 Description Sets the VB logical ports.
Issue 02 (2011-10-31)
468
Field Mount Port Operation Type
Value For example: PORT1 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
Description The mount port may be the PORT port or VC trunk port. You can perform operations as follows: l Mounting that is based on port and for which the SVLAN tag is added l Mounting that is based on port and C-VLAN and for which the S-VLAN tag is added l Mounting that is based on port l Mounting that is based on port and S-VLAN
Port Type
UNI, C-Aware, S-Aware (for boards that support QinQ) Default: UNI
Sets the network attributes for a port. If the port is of the UNI type, the port processes the TAG attributes in 802.1Q and the port has the Tag Aware, Access and Hybrid attributes. If the port is of the C-Aware type, the port does not process the tag attributes in 802.1Q. It determines that the data packet carries no SVLAN tag and processes only the data packet that has the C-VLAN tag. If the port is of the S-Aware type, it can identify and process the VLAN information about the provider. If the QinQ Type field is valid, this port treats the outmost label carried by the packets as S-VLAN.
Service Direction
Bidirectional Default: Bidirectional
Displays the direction of an Ethernet service.
Issue 02 (2011-10-31)
469
Field Port Enabled
Value Enabled, Disabled
Description Enables or disables a port. Enabled: This port can access services. Disabled: This port cannot access services.
TAG Hub/Spoke
Access, Tag aware, Hybrid Hub, Spoke Default: Hub
Sets the tag attribute of the VB. Hub/Spoke (Ethernet LAN Service) is used to separate packets between the logical ports in the network bridge. Sets the VLAN ID. To set the VLAN ID, right-click a port, and choose VLAN Allocation from the shortcut menu. Then, in the dialog box displayed, set the VLAN ID of the VB link that the port belongs to. You can also set the VLAN ID in the VLAN Filtering tab. Displays the working modes of the Ethernet port. AutoNegotiation can automatically determine the optimized working modes of the connected ports. This mode is easy to maintain and is recommended. During configuration, make sure that working modes of the connected ports are consistent. If the working modes are different, the services are down.
Default VLAN ID
1 to 4095
Working Mode
For example: 10M HalfDuplex
Service Direction C-VLAN S-VLAN
Bidirectional 0 to 4095 0 to 4095
Sets the direction of service. Sets the C-VLAN value. Sets the S-VLAN value.
Issue 02 (2011-10-31)
470
Field VLAN ID
Value 1 to 4095
Description Sets the VLAN ID. To set the VLAN ID, right-click a port, and choose VLAN Allocation from the shortcut menu. Then, in the dialog box displayed, set the VLAN ID of the VB link that the port belongs to. You can also set the VLAN ID in the VLAN Filtering tab. Sets the MAC address of VLAN unicast. To set the MAC address of VLAN unicast, right-click a port that is already allocated with a VLAN ID, and choose VLAN Unicast from the shortcut menu. Then, in the dialog box displayed, set the MAC address of VLAN unicast for the port. You can also set the MAC address of VLAN unicast in the VLAN Unicast tab.
MAC Address
00-00-00-00-00-01 to FEFF-FF-FF-FF-FF The first byte is an even number.
Table 10-50 VLAN Filtering Field VLAN ID Value 1 to 4095 Description Specifies the VLAN ID and configures the forwarding filter table. Sets the VB logical ports. Displays the physical port that is actually attached to the VB link. Displays the queried physical ports that can be used for forwarding. Displays the selected ports that can be used for forwarding.
VB Port Forwarding Physical Port
For example: (1-2) For example: PORT1, VCTRUNK1 For example: PORT4
Available forwarding ports
Selected forwarding ports
For example: PORT4
Issue 02 (2011-10-31)
471
Table 10-51 VLAN Unicast Field VLAN ID Value 1 to 4095 Description Only the VLAN ID specified in the forwarding filter table can be selected. VLAN unicast is different from common unicast. A VLAN unicast uses VB, VLAN ID, port, and MAC address as its unique identifier. Displays the MAC address of VLAN unicast.
MAC Address
00-00-00-00-00-01 to FEFF-FF-FF-FF-FF The first byte is an even number.
VB Port Physical Port Aging Status
For example: 1 For example: PORT1 Static
Sets the VB logical ports. Displays the name of the port. Displays the aging status of unicast items, including static and dynamic. VB is automatically displayed by the U2000.
VB
VB ID-VB Name
Table 10-52 Disable MAC Address Field VLAN ID MAC Address Value 1 to 4095 00-00-00-00-00-01 to FEFF-FF-FF-FF-FF The first byte is an even number. Description Inhibits a MAC address in the VLAN of a certain VB. Enters a MAC address that is to be inhibited. Hence, enters a MAC address that is not associated to the VLAN unicast of this VLAN.
Table 10-53 Bound Path Field VCTRUNK Port Level Value For example: VCTRUNK1 For example: VC12 Description Displays the name of the configured VC trunk port. Displays the level of a VC trunk-bound path.
Issue 02 (2011-10-31)
472
Field Service Direction
Value Bidirectional, Uplink, Downlink Default: Bidirectional
Description Displays the direction of an Ethernet service.
Bound Path
For example: VC4-1-VC3(1)
Specifies the number of the path that you want to bind, including VC4 path No. and VC12/VC3 path No. VC4-1VC12(1-3). Displays the number of the bound paths.
Number of Bound Paths
For example: 1
Table 10-54 Self-learning MAC address Field MAC Address Value 00-00-00-00-00-01 to FEFF-FF-FF-FF-FF The first byte is an even number. VB Port VLAN ID For example: 1 1 to 4095 Sets the VB logical ports. Displays the VLAN ID. Description Enters a MAC address.
10.20.11 Parameters: Aging Time

In this user interface, you can set the life cycle for filtering dynamic records in the database and the aging time for the MAC address.
Parameters
Field Board Value For example: NE1-3N1EFS4 For example: NE1-8-TBE MAC Address Aging Time / Aging Time Unit 1-120 Default: 5 The MAC Address Aging Time parameter specifies the valid duration of a dynamically learnt MAC address in the MAC address table. Description Displays the board name.
Issue 02 (2011-10-31)
473
10.20.12 Parameters: VLAN Unicast

In this user interface, you can create, query or delete a VLAN unicast item.
Parameters
Field Board VLAN ID Value For example: NE70-4-ER4 1 to 4095 Description Displays the Board. Only the VLAN ID that has been created in earlier VLAN Filtering can be selected. MAC Address Logical port (LP) +port No. Aging status of unicast items, including static, dynamic and so on.
MAC Address Port Aging Status
The first digit is an even number For example: LP1 Static, Dynamic Default: Static
10.20.13 Parameters: Port Mirroring

In this user interface, you can configure the port mirroring of the Ethernet interface board. Then, you can use the port mirroring to perform packet monitoring, daily maintenance and in-service commissioning.
Parameters
Field Board Value For example: 8-N1EAS2 For example: 5-L4G Mirror Listener Port For example: PORT4 Displays the mirror listener port. It is used to perform packet detection and daily maintenance. Sets the uplink listened port. Sets the downlink listened port. Description Selects a board for port mirroring.
Uplink Listened Port Downlink Listened Port
For example: PORT3 For example: PORT5
10.20.14 Parameters: Ethernet Test

This user interface is for commissioning of installed Ethernet boards and fault location. You can set the send mode, send direction and the number of test frames to be sent. At the same time, you can query the number of received test frames and response frames, and carry out a service connection test to check whether the service connection is normal.
Parameters
Table 10-55 Ethernet test Field Port Send Mode Value For example: 3-L4GVCTRUNK1 Disabled, Burst Mode, Continue Mode Default: Disabled Description Displays the internal port name. Send Mode(Ethernet Test) is used to set the test frame and the transmit mode of the test frame. The test frame is used for simulating packet transmission to check whether the link is normal. Send Direction (Ethernet Test) indicates the transmit direction of the test packet. Frames to Send indicates the number of test packets to be transmitted. With this parameter enabled, the system transmits a test packet every one second until the number of transmitted test packets reaches the specified value.
NOTE The number of Frames to Send could be slightly different for some equipment.
Send Direction
WDM Direction
Frames to Send
0-255 Default: 0
Status
Sending, Finished Sending Default: -
Status indicates the transmit status of the current test frames at the port. This parameter is displayed as the current test status after you configure Send Mode and Frames to Send and then click Apply.
Issue 02 (2011-10-31)
475
Field Counter of Frames Sent
Value For example: 1
Description Counter of Frames Sent indicates the number of test frames that are transmitted by the VC trunk port in the Ethernet test. This parameter value is accumulative. The value indicates the total number of test frames that are transmitted from last time when the parameter value is cleared to this time when the value is queried. Counter of Received Response Test Frame indicates the number of response test frames that are received by the VC trunk port in the Ethernet test. This parameter value is accumulative. The value indicates the total number of response test frames that are received from last time when the parameter value is cleared to this time when the value is queried. Counter of Test Frames to Receive indicates the number of test frames that are received by the VC trunk port in the Ethernet test. This parameter value is accumulative. The value indicates the total number of test frames that are transmitted from last time when the parameter value is cleared to this time when the value is queried.
Counter of Received Response Test Frame
For example: 1
Counter of Test Frames to Receive
For example: 1
Table 10-56 Setting the bearer mode Field Port Value For example: VCTRUNK1 Description Selects the port at which you want to set the bearer mode.
Issue 02 (2011-10-31)
476
Field Bearer Mode
Value Values of parameters vary with different boards and products.
Description Bearer Mode (Ethernet Test) indicates the transmit path of the test frame. Different bearer modes correspond to different types of test frames. If the bearer mode of the received test frame is inconsistent with the bearer mode of this port, the test frame is discarded directly. Displays the bearer mode at the opposite end.
Remote Bearer Mode
GFP, Ethernet
Table 10-57 Service Connection Test Field Port Opposite Port Information Value For example: VCTRUNK1 NE-board-VCTRUNK number Description Selects the port to query the opposite port information. Displays the opposite port information that is queried.
10.20.15 Parameters: Protocol Fault Management

In this user interface, you can diagnose the Ethernet protocol and restart the protocol state machine by restoring the protocol, to remove the protocol faults.
Parameters
Field Diagnose Port Protocol Type Diagnose Information Fault Description Selects the diagnose port. Selects the Ethernet protocol type. Select the diagnose information. Displays the fault diagnosis result.
10.20.16 Parameters: Port MAC Address Filtering

In this user interface, you can set the port MAC address filtering.
Issue 02 (2011-10-31)
477
Parameters
Field Port MAC Address Value For example: Port1 00-00-00-00-00-01 to FEFF-FF-FF-FF-FF Description Displays the port name. Displays the opposite router MAC address.
Issue 02 (2011-10-31)
478
11 Modifying the Configuration Data
11
Modifying the Configuration Data
About This Chapter

11.1 Modifying Port The client-side and line-side ports of the OTU board in the NG WDM equipment can be configured as color ports or grey ports. The port type needs to be set according to type of the small form-factor pluggable (SFP) optical module used in the equipment. 11.2 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. 11.3 Conversion Between EPL Ethernet Services and VLAN SNCP Services The conversion between the created EPL Ethernet services and VLAN SNCP services can be realized on the U2000.
Issue 02 (2011-10-31)
479
11.1 Modifying Port

The client-side and line-side ports of the OTU board in the NG WDM equipment can be configured as color ports or grey ports. The port type needs to be set according to type of the small form-factor pluggable (SFP) optical module used in the equipment.
Prerequisite

Background Informations
l Only the TOM board supports interchange of line-side ports and client-side ports. When a TOM board is created, the ports on the TOM board are created automatically and are defined as client-side ports by default. When a board is created, the ports on the board are created automatically and the clientside ports are defined as Client Side Grey Optical Port by default.

Step 1 Right-click the board in the NE panel, and choose Path View from the shortcut menu. Step 2 Right-click the port for which you want to modify the port type and choose Modify Port from the shortcut menu. The Modify Port dialog box is displayed. Set Type and click OK to apply the configuration.
NOTE
If you need to modify Type to Client Side Color Optical Port, Line Side Color Optical Port or Electrical Port, you must first delete the port, and then add the port. Otherwise the port cannot be modified successfully.
Step 3 Optional: In Path View, right-click the desired port, and click Delete Port. Step 4 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. ----End
Issue 02 (2011-10-31)
480
11.2 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.
11.2.1 Deactivating Cross-Connection Service

To release the occupied channel resources, you need to deactivate cross-connections and then delete the cross-connections.
Prerequisite

Precautions
CAUTION
The deactivation operation may interrupt services.

Step 1 In the NE Explorer, select the NE and choose Configuration > WDM Service Management from the Function Tree.
NOTE
If the Web LCT is used, the navigation path is as follows: in the NE Explorer, select the NE and choose Configuration > Electrical Cross-Connection Service Management from the Function Tree.
Step 2 Click the WDM Cross-Connection Configuration tab.

NOTE
If the Web LCT is used, the navigation path is as follows: click the Electrical 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. Step 5 Click OK. The Operation 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
11.2.2 Deleting Cross-Connections

When you need to modify or re-configure cross-connections, you need to first delete them.
Prerequisite
You are an NMS user with "Operator Group" authority or higher. The cross-connections must be created and inactive.

Precautions
CAUTION
Deleting cross-connections may interrupt services.

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 Select the cross-connections to be deleted and click Delete. Step 4 In the Confirm dialog box that is displayed, click OK and then click Close. In the Operation Result dialog box. ----End

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 Select the cross-connections to be deleted and click Delete. ----End
11.2.3 Modifying SDH Services

When a network changes or services are adjusted, you can modify an SDH service by using the modification function of the U2000 and Web LCT. Alternatively, you can modify the SDH service by deleting it and then creating a cross-connection again.
Prerequisite

Precautions
CAUTION
Performing this operation interrupts the service that you modify.

NOTE
If the Web LCT is used, the navigation path is as follows: in the NE Explorer, select the NE and choose Configuration > Cross Connection Configuration from the Function Tree.
Step 2 Select a cross-connection and choose Display > Expand to Unidirectional. Step 3 You can modify the SDH service by using the method described in Step Step 4 or Step 5.
NOTE
l By using the method described in Step Step 4, you can modify the source or sink of a service, but the source and sink must be on the same board before and after the modification. l If the modification requirement cannot be met in the method described in Step Step 4 (for example, a pass-through service needs to be configured to the local through modification), you can delete the original service and create the cross-connection again in the method described in Step Step 5, to achieve the modification.
Step 4 Optional: To modify the SDH service, choose Modify from the shortcut menu. 1. 2. Select the service that you want to modify, right click the service and choose Modify from the shortcut menu. The Modify SDH Service dialog box is displayed. Modify Source VC4 or Sink VC4, Source Timeslot Range (e.g.1,3-6), and Sink Timeslot Range (e.g.1,3-6). For details of the parameters, see 9.7.1 SDH Service Configuration.
Issue 02 (2011-10-31)
483
NOTE
In this method, you can modify only Source VC4 or Sink VC4 at a time. The source VC4 and sink VC4 cannot be modified at the same time.
3. 4. 5. 6. 7. 1. 2. 3. 4.
Click OK. The Operation Result dialog box is displayed telling you that the operation was successful. Click Close. Select the service that is modified, and click Activate. Click OK. The Operation Result dialog box is displayed. Click Close. Select the service that you want to modify, and click Delete. Click OK and the Operation Result dialog box is displayed telling you that the operation was successful. Click Close. The service is deleted. Create the service again as required. For details, see 12.6.2 Creating SDH CrossConnections.
Step 5 Optional: To modify the SDH service, delete the service and then create the service again.
----End
11.2.4 Deleting SDH Services

You can delete an existing SDH when it is no longer applicable or is adjusted.
Prerequisite


NOTE
If the Web LCT is used, the navigation path is as follows: in the NE Explorer, select the NE and choose Configuration > Cross Connection Configuration from the Function Tree.
Step 2 Click Query to query existing services. Click OK in the Confirm dialog box. Step 3 Click Close in the Operation Result dialog box. Step 4 Optional: If the service to be deleted is active, you should deactivate the service. Select the service that you want to delete and click Deactivate.
CAUTION
Deactivation will interrupt services. Step 5 Select the desired service and click Delete. Step 6 In the Confirm dialog box displayed, click OK. Step 7 In the Operation Result dialog box displayed, click Close. ----End
11.2.5 Converting a Non-Protection Service to an SNCP Service

The SNCP service features the dual fed and selective receiving function and is used to protect cross-subnet services. When configuring SDH services on a per-NE basis, you can perform this operation to convert a configured non-protection service to an SNCP service.
Prerequisite
You are an NMS user with "Operator Group" authority or higher. The normal service is created.
Precaution
CAUTION
Converting a normal cross-connection service to an SNCP service may interrupt services.
Procedure
Step 2 Click Query to query the SDH services from the NE. Step 3 In the Confirm dialog box, click OK. In the Operation Result dialog box, click Close. Step 4 Select the desired normal service, click Display and choose Expand to Unidirectional from the drop-down list. Right-click a desired normal service and choose Convert to SNCP from the shortcut menu.
NOTE
You can select multiple services to change them in batches.
Step 5 In the Prompt dialog box displayed, click OK. Step 6 In the Create SNCP Service dialog box displayed, configure the protection service and click OK.
NOTE
You need to perform the operation on the NEs that are set as the dual fed nodes and selective receiving nodes on the source or sink, or in the cross protection subnets.
Step 7 Click Create. In the Create SDH Service dialog box displayed, configure a unidirectional service from the service source board to the line board of another direction.
NOTE
Step 8 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
11.2.6 Converting an SNCP Service to a Non-Protection Service

The SNCP service features the dual fed and selective receiving function and is used to protect cross-subnet services. When configuring SDH services on a per-NE basis, you can perform this operation to change a configured SNCP service to a non-protection service.
Prerequisite
You are an NMS user with "Operator Group" authority or higher. The SNCP service must be created.
Precaution
CAUTION
Converting an SNCP service to a normal cross-connection service may interrupt services.
Issue 02 (2011-10-31)
486
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > SDH Service Configuration from the Function Tree. Step 2 Click Query to query the SDH services from the NE. Step 3 In the Confirm dialog box, click OK. In the Operation Result dialog box, click Close. Step 4 Select the desired SNCP service, click Display and choose Expand to Unidirectional to display the service one by one. Right-click the SNCP service and choose Convert to Non-Protection Service from the shortcut menu. The protection service is then deleted.
NOTE
To convert the service in the protection path into a normal service, select a cross-connection in the AutoCreated Cross-Connection pane, right-click the SNCP service and choose Convert to Non-Protection Service from the shortcut menu.
Step 5 In the Prompt dialog box displayed, click OK. Step 6 Select a unidirectional service from the service source board to the line board of another direction, and click Deactivate. In the Confirm dialog box displayed, click OK. In the Operation Result dialog box displayed, click Close.
NOTE
Step 7 Select the unidirectional service that you deactivated, right-click, and choose Delete from the shortcut menu. In the Confirm dialog box that is displayed, click OK. In the Operation Result dialog box displayed, click Close.
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 8 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.
----End
11.3 Conversion Between EPL Ethernet Services and VLAN SNCP Services
The conversion between the created EPL Ethernet services and VLAN SNCP services can be realized on the U2000.
11.3.1 Converting an EPL Ethernet Service to a VLAN SNCP Service

You can convert an EPL service to a VLAN SNCP service by using the U2000 or the Web LCT.
Prerequisite
Applicable to the TBE, L4G, LEM24 and LEX4 board. An EPL Ethernet services must be created. An idle port must be available when you convert an EPL service to a VLAN SNCP service.


Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Step 2 Click the EPL Service tab. Select a service that you want to convert, right-click, and choose Convert to VLAN SNCP from the shortcut menu. The Convert to VLAN SNCP Service dialog box is displayed. Step 3 Set protection service parameters such as Source Port according to the actual requirements.
NOTE
l Make sure that the port settings of the protection service and the service being protected are consistent. l If the port type of protection services is not UNI, the U2000 automatically sets the port type to UNI.
Step 4 Click OK. Step 5 In the NE Explorer, select the NE and choose Configuration > WDM Service Management from the Function Tree. Click the WDM Cross-Connection Configuration tab. Then, create the cross-connections between the Ethernet board and the east line board and between the Ethernet board and the west line board.
Issue 02 (2011-10-31)
488

NOTE
l When the Ethernet board is the L4G board, create the cross-connection between this L4G board and the L4G board that is in another direction. l If the cross-connection already exists, skip this step.
Step 6 In the NE Explorer of the opposite NE, create the Ethernet dual fed service of the opposite NE and the corresponding cross-connections between the Ethernet board and the east line board and between the Ethernet board and the west line board. Step 7 Optional: If the service passes through an intermediate station, on the intermediate station, you should configure the pass-through for the service between the line boards. ----End

Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Step 2 Click the EPL Service tab. Select a service that you want to convert, right-click, and choose Convert to VLAN SNCP from the shortcut menu. The Convert to VLAN SNCP Service dialog box is displayed. Step 3 Set protection service parameters such as Source Port according to the actual requirements.
NOTE
l Make sure that the port settings of the protection service and the service being protected are consistent. l If the port type of protection services is not UNI, the Web LCT automatically sets the port type to UNI.
Step 4 Click OK. Step 5 In the NE Explorer, select the NE and choose Configuration > Electrical Cross-Connection Configuration tab. Then, create the cross-connections between the Ethernet board and the east line board and between the Ethernet board and the west line board.
NOTE
l When the Ethernet board is the L4G board, create the cross-connection between this L4G board and the L4G board that is in another direction. l If the cross-connection already exists, skip this step.
Step 6 In the NE Explorer of the opposite NE, create the Ethernet dual fed service of the opposite NE and the corresponding cross-connections between the Ethernet board and the east line board and between the Ethernet board and the west line board. Step 7 Optional: If the service passes through an intermediate station, on the intermediate station, you should configure the pass-through for the service between the line boards. ----End
11.3.2 Converting a VLAN SNCP Service to an EPL Ethernet Service

You can convert a VLAN SNCP service to an EPL service by using the U2000.
Prerequisite
Applicable to the TBE, L4G, LEM24 and LEX4 boards. VLAN SNCP services must be created.


Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Step 2 Click the VLAN SNCP Service Management tab. Step 3 Select a VLAN SNCP working service, right-click, and choose Convert to Normal Service from the shortcut menu, a confirm dialog box is displayed. Step 4 Click OK to convert the service to an EPL service. ----End
11.3.3 Deleting EPL Services

To release network resources, you can delete the unwanted EPL services.
Prerequisite
You are an NMS user with "Operator Group" authority or higher. EPL services must be created.

Precautions
CAUTION
The deletion operation affects services. Exercise caution when you perform this operation.

Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Step 2 Click the EPL Service tab and click Query to view the created EPL services. Step 3 Select the desired EPL service and click Delete. In the dialog box that is displayed, click OK to delete the service. ----End
11.3.4 Deleting EVPL (QinQ) Services

To release network resources, you can delete the unwanted EVPL (QinQ) services.
Prerequisite
You are an NMS user with "Operator Group" authority or higher. EVPL (QinQ) services must be created.

Precautions
CAUTION

Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Step 2 Click the Ethernet Line ServiceEPL Service tab and click Query to view the created EVPL (QinQ) services. Step 3 Select the desired EVPL (QinQ) service and click Delete. In the dialog box that is displayed, click OK to delete the service. ----End
11.3.5 Deleting EPLAN Services

To release network resources, you can delete the unwanted EPLAN services.
Prerequisite
You are an NMS user with "Operator Group" authority or higher. EPLAN services must be created.

Issue 02 (2011-10-31)
491
Precautions
CAUTION

Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Step 2 Click the Service Mount tab and click Query to view the created EPLAN services. Step 3 Select the desired EPLAN service and click Delete. In the dialog box that is displayed, click OK to delete the service.
NOTE
Before delete the EPLAN service, you must delete the VLAN filtering table.
Step 4 Optional: On the Service Mount tab page, select the port that does not need to be mounted, and then double-click Mount Port. In the drop-down list, select unconnected. Then, click Apply. The port is then disconnected.
NOTE
Before disconnecting the EPLAN service mounting port, delete the port on the VLAN Filtering tab page.
----End
11.3.6 Modifying a VLAN Group

You can modify the configuration of a VLAN group to meet service requirements. Modifying a VLAN group is to modify the number of VLAN members.
Prerequisite
You must be an NM user with "NE operator" authority or higher. The VLAN group must be created.

Precautions
CAUTION
Modifying a VLAN group may affect the services.
Issue 02 (2011-10-31)
492

Step 1 In the NE Explorer, select the Ethernet board and choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Step 2 Click the VLAN Group tab. Step 3 Select a VLAN group that you want to modify, and double-click the VLAN Group Member Count to modify the number of VLANs. Then, click Apply.
NOTE
The modified VLAN Group Member Count is restricted as follows: 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 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 the configuration of related parameters, see 10.20.9 Parameters: VLAN Group.
Step 4 In the confirmation dialog box, click OK. The configuration is complete. Step 5 Click Query. Confirm that the query results are the same as the values that are set. ----End
11.3.7 Deleting a VLAN Group

You can delete VLAN groups according to service requirements.
Prerequisite
You are an NMS user with "Operator Group" authority or higher. The VLAN group must be created.

Precautions
CAUTION
Deleting a VLAN group may interrupt the services in the VLAN group.
Issue 02 (2011-10-31)
493

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 Select a VLAN group that you want to delete, and click Delete. Step 4 In the confirmation dialog box, click OK. The configuration is complete. ----End
Issue 02 (2011-10-31)
494
12 Configuration Tasks
12
About This Chapter
Configuration Tasks
This chapter describes basic operations that may be used when you configure services. For example, configure the service type and WDM-side port attributes of the board. You can see this topic if required. 12.1 Configuring Working Modes Before using some boards, you need to configure the port working modes for the boards. Different port working modes enable a board to process services differently. 12.2 Configuring the Service Type The services can be transmitted normally only when the type of the services at the WDM interface of the board is the same as the actual service type. 12.3 Configuring the Service Mode If services such as OTU1 are input to a board, you need to configure the service mode of the board. 12.4 Configuring Common Cross-Connections This section describes how to configure common electrical cross-connections. 12.5 Configuring Service Timeslots For some boards the transmit and receive timeslots of the client-end services should be configured during service creation. 12.6 Configuring SDH Cross-Connections This topic describes how to configure SDH cross-connections. 12.7 Configuring Path Overhead for SDH Services The path overhead is configured for services, which helps network maintenance personnel to maintain the network. 12.8 Configuring the Board Mode The board supports different functions in different board modes. Set the board mode of the board properly according to the actual requirements. For example, when the ND2 board is used as a regeneration board, set the board mode of the ND2 board to the regeneration mode. 12.9 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. 12.10 Configuring the Aging Time for MAC Addresses You can configure the aging time for MAC addresses, to implement the dynamic address aging. The MAC addresses that do not appear again on a transport network during the aging time are regarded as having no route requirements. Then these MAC addresses are deleted from the MAC address table to make space for more MAC addresses. 12.11 Configuring MAC Address Filtering MAC address filtering is a broadband transmission solution intended to alleviate the load of the standby router. 12.12 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. 12.13 Diagnosing Ethernet Protocol Faults When the Ethernet protocol operates abnormally, the U2000 diagnoses the protocol fault, displays the diagnosis contents, and restores the normal operation of the Ethernet protocol. 12.14 Configuring Non-Intrusive Monitoring Non-intrusive monitoring indicates that the board monitors the overhead, however, does not handle it, thus the service is not affected. The non-intrusive monitoring is performed for the overheads that are transmitted through the intermediate nodes between the nodes where the overhead bytes are added or dropped.
Issue 02 (2011-10-31)
496
12.1 Configuring Working Modes

Before using some boards, you need to configure the port working modes for the boards. Different port working modes enable a board to process services differently.
Prerequisite
You must be an NM user with "NE operator" authority or higher. The required boards must be created. Before changing the working mode or port working mode of a board, delete the crossconnections on the board and logical fiber connections at the optical ports.
Context
l l l You need to configure working modes for the following boards: TN52TOM, THA, TOA, LOA, TN53TDX, and TN55TQX. You need to configure only Port Working Mode for the following boards: THA, TOA, LOA, TN53TDX, and TN55TQX. For the TN52TOM board, you need to configure not only Board Working Mode but also Port Working Mode (such as ODU0/ODU1 mapping and tributary-line integration) to achieve different service signal flows. If you set Board Working Mode to Non-Cascading mode for the TN52TOM board, you need to set Port Working Mode only for optical ports ClicentLP1, ClicentLP3, ClicentLP5, and ClicentLP7.
Procedure
Step 1 In the NE Explorer, select the board that you want to configure and choose Configuration > Working Mode from the Function Tree. Step 2 In the Board Working Mode pane, set Board Working Mode to Cascading mode or NonCascading mode.
NOTE
This step is applicable only to the TN52TOM board.
Step 3 In the Port Working Mode pane, select the desired optical port. Click the Port Working Mode field and select the corresponding mode from the drop-down list. Step 4 Click Apply. Step 5 Click Query. Confirm that the query results are the same as the values that are set. ----End
12.2 Configuring the Service Type

The services can be transmitted normally only when the type of the services at the WDM interface of the board is the same as the actual service type.
Prerequisite
You must be an NMS user with "NE operator" authority or higher.

Precautions
CAUTION
l Modifying the service type will lead to service interruption. l When configuring a GE service, make sure that the service types specified for the transmitter and receiver in one direction are the same.

Step 1 In the NE Explorer, select the desired board, and choose Configuration > WDM Interface from the Function Tree. Step 2 Select By Board/Port(Channel) and choose Channel from the drop-down list. Step 3 In the Basic Attributes tab, select the desired optical port. Double-click the Service Type field and select the required service type.
NOTE
If you set Service Type to Any, you must set the service rate in Client Service Bearer Rate (Mbit/s).
Step 4 Click Apply. Click OK in the dialog box displayed.
Issue 02 (2011-10-31)
498
Step 5 Click Query, and the Operation Result dialog box is displayed. Click Close. The value of Service Type is the same as the one set previously. ----End
12.3 Configuring the Service Mode

If services such as OTU1 are input to a board, you need to configure the service mode of the board.
Prerequisite
You must be an NMS user with "NE operator" authority or higher. This task is applicable to the following boards: TOM, TQM, ND2, NS2, NQ2, L4G, LQG, LQMD, LQMS, and LQM.

Precautions
CAUTION
Modifying the service mode interrupts the existing services.

Step 1 In the NE Explorer, select the desired board and choose Configuration > WDM Interface from the Function Tree. Step 2 Click By Board/Port(Channel), and then choose Channel from the drop-down list. Step 3 Select the Basic Attributes tab, and then select the desired optical port. Step 4 Double-click the Service Mode field, and then choose the desired service mode from the dropdown list. For details, see A.23 Service Mode (WDM Interface).
NOTE
You do not need to set Service Mode for a line board that works in standard mode.
Step 5 Click Apply. Step 6 Click Query. Confirm that the query results are the same as the values that are set. ----End
12.4 Configuring Common Cross-Connections

This section describes how to configure common electrical cross-connections.
12.4.1 Creating Cross-Connections

By creating a normal cross-connection, you can create the intra-board or inter-board route for a single service.
Prerequisite

l For the OptiX OSN 6800, the available cross-connection capacity of a board is related to the slot where the board is installed. For example, when the TQX or NQ2 board is installed in slots 1, 4, 11 or 14, the available cross-connection capacity of the board is 40 Gbit/s; when the TQX or NQ2 board is installed in any other slots, the available cross-connection capacity of the board is 20 Gbit/s. Different boards have different cross-connection capacities. Fore details, see the functions and features of each board as specified in the Hardware Description. If the capacity of the configured services is greater than the available cross-connection capacity, the service configuration fails.

Step 1 When configuring the cross-connection services, first configure the service type of the WDM interface of the OTU. For detailed configuration method, see 12.2 Configuring the Service Type. Step 2 In the NE Explorer, select the NE and choose Configuration > WDM Service Management from the Function Tree. Step 3 Click the WDM Cross-Connection Configuration tab. Click New to display the Create CrossConnection Service dialog box. For parameter descriptions, see 2.8.1 WDM CrossConnection Configuration. Step 4 Select corresponding values for Level and Service Type and set other parameters for the service. 1. The following figure shows the parameters to be set when the board where you want to configure cross-connection services is in compatible mode.
Issue 02 (2011-10-31)
500
2.
The following figure shows the parameters to be set when the board where you want to configure cross-connection services is in standard mode.
3.
If you set Level to ODUflex, you also need to set ODUFlex Timeslots.
Issue 02 (2011-10-31)
501
NOTE
For details about the standard mode and ODUflex, see 2.1.3 Board Model (Standard Mode and Compatible Mode) and 2.1.4 ODUflex.
Step 5 Click OK. A Operation Result dialog box appears telling you that the operation was successful. Step 6 Click Close. ----End

Step 1 When configuring the cross-connection services, first configure the service type of the WDM interface of the OTU. For detailed configuration method, see 12.2 Configuring the Service Type. Step 2 In the NE Explorer, select the NE and choose Configuration > Electrical Cross-Connection Service Management from the Function Tree. Step 3 Click the Electrical Cross-Connection Configuration tab. Click New and the Create CrossConnection Service dialog box is displayed. For parameter descriptions, see 2.8.1 WDM CrossConnection Configuration. Step 4 Select corresponding values for Service Level and Service Type and set other parameters for the service. Step 5 Click OK and the created cross-connection is displayed in the user interface. ----End
12.4.2 Activating Cross-Connections

Do as follows to apply cross-connections to a board.
Prerequisite
The cross-connections must be created and inactive.


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 Operation 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

For some boards the transmit and receive timeslots of the client-end services should be configured during service creation.
Prerequisite
You must be an NM user with "NE operator" authority or higher. Applies to the TQM, TOM, LQM, LQMD, LOM, LQMS, LDMD, LDM, LDMS.


Step 1 In the NE Explorer, select the NE and choose Configuration > WDM Service Configuration from the Function Tree.
Step 2 Click Query to query the status of configured services for each port on the board. Step 3 Choose the port, double-click Timeslot Configuration Mode and select Automatically Assign.
NOTE
When Timeslot Configuration Mode is set as Automatically Assign, Timeslot Configuration Mode of the receive end and transmit end in the same direction of the service must be set as Automatically Assign, and Send Timeslots and Receive Timeslots do not need to be set. When Timeslot Configuration Mode is set as Manual, you can set parameters, such as Send Timeslots and Receive Timeslots. l The format of timeslots can be one of the following two: l 1, 2, 3, 4: Indicates that four (1-4) timeslots are used. l 1-4: Indicates that four (1-4) timeslots are used. l Please obey the following rules during service configuration: l The transmit and receive timeslots should be specified for each board. l For each board, the same timeslot in the same direction cannot be shared by multiple services. l In one direction of one service, the timeslot of the receive end must be the same as that of the transmit end. l Timeslots must be set again after the service type is changed. For details, see A.22 Service Timeslot (WDM Services).
Step 4 Click Apply. Step 5 Click Query. The configured timeslots of the board are displayed in the interface. ----End
12.6 Configuring SDH Cross-Connections

This topic describes how to configure SDH cross-connections.
12.6.1 Querying the Lower Order Cross-Connection Capacity

The lower order cross-connection capacity of the OptiX OSN 8800 determines the lower order access capability of the equipment. Therefore, when configuring an SDH service, consider whether the lower order cross-connection capacity of the equipment is sufficient.
Prerequisite
You are an NMS user with " Monitor Group" authority or higher.


Step 1 In the NE Explorer, select the NE and choose Configuration > Query Low Crossing Capacity from the Main Menu. Step 2 Click Query. ----End
12.6.2 Creating SDH Cross-Connections

To groom SDH services, the SDH service cross-connections between line boards must be created.
Prerequisite
You must be an NM user with "NE operator" authority or higher. The cross-connect board and the clock board must be configured.


Step 1 In the NE Explorer, select the NE and choose Configuration > SDH Service Configuration from the Function Tree. Step 2 Click Query to query SDH services from the NE. Step 3 In the Confirm dialog box, click OK. In the Operation Result dialog box, click Close. Step 4 Click Create and set the required parameters in the Create SDH Service dialog box that is displayed. For the meaning of parameters, see 9.7.1 SDH Service Configuration.
Issue 02 (2011-10-31)
505

NOTE
l If you activate the service immediately, the service configuration data is applied to NEs. l If you do not activate the service, the service configuration data is only saved on the U2000.
Step 5 Click OK. Step 6 In the Operation Result dialog box, click Close. ----End
12.7 Configuring Path Overhead for SDH Services

The path overhead is configured for services, which helps network maintenance personnel to maintain the network.
12.7.1 Configuring Trace Byte

The trace byte is used by the receive end to confirm if it has a continuous connection with the transmit end. The trace byte can be set to any identical character for equipment of the same vendor but if the equipment is from different vendors, the trace byte must be set to the characters previously specified to ensure successful interconnection.
Prerequisite
You are an NMS user with "Maintenance Group" authority or higher. When the cross-connections of the VC12, VC3 or VC4 levels are created, you can query or set the trace byte of the VC12, VC3 or VC4.

Trace bytes are used to trace the connection status between the receive end and transmit end. For details, see 9.2.1 Trace Byte.
NOTE
The settings of J0 and J1 bytes must be consistent on the transmit and receive sides; otherwise, J0_MM and HP_TIM are generated at the receive equipment.

Step 1 Select the type of the trace byte. If you need to configure Perform the following operations J0 byte In the NE Explorer, select a board and choose Configuration > Overhead Management > Regenerator Section Overhead from the Function Tree.
Issue 02 (2011-10-31)
506
If you need to configure Perform the following operations J1 byte In the NE Explorer, select a board and choose Configuration > Overhead Management > VC4 Path Overhead from the Function Tree. Click the Trace Byte J1 tab.
Step 2 Right-click the trace byte and choose the input mode. If you choose Perform the following operations
Copy All Form Received Click Copy All Form Received. Manual Input Click Manual Input and the Please input the overhead byte dialog box is displayed. Choose Byte Mode and Input Mode and enter the value of the trace byte. Click OK.
NOTE
l Choose Copy All Form Received and the contents of the trace byte received are automatically copied to the table. l Choose Manual Input to customize the contents of the trace byte.
Step 3 Click Apply. The Confirm dialog box is displayed. Step 4 Click OK. A prompt appears telling you that the operation was successful. Click Close. ----End
12.7.2 Configuring C2 Byte

The C2 byte indicates the multiplexing structure of the VC frame and the service types contained in the VC frame.
Prerequisite
You are an NMS user with "Maintenance Group" authority or higher. The cross-connection must be created on the NE.

NOTE
The C2 byte settings on the transmit and receive ends must be consistent. Otherwise, higher order path signal label mismatch (HP_SLM) alarm may occur on the receive-end equipment.
Issue 02 (2011-10-31)
507

Step 1 Select the service level of the C2 byte. If the service level of the C2 byte is Perform the following operations VC4 In the NE Explorer, select a board and choose Configuration > Overhead Management > VC4 Path Overhead from the Function Tree. Click the Signal Flag C2 tab. In the NE Explorer, select a board and choose Configuration > Overhead Management > VC3 Path Overhead from the Function Tree. Click the Signal Flag C2 tab.
VC3
Step 2 Set the values of C2 to be Sent and C2 to be Received. Step 3 Click Apply and the Confirm dialog box is displayed. Step 4 Click OK and a prompt appears telling you that the operation was successful. Click Close. ----End
12.8 Configuring the Board Mode

The board supports different functions in different board modes. Set the board mode of the board properly according to the actual requirements. For example, when the ND2 board is used as a regeneration board, set the board mode of the ND2 board to the regeneration mode.
Prerequisite
You must be an NM user with "NE operator" authority or higher. The necessary OTU boards must be created.


Step 1 In the NE Explorer, select the desired board and choose Configuration > WDM Interface from the Function Tree. Step 2 Click By Board/Port(Channel), Select Board from the drop-down list. Step 3 Double-click Board Mode to choose the desired mode from the drop-down list. For details on the values, see A.24 Board Mode (WDM Interface).
NOTE
Issue 02 (2011-10-31)
508
Step 4 Click Apply. Step 5 Click Query. Confirm that the query results are the same as the values that are set. ----End
12.9 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
You must be an NM user with "NE operator" authority or higher. Applicable to the TBE board of the OptiX OSN 6800 and OptiX OSN 3800. Applicable to the LEX4 and LEM24 boards of the OptiX OSN 8800 and OptiX OSN 6800. Applicable to the EGSH board of the OptiX OSN 8800.

The configuration principles are as follows: l l 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. The configuration of a VLAN group is based on the C-VLAN. 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, flow configuration and ETH OAM configuration. 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. The maximum number of VLAN groups is consistent with the number of board Links. 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.
l l l
CAUTION
Creating a VLAN group may affect the services.
Issue 02 (2011-10-31)
509

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.
NOTE
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 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 the configuration of related parameters, see 10.20.9 Parameters: VLAN Group.
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
12.10 Configuring the Aging Time for MAC Addresses

You can configure the aging time for MAC addresses, to implement the dynamic address aging. The MAC addresses that do not appear again on a transport network during the aging time are regarded as having no route requirements. Then these MAC addresses are deleted from the MAC address table to make space for more MAC addresses.
Issue 02 (2011-10-31)
510
Prerequisite
You must be an NM user with "NE operator" authority or higher. This task is applicable to the TBE and L4G boards for the OptiX OSN 6800 and OptiX OSN 3800. This task is applicable to the LEM24 and LEX4 boards for the OptiX OSN 8800 and OptiX OSN 6800.

l If the aging time is too long, the MAC address table may save many outdated MAC address entries. This may use up the resources of the MAC address table. As a result, the MAC address table may not be updated according to changes on the network. If the aging time is too short, effective MAC address entries may be deleted. As a result, packets that are broadcasted cannot find their destination MAC addresses and performance of the network is affected.

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. 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.
12.11 Configuring MAC Address Filtering

MAC address filtering is a broadband transmission solution intended to alleviate the load of the standby router.
12.11.1 Adding the MAC Address of the Opposite Router

On the Ethernet data board at the standby station, add the MAC address of the opposite router, to implement MAC address filtering at the standby station.
Prerequisite
You must be an NM user with "NE operator" authority or higher. This task is applicable to the TBE and L4G boards for the OptiX OSN 6800 and the OptiX OSN 3800. This task is applicable to the LEM24 and LEX4 boards for the OptiX OSN 8800 and the OptiX OSN 6800.

NOTE
l For the Windows operating system: To complete the operation, set the General tab of the Internet option of the browser as follows: 1. In Internet Temporary Files, click Settings. The Settings dialog box is displayed. 2. In Check for newer version of stored pages, select Every visit to the page. l For the Solaris operating system: 1. Install the flash plug-in. 2. Navigate to Mozilla, and enter about:config in the address bar. In Filter, enter cache. Then, set the Value of browser.cache.disk.enable to true.

Step 1 In the NE Explorer, select an Ethernet data board and choose Configuration > Ethernet Maintenance > Port MAC Address Filtering from the function tree. Step 2 Click New. The Create MAC Address Filter dialog box is displayed. Step 3 Set the MAC Address and click OK. The added MAC address of the opposite router is displayed in the list.
Issue 02 (2011-10-31)
512
----End
12.11.2 Deleting the MAC Address of the Opposite Router

You can delete the MAC address of the opposite router when port MAC address filtering is not required.
Prerequisite
You must be an NM user with "NE operator" authority or higher. This task is applicable to the TBE and L4G boards for the OptiX OSN 6800 and the OptiX OSN 3800. This task is applicable to the LEM24 and LEX4 boards for the OptiX OSN 6800 and the OptiX OSN 8800.


Step 1 In the NE Explorer, select the Ethernet data board and choose Configuration > Ethernet Maintenance > Port MAC Address Filtering from the function tree. Step 2 Select the port from the Port List. Choose the MAC address from the Opposite Router MAC Address List.
Step 3 Click Delete to delete the MAC address. ----End
12.12 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
You must be an NM user with "NE operator" authority or higher. Applicable to the TBE and L4G boards of the OptiX OSN 6800 and OptiX OSN 3800. Applicable to the LEX4 and LEM24 boards of the OptiX OSN 8800 and OptiX OSN 6800. Applicable to the EGSH board of the OptiX OSN 8800. The mirror listener port should contain no Ethernet service, and has not been aggregated.

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.

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.
Issue 02 (2011-10-31)
514

NOTE
l For the EGSH, LEX4, LEM24 and TBE board, you can set Uplink Listened Port or Downlink Listened Port, and the two ports cannot be set at the same time. l For the L4G boards, only Uplink Listened Port is supported. 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. The Operation Result dialog box is displayed. Click Close. ----End
12.13 Diagnosing Ethernet Protocol Faults

When the Ethernet protocol operates abnormally, the U2000 diagnoses the protocol fault, displays the diagnosis contents, and restores the normal operation of the Ethernet protocol.
Prerequisite
You must be an NM user with "NE operator" authority or higher. Applies to the TBE, L4G board of the OptiX OSN 6800 and the OptiX OSN 3800. Applies to the LEX4, LEM24 board of the OptiX OSN 6800 and the OptiX OSN 8800.

The protocol types that can be diagnosed include 802.1agOAM, 802.3ahOAM, LAG, DLAG, RSTP, IGMP Snooping and LCAS. For the L4G board, the 802.1agOAM, 802.3ahOAM and DLAG protocols are not supported.

Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Maintenance > Protocol Fault Management from the Function Tree. Step 2 Click the Protocol Type tab and click Diagnosis. The user interface of the U2000 displays the diagnosis result. Step 3 Select a protocol in the Protocol Type and click Diagnosis. The user interface of the U2000 displays the diagnosis result. ----End
12.14 Configuring Non-Intrusive Monitoring

Non-intrusive monitoring indicates that the board monitors the overhead, however, does not handle it, thus the service is not affected. The non-intrusive monitoring is performed for the overheads that are transmitted through the intermediate nodes between the nodes where the overhead bytes are added or dropped.
Prerequisite
You must be an NMS user with "NE operator" authority or higher. The board must be created.


Step 1 In the NE Explorer, select the required board and choose Configuration > OTN Overhead Management > PM Overhead the Function Tree. Step 2 Select the required port on the board and double-click Non-Intrusive Monitoring. Then, choose the required value from the drop-down list. For details on the values, see A.36 Non-Intrusive Monitoring. Step 3 Click Apply. Step 4 Click Query. Ensure that the query result is consistent with the configuration. ----End
Issue 02 (2011-10-31)
516
A Parameters Description
A
A.1 Enabled/Disabled A.2 Max. Frame Length A.5 MAC Loopback A.6 PHY Loopback A.7 QinQ Type Area A.8 Port (Ethernet Port Attribute)
Parameters Description
This chapter describes the parameters of all the WDM products of Huawei. Each parameter is described in terms of description, impact on the system, values, configuration guidelines, and relationship with other parameters in detail.
A.3 Non-Autonegotiation Flow Control Mode A.4 Autonegotiation Flow Control Mode
A.9 Port Physical Parameters (Ethernet Port Attribute) A.10 Working Mode A.11 Broadcast Packet Suppression Threshold A.12 Enabling Broadcast Packet Suppression A.13 Default VLAN ID A.14 VLAN Priority A.15 Entry Detection A.16 Tag Identifier A.17 Source Channel (WDM Cross-Connection) A.18 Sink Channel (WDM Cross-Connection Configuration) A.19 Activation Status (WDM Cross-Connection Configuration) A.20 Level (WDM Cross-Connection Configuration) A.21 Direction (WDM Cross-Connection Configuration)
A.22 Service Timeslot (WDM Services) A.23 Service Mode (WDM Interface) A.24 Board Mode (WDM Interface) A.25 Explicit Link A.26 Explicit Node A.27 Excluded Node A.28 Auto-Calculation A.29 Copy after Creation A.30 Level (WDM Trail Creation) A.31 Direction (WDM Trail Creation) A.32 Rate (WDM Trail Creation) A.33 Source (WDM Trail Creation) A.34 Sink (WDM Trail Creation) A.35 OVPN Customer (ASON Trail Management) A.36 Non-Intrusive Monitoring
Issue 02 (2011-10-31)
518
A.1 Enabled/Disabled
Description
The Enabled/Disabled parameter determines whether to enable a port. A port can receive services if this parameter is set to Enabled but cannot receive services if this parameter is set to Disabled.
Impact on the System

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.
Values
Value Range Enabled, Disabled Default Value Disabled
The following table lists the description of each value. Value Enabled Disabled Description Enables a port. In this case, the attributes configured for the port take effect. Disables a port. In this case, the attributes configured for the port becomes invalid and the service at the port is interrupted.
Configuration Guidelines
None.
Relationship with Other Parameters

None.
A.2 Max. Frame Length

Description
Max. Frame Length (Ethernet Port Attribute) parameter specifies the maximum transmission unit (MTU).

This parameter specifies the maximum length of a frame traversing a port. When the length of a frame exceeds the specified maximum frame length, the frame will be discarded or the service will be interrupted.
Values
Board Name TN11LEM24 TN11LEX4 Value Range 1518-9600 Default Value 1522 Unit Byte
Set this parameter based on the actual service configurations. It is recommended to set this parameter to a value that is equal to or greater than the maximum length of a frame that users want to transmit.

This parameter is available only when the Enable Port parameter is set to Enabled.
A.3 Non-Autonegotiation Flow Control Mode

Description
Non-Autonegotiation Flow Control Mode is selected when a port works in nonautonegotiation mode.

Non-autonegotiation flow control cannot take effect if this parameter is set incorrectly.
Values
Board TN11LEM24 TN11LEX4 Value Range Disabled, Enable Symmetric Flow Control, Send Only, Receive Only Default Value Disable
The following table lists the description of each value.

Value Disabled Enable Symmetric Flow Control Send Only Receive Only
Description Disables port flow control at both the transmit and receive ends. Enables symmetric flow control frames (allows transmission and receiving) in non-autonegotiation mode. Enables only transmission of flow control frames in nonautonegotiation mode. Enables only receiving of flow control frames in nonautonegotiation mode.
Set this parameter properly according to actual service configurations.

This parameter is available only when the working mode of an Ethernet port is Nonautonegotiation mode.
A.4 Autonegotiation Flow Control Mode

Description
Autonegotiation Flow Control Mode is selected when a port works in auto-negotiation mode.

Auto-negotiation flow control cannot take effect if this parameter is set incorrectly.
Values
Board Name TN11LEM24 TN11LEX4 Value Range l Disabled l Enable Dissymmetric Flow Control l Enable Symmetric Flow Control l Enable Symmetric/ Dissymmetric Flow Default Value Disabled

Value Disabled Enable Dissymmetric Flow Control Enable Symmetric Flow Control Enable Symmetric/ Dissymmetric Flow
Description Disables port flow control at both the transmit and receive ends. (None) Enables dissymmetric flow control. (Asymmetric > Link Partner) Enables symmetric flow control. (Symmetric) Enables either symmetric or dissymmetric flow control, which is determined in the autonegotiation process. (Asymmetric->Local Device)
Set this parameter properly based on actual service configurations.

This parameter is available only when the working mode of an Ethernet port is Autonegotiation mode.
A.5 MAC Loopback

Description
The MAC Loopback parameter specifies the MAC loopback state at an Ethernet port. With this parameter, users can test whether equipment runs normally by creating a looped path at the MAC layer and then sending and receiving signals over the path.

A MAC loopback is used for fault locating but can interrupt services. When this parameter is set to Inloop, the PHY Loopback parameter is automatically set to Non-Loopback. When the PHY Loopback parameter is set to Inloop, this parameter is automatically set to NonLoopback.
Values
Board TN11LEM24 TN11LEX4 Value Range Non-Loopback, Inloop Default Value Non-Loopback

Value Non-Loopback Inloop
Description Indicates that no loopback is configured. Indicates that an internal loopback is configured for a port. In this case, the port receives packets sent by itself.
l l l l For a GE optical port, GE electrical port, FE optical port, and FE electrical port, an MAC loopback can be set to only inloop. For a 10GE optical port, an MAC loopback can be set to either inloop or outloop. An inloop and an outloop cannot be configured at the same time at a port. By default a loopback is released automatically after it is configured at a port for five minutes.

A.6 PHY Loopback

Description
The PHY Loopback parameter specifies the PHY loopback state at an Ethernet port. With this parameter, users can test whether equipment runs normally by creating a looped path at the PHY layer and then sending and receiving signals over the path.

A PHY loopback is used for fault locating but interrupts services. When this parameter is set to Inloop, the MAC Loopback parameter is automatically set to Non-Loopback. When the MAC Loopback parameter is set to Inloop, this parameter is automatically set to Non-Loopback.
Values
Value Range Non-Loopback, Inloop Default Value Non-Loopback
The following table lists the description of each value. Value Non-Loopback
Issue 02 (2011-10-31)
Description Indicates that no loopback is configured.

523
Value Inloop
Description Indicates that an internal loopback is configured for a port. In this case, the port receives packets sent by itself.
l l l l l For a GE optical port, a PHY loopback can be set to only inloop; for a GE electrical port, a PHY loopback can be set to either inloop or outloop. For a 10GE optical port, a PHY loopback can be set to either inloop or outloop. For an FE optical port, a PHY loopback can be set to only inloop; for an FE electrical port, a PHY loopback can be set to either inloop or outloop. An inloop and an outloop cannot be configured at the same time at a port. By default, a loopback is released automatically after it is configured at a port for five minutes.

A.7 QinQ Type Area

Description
The QinQ Type Area parameter specifies the QinQ type field.

None.
Values
Board Name TN11LEM24 TN11LEX4 Value Range 0x0600-0xFFFF Default Value 0x8100
Set this parameter based on actual service configurations.

None.
A.8 Port (Ethernet Port Attribute)

Description
The Port parameter specifies a port for which tag attributes needs to be set. Users need to set the tag attributes of boards separately.

None.
Values
Value Range ip1-ipN, vctrunk1-vctrunkM Default Value None
The following table lists the description of each value. Value ip1-ipN vctrunk1-vctrunkM Description Represent Ethernet ports. Represent VC-Trunk ports.
None.

None.
A.9 Port Physical Parameters (Ethernet Port Attribute)

Description
The Port Physical Parameters parameter displays the physical parameters of a port, including port enable status, working mode, flow control enable status, MAC loopback, and PHY loopback.

This parameter is read only and does not affect the normal running of a system.
Values
Enable status Value Range Enabled, Disabled Default Value Disabled
The following table lists the description of each value. Value Enabled Disabled Description Enables a port. The attributes configured for a port take effect only after the port is enabled. Disables a port. The attributes configured for a port becomes invalid and the service at the port is interrupted if the port is disabled.
Working mode Board Name TN11LEM24 TN11LEX4 Value Range l Auto-Negotiation l 10M Half_Duplex l 10M Full_Duplex l 100M Half_Duplex l 100M Full_Duplex l 1000M Half_Duplex l 1000M Full_Duplex l 10G Full_Duplex LAN l 10G Full_Duplex WAN Default Value Auto-Negotiation
The following table lists the description of each value. Value Auto-Negotiation 10M Half_Duplex 10M Full_Duplex 100M Half_Duplex 100M Full_Duplex
Issue 02 (2011-10-31)
Description Indicates autonegotiation. Indicates 10M half-duplex. Indicates 10M full-duplex. Indicates 100M half-duplex. Indicates 100M full-duplex.
526
Value 1000M Half_Duplex 1000M Full_Duplex 10G Full_Duplex_LAN 10G_Full_Duplex_WAN
Description Indicates 1000M half-duplex. Indicates 1000M full-duplex. Indicates 10G full-duplex for LAN services. Indicates 10G full-duplex for WAN services.
Flow control enable status Board Name TN11LEM24 TN11LEX4 Value Range l Disabled l Receive Only l Send Only l Enable Symmetric Flow Control Default Value Disabled
The following table lists the description of each value. Value Disabled Receive Only Send Only Enable Symmetric Flow Control Description Disables port flow control at both the transmit and receive ends. Enables only receiving of flow control frames. Enables only transmission of flow control frames. Enables symmetric flow control frames.
MAC loopback, PHY loopback Board Name TN11LEM24 TN11LEX4 Value Range l Non-Loopback l Inloop l Outloop Default Value Non-Loopback
Issue 02 (2011-10-31)
527
Value Non-Loopback Inloop
Description Indicates that no loopback is configured. Indicates that an internal loopback is configured for a port. In this case, the port receives packets sent by itself. Indicates that an external loopback is configured for a port. In this case, the port transmits packets after receiving them.
Outloop
None.

A.10 Working Mode

Description
The Working Mode parameter specifies the working mode for an Ethernet port. With autonegotiation, equipment can automatically determine the optimal combination of working modes of two connected ports. The autonegotiation mode is recommended because it makes maintenance easy. During configuration, ensure that working modes of two connected ports are the same. Services will be interrupted if the working modes of two connected ports are different.

Services will be interrupted if working modes of ports are set incorrectly.
Values
Board Name TN11LEM24 TN11LEX4 Value Range l Auto-Negotiation l 10M Half_Duplex l 10M Full_Duplex l 100M Half_Duplex l 100M Full_Duplex l 1000M Half_Duplex l 1000M Full_Duplex l 10G Full_Duplex LAN l 10G Full_Duplex WAN Default Value Auto-Negotiation
Issue 02 (2011-10-31)
528
The following table lists the description of each value. Value Auto-Negotiation 10M Half_Duplex 10M Full_Duplex 100M Half_Duplex 100M Full_Duplex 1000M Half_Duplex 1000M Full_Duplex 10G Full_Duplex LAN 10G Full_Duplex WAN Description Indicates autonegotiation. Indicates 10M half-duplex. Indicates 10M full-duplex. Indicates 100M half-duplex. Indicates 100M full-duplex. Indicates 1000M half-duplex. Indicates 1000M full-duplex. Indicates 10G full-duplex for LAN services. Indicates 10G full-duplex for WAN services.
Users need to set this parameter based on the actual physical port types and service configurations. For FE electrical ports, this parameter can be set to Auto-Negotiation, 10M Half_Duplex, 10M Full_Duplex, 100M Half_Duplex, or 100M Full_Duplex. For FE optical ports, this parameter must be set to 100M Full_Duplex. For GE optical ports, this parameter can be set to 1000M Half_Duplex or 1000M Full_Duplex. For 10GE optical ports, this parameter can be set to 10G Full_Duplex_LAN or 10G_Full_Duplex_WAN.

A.11 Broadcast Packet Suppression Threshold

Description
The Broadcast Packet Suppression Threshold parameter specifies the percentage of broadcast traffic in the bandwidth of a port. The broadcast packets beyond this percentage will be discarded.

After suppression of broadcast packets is enabled, the flow of broadcast packets will be limited according to the specified threshold. If the traffic of the broadcast packets exceeds the specified threshold, the excess broadcast packets will be discarded.
Values
Value Range 10%-100% Default Value 30%
Value 10% Description Indicates that the broadcast packets can account for a maximum of 10% of the bandwidth of a port. Indicates that the broadcast packets can account for a maximum of 20% of the bandwidth of a port. Indicates that the broadcast packets can account for a maximum of 30% of the bandwidth of a port. Indicates that the broadcast packets can account for a maximum of 40% of the bandwidth of a port. Indicates that the broadcast packets can account for a maximum of 50% of the bandwidth of a port. Indicates that the broadcast packets can account for a maximum of 60% of the bandwidth of a port. Indicates that the broadcast packets can account for a maximum of 70% of the bandwidth of a port. Indicates that the broadcast packets can account for a maximum of 80% of the bandwidth of a port. Indicates that the broadcast packets can account for a maximum of 90% of the bandwidth of a port. Indicates that the broadcast packets can account for a maximum of 100% of the bandwidth of a port.
20%
30%
40%
50%
60%
70%
80%
90%
100%
Issue 02 (2011-10-31)
530

This parameter is available only when Enabling Broadcast Packet Suppression is set to Enabled.
A.12 Enabling Broadcast Packet Suppression

Description
The Enabling Broadcast Packet Suppression parameter determines whether to suppress the traffic of broadcast packets.

After suppression of broadcast packets is enabled, the traffic of broadcast packets will be limited according to the specified threshold. If the traffic of the broadcast packets exceeds the specified threshold, the excess broadcast packets will be discarded.
Values
Value Range Disabled, Enabled Default Value Disabled
The following table lists the description of each value. Value Enabled Disabled Description Indicates that the traffic of broadcast packets is not limited. Indicates that excess broadcast packets will be discarded if the traffic of broadcast packets exceeds the specified threshold.
Set this parameter only when you need to limit the traffic of broadcast services.

Suppression of broadcast packets is implemented only when this parameter is set to Enabled.
Issue 02 (2011-10-31)
531
A.13 Default VLAN ID

Description
The Default VLAN ID parameter specifies a default VLAN ID for a port that transmits untagged packets.

The default VLAN ID of a packet will be stripped when it traverses a HYBRID port.
Values
Value Range 1-4095 Default Value 1
None.

None.
A.14 VLAN Priority

Description
The VLAN Priority parameter specifies the priority of the default VLAN ID of a port.

None.
Values
Value Range 0-7 Default Value 0
None.

None.
A.15 Entry Detection

Description
The Entry Detection parameter determines whether a port detects packets by tag identifier.

None.
Values
Value Range Enabled, Disabled Default Value Enabled
The following table lists the description of each value. Value Enabled Disabled Description Enables a port to detect packets by tag identifier. Disables a port to detect packets by tag identifier. In this case, all packets can traverse the port.
None.

The entry detection states at the ingress and egress ports of a service must be the same.
A.16 Tag Identifier

Description
The Tag Identifier parameter determines whether a port transmits packets with tags. Three types of tag identifier are available: ACCESS, TAG, and HYBRID.
Issue 02 (2011-10-31)
533

Tag Identifier ACCESS TAG HYBRID Impact on Ports Allows a port to transmit only untagged packets. Allows a port to transmit only tagged packets. Allows a port to transmit both untagged and tagged packets.
Values
Value Range ACCESS, TAG, HYBRID Default Value TAG
The following table lists the description of each value. Value ACCESS TAG HYBRID Description Allows a port to transmit only untagged packets. Allows a port to transmit only tagged packets. Allows a port to transmit both untagged and tagged packets.
None.

A tag identifier is valid only for a UNI port.
A.17 Source Channel (WDM Cross-Connection)

Description
The Source Channel parameter is used to query the transmit channel of a certain electrical crossconnect service (unidirectional service flow).

None.
Values
Value Range Slot ID-Board Name-Optical Interface ID-Optical Channel ID Default Value Null
The following table lists the description of each value. Value Slot ID-Board Name-Optical Interface ID-Optical Channel ID Description Slot ID: The ID of the slot on the local NE where the crossconnect board is located. Board Name: The name of the cross-connect board. Optical Interface ID: The ID of the optical interface where the cross-connect services are configured. Optical Channel ID: The ID of the optical channel where the cross-connect services are configured.
None.

None.
A.18 Sink Channel (WDM Cross-Connection Configuration)

Description
The Sink Channel parameter is used to query the receive channel of a certain electrical crossconnect service (unidirectional service flow).

None.
Issue 02 (2011-10-31)
535
Values
Value Range Slot ID - Board Name Optical Interface ID - Optical Channel ID Default Value Null
The following table lists the description of each value. Value Slot ID-Board Name Optical Interface ID - Optical Channel ID Description Slot ID: The ID of the slot on the local NE where the crossconnect board is located. Board Name: The name of the cross-connect board. Optical Interface ID: The ID of the optical interface where the cross-connect services are configured. Optical Channel ID: The ID of the optical channel where the cross-connect services are configured.
None.

None.
A.19 Activation Status (WDM Cross-Connection Configuration)

Description
The Activation Status parameter is used to display whether the service cross-connection configuration is activated. Only when the configuration is activated, can the U2000 deliver the service cross-connection configuration to the NE software.

When Active is selected, the U2000 delivers the information of the service type, source/sink services and service direction that have been configured to the NE software; when Inactive is selected, the U2000 does not deliver the configuration to the NE software. The configuration does not take effect when Inactive is selected during the cross-connection configuration; the configuration takes effect only when Active is selected during the crossconnection configuration.
Values
Value Range Active, Inactive Default Value Active
The following table lists the description of each value. Value Active Inactive Description Indicates that the configuration is activated. The service crossconnection configuration will be delivered to the NE software. Indicates that the configuration is not activated. The service crossconnection configuration will not be delivered to the NE software.
When creating service cross-connections, determine whether to deliver the configuration immediately to the NE software.

When Active is displayed in the Activation Status column, the values of the Source Interface, Sink Interface, Service Type, and Direction parameters will be delivered to the NE software.
A.20 Level (WDM Cross-Connection Configuration)

Description
The Level parameter is used to differentiate the service types configured when electrical crossconnections are configured. The OptiX OSN 8800 supports Any, GE, ODU0, ODU1, ODU2, ODU3, ODUflex, and OTU1 services. The OptiX OSN 6800 supports Any, GE, ODU1, ODU2, and OTU1 services. The OptiX OSN 3800 supports Any, GE, ODU1, and OTU1 services.

When you configure an electrical cross-connection, if the level of the services to be crossconnected is set incorrectly, the configuration of the electrical cross-connection will fail and the cross-connect services cannot be configured successfully.
Issue 02 (2011-10-31)
537
Values
Value Range ANY, GE, ODU0, ODU1, ODU2, ODU5G, ODU3, OTU1, ODUflex Default Value -
The following table lists the description of each value. Value ANY Description Includes the following services: 10GE, FE, STM-1, STM-4, STM-16, STM-64, STM-254, OC-3, OC-12, OC-48, OC-192, OC-768, FC50, FC100, FC200, FC100(Slice), FC200(Slice), FICON(Slice), FICONEXPRESS(Slice), DVB-ASI, GE(Slice), FC400, FC1000, FICON, FICON Express, HD-SDI, SDI, ESCON, FDDI, ISC 1G, ISC 2G, FICON4G, ETR, CLO Indicates the data GE services. Indicates a 1.25 Gbit/s signal. Indicates a 2.5 Gbit/s signal. Indicates a 10 Gbit/s signal. Indicates a 40 Gbit/s signal. Indicates that one ODU5G service encapsulates four GE services. The ODU5G services can be accessed by the L4G board or the LQG board. 1.25Gbit/s to 10Gbit/s (n x 1.25Gbit/s). Indicates a 2.5 Gbit/s signal.
GE ODU0 ODU1 ODU2 ODU3 ODU5G
ODUflex OTU1
NOTE
For the services listed in the table above, the ODU5G service is used only for intra-board fixed crossconnections. For new cross-connections, only GE, Any, ODU0, ODU1, ODU2, ODU3, ODUflex and OTU1 services can be used. The LSX, LSXR, TMX, LOM, LSXL, and LSXLR boards do not support electrical cross-connections but fixed cross-connections.
The value of the parameter varies according to boards. For details, see the Hardware Description.
Issue 02 (2011-10-31)
538

The cross-connect level must be configured before the Sink Port parameter and optical ports are configured. When you configure electrical cross-connections by using the cross-connect board, the services at the source and sink nodes configured with cross-connections must be consistent. The fixed cross-connection within a board does not need to be configured manually. It is configured automatically by the U2000.
A.21 Direction (WDM Cross-Connection Configuration)

Description
The Direction parameter indicates the service direction mode when the service cross-connection is configured. It can be set to either Unidirectional or Bidirectional.

If the service cross-connection is configured in only one direction, only the services in that direction can be configured successfully. The services in the other direction, however, cannot be configured successfully.
Values
Value Range Unidirectional, Bidirectional. Default Value Unidirectional
The following table provides a description of each value. Value Unidirectional Bidirectional Description When the received and transmitted services travel through different route, the services are unidirectional. When the received and transmitted services travel through the same route, the services are bidirectional.
The values of the parameter are different according to the boards. For details, see the Hardware Description.

None.
A.22 Service Timeslot (WDM Services)

Description
The Service Timeslot parameter is used to configure the number of timeslots of a service. The number must be within the timeslot range of the service type.

None.
Values
Value Range 1-16 (If the number is 0, it indicates that the timeslot is unavailable.) Default Value Select a value based on the service type.
The following table lists the required timeslots of each board for the OptiX OSN 6800, the OptiX OSN 3800 and OptiX OSN 8800. Supported Board LDM/LDMD/LDMS/ LQM/LQMD/LQMS/ TOM/TQM Service Type FE GE OTU-1 STM-1 STM-4 STM-16 OC-3 OC-12 OC-48 FC100 FC200 FICON FICON Express
Issue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
Required Timeslots 1 7 16 1 4 16 1 4 16 6 12 6 12
540
Supported Board
Service Type HD-SDI DVB-ASI SDI ESCON FDDI
Required Timeslots 11 2 3 2 1 1 1 2 4 1 4 2 1 2 2 4
LOM
GE FC100 FC200 FC400 FICON FICON4G FICON Express ISC 1G ISC 2G InfiniBand 2.5Ga InfiniBand 5Ga
a: Only the TN12LOM board supports the InfiniBand 2.5G and InfiniBand 5G services.
l l l
The number of timeslots required by a service is the number of unoccupied timeslots required by the service type. For multiple timeslots, the timeslots with larger numbers are used with precedence. It is recommended to use contiguous timeslots. Several configuration methods are provided for configuring multiple timeslots. The following description considers configuring four timeslots as an example. "1-4" indicates configuration of four contiguous timeslots numbered 1, 2, 3, and 4. "1, 3, 6, 9" indicates configuration of four noncontiguous timeslots. "1-3, 6" indicates configuration of four timeslots where three are contiguous.

The timeslots in the above table are determined by the value range and the number of timeslots required.
Issue 02 (2011-10-31)
541
A.23 Service Mode (WDM Interface)

Description
The Service Mode parameter sets the service mode of a board.

None.
Values
For the L4G, LDGS, LDGD, and LQG Value Range OTN, SDH Default Value OTN
For the ND2, NQ2, NS2 Value Range ODU0, ODU1, ODU2, Automatic Default Value Automatic
For the NS3 Value Range ODU0, ODU1, ODU2, Mix, Automatic Default Value Automatic
For the LQM, TN12LQMD, TN12LQMS, TOM, THA, TOA, LOA and TQM Value Range Client Mode, OTN Mode Default Value Client Mode
l In the case of the L4G, LDGS, LDGD, and LQG boards: The mode of line-side services of boards on an NE at the local end should be the same as that at the opposite end. When a local-end board need be connected to an SDH service board of another product, the mode of line-side services should be set to SDH.
Issue 02 (2011-10-31)
In the case of the LQM, LQMD, LQMS, TOM, THA, TOA, LOA and TQM boards: When the client side accesses OTN services, set this parameter to OTN Mode. When the client side accesses other services, set this parameter to Client Mode.

None.
A.24 Board Mode (WDM Interface)

Description
The Board Mode parameter is used to set the board mode of a board depending on the service application scenario.

The signal flow, work mode, and functions of a board vary with the board mode. Therefore, switching between different board modes interrupts the active services.
Values
The following table lists the work modes of the ECOM board. Value Range Service Mode, HUB Mode Default Value HUB Mode
The following table lists the description of each value of the ECOM board. Parameter Value Service Mode HUB Mode Remarks Supports converging 8 x FE services to 1 x GE service. Supports converging 8 x FE services to 1 x FE service.
The following table lists the work modes of the TN12LQMS board. Value Range NS1 Mode, LQM Mode Default Value LQM Mode
The following table lists the description of each value of the TN12LQMS board.
Issue 02 (2011-10-31)
543
Parameter Value NS1 Mode LQM Mode
Remarks As a line board, this board adds and drops OTU1 signals in conjunction with another tributary board. As a tributary/line integrated board, this board converges four channels of Any signals into a channel of OTU1 signals.
NOTE
The NS1 Mode field is valid only when the TN12LQMS board is housed in an OptiX OSN 6800 subrack or OptiX OSN 3800 subrack.
The following table lists the work modes of the TN11TOM. Value Range Cascading Mode, Non-cascading Mode Default Value Non-cascading Mode
The following table lists the description of each value of the TN11TOM. Parameter Value Cascading Mode Remarks Only RX7/TX7 and RX8/TX8 can be used as WDM side optical ports. The board supports multiplexing up to six channels of Any signals into one channel of OTU1 signals. RX1/TX1-RX8/TX8 can be used as WDM-side optical ports. The board supports multiplexing up to four channels of Any signals into two channels of OTU1 signals.
Non-cascading Mode
The following table lists the work modes of the TN11LSXR/TN11LSXLR/TN12LSXLR. Value Range Electrical Relay Mode, Optical Relay Mode Default Value Electrical Relay Mode
The following table lists the description of each value of the TN11LSXR/TN11LSXLR/ TN12LSXLR. Parameter Value Electrical Relay Mode Optical Relay Mode Remarks In the case of an optical-layer system, however, the regeneration mode must be set to Optical Relay Mode.
Issue 02 (2011-10-31)
544
The following table lists the work modes of the TN12ND2/TN52ND2/TN53ND2/TN53NQ2/ TN54NQ2/TN54NS3. Value Range Line Mode, Electrical Relay Mode, Optical Relay Mode Default Value Line Mode
The following table lists the description of each value of the TN12ND2/TN52ND2/TN53ND2/ TN53NQ2/TN54NQ2/TN54NS3. Parameter Value Line Mode Electrical Relay Mode Optical Relay Mode Remarks The board works as a line board. The board works as a wavelength conversion relay unit. In the case of an optical-layer system, however, the regeneration mode must be set to Optical Relay Mode.
Select the board mode according to the actual service application scenario.

None.
A.25 Explicit Link

Description
The Explicit Link parameter specifies a link that a service must traverse when a trail is created, optimized, or precalculated.

A service cannot be created successfully if a specified explicit link is incorrect or the explicit links are not specified sequentially.
Values
Value Range Links on a network Default Value None

Value Links on a network
Description Lists all links available at a node.
In general, only one explicit link is available on an NE. In addition, the explicit link can be set only at the egress port on the link that a service traverses.

A link can be specified only after a node is specified.
A.26 Explicit Node

Description
The Explicit Node parameter specifies a node that a service must traverse when a trail is created, optimized, or precalculated.

A service cannot be created successfully if a specified explicit node is incorrect or the explicit nodes are not specified sequentially.
Values
Value Range Nodes on a network Default Value None
The following table lists the description of each value. Value Nodes on a network Parameter Specifies a node that a service must traverse.
Check whether the number of nodes that an ASON service traverses exceeds the maximum number of nodes. In the process of creating an ASON service, the ASON software by default considers that the maximum hops of the ASON service is 64. That is, the maximum number of nodes that an ASON service travels is 65. In general, only one explicit node is available on an NE.

None.
A.27 Excluded Node

Description
The Excluded Node parameter specifies a node that a service cannot traverse when a trail is created, optimized, or precalculated.

None.
Values
Value Range Nodes on a network Default Value None
The following table lists the description of each value. Value Nodes on a network Parameter Specifies a node that a service cannot traverse.
Set this parameter according to customer requirements.

None.
A.28 Auto-Calculation
Description
The Auto-Calculation parameter enables auto-calculation of the trails that comply with the specified level, direction, rate, source, sink, and route constraints.

If auto-calculation of trails fails, it indicates that a service that complies with the specified level, direction, rate, source, sink, and route constraints does not exist.
Values
Value Range None Default Value None
None.

After this parameter is selected, the system automatically calculates the trails that comply with the level, direction, rate, source, sink, and route constraints specified for a service.
A.29 Copy after Creation

Description
The Copy after Creation parameter specifies the source and sink nodes for a service and the route constraints for creating a service. Users can create services in batches if the services have the same source node and the same sink node and comply with the same specified route constraints.

None.
Values
Value Range Source, Sink Default Value Null
The following table lists the description of each value. Value Source Sink Description Lists all nodes that can function as the source of a service complying with the specified constraints. Lists all nodes that can function as the sink of a service complying with the specified constraints.
Issue 02 (2011-10-31)
548

The services created in batches by using this parameter have the same level, direction, and rate. In addition, the services comply with the same route constraints.
A.30 Level (WDM Trail Creation)

Description
The Level parameter determines the type of a service configured during configuration of an electrical cross-connection, OCh trail, or Client trail. ODU0, ODU1, ODU2, ODU3, and OCh levels are supported.

An electrical cross-connection cannot be configured successfully if this parameter is set incorrectly and thus a service cannot be provisioned.
Values
Value Range ODU0, ODU1, ODU2, ODU3, OCh, Client Default Value Client
The following table lists the description of each value. Value ODU0 ODU1 ODU2 ODU3 OCh Client Description Indicates a 1.25 Gbit/s signal. Indicates a 2.5 Gbit/s signal. Indicates a 10 Gbit/s signal. Indicates a 40 Gbit/s signal. Indicates the optical-layer signal. Indicates the client-side signal.
None.

l
Issue 02 (2011-10-31)
Level must be set prior to Sink Port.

l l
When configuring an electrical cross-connection implemented by a cross-connect board, ensure that the service levels at the source and sink ends are the same. The fixed cross-connections on a board do not need to be configured manually; instead, they are configured automatically by the NMS.
A.31 Direction (WDM Trail Creation)

Description
The Direction parameter indicates the direction of a trail.

None.
Values
Value Range Unidirectional, Bidirectional Default Value Bidirectional
The following table lists the description of each value. Value Unidirectional Bidirectional Description Indicates that the source can transmit services, and the sink can receive services. Indicates that the source and sink can receive and transmit services.
Ensure that a created ASON service is bidirectional.

None.
A.32 Rate (WDM Trail Creation)

Description
The Rate parameter specifies the rate for a trail. The rate for an OCh-level ASON trail cannot be specified.

If the service rates for the boards that the service traverse are different, the service will be interrupted.
Values
Value Range GE, 10GE, 10GELAN, 10GEWAN, OTU1, OTU5G, OTU2, OTU3, ANY, FC25, FC50, FC100, FC200, OC-3, OC-12, OC-48, OC-192, OC-768, STM-1, STM-4, STM-16, STM-64... Default Value The default rate varies according to service levels.
l l Ensure that the service rates for upstream and downstream boards are the same. Set this parameter according to the actual service mapping mode and signal rate. The parameter value varies according to boards. For details, see the Hardware Description.

The value of this parameter depends on the service level.
A.33 Source (WDM Trail Creation)

Description
The Source parameter specifies the source of a trail. For an optical service, the parameter value is expressed as optical NE-NE-subrack-slot-boardport-wavelength number/wavelength/frequency. For an electrical service, the parameter value is s expressed as optical NE-NE-subrack-slotboard-port.

During configuration of a service, the source, including NE, subrack, slot, board, and port, must be specified for the service. A source slot must be specified if a board-level optical crossconnection needs to be configured. If no source slot is specified, a board-level optical crossconnection cannot be created. In addition, a configured board-level optical cross-connection will become invalid if a source port is configured incorrectly.
Issue 02 (2011-10-31)
551
Values
Value Range Source NE, source subrack, source slot, source board, source port, null Default Value Null
The following table lists the description of each value. Value Source NE Source subrack Source board Description Specifies a node where a service is added. Specifies a subrack at the node where a service is added. Specifies the type of a board where the source edge port is located. Specifies a source port for a board-level optical crossconnection. Indicates that no source is configured for an optical cross-connection.
Source port
Null
l l Only one source port can be set for one board-level optical cross-connection. A MON port cannot be used as the source port for a board-level optical cross-connection.

This parameter is available only when a source slot is specified.
A.34 Sink (WDM Trail Creation)

Description
The Sink parameter specifies the sink of a trail. For an optical service, the parameter value is expressed as optical NE-NE-subrack-slot-boardport-wavelength number/wavelength/frequency. For an electrical service, the parameter value is s expressed as optical NE-NE-subrack-slotboard-port.

During configuration of a service, the sink, including NE, subrack, slot, board, and port, must be specified for the service. A sink slot must be specified if a board-level optical cross-connection needs to be configured. If no sink slot is specified, a board-level optical cross-connection cannot be created. In addition, a configured board-level optical cross-connection will become invalid if a sink port is configured incorrectly.
Values
Value Range Sink NE, sink subrack, sink slot, sink board, sink port, null Default Value Null
The following table lists the description of each value. Value Sink NE Sink subrack Sink board Description Indicates a node where a service is dropped. Specifies a subrack at a node where a service is dropped. Specifies the type of a board where the sink edge port is located. Specifies a sink port for a board-level optical crossconnection. Indicates that no sink is configured for an optical cross-connection.
Sink port
Null
l l Only one sink port can be set for one board-level optical cross-connection. A MON port cannot be used as a sink port for a board-level optical cross-connection.

This parameter is available only when a sink slot is specified.
Issue 02 (2011-10-31)
553
A.35 OVPN Customer (ASON Trail Management)

Description
The OVPN (Optical Virtual Private Network) parameter specifies a customer on an optical virtual private network (OVPN). The OVPN classifies different OVPN customers by resource type. The timeslot resources allocated to an OVPN customer can be used only by the services of this OVPN customer.

None.
Values
Value Range OVPN customer resources Default Value None
The following table lists the description of the value. Value OVPN customer resources Description The resources for TE links are classified into three types: shared resources, exclusive resources, and OVPN customer resources.
This parameter is available on the NMS only when Level is set to OCh, Direction is set to Bidirectional, and SPC First is selected.

l l l The OVPN function is available only when OVPN is enabled for all ASON NEs in an ASON domain and the OVPN license can be enabled on the NMS. OVPN NMS user: This user can use the OVPN customer resources and shared resources allocated by user admin. User admin: This is the default super user of the NMS and is the only user that can manage OVPN customers and allocate OVPN resources. This user can use all TE link resources.
Issue 02 (2011-10-31)
554
A.36 Non-Intrusive Monitoring

Description
The Non-Intrusive Monitoring parameter provides an option for enabling or disabling the nonintrusive monitoring. When the client side of a board receives OTN signals, the board does not need to terminate and then regenerate PM or TCM overheads. In this case, the non-intrusive monitoring function can be enabled to monitor the received OTN signals. The function does not affect service signals.

When the non-intrusive monitoring function is enabled for an optical interface on a board, the board detects the QoS of the service and reports alarms if the QoS is poor. Other modules perform operations according to the detected QoS, such as protection switching. If the non-intrusive monitoring function is disabled, the services at the optical port are transmitted transparently.
Values
Value Range Enabled, Disabled Default Value Disabled
The following table lists the description of each value. Value Range Disabled Enabled Description Indicates that the non-intrusive monitoring function is disabled. Indicates that the non-intrusive monitoring function is enabled.
Set this parameter according to the actual service requirements and the user requirement.

None
Issue 02 (2011-10-31)
555
B Glossary
B
A
AC access control list ACK acknowledgement See alternating current See acknowledgement
Glossary
A list of entities, together with their access rights, which are authorized to have access to a resource. 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. See access control list 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 refers to the wavelength that carries the add/drop services in the OADM equipment. 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. See add/drop multiplexer 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. 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. See asymmetric digital subscriber line See automatic gain control
ACL add/drop multiplexer
Add/drop wavelength Address Resolution Protocol
ADM administrative unit
Administrator ADSL AGC
Issue 02 (2011-10-31)
556
B Glossary
AID AIS alarm
access identifier See alarm indication signal 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. The cable for generation of visual or audio alarms. The shunt-wound output of the alarm signals of several subracks or cabinets. 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. 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 cable alarm cascading alarm cause
alarm indication
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. 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. 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. 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 See automatic level control 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. 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. See automatic laser shutdown Electric current that reverses its direction of flow (polarity) periodically according to a frequency measured in hertz, or cycles per second.
alarm severity
alarm suppression
alarm type
ALC ALC link
ALC node
ALS alternating current
Issue 02 (2011-10-31)
557
B Glossary
American National Standard Institute American Standard Code for Information Interchange ANSI antistatic floor APD APE APID application-specific integrated circuit
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 - the standard system for representing letters and symbols. Each letter or symbol is assigned a unique number between 0 and 127. See American National Standard Institute A floor that can quickly release the static electricity of the object contacting it to prevent accumulated static electricity See avalanche photodiode automatic power equilibrium access point identifier 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. See automatic protection switching See Address Resolution Protocol 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. See American Standard Code for Information Interchange amplified spontaneous emission See application-specific integrated circuit See automatically switched optical network 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. 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. autonomously generated correlation tag See Asynchronous Transfer Mode See administrative unit 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.
APS ARP arrayed waveguide grating ASCII ASE ASIC ASON asymmetric digital subscriber line
Asynchronous Transfer Mode
ATAG ATM AU auto-negotiation
Issue 02 (2011-10-31)
558
B 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. See arrayed waveguide grating
AWG
B
background block error ratio backup 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. 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. 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. See broadband access server 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. A connector used for connecting two coaxial cables. background block error See background block error ratio See boundary clock Backward Defect Indication backward error indication See bit error rate backward incoming alignment error
bandwidth
BAS basic input/output system bayonet-neillconcelman BBE BBER BC BDI BEI BER BIAE
Issue 02 (2011-10-31)
559
B 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]. See basic input/output system See bit-interleaved parity See bit interleaved parity order 8 An incompatibility between a bit in a transmitted digital signal and the corresponding bit in the received digital signal. Ratio of received bits that contain errors. BER is an important index used to measure the communications quality of a network. 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. 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. See building integrated timing supply best master clock See bayonet-neill-concelman See bill of material A clock with a clock port for each of two or more distinct PTP communication paths. See bridge protocol data unit board-level protection switching 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. The action of transmitting identical traffic on the working and protection channels simultaneously. 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. A means of delivering information to all members in a network. The broadcast range is determined by the broadcast address.
BIOS BIP BIP-8 bit error bit error rate bit interleaved parity order 8 bit-interleaved parity
BITS BMC BNC BOM boundary clock BPDU BPS bridge protocol data unit
bridging broadband access server broadcast
Issue 02 (2011-10-31)
560
B Glossary
broadcast service building integrated timing supply
The unidirectional services from one service source to multiple service sinks. 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. Backbone WDM System
BWS
C
cable tie capex capital expenditure The tape used to bind the cables. See 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. See committed access rate See committed burst size See connectivity check connection control interface See continuity check message chromatic dispersion See Code Division Multiple Access See customer edge See European Committee for Electrotechnical Standardization
CAR CBS CC CCI CCM CD CDMA CE CENELEC
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 CF CGMP channel The system that gathers all the information about alarms into a certain terminal console. See compact flash Cisco Group Management Protocol 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). The center-to-center difference in frequency or wavelength between adjacent channels in a WDM device. See committed information rate
channel spacing CIR
Issue 02 (2011-10-31)
561
B Glossary
CIST CLEI CLNP CLNS clock synchronization
Common and Internal Spanning Tree common language equipment identification connectionless network protocol connectionless network service 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 CM CMEP CMI coarse wavelength division multiplexing The method to keep the time on each node being synchronized with a clock source in a network. See configuration management connection monitoring end point coded mark inversion 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. 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 burst size
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 (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. 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.
compact flash
concatenation
Issue 02 (2011-10-31)
562
B 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. 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.
configuration management
configure congestion connecting plate connection point
To set the basic parameters of an operation object. An extra intra-network or inter-network traffic resulting in decreasing network service efficiency. A metallic plate which is used to combine two cabinets. 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. Ethernet CFM can detect the connectivity between MEPs. The detection is achieved by each MEP transmitting a Continuity Check Message (CCM) periodically. CCM is used to detect the link status. 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.
connectivity check continuity check message convergence
convergence service CORBA corrugated pipe CPLD CPU CRC CSA CSES CSMA CST current alarm current performance data
A service that provides enhancements to an underlying service in order to provide for the specific requirements of the convergence service user. See Common Object Request Broker Architecture Used to protect optical fibers. Complex Programmable Logical Device See central processing unit See cyclic redundancy check Canadian Standards Association consecutive severely errored second carrier sense multiple access Common Spanning Tree An alarm not handled or not acknowledged after being handled. 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 02 (2011-10-31)
563
B Glossary
customer edge CWDM cyclic redundancy check
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. See coarse wavelength division multiplexing 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 Data backup data communication network data communications channel destination access point identifiers 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. A communication network used in a TMN or between TMNs to support the Data Communication Function (DCF). 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. distribute board protect system See data communications channel See dispersion compensation fiber See dispersion compensation module A frame which is used to hold the DCM (Dispersion Compensation Module). See data communication network See digital distribution frame See digital data network A device that separates signals that have been combined by a multiplexer for transmission over a communications channel as a single signal. 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. 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. See Dynamic Host Configuration Protocol
DBPS DCC DCF DCM DCM frame DCN DDF DDN demultiplexer dense wavelength division multiplexing device set
DHCP
Issue 02 (2011-10-31)
B Glossary
diamond-shaped nut digital data network
A type of nut that is used to fasten the wiring frame to the cabinet. 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. 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. 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. 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. A module, which contains dispersion compensation fibers to compensate for the dispersion of transmitting fiber. 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. 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. See distributed link aggregation group See demultiplexer Dual Node Interconnection A logical subscriber group based on which the subscriber rights are controlled. differential quadrature phase shift keying dynamic random database differential phase return to zero Differentiated Services Code Point dispersion slope compensation rate See digital subscriber line access multiplexer Digital Signal Processing Data Terminal Equipment See dual tone multiple frequency data terminal ready 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. 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.
digital distribution frame digital subscriber line access multiplexer dispersion compensation fiber dispersion compensation module Distance Vector Multicast Routing Protocol distributed link aggregation group
DLAG DMUX; DEMUX DNI domain DQPSK DRDB DRZ DSCP DSCR DSLAM DSP DTE DTMF DTR dual tone multiple frequency dual-ended switching
Issue 02 (2011-10-31)
565
B Glossary
DVB DVMRP DWDM
Digital Video Broadcasting See Distance Vector Multicast Routing Protocol See dense wavelength division multiplexing
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 EAPE EBS ECC EDFA eDQPSK EFM ejector lever electric supervisory channel electromagnetic compatibility End to End enhanced automatic power pre-equilibrium See excess burst size See embedded control channel See erbium doped fiber amplifier enhanced differential quadrature phase shift keying See Ethernet in the first mile A lever for removing circuit boards from an electronic chassis. 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 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. Any electromagnetic disturbance that interrupts, obstructs, or otherwise degrades or limits the effective performance of electronics/electrical equipment. 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. 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). 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. See electromagnetic compatibility See electromagnetic interference See element management system 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. See Ethernet private line
electromagnetic interference electrostatic discharge element management system
embedded control channel EMC EMI EMS enterprise system connection EPL
Issue 02 (2011-10-31)
B Glossary
EPLAN erbium doped fiber amplifier
See Ethernet private LAN service 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. See electric supervisory channel See enterprise system connection See electrostatic discharge Electrostatic discharge jack. A hole in the cabinet or shelf, which connect the shelf or cabinet to the insertion of ESD wrist strap. enhanced small form-factor pluggable 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.. 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). 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. 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. 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. 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. European Telecommunication Standards European Telecommunications Standards Institute A cabinet which is 600mm in width and 300mm in depth, compliant with the standards of the ETSI. 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. electrical variable optical attenuator See Ethernet virtual private line See Ethernet virtual private LAN service
ESC ESCON ESD ESD jack eSFP Ethernet
Ethernet in the first mile
Ethernet private LAN service Ethernet private line Ethernet virtual private LAN service Ethernet virtual private line ETS ETSI ETSI 300mm cabinet European Committee for Electrotechnical Standardization EVOA EVPL EVPLAN
Issue 02 (2011-10-31)
567
B 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. 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. 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. An oscilloscope display of synchronized pseudo-random digital data (signal amplitude versus time), showing the superposition of accumulated output waveforms.
Extended ID External cable eye pattern
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. 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). 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. fiber Bragg grating See fiber channel flash database See fiber distributed data interface See fast Ethernet See forward error correction 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. 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.
fast Ethernet
fault
FBG FC FDB FDDI FE FEC fiber channel
fiber distributed data interface
fiber management tray A device used to coil up extra optical fibers.
Issue 02 (2011-10-31)
568
B Glossary
fiber patch cord fiber spool Fiber trough fiber/cable
A kind of fiber used for connections between the subrack and the ODF, and for connections between subracks or inside a subrack. A device used in coiling up an extra length of optical fibers. The trough that is used for routing fibers. 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. 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. See First in First out 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. A stack management mechanism. The first saved data is first read and invoked. 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. See fiber management tray fixed optical add/drop multiplexer fixed optical attenuator 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. 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 (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. See field programmable gate array
field programmable gate array
FIFO File Transfer Protocol
First in First out Flow
FMT FOADM FOAs Forced switch
forward error correction four-wave mixing
FPGA
Issue 02 (2011-10-31)
569
B Glossary
frame
A frame, starting with a header, is a string of bytes with a specified length. Frame length is represented by the sampling circle or the total number of bytes sampled during a circle. A header comprises one or a number of bytes with pre-specified values. In other words, a header is a code segment that reflects the distribution (diagram) of the elements prespecified by the sending and receiving parties.
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 full-duplex See File Transfer Protocol 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 (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. 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. A network element that is used for communication between the NE application layer and the NM application layer See gigabit general communication channel See GMPLS control plan See gigabit Ethernet 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. A framing and encapsulated method which can be applied to any data type. It has been standardized by ITU-T SG15. See gain flattening filter See generic framing procedure
gain flattening filter
Gateway IP
gateway network element Gb GCC GCP GE GE ADM
generic framing procedure GFF GFP

Issue 02 (2011-10-31)
B 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. 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. A global navigation satellite system. It provides reliable positioning, navigation, and timing services to worldwide users. generalized multiprotocol label switching 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. See gateway network element See Global Positioning System
gigabit Ethernet
Global Positioning System GMPLS GMPLS control plan
GNE GPS
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 GSSP GUI 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. General Snooping and Selection Protocol See graphical user interface
H
Hardware loopback HCS HDB HDLC hierarchical cell structure high level data link control History alarm History Performance Data 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. See hierarchical cell structure high density bipolar code See high level data link control 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. 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. The confirmed alarms that have been saved in the memory and other external memories. The performance data that is stored in the history register or that is automatically reported and stored in the NMS.
Issue 02 (2011-10-31)
571
B Glossary
I
IAE IC ICC ICMP ID identity Idle resource optical NE incoming alignment error See integrated circuit ITU carrier code See Internet Control Message Protocol See identity The collective aspect of the set of characteristics by which a thing is definitively recognizable or known. 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. See Internet Explorer See International Electrotechnical Commission See Institute of Electrical and Electronics Engineers See Internet Engineering Task Force See Internet Group Management Protocol 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. 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. 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. 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. 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. The cables and optical fibers which are used for interconnecting electrical interfaces and optical interfaces within the cabinet. A segment of CIST in a certain MST region. An IST is a special MSTI whose ID is 0.
IE IEC IEEE IETF IGMP Input jitter tolerance
Institute of Electrical and Electronics Engineers integrated circuit integrated services digital network
intelligent power adjustment
Internal cable internal spanning tree
Issue 02 (2011-10-31)
572
B Glossary
International Electrotechnical Commission International Organization for Standardization International Telecommunication Union International Telecommunication UnionTelecommunication Standardization Sector Internet Control Message Protocol
The International Electrotechnical Commission (IEC) is an international and nongovernmental standards organization dealing with electrical and electronical standards. 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. 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). 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. 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). 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. 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. 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. 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. See Internet Protocol 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. 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. See intelligent power adjustment
Internet Engineering Task Force
Internet Explorer
Internet Group Management Protocol Internet Protocol
IP IP address
IP over DCC
IPA
Issue 02 (2011-10-31)
B Glossary
IPG ISDN ISO IST ITU ITU-T
inter-packet gap See integrated services digital network See International Organization for Standardization See internal spanning tree See International Telecommunication Union See International Telecommunication Union-Telecommunication Standardization Sector
J
Jitter Jitter transfer Short waveform variations caused by vibration, voltage fluctuations, and control system instability. 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. See Link Aggregation Control Protocol See link aggregation group See local area network link access procedure on the D channel link access protocol-SDH 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. 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. See loopback See link capacity adjustment scheme See liquid crystal display local communication network local craft terminal See light emitting diode long hop
LACP LAG LAN LAPD LAPS Laser
layer
LB LCAS LCD LCN LCT LED LHP
Issue 02 (2011-10-31)
574
B 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. 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 Control Protocol
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. In the Point-to-Point Protocol (PPP), the Link Control Protocol (LCP) establishes, configures, and tests data-link Internet connections. The link in LSA is any type of connection between OSPF routers, while the state is the condition of the link. 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. 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. A type of display that uses a liquid compound having a polar molecular structure, sandwiched between two transparent electrodes. See logical link control link management protocol loss of clock 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). 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. 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). A logical port is a logical number assigned to every application.
Link Control Protocol link state advertisement linktrace message
linktrace reply
liquid crystal display LLC LMP LOC local area network
Locked switching
logical link control
logical port
Issue 02 (2011-10-31)
575
B Glossary
loopback LOP LOS loss of pointer
A troubleshooting technique that returns a transmitted signal to its source so that the signal or message can be analyzed for errors. See loss of pointer See Loss Of Signal 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 (LOS) indicates that there are no transitions occurring in the received signal. The subrack close to the bottom of the cabinet when a cabinet contains several subracks. See logical port link-state pass through See link state advertisement See label switched path linktrace See linktrace message See linktrace reply
Loss Of Signal Lower subrack LP LPT LSA LSP LT LTM LTR
M
MA MAC MADM main distribution frame main path interface at the transmitter main topology Maintenance Associations See media access control multiple add/drop multiplexer A device at a central office, on which all local loops are terminated. A reference point on the optical fiber just after the OM/OA output optical connector. 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. 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 (MP) is one of either a MEP or a MIP. See metropolitan area network 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.
maintenance domain maintenance point MAN managed object
Issue 02 (2011-10-31)
576
B Glossary
Management information management information base manual switch
The information that is used for network management in a transport network. 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. 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. A procedure by which tributaries are adapted into virtual containers at the boundary of an SDH network. A quadrate cardboard with four holes. It is used to mark the positions of the installation holes for the cabinet. See maintenance domain Memory Database See main distribution frame message dispatch process message distribution service software maintenance entities The average power of a pseudo-random data sequence coupled into the fiber by the transmitter. The average time between consecutive failures of a piece of equipment. It is a measure of the reliability of the system. 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. maintenance end point 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. See multiframe alignment signal See management information base maintenance intermediate point See multicast listener discovery
Mapping marking-off template MD MDB MDF MDP MDS ME mean launched power Mean Time Between Failures media access control
MEP metropolitan area network
MFAS MIB MIP MLD
Issue 02 (2011-10-31)
577
B Glossary
MLM laser MO mother board mounting ear MP MPI MPI-R MPI-S MPLS MS MSA MSI MSOH MSP MSPP MST MSTI MSTP MTA MTBF MTU multi-longitudinal mode laser multicast listener discovery
See multi-longitudinal mode laser See managed object A printed board assembly that is used for interconnecting arrays of plug-in electronic modules. A piece of angle plate with holes in it on a rack. It is used to fix network elements or components. See maintenance point main path interface main path interface at the receiver See main path interface at the transmitter See Multiprotocol Label Switching Multiplex Section Multiplex Section Adaptation multi-frame structure identifier See multiplex section overhead See multiplex section protection multi-service provisioning platform See multiplex section termination See multiple spanning tree instance See Multiple Spanning Tree Protocol Mail Transfer Agent See Mean Time Between Failures Maximum Transmission Unit An injection laser diode which has a number of longitudinal modes. 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. 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.
multiframe alignment signal
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 02 (2011-10-31)
578
B 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. The overhead that comprises rows 5 to 9 of the SOH of the STM-N signal. See SOH definition. 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. The function performed to generate the MSOH in the process of forming an SDH frame signal and terminates the MSOH in the reverse direction. 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. 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. 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. See multiplexer mechanical variable optical attenuator
multiplex section overhead multiplex section protection multiplex section termination multiplexer
Multiplexing
Multiprotocol Label Switching
MUX MVOA
N
NA NCP NE NE database No Acknowledgment See Network Control Protocol See network element 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 02 (2011-10-31)
579
B 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. An ID that indicates a managed device in the network. In the network, each NE has a unique NE ID. 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. 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. Network Equipment Building System See network element function This is the program that switches the virtual circuit connections into place, implements path control, and operates the Synchronous Data Link Control (SDLC) link. 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. 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. 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.
NE ID NE Panel
NE-side data
NEBS NEF Network Control Protocol network element
network element function network 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 NMS NNI NOC Noise figure NSAP NTP See network management See Network Management System See network node interface network operation center An index that represents the degrade extent of optical signals after the signals passing a system. See network service access point See Network Time Protocol
Issue 02 (2011-10-31)
580
B Glossary
O
OA OADM OADM frame OAM OC OCI OCP OD ODB ODF ODUk OEQ OFC OLA OLP OM OMS ONE Online Help OOF OPA See optical amplifier See optical add/drop multiplexer A frame which is used to hold the OADM boards. See operation, administration and maintenance See optical coupler open connection indication See optical channel protection optical demultiplexing optical duobinary See optical distribution frame optical channel data unit-k optical equalizer open fiber control See optical line amplifier See optical line protection optical multiplexing optical multiplexing section See optical network element The capability of many programs and operating systems to display advice or instructions for using their features when so requested by the user. See out of frame 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. 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. operation expenditure optical physical section
operation, administration and maintenance
OpEx; OPEX OPS

Issue 02 (2011-10-31)
B 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).+ 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. Devices or subsystems in which optical signals can be amplified by means of the stimulated emission taking place in a suitable active medium. 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. A signal transmitted at one wavelength in a fiber-optic system. 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. 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. A frame which is used to transfer and spool fibers. 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. 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. 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. 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. A device that allows the details of a region of an optical spectrum to be resolved. Commonly used to diagnose DWDM systems. 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). A passive component possessing two or more ports which selectively transmits, redirects, or blocks optical power in an optical fiber transmission line.
optical add/drop multiplexer optical amplifier optical attenuator
optical channel optical channel protection optical coupler
optical distribution frame optical line amplifier
optical line protection
optical network element
optical signal-to-noise ratio optical spectrum analyzer optical supervisory channel Optical switch
Issue 02 (2011-10-31)
B Glossary
optical time domain reflectometer optical transmission section optical transponder unit optical transport network optical wavelength shared protection
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 allows the network operator to perform monitoring and maintenance tasks between NEs. A device or subsystem that converts the accessed client signals into the G.694.1/G.694.2compliant WDM wavelength. A network that uses the optical signal to transmit data 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. optical channel payload unit optical channel payload unit-k A channel that provides voice communication between operation engineers or maintenance engineers of different stations. 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. See optical spectrum analyzer See optical supervisory channel See Open Systems Interconnection optical switch node See optical signal-to-noise ratio See open shortest path first See optical time domain reflectometer optical terminal multiplexer See optical transport network See optical transmission section See optical transponder unit optical channel transport unit-k An NE transmits an OOF downstream when it receives framing errors in a specified number of consecutive frame bit positions. The ranger of optical energy level of output signals. Cables or fibers connect the cabinet with other equipment from the top of the cabinet. See optical wavelength shared protection
OPU OPUk orderwire original equipment manufacturer OSA OSC OSI OSN OSNR OSPF OTDR OTM OTN OTS OTU OTUk out of frame Output optical power overhead cabling OWSP
Issue 02 (2011-10-31)
583
B Glossary
P
PA packet over SDH/ SONET packet switched network Packing case Paired slots pass-through PBS PCB PCC PCC PCS PDH PDL PDU PE peak burst size pre-amplifier 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. A telecommunication network which works in packet switching mode. A case which is used for packing the board or subrack. Two slots of which the overheads can be passed through by using the bus on the backplane. The action of transmitting the same information that is being received for any given direction of transmission. See peak burst size See printed circuit board protection communication channel See policy and charging control See physical coding sublayer See plesiochronous digital hierarchy See polarization dependent loss Protocol Data Unit Provider Edge 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. A traffic parameter, expressed in bit/s, whose value should be not less than the committed information rate. 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. protection ground 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. See physical sublayer & physical layer
peak information rate Performance register
PGND phase-locked loop
PHY
Issue 02 (2011-10-31)
584
B Glossary
physical coding sublayer physical sublayer & physical layer PID PIM-DM PIM-SM PIN PIR plesiochronous digital hierarchy PLL PMD PMI POH point to multipoint
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. 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 photonics integrated device protocol independent multicast-dense mode See protocol independent multicast sparse mode See Positive Intrinsic Negative See peak information rate 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. See phase-locked loop polarization mode dispersion payload missing indication path overhead 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 POS Positive Intrinsic Negative Power box 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. See packet over SDH/SONET 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. 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 PPPoE See Point-to-Point Protocol See Point-to-Point Protocol over Ethernet
Issue 02 (2011-10-31)
585
B Glossary
PRBS PRC PRI primary rate interface printed circuit board
See pseudo random binary sequence primary reference clock See 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. 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. 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. A specific path that is part of a protection group and is labeled protection. 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. A specific service that is part of a protection group and is labeled protection. It is applicable to large-scale multicast networks with scattered members.
protection ground cable Protection path Protection policy
Protection service protocol independent multicast sparse mode
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 PSN PSTN PT PTMP PTN PTP public switched telephone network payload structure identifier See packet switched network See public switched telephone network payload type See point to multipoint packet transport network Point-To-Point A telecommunications network established to perform telephone services for the public subscribers. Sometimes called POTS.
Q
QA QoS quality of service Q adaptation See 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 02 (2011-10-31)
586
B Glossary
R
radio network controller RAI RAM An equipment in the RNS which is in charge of controlling the use and the integrity of the radio resources. remote alarm indication 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 Receiver Sensitivity 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 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 reference clock Reflectance REG Regeneration REI Resource Reservation Protocol A type of forward error correcting codes invented in 1960 by Irving Reed and Gustave Solomon, which has become commonplace in modern digital communications. A kind of stable and high-precision autonous clock providing frequencies for other clocks for reference. The ratio of the reflected optical power to the incident optical power. A piece of equipment or device that regenerates electrical signals. 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. Remote Error Indication 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). Radio Frequency Requirement for Comments remote failure indication A type of network topology in which each node connects to exactly two other nodes, forming a circular pathway for signals. See Routing Information Protocol
RF RFC RFI ring network RIP
Issue 02 (2011-10-31)
587
B Glossary
RMON RNC ROADM route Routing Information Protocol
remote network monitoring See radio network controller See reconfiguration optical add/drop multiplexer 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. 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. See Reed Solomon Code 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. See Rapid Spanning Tree Protocol See Resource Reservation Protocol return to zero code
RS Code RS232
RSTP RSVP RZ
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. 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. See storage area network service access point source access point identifiers stimulated Brillouin scattering See square connector See signal degrade 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. See synchronous digital hierarchy
Safe control switch
SAN SAP SAPI SBS SC SD SD trigger flag
SDH
Issue 02 (2011-10-31)
B Glossary
SDI SDP Search domain
See Serial Digital Interface serious disturbance period 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. A network protocol designed to provide secure file transfer over SSH. 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 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.
Secure File Transfer Protocol Self-healing
Serial Digital Interface An interface for transmitting digital signals. Serial Line Interface Protocol
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 SES SETS settings A measure that ensures that the services can be received at the receive end. See severely errored second See synchronous equipment timing source 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 SFP SFTP shock-proof reinforce shortcut menu side door See signal fail See small form-factor pluggable See Secure File Transfer Protocol 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. A menu that is displayed when right-clicking an object's name or icon. This is also referred to a context menu. The side door of a cabinet is used to protect the equipment inside the cabinet against unexpected touch and environment impact.
Issue 02 (2011-10-31)
589
B 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 signal cable signal degrade signal fail signal to noise ratio The trough on the side of the cable rack, which is used to place nuts so as to fix the cabinet. Common signal cables cover the E1 cable, network cable, and other non-subscriber signal cable. A signal indicating the associated data has degraded in the sense that a degraded defect (e.g., dDEG) condition is active. A signal that indicates the associated data has failed in the sense that a near-end defect condition (non-degrade defect) is active. 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). 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.
Simple Network Management Protocol
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. See service level agreement See Serial Line Interface Protocol single longitudinal mode section monitoring A specification for a new generation of optical modular transceivers. See single-mode fiber See side mode suppression ratio See subnetwork connection protection See subnetwork connection tunnel protection See Simple Network Management Protocol See signal to noise ratio An ASON connection which features flexible and dynamic adjustment of routes. SPC includes different classes of services (CoS). See synchronous optical network
SLA SLIP SLM SM small form-factor pluggable SMF SMSR SNCP SNCTP SNMP SNR soft permanent connections SONET
Issue 02 (2011-10-31)
590
B Glossary
span
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 SPM SQL square connector SRLG SRS SSM SSMB SSU STM STM-1 STM-4 storage area network See soft permanent connections self phase modulation See structured query language Cables may use two styles of connectors: "square" and "D-style". Shared Risk Link Group stimulated Raman scattering See Synchronization Status Message synchronization status message byte synchronization supply unit Synchronous Transfer Mode See synchronous transport mode 1 Synchronous Transport Module of order 4 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. See Spanning Tree Protocol A database query and programming language widely used for accessing, querying, updating, and managing data in relational database systems. 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. 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. 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.
STP structured query language sub-network
sub-network number
subnet mask
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.
B 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. 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. 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.
Suppression state
Switching 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 synchronous digital hierarchy To send the system time of the server of the network management system to NEs so as to synchronize all NEs with the server. 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. The SETS function provides timing reference to the relevant component parts of multiplexing equipment and represents the SDH network clement clock. 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 equipment timing source synchronous optical network
synchronous transport Synchronous Transfer Mode at 155 Mbit/s. mode 1
T
TCM TCP TDM TE Tandem Connection Monitoring See Transmission Control Protocol See time division multiplexing See traffic engineering
Issue 02 (2011-10-31)
592
B 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. See Trivial File Transfer Protocol trace identifier mismatch 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. Continuously repeating interval of time or a time period in which two devices are able to interconnect. 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. 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. See Transaction Language 1 Type/Length/Value See terminal multiplexer See Telecommunication Management Network traffic Policing 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.
TFTP TIM time division multiplexing
Time Slot Time Synchronization
time to live
TL1 TLV TM TMN TP traffic engineering
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 02 (2011-10-31)
593
B 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. A component that can be installed in the cabinet for holding chassis or other devices. 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 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. Two Rate Three Color Marker trail trace identifier See time to live tributary unit See tributary unit group
tray tributary unit group
Trivial File Transfer Protocol
trTCM TTI TTL TU TUG
U
UAS UAT UDP unavailable second See unavailable time event 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 universal time coordinated Unprotected See user network interface The world-wide scientific standard of timekeeping. It is based upon carefully maintained atomic clocks and is kept accurate to within microseconds worldwide. 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. 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. The subrack close to the top of the cabinet when a cabinet contains several subracks. A client user of the NMS. The user name and password uniquely identifies the operation rights of a user in the NMS.
upload
Upper subrack User
Issue 02 (2011-10-31)
594
B Glossary
User Datagram Protocol
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 VC VCG VCI virtual channel identifier virtual concatenation group virtual container virtual bridge See virtual container See virtual concatenation group See 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. A group of co-located member trail termination functions that are connected to the same virtual concatenation link 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. 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. The field in the ATM (Asynchronous Transfer Mode) cell header that identifies to which VP (Virtual Path) the cell belongs.
virtual local area network virtual path identifier
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 VOA voice over IP See virtual local area network Variable Optical Attenuator 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). See voice over IP See virtual path identifier See virtual private network Virtual Router Redundancy Protocol
VoIP VPI VPN VRRP
Issue 02 (2011-10-31)
595
B Glossary
W
WAN wavelength division multiplexing See wide area network 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 WEEE wide area network See wavelength division multiplexing waste electrical and electronic equipment 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. The channels allocated to transport the normal traffic. A specific service that is part of a protection group and is labeled working. weighted round Robin wavelength selective switching Wait To Restore wavelength cross-connection protection 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.
Working path Working service WRR WSS WTR WXCP WXCP service
X
XFP XPM 10Gbit/s Small Form-Factor Pluggable cross-phase modulation
Issue 02 (2011-10-31)
596

Configuration Guide (V100R006C001 02)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Configuration Guide (V100R006C001 02)

Uploaded by

Copyright:

Available Formats

OptiX OSN 8800/6800/3800 V100R006C01

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

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

OptiX OSN 8800/6800/3800 Configuration Guide

About This Document

About This Document

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

OptiX OSN 8800/6800/3800 Configuration Guide

About This Document

Updates in Issue 02 (2011-10-31) Based on Product Version V100R006C01

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

OptiX OSN 8800/6800/3800 Configuration Guide

About This Document

Description l 5.7.3 Configuration Process is modified.

l 6.6.3 Configuration Process is modified.

Updates in Issue 01 (2011-07-30) Based on Product Version V100R006C01

5 Configuring the THA/TOA Board (Manually by Station)

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

OptiX OSN 8800/6800/3800 Configuration Guide

About This Document

Update 11 Modifying the Configuration Data 12 Configuration Tasks

Updates in Issue 03 (2011-09-15) Based on Product Version V100R006C00

l 5.2 Configuration Procedures is added.

Updates in Issue 02 (2011-04-15) Based on Product Version V100R006C00

OptiX OSN 8800/6800/3800 Configuration Guide

About This Document

Update Whole manual

Updates in Issue 01 (2010-12-31) Based on Product Version V100R006C00

Make configuring WDM Services by trail as an independent chapter.

Updates in Issue 04 (2011-08-30) Based on Product Version V100R005C00

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

OptiX OSN 8800/6800/3800 Configuration Guide

About This Document

Update Whole manual

Make configuring WDM Services by trail as an independent chapter.

Updates in Issue 03 (2011-05-25) Based on Product Version V100R005C00

Updates in Issue 02 (2010-11-20) Based on Product Version V100R005C00

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

OptiX OSN 8800/6800/3800 Configuration Guide

About This Document

Description Modify the "configuration process".

Modify the "configuration process".

Updates in Issue 01 (2010-10-30) Based on Product Version V100R005C00

8.2 Creating OCh Trails by Trail Search is added.

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

OptiX OSN 8800/6800/3800 Configuration Guide

About This Document

8.4 Parameters: End to End Service Configuration is added.

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

OptiX OSN 8800/6800/3800 Configuration Guide

About This Document

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

OptiX OSN 8800/6800/3800 Configuration Guide

About This Document

Configuring the Receive Wavelength of Boards is added.

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

OptiX OSN 8800/6800/3800 Configuration Guide

OptiX OSN 8800/6800/3800 Configuration Guide

3 Configuring the TN11TOM Board (Manually by Station)..................................................59

4 Configuring the TN52TOM Board (Manually by Station)..................................................85

OptiX OSN 8800/6800/3800 Configuration Guide