HCIP-Transmission V2.5 Lab Guide

Huawei Transmission Certification Training
HCIP-Transmission
Lab Guide
ISSUE: 2.5
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2021 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
a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129
People's Republic of China
Website: http://e.huawei.com
HCIP-Transmission V2.5 Lab Guide Page 1
Huawei Certificate System

Huawei Certification is an integral part of the company's "Platform + Ecosystem"
strategy, and it supports the ICT infrastructure featuring "Cloud-Pipe-Device". It evolves
to reflect the latest trends of ICT development. Huawei Certification consists of two
categories: ICT Infrastructure Certification, and Cloud Service & Platform Certification,
making it the most extensive technical certification program in the industry.
Huawei offers three levels of certification: Huawei Certified ICT Associate (HCIA),
Huawei Certified ICT Professional (HCIP), and Huawei Certified ICT Expert (HCIE).
With its leading talent development system and certification standards, Huawei is
committed to developing ICT professionals in the digital era, building a healthy ICT
talent ecosystem.
HCIP-Transmission V2.5 aims to train and certificate senior engineers with
professional knowledge and skills in the transmission network field.
The certificate system introduces you to the industry and market, helps you in
innovation, and enables you to stand atop the transmission network frontiers.
About This Document
Overview
This document is applicable to the candidates who are preparing for the HCIP-
Transmission exam and the readers who want to understand the MS-OTN basics, the
MPLS&OTN protocol, MS-OTN networking, Huawei MS-OTN product features, service
configuration, MS-OTN advanced technology and MS-OTN fault troubleshooting.
Description
This document consists of 3 experiments, including:
⚫ Experiments 1 is basic NE configuration experiments. Basic NE configuration, optical-
layer service configuration, and system commissioning. Through basic operations,
configuration, and commissioning, the transmission function of the equipment is
implemented.
⚫ Experiment 2 shows the configuration process of MS-OTN services. It demonstrates
the configuration process to help readers master the configuration methods of
common MS-OTN services.
⚫ Experiment 3 shows the configuration process of NG WDM protection and helps
readers master the configuration methods of NG WDM protection.
Background Knowledge Required

The intended audience should know basic knowledge of transmission network, be
familiar with Huawei transmission equipment.
Common Icons
Experiment Environment Overview

Networking Introduction
This lab environment is intended for transport network engineers who are preparing for
the HCIP-Transmission exam. Each lab environment consists of three NG WDM devices
(12 devices in total) and one NCE server. Each lab environment can be used by 4 to 12
trainees at the same time.
Device Introduction
To meet the requirements of the HCIP-Transmission experiment, you are advised to use
the following configurations for each experiment environment:
The mapping between device names, models, and versions is as follows:
Device Name Device Model Software Version
E6616 V100R019C10SPC600
NG WDM E6608 V100R019C10SPC600
E6608T V100R019C10SPC600
NCE server TaiShan 2280 V100R019C00
Experiment Environment Preparation

Checking Whether All Devices Are Available
Before starting the experiment, check whether all required devices are ready. The
following table lists the required devices.
Device Quantity Remarks
E6616 3 Shared by all lab groups
E6608 3 Shared by all lab groups
E6608T 6 Shared by all lab groups
NCE server 1 Shared by all lab groups
The PC must be connected

Notebook or desktop One for each group to the network where the
NCE server resides.
Twisted pair Two for each group At least two meters long.
Each group must check whether the following devices are ready:
⚫ Three E6616s, three E6608s and six E6608Ts.
⚫ One NCE server (installed)
⚫ One laptop or desktop

⚫ Two twisted pairs
Experiment topology
For details about the topology, see the Networking and Service Description and
Networking Design in each chapter.
Contents
About This Document...............................................................................................................3

Overview ................................................................................................................................................................................... 3
Description................................................................................................................................................................................ 3
Background Knowledge Required ...................................................................................................................................... 3
Common Icons......................................................................................................................................................................... 3
Experiment Environment Overview ................................................................................................................................... 4
Experiment Environment Preparation............................................................................................................................... 4
1 NG WDM System Commissioning .......................................................................................9
1.1 NG WDM Common Data Configuration ................................................................................................................... 9
1.1.1 About this Experiment ................................................................................................................................................ 9
1.1.2 Creating an NE ............................................................................................................................................................ 10
1.1.3 Configuring NE Data ................................................................................................................................................. 14
1.1.4 Creating an Optical NE ............................................................................................................................................. 19
1.1.5 Set the Wavelength of an OTU/LU Board Port .................................................................................................. 21
1.1.6 Creating Fiber Connections...................................................................................................................................... 23
1.1.7 Synchronizing the NE Time ..................................................................................................................................... 30
1.1.8 Setting NE Performance Monitoring Parameters .............................................................................................. 33
1.2 Configuring Optical-Layer Services ........................................................................................................................... 36
1.2.1 About this Experiment .............................................................................................................................................. 36
1.2.2 Searching for OCh trails ........................................................................................................................................... 39
1.2.3 Configure OCh Station by Station ......................................................................................................................... 41
1.2.4 Configure OCh by Trail ............................................................................................................................................. 44
1.3 NG WDM Power Commissioning .............................................................................................................................. 48
1.3.2 Commissioning OSC................................................................................................................................................... 51
1.3.3 Commissioning Optical Power ................................................................................................................................ 53
1.3.4 Backing Up Data ......................................................................................................................................................... 61
2 MS-OTN Service Configuration ......................................................................................... 63
2.1 OTN Service Configuration ......................................................................................................................................... 63
2.1.2 Create OTN Service by Trail .................................................................................................................................... 64
2.1.3 Create OTN Service Station by Station................................................................................................................. 69
2.2 UNI-UNI E-Line service ................................................................................................................................................ 73
2.2.2 Configuration Procedure .......................................................................................................................................... 74

2.2.3 Verification ................................................................................................................................................................... 77
2.3 E-Line services carried by ports(Based on VLAN) ................................................................................................. 79
2.3.3 Verification ................................................................................................................................................................... 85
2.4 E-Line services carried by QinQ ................................................................................................................................. 87
2.4.3 Verification ................................................................................................................................................................... 94
2.5 E-Line services carried by PWs (VPWS) ..................................................................................................................... 1
2.5.1 About this Experiment ................................................................................................................................................ 1
2.5.2 Configuration Procedure ............................................................................................................................................ 4
2.5.3 Verification ................................................................................................................................................................... 12
2.6 E-LAN services Based on the 802.1d Bridge ........................................................................................................... 13
2.6.3 Verification ................................................................................................................................................................... 16
2.7 E-LAN services Based on the 802.1q Bridge ........................................................................................................... 19
2.7.3 Verification ................................................................................................................................................................... 24
2.8 E-LAN services carried by PWs(VPLS) ...................................................................................................................... 25
2.8.3 Verification ................................................................................................................................................................... 31
3 MS-OTN Protection ............................................................................................................ 33
3.1 Equipment-level protection ........................................................................................................................................ 33
3.2 1+1 optical line protection .......................................................................................................................................... 35
3.2.3 Verification ................................................................................................................................................................... 39
3.3 Intra-board 1+1 protection ......................................................................................................................................... 40
3.3.3 Verification ................................................................................................................................................................... 43
3.4 Client 1+1 protection .................................................................................................................................................... 44

3.4.3 Verification ................................................................................................................................................................... 47
3.5 ODUk SNCP protection ................................................................................................................................................ 48
3.5.3 Verification ................................................................................................................................................................... 51
3.6 Tributary SNCP protection .......................................................................................................................................... 53
3.6.3 Verification ................................................................................................................................................................... 55
3.7 LAG protection ............................................................................................................................................................... 57
3.7.3 Verification ................................................................................................................................................................... 60
3.8 Tunnel APS protection .................................................................................................................................................. 60
3.8.3 Verification ................................................................................................................................................................... 64
3.9 PW APS/FPS protection ................................................................................................................................................ 64
3.9.3 Verification ................................................................................................................................................................... 69
3.10 ERPS protection............................................................................................................................................................ 70
3.10.1 About this Experiment ............................................................................................................................................ 70
3.10.2 Configuration Procedure ........................................................................................................................................ 71
3.10.3 Verification ................................................................................................................................................................. 73
1 NG WDM System Commissioning
1.1 NG WDM Common Data Configuration

1.1.1 About this Experiment
An NE represents a subrack of a WDM device. There are two methods for creating NEs:
creating a single NE and creating NEs in batches. The results of the two methods are
same. You are advised to use both methods during the practice.
1.1.1.1 Objective
⚫ Grasp the procedure for creating a single NE.
⚫ Grasp the procedure for creating NEs in batches.
1.1.1.2 Networking and Service Description
NG WDM network topology
1.1.1.3 Networking Design

Three sites are planned to form a ring network. Each site is configured with one E6616
and two E6608s. Master and slave subracks are used between the devices. Table 1-1 lists
the device ID and IP address planning.
To facilitate management, GNEs are planned for NE A and NE C.
Table 1-1 Site planning and design

Extended Gateway Gateway NE IP
Site Device ID Subrack Type
ID. Type Address/GNE
E6616 Master subrack
E6608 184 223 Slave subrack 1 Gateway 10.154.184.223

NEA
E6608 Slave subrack 2
E6608 184 226 Master subrack Gateway 10.154.184.226
E6616 Master subrack

Non-
E6608 184 224 Slave subrack 1 184-223
NE B gateway
E6608 Slave subrack 2
E6608T Master subrack Non-

NE C 184 228 184-225
E6608T Slave subrack 1 gateway
1.1.2 Creating an NE
An NE represents a subrack of a WDM device. There are two methods for creating NEs:
Create a single NE and Create NEs in batches. The results of the two methods are the
same. You are advised to use both methods during the hands-on exercise.
1) Creating a Single NE
Right-click on the blank space of the Main Topology and choose New > NE from
the shortcut menu. The Create NE dialog box is displayed.
Select required NE type ”OptiXtrans E6616” from tree structure at left top. Input
NE ID, Extended ID, Name, and Remarks based on the information planned in
Table 1-1. To create a gateway NE, perform step 3. To create a non-gateway NE,
perform steps 4 and 5. Before creating a non-gateway NE, you need to create a
gateway NE.
Manually create a GNE. Select Gateway from the Gateway Type drop-down list
and set IP Address. As shown in the following figure, the ID is 223 and the
extended ID is 184. Change the IP address to be the same as that on the NE.
Otherwise, the gateway NE cannot communicate with the NCE. The default NE
user name is “root” and the password is “Changeme_123”.
Manually create a non-gateway NE. Set Gateway Type to Non-gateway and select
the gateway of this NE. Set NE User and Password.
Click OK. The cursor displayed as ”+”. Click in the Main Topology. Click on the
blank space of the physical view and the NE is created.
Create other NEs in the same way.
2) Creating NEs in batches
When the NCE communicates properly with a GNE, you can search for all NEs that
communicate with the GNE by using the IP address of the GNE or the network segment
to which the IP address is associated. Then, you can create NEs in batches. This method is
better than manual creation. Therefore, the method of creating NEs in batches is
recommended.
Choose Topology > Discovery > NE from the main menu. The NE Search window is
displayed.
Click the Transport NE Search tab. Select Search for NE from the Search Mode
drop-down list. If the network segment of the NE to be searched cannot be
correctly specified, set Search Mode to IP Auto Discovery so that the IP address of
the gateway NE can be obtained and all NEs under the gateway NE can be
searched out. If the NEs to be searched are connected to the NCE through
different routers, you cannot search for the NEs by using IP Auto Discovery.
Instead, you can search for the NEs by using Search for NE.
In the Search Domain dialog box, click Add. The Search Domain Input dialog box
is displayed. Set Address Type to IP Address Range of GNE, set Search Address,
User Name, and Password, and click OK.
Click Next. The Searched NEs area is displayed, and Operation Results is
“Discovery…”.
Wait until the search is complete. The NEs that are found are displayed in
“Results”. Select the NEs to be created.
Click Create. The Create NE progress bar is displayed, indicating that the NE is
automatically created.
1.1.3 Configuring NE Data

NCE supports three methods for configuring NE data: manually configuring NE data,
copying NE data, and uploading NE data one by one or in batches.
There are multiple NEs on the network. Therefore, you can use multiple configuration
methods to configure NE data. The recommended configuration methods are as follows:
Table 1-2 Recommended Configuration
Site NE Recommended Configuration
184-223
NE A Initialize and Manually configure NE data
184-226
184-224
NE B Upload
184-227
184-225
NE C 184-228 Upload in batches
184-229
1) Initialize and Manually configure NE data

Double-click the unconfigured NE in the Main Topology. The NE Configuration

Wizard dialog box is displayed.
Select Initialize and Manually configure NE data and click Next. The Confirm
dialog box is displayed, indicating that the manual configuration will clear the NE
data. Click OK. The Confirm dialog box is displayed, indicating that manual
configuration interrupts NE services.
Click YES. The Set NE Attributes dialog box is displayed. To modify NE attributes,
set NE Name, Device Type, NE Remarks, Subrack Type, Service Type, and Service
Capacity.
Click Next. The NE Slot page is displayed.
Click Query Physical Information to query the physical boards of the NE.
Click Next. The Send Configuration page is displayed. Select Verify and Run and
click Finish.
Configure other NEs in the same way.
2) Upload a Single NE
In the Main Topology, double-click an optical NE that contains unconfigured NEs.

In the left pane, double-click the unconfigured NE. Alternatively, double-click the
unconfigured NE in the Main Topology. The NE Configuration Wizard dialog box is
displayed.
Select Manual Configuration and click Next. The Confirm dialog box is displayed.
Click YES. The upload progress bar is displayed. Wait until the upload is complete.
Configure other NEs in the same way.
3) Upload NEs in batches
Choose Configuration > NE Configuration Data Management from the main

menu.
In the navigation tree on the left, select the created NE and click . In the NE
Configuration List area, select the NE whose NE Status is Unconfigured.
Click Upload. The Confirm dialog box is displayed. Click OK.
The upload progress bar is displayed. Wait until the upload is complete.
1.1.4 Creating an Optical NE

On NCE, if a site uses more than one WDM device, all the devices at the same site can be
grouped into the same optical NE for management. After creating an optical NE, you
need to add each subrack NE to the corresponding optical NE for management. This is
the process of resource division. NCE defines four optical NE types: WDM_OTM,
WDM_OLA, WDM_OADM, and WDM_OEQ.
The following table lists the planning of optical NE information at each site.
Table 1-3 Optical NE planning table

Optical NE Number of
Site Optical NE Type NEs involved
Name Wavelengths
184-223
A NE A WDM_OADM 40
184-226
184-224
B NE B WDM_OADM 40
184-227
184-225
C NE C WDM_OADM 40 184-228
184-229
Right-click in the Main Topology and choose New > NE from the shortcut menu.
In the Create NE dialog box, click to Optical NE and select the optical NE type
to be created. Click Basic Attributes and set basic attributes such as the optical NE
name and number of wavelengths based on the customer plan.
Click Resource Division, select optical NEs from idle resources according to the
resource allocation plan in Table 1-3, and click to allocate the NEs to
the optical NEs.
Click OK.
Create other optical NEs in the same way.
1.1.5 Set the Wavelength of an OTU/LU Board Port

Before creating fibers, you are advised to set the wavelength number/optical port
wavelength (nm)/frequency (THz) of the tunable OTU/LU port to the planned
wavelength. After creating a fiber, you can set parameters such as the fiber type and
transmission distance.
The following table lists the wavelength planning for the ports on the line boards at each
site.
Table 1-4 Port wavelength planning table
Site Board NE Subrack Slot Port Planning

Name Wavelengths
1 76/192.3THz
UNQ2 184-223 0 4
2 80/192.1THz
A
1 76/192.3THz
UNQ2 184-223 0 5
2 80/192.1THz
1 80/192.1THz
UNQ2 184-224 0 4
2 78/192.2THz
B
1 78/192.2THz
UNQ2 184-224 0 5
2 80/192.1THz
1 76/192.3THz
UNQ2 184-225 0 4
2 78/192.2THz
C
1 76/192.3THz
UNQ2 184-225 0 5
2 78/192.2THz
In the Main Topology, double-click NE A. In the NE Panel, right-click the UNQ2

board and choose Path View from the shortcut menu.
In the path view, right-click in the blank area and choose Port Attributes from the
shortcut menu.
In the Port Attributes dialog box, click the Wavelength Band tab, locate IN1/OUT1,
and select 80/150.61/192.100 from the Wavelength drop-down list.
Change the wavelengths of all OTU/LU boards in the same way.

Click Apply.
Modify the wavelengths of all OTU/LU boards in the same way.
1.1.6 Creating Fiber Connections

Logical fiber connections on NCE include inter-site fibers and intra-site fibers.
Logical fibers between sites represent actual optical cables and can only be manually
created by operators. Logical fibers inside a site are the basis for configuring optical-layer
cross-connections and managing trails. You need to manually create logical fibers.
Information about inter-site fibers between NEs is as follows:
Inter-site fiber connection diagram

Note: "1-8-DSFIU-ELINE1" indicates the ELINE port on the DSFIU board in slot 8 of slave
subrack 1.
The following figure shows the internal fiber connection diagram of each site. (Note:
DSFIU(108) indicates the DSFIU board in slot 08 of slave subrack 1.)
Internal fiber connections of NE A

Internal fiber connections of NE B
Internal fiber connections of NE C

All the UNQ2 boards on NE C are installed on NE 184-225, and other boards are installed
on NE 184-228.
1) Create an inter-site fiber. (The following uses the inter-site fiber between the DSFIU
ELINE1 board in slot 8 of subrack 1 on NE A and the DSFIU ELINE1 board in slot 8 of
subrack 1 on NE B as an example.)
Right-click in the Main Topology and choose Create Fiber from the shortcut menu.
The cursor is displayed as ”+”.
In the Main Topology, click the source NE of the fiber/cable. In the Select Source
Fiber dialog box, select the source board (DSFIU in slot 8 of subrack 1 on NE A)
and source port (ELINE1).
Click OK to return to the main view. The cursor changes to “+” again.
In the Main Topology, click the sink NE of the fiber/cable. In the Select Sink of
Fiber dialog box, select the sink board (DSFIU in slot 8 of subrack 1 on NE B) and
the sink port (ELINE1).
Click OK. In the displayed Create Fiber/Cable dialog box, set the attributes of the
fiber/cable. (If the parameters are not modified, subsequent service configuration
is not affected.)
Click OK. The created unidirectional fiber is displayed between the source and sink
NEs in the Main Topology.
Repeat the preceding steps to create reverse fiber connections between NEs and
all inter-site fibers between other NEs.
2) Create an intra-site fiber. (The fiber from the OUT_1 port on the DAP board in slot 5 of
subrack 1 to the LINE port on the EX40 board in slot 1 of subrack 1 on NE A is used as
an example.)
In the Main Topology, double-click the optical NE icon and click the Signal Flow
Diagram tab.
Right-click in the blank area of the Signal Flow Diagram and choose Create Fiber
from the shortcut menu. The cursor is displayed as “+”.
Select the source board (DAP in slot 5 of subrack 1) and the source port (OUT_1
port) and click OK. The cursor is displayed as “+”.
Select the sink board (EX40 in slot 1 of subrack 1) and sink port (LINE port), and
click OK.
In the Create Fiber/Cable dialog box, set the fiber attributes.

Click OK. Move the cursor to the created fiber. The information about the fiber is
displayed. Check the information to check whether the fiber is correctly created.
Repeat the preceding steps to create reverse fiber connections and other
bidirectional fiber connections on the NE.
1.1.7 Synchronizing the NE Time

Synchronizing NE time does not affect the normal running of services. Before
synchronizing NE time, ensure that the system time of the NCE server is correct. To
change the system time of the server computer, exit NCE, reset the system time of the
computer, and then restart NCE.
You can synchronize the time of a single NE or in batches.
1) Time synchronization for a single NE
Double-click an optical NE. Right-click the NE to be configured and choose NE

Explorer from the shortcut menu.
In the NE Explorer, choose Configuration > NE Time Synchronization from the

Function Tree.
Right-click an NE in the right pane and choose Synchronize with NMS Time from
the shortcut menu.
The Synchronize Time dialog box is displayed, indicating that the time
synchronization will change the NE time. Click Yes. The NE Time Synchronization
progress bar is displayed.
After the synchronization is complete, the Operation Result dialog box is

displayed. Click Close.
Configure NE time synchronization for other NEs in the same way.
2) Synchronizing NE Time in Batches
Choose Configuration > Network Common Configuration > NE Time Sync from the
main menu. The NE Time Synchronization window is displayed.
In the navigation tree on the left, select the NE that synchronizes time with the
NCE and click . In the NE Time Synchronization list, select the NE and
choose Synchronize with NM Time from the shortcut menu.
The Synchronize Time dialog box is displayed, indicating that the time
synchronization will change the NE time. Click Yes. The NE Time Synchronization
progress bar is displayed.
After the synchronization is complete, the Operation Result dialog box is

displayed. Click Close.
1.1.8 Setting NE Performance Monitoring Parameters

Performance monitoring is classified into 15-minute performance monitoring and 24-
hour performance monitoring. Generally, both of them must be enabled.
For the 15-minute monitoring period, the device can store 16 x 15-minute historical
performance data, that is, the 15-minute historical performance data of 4 hours. For a
24-hour monitoring period, the device can store the historical performance data of 6 x 24
hours, that is, the historical performance data of 6 days.
1) Setting performance monitoring parameters for a single NE
Double-click an optical NE. Right-click the NE to be configured and choose NE

Explorer from the shortcut menu.
In the NE Explorer, choose Performance > NE Performance Monitoring Time from

the Function Tree.
Select the 15 minutes or 24 hours check box as required. In the Set 15-minute
monitoring or Set 24-hour monitoring area, click Enable.
Click and set the start and end time of the monitoring as required. The start
time must be later than the current time of the NCE and NEs. To start monitoring
immediately, set the start time to a value later than the current time of the NCE
and NEs. To set the end time, select End Time and ensure that the end time is
later than the start time. If you do not select End Time, the monitoring function is
always enabled.
Click Apply. The Set Monitoring Time dialog box is displayed, showing the
progress. When the progress reaches 100%, the dialog box is closed.
Set performance monitoring for other NEs in the same way.
2) Setting NE Performance Monitoring Time in Batches
Choose Monitor > Performance > Monitoring Time Settings from the main menu.
Select a subnet or NE from the navigation tree in the left pane, click , and
select the NE for which the performance monitoring function is to be enabled.
Select the 15 minutes or 24 hours check box as required. In the Set 15-minute
monitoring or Set 24-hour monitoring area, click Enable.
Click and set the start and end time of the monitoring as required. The start
time must be later than the current time of the NCE and NEs. To start monitoring
immediately, set the start time to a value later than the current time of the NCE
and NEs. To set the end time, select End Time and ensure that the end time is
later than the start time. If you do not select End Time, the monitoring function is
always enabled.
Click Apply. The Set Monitoring Time dialog box is displayed, showing the
progress. When the progress reaches 100%, the dialog box is closed.
In the Operation Result dialog box, click Close.
1.2 Configuring Optical-Layer Services

After configuring NEs and networks, you need to configure wavelength grooming. An
OCh trail that traverses an ROADM needs to be manually created. If no ROADM is
configured on the service trail, you only need to search for WDM trails. The OCh trail will
be automatically generated on NCE. This chapter describes how to search for OCh trails
at an FOADM site and how to configure optical cross-connections at an ROADM site.
1.2.1.1 Objective
⚫ Understand the meaning of the path.
⚫ Understand the characteristics of FOADM and ROADM.
⚫ Grasped how to search for and configure OChs.

The following figure shows the planning of optical-layer services between sites.
Note: "1-8-DSFIU-ELINE1" indicates the ELINE port on the DSFIU board in slot 8 of slave
subrack 1.
Wavelength diagram
The following figure shows the signal flow of each site.

1.2.2 Searching for OCh trails

If no ROADM unit is configured on the service trail, you only need to search for WDM
trails. OChs are automatically generated on NCE. When an OCh trail traverses an
ROADM, you need to manually create an OCh trail.
You can manually create OCh trails by using the NE Explorer or trail method.
1) Searching for OChs (without ROADM)
Choose Service > View > WDM Trail from the main menu.
In the WDM Trail dialog box, click Search for WDM Trail.
In the WDM Trail Search dialog box, click Next.
After the search is complete, click Next.
If the fiber connections and NE parameters are correct, the OCh trail is displayed
in the Trails found list.
Click Next. If the fiber connection or NE parameters are incorrect, the OCh trail is
incomplete and displayed in the Discrete Service list.
Click Finish.
1.2.3 Configure OCh Station by Station

In the station by station configuration mode, you need to configure edge ports first.
An edge port refers to a port that has fiber connections between an NE and other NEs.
To set the edge point of an NE is to set the optical port as the connection point between
the local NE and other NEs. You need to configure the edge port only when the OTU/LU
board and the multiplexer/demultiplexer board are not on the same set of equipment.
The following uses 80/192.1THz (NE A-NE C-NEB) as an example to demonstrate the
operation procedure.
(Optional) Configure edge ports:
In the NE A Explorer, choose Configuration > Optical Cross-Connection

Management from the Function Tree. Click the Edge Port tab.
In the Available Board Ports area, select 102-EX40-MD01:IN and 102-EX40-

MD01:OUT and click to add it to Selected Border Ports.
Click Apply. In the displayed dialog box, click Close.
Configure optical service:
Click the NE –Level Optical Cross-Connection tab. Click New. The New Optical
Cross-Connection Service window is displayed.
In the create service dialog box, select the source slot 5-UNQ2, source port
IN2/OUT2, sink slot 108-DSFIU and sink port WLINE1/WLINE2. Click on the right
of Source Wavelength No. and select 80/192.1THz from the available wavelengths
menu. Set the optical power adjustment mode to Manual, checked Create Reverse
Cross-Connection and click Apply.
After the operation is complete, the configuration result is displayed in the Single-
Site Optical Cross-Connection window.
Refer to step 1-6 to configure NE-Level optical cross-connection on NE B

according to the network design in section 1.2.1.3.
Login the NE explorer of NE C, Click the NE –Level Optical Cross-Connection tab.

Click New. The New Optical Cross-Connection Service window is displayed.
In the create service dialog box, select the source slot 108-DSFIU, source port
ELINE1/ELINE2, sink slot 108-DSFIU and sink port WLINE1/WLINE2. Click on the
right of Source Wavelength No. and select 80/192.1THz from the available
wavelengths menu. Set the optical power adjustment mode to Manual, checked
Create Reverse Cross-Connection and click Apply.
After the creation is complete, search and connect the single-NE optical cross-
connections into complete OCh services by referring to section "1.2.2 Searching for
OCh".
1.2.4 Configure OCh by Trail

The trail-based OCh configuration method allows you to configure optical-layer services
in an E2E manner by searching for trails and creating trails at each layer. In addition, the
trail signal flow diagram is provided, which intuitively displays the signal flow direction of
trails, improves O&M efficiency, and reduces O&M costs.
The following uses 80/192.1THz (NE A-NE C-NEB) as an example to demonstrate the
operation procedure.
Choose Service > Create > WDM Trail from the main menu.
In the Create WDM Trail window, set Level to OCh and Direction to Bidirectional.
Click Browse on the right of the Source field. In the dialog box that is displayed,
select the 005-UNQ2-IN2/OUT2 on NE A as the source port of the E2E trail, set
the wavelength to 80/192.1THz, and click OK.
Click Browse on the right of the Sink field. In the dialog box that is displayed,
select the 005-UNQ2-IN2/OUT2 on NE C as the source port of the E2E trail, set
the wavelength to 80/192.1THz, and click OK.
(Optional) Set route constraints. Choose Set Explicit Node > NE or Set Explicit
Node > Board/Port to set an NE, board, or port as the explicit node of the trail to
be created. Indicates whether an NE is displayed. Double-click the NE again to
deselect the NE .
Select Auto Calculate and Activate. If the OPA function is not required in the
network planning, click Power Adjustment Mode. In the dialog box that is
displayed, select Manual. After route calculation is successful, the server-layer
route information and port attribute list of the trail to be created are displayed at
the bottom of the topology view.
Click Apply. The Create Trail dialog box is displayed, showing the path creation
progress. After the trail is created successfully, a dialog box is displayed, indicating
that the operation is successful.
1.3 NG WDM Power Commissioning

After configuring NEs and networks, you need to configure wavelength grooming. An
OCh trail that traverses an ROADM needs to be manually created. If no ROADM is
configured on the service trail, you only need to search for WDM trails. The OCh trail will
be automatically generated on NCE. This chapter describes how to search for OCh trails
at an FOADM site and how to configure optical cross-connections at an ROADM site.
1.3.1.1 Objectives
⚫ Grasped the methods and procedures for commissioning the optical supervisory
channel.
⚫ Grasped the methods and procedures for system commissioning.
⚫ Grasped the procedure for backing up data.
NG WDM Experiment Topology

The following figure shows the OSC signal flow of each site.

All the UNQ2 boards on NE C are installed on NE 184-225, and other boards are installed
on NE 184-228.
OPM8 monitoring port connection information at each site:
Table 1-5 Connections of the monitoring ports of the OPM8 on NE A
Site Board Port Connection port
1 Slot 05 in subrack 1 - DAP-MON_1
4 Slot 05 of subrack 2 - DAP-MON_2

A OPM8
5 Slot 1 in subrack 1, EX40-MOND
6 Slot 02 in subrack 1 - EX40-MOND
7 Subrack 2 - Slot 01 - EX40-MOND
Table 1-6 Connections of the monitoring ports of the OPM8 on NE B


B OPM8
4 Slot 05 of subrack 2 - DAP-MON_2

7 Subrack 2 - Slot 01 - EX40-MOND
Table 1-7 Connections of the monitoring ports of the OPM8 on NE C
1 Slots 0-05-DAP-MON_1 in subrack 0
2 Slot 0-05-DAP-MON_2

B OPM8
5 Slot 0-01-EX40-MOND
6 Slot 0-02-EX40-MOND
The following figure shows the planning of optical-layer services between sites.
Wavelength diagram
1.3.2 Commissioning OSC

The received optical power of OSC boards at each site must be commissioned according
to the OSC signal flow. Based on the requirements for the received and transmit optical
power and insertion loss of the board, check whether the attenuation of the line or board
is abnormal.
The following table lists the received and transmit optical specifications of the optical
module on the monitoring board.
Table 1-8 OSC Board Commissioning Specifications

OSC
Launch optical power range Receive optical power range
board
SC1
TM port: –4 dBm to 0 dBm RM port: –45 dBm to –8 dBm
SC2
ST2 RM port: -34 dBm to -10 dBm (80 km)

TM port: –4 dBm to 1 dBm (80 km)
AST2 RM port: –42 dBm to –10 dBm (150
TM port: 0.5 dBm to 5 dBm (150 km)
AST4 km)
The following uses the commissioning of the supervisory channel between NE A and NE
B as an example.
Check whether the optical fibers of the optical supervisory channel board are
correctly connected. Check whether the fiber connections are the same as those in
the signal flow diagrams shown in Figure 1-9 and Figure 1-10. Use an optical
power meter to query the optical power. Skip step 4. If you use the NMS to query
the optical power, skip steps 2 and 3.
Set the wavelength range of the optical power meter to 1510 nm and check
whether the transmit optical power of the TMO port on the optical supervisory
channel board meets the requirements (Refer to Table 1- 8 for the Launch optical
power range). If the transmit optical power does not meet the requirement,
replace the board. (Checking launch power)
Set the wavelength range of the optical power meter to 1510 nm and check
whether the actual receive optical power of the RM port on the optical supervisory
channel meets the requirements.(Refer to Table 1- 8 for the Receive optical power
range). You can adjust the actual receive optical power by adding, deleting, or
replacing the fixed optical attenuator. (Check receive power.)
Alternatively, open the NE Explorer on NCE, select the AST2 board in the
navigation tree, choose Configuration > Optical Power Management from the
Function Tree, and click Query to query the received and transmit optical power of
the port.
The received optical power must meet the commissioning requirements listed in
Table 1-8. If the receive optical power is too high, add a fixed attenuator to the
RM port. If the receive optical power is too low, check whether the attenuation of
the inter-site line is normal. If the attenuation is abnormal, handle the fault on
site.
1.3.3 Commissioning Optical Power

Single-site commissioning and system commissioning are two common optical power
commissioning modes on live networks.
When a large number of EVOAs and spectrum analyzer boards are configured on the live
network, remote commissioning is convenient. However, if FOAs are required or
hardware is replaced during the commissioning, only onsite commissioning is required.
This section uses the services from NE A to NE B to NE C as an example to describe how
to commission optical power in site visits and remote cooperation modes.
Commission the optical power of each station and each board according to the signal
flow sequence. Based on the optical power, gain, and insertion loss of the board, che ck
whether the attenuation of the line or board is abnormal.
The optical power adjustment is performed based on the optical power commissioning
requirements of tributary boards, line boards, and optical amplifier boards.
Optical power commissioning sequence:
In a WDM system, the stations between two end stations (OTMs) are generally
considered as a network segment. Each network segment contains two signal flows in
the corresponding transmit and receive directions.
In each network segment, the WDM system commissions the optical power site by site
according to the signal flow direction.
Commission the optical power in the transmit direction of an OTM terminal site, and
commission the optical power of each downstream station along the signal direction.
Finally, commission the optical power in the receive direction of the signal flow to the
destination OTM station.
Then, commission the optical power in the opposite direction of the signal flow.
Take the 80/192.1 THz service from NE A to NE B as an example. Based on the signal
flow diagrams shown in Figure 1-9, Figure 1-10, and Figure 1-11, you can analyze the
signal flow diagram of the service.
During the commissioning, pay attention to the following commissioning specifications of
different boards:
OTU board commissioning specifications:
Table 1-9 Commissioning specifications of the UNQ2
Item Indicator Value
Nominal center frequency 191.3-196.05THz
Maximum mean launched

0dBm
optical power
Minimum mean launched

-5 dBm
optical power
center frequency offset ±2.5GHz
Operating wavelength
1529-1568nm
range
Receiver sensitivity -16dBm
Minimum overload point 0 dBm
The commissioning specifications of the TNB1DAP board are as follows:

Table 1-10 OA Subboard Commissioning Specifications (40 Wavelengths)

Nominal Single Nominal Single
Input optical Wavelength Wavelength Nominal gain
subboard
power range Input optical Output optical gain Scope
power power
20 - 31
OAC101 -32 - -16 dBm -16 dBm 4 dBm 20 dB
dB
24 - 36
OAC103 -32 - -20 dBm -20 dBm 4 dBm 24 dB
dB
24 - 36
OAC106 -24 - -12 dBm -12 dBm 4 dBm 16 dB
dB
OBC103 -32 - -19 dBm -19 dBm 4 dBm 23 dB 23 dB
Table 1-11 OA Subboard Commissioning Specifications (80 Wavelengths)

Nominal Single Nominal Single
Input optical Wavelength Wavelength Nominal gain
subboard
power range Input optical Output optical gain Scope
power power
20 - 31
OAC101 -30 - -19 dBm -19 dBm 1 dBm 20 dB
dB
24 - 36
OAC103 -32 - -23 dBm -23 dBm 1 dBm 24 dB
dB
24 - 36
OAC106 -24 - -15 dBm -15dBm 1 dBm 16 dB
dB
OBC103 -32 - -22dBm -22 dBm 1 dBm 23 dB 23 dB
Common board insertion loss specifications:
Table 1-12 Insertion loss of multiplexer/demultiplexer boards
Board Board
Insertion loss Insertion loss
Name Name
EX40 ≤ 6.5 dB ≤ 1 dB (LINE1-SYS1, LINE B-SYS2)

DSFIU
X40 < 6.5 dB ≤ 1.5 dB (LINE1-OSC1, LINE B-OSC2)
<5 dB (RE-OUT, RO-OUT) ≤ 1.5 dB (IN-TM, RM-OUT)

ITL DFIU
<2.5 dB (IN-TE, IN-TO) ≤ 1 dB (IN-TC, RC-OUT)
WSMD4 ≤8dB (IN-DMx, AMx-OUT) FIU ≤1 dB
Incident optical power requirements:
Table 1-13 Incident optical power requirements

Number of Incident optical power
Module Type system
wavelengths G.652 (dBm) G.655 (dBm)
40
+1 -1
wavelengths
100G ePDM-QPSK
80
+1 -1
wavelengths
40
+4 +2
wavelengths
40G DQPSK
80
+1 +1
wavelengths
40
+4 +4
wavelengths
10G DRZ
80
+1 +1
wavelengths
Take the 80/192.1TH service from NE A to NE B as an example. Adjust the optical power in the
direction from NE A to NE B.
Open the NE Explorer of NE A. In the navigation tree, select the UNQ2 board in
slot 4 of subrack 0 and choose Configuration > WDM Interface from the Function
Tree.
Ensure that Channel Use Status is Used, Optical Port Loopback is No Loop, and
Laser Status is On for the IN2/OUT2 port.
According to the signal flow diagram shown in Figure 1-9, adjust the optical
power of each wavelength on the EX40 board in slot 2 of subrack 2 to ensure that
the optical power of each wavelength is the same (adjust the flatness). Based on
the information in Tables 1-5, the IN7 port on the OPM8 board in slot 6 of
subrack 2 of NE A is connected to the MOND port on the EX40 board.
In the NE Explorer of NE A, select the OPM8 board in slot 6 of subrack 2 from the
navigation tree. Choose Configuration > Laser Spectrum Analysis from the
Function Tree.
Select 7(IN7) from the Port No. drop-down list on the right, set Compensation
Power to 10, and click Refresh.
Check whether the optical power is flat based on the optical power in the
spectrum data. If the optical power is too high, add a fixed attenuator to the port
connected to the EX40 board. (In this example, the EX40 board does not support
EVOAs. Therefore, a fixed refresh is required. If the M40V or ROADM board is
configured, you can commission the EVOA of each channel on the board to adjust
the flatness.)
According to the signal flow diagram shown in Figure 1-9, adjust the IN_2 input
optical power and OUT_2 output optical power of the DAP board in slot 5 of
subrack 2.
In the NE Explorer of NE A, right-click the DAP in slot 05 of subrack 2 in the

navigation tree and choose Board Manufacturer Information from the shortcut
menu to query the type of the OA subboard.
In the dialog box that is displayed, the type of the OA subboard used between
IN_2 and OUT_2 is TN15OAC106.
Query the input optical power, output optical power, and gain specifications of the
TN15OAC106 board in Table 1-10.
According to the information in Table 1-5, port 4 of the OPM8 board in slot 6 of
subrack 2 on NE A is connected to the MON_2 port of the DAP board. Therefore,
you can query the signal quality of the output optical signals at the OUT_2 port of
the DAP board.
In the NE Explorer of NE A, select the OPM8 board in slot 6 of subrack 2 from the
navigation tree. Choose Configuration > Laser Spectrum Analysis from the
Function Tree.
Select 4(IN4) from the Port No. drop-down list on the right, set Compensation
Power to 20, and click Refresh.
Check whether the optical power meets the nominal output optical power based
on the optical power in the spectrum data. If the optical power is too high or too
low, go to step 15. Otherwise, go to step 20.
In the NE Explorer of NE A, select the DAP in slot 5 of subrack 2 from the

navigation tree. Choose Configuration > WDM Interface from the Function Tree.
On the Basic Attributes tab page, check whether the gain value of the OUT_2 port
is the same as the nominal gain value of the OAC16 port listed in Table 1-10. If
yes, go to Step 17. If no, increase or decrease the nominal gain value of the
OUT_2 port, after the modification, click Apply. Ensure that the value of Gain is
the same as the nominal gain of the OAC16 in Table 1-10.
Repeat steps 12 to 13 to view the optical power in the Spectrum Data area and
calculate the difference between the optical power and the nominal single-
wavelength output optical power. (Difference = Query optical power – Nominal
single-wavelength output optical power)
Repeat step 15 to modify the Optical Interface Attenuation Ratio of the

1(subrack)-5-B1DAP-6(VI_2)-1 board in the optical channel subrack based on the
calculated Difference. The modified value is the current value plus the Difference.
After the modification, repeat steps 12 to 13 to check whether the optical power
meets the requirement (the difference between the current optical power and the
nominal optical power does not exceed 1 dB). If the optical power meets the
requirement, go to step 20. If the optical power does not meet the requirement,
go to step 18 to adjust the optical port attenuation until the optical power meets
the requirement.
Repeat steps 3 to 19 to adjust the input optical power and output optical power
and gain of IN_1 on the DAP board in slot 5 of subrack 0 on NE B.
Open the NE Explorer of NE A. Select the UNQ2 board in slot 4 of subrack 0 from
the navigation tree. Choose Configuration > Optical Power Management from the
Function Tree to view the received optical power of the IN1 port.
If the receive optical power is too high, add a fixed attenuator to the IN1 port to
adjust the received optical power to the value listed in Table 1-9. If yes, replace
the FOA or check the pigtail.
Repeat the preceding steps to adjust the reverse signal flow.
1.3.4 Backing Up Data

Back up the NE database after configuring data. The NE database ensures that the NE
automatically recovers after the data on the SCC board is lost or the NE is powered off.
NE data backup can be performed on the OSS client or server. For details about the
backup location of each NE, see the following table.
Table 1-14 Backup information
Site NE Backup Location
Backing Up Data to the

NE A 184-223
OSS Server
Backing Up Data to the

NE B 184-224
OSS Server
184-225 Backing Up Data to the

NE C
184-228 OSS Client
Before backing up data, ensure that the DC user has logged in. If the DC user has not
logged in, choose Security > NE Login Management from the main menu and manually
log in to the DC User Management tab. Generally, the szhw user is used for login.
Choose Maintenance > NE Software Management > NE Data Backup/Restoration

from the main menu.
In the NE View list, select the NE to be backed up and click Backup in the lower
right corner. The Backup dialog box is displayed.
Select OSS Server or OSS Client to back up the selected device information.
(Optional) If you select OSS Client, the backup file is automatically downloaded to
the PC using a browser after the backup is complete.
Click Start. The backup progress is displayed on the NE View tab page.
After the backup is successful, the NCE creates the

NEName/yyyymmddhhmmss/dbf.pkg directory and file in the specified directory.
In the preceding command, NEName indicates the NE name, yyyymmdd indicates
the year, month, and day, and hhmmss indicates the backup time.
2 MS-OTN Service Configuration
2.1 OTN Service Configuration

In this experiment, you can configure electrical-layer cross-connections on tributary and
line boards to implement OTN service communication between clients.
2.1.1.1 Objective
⚫ Understand the basic working principles of electrical-layer cross-connections.
⚫ Master the methods of configuring electrical-layer services.
2.1.1.2 Experiment Networking
2.1.1.3 Experiment Planning

Configure a client service at the GE rate between OADM A and OADM B. The following
table lists the service planning.
Table 2-1 Service parameter planning

Parameter Source NE
Service type GE
Service route OADM A-----OADM B
Carrying wavelength 80th wavelength
Source NE NE A
Source Board 006-TTA
Source Port TX1/RX1
Sink NE NE A
Sink Board 006-TTA
Sink Port TX1/RX1
Wavelength diagram
2.1.2 Create OTN Service by Trail

Create a WDM trail. After configuring optical-layer trails on NCE, you can create ODUk or
Client trails by specifying the source and sink of the trails. This section uses the TTA +
UNQ2 board as an example to describe how to configure GE services in end-to-end
mode.
In the Main Topology, right-click in the blank area and choose Create Trail >
Create WDM Trail from the shortcut menu.
In the dialog box that is displayed, set Level to Client and Rate to GE (GFP-T).
Click Browse on the right of the Source field. In the dialog box that is displayed,
select the required NE OADM -A and the source board TTA.
If the board where the source port resides is a multi-application board, click Set
Working Mode in the Select Board Port-Source dialog box and set Working Mode
for the source port based on the network plan. In this example, set Working Mode
to ODU0 Non-convergence Mode.
Select the RX1/TX1 port on the TTA board as the source port of the end-to-end
trail and click OK.
Repeat the preceding steps to set the sink port. Click Browse on the right of the
Sink field. In the dialog box that is displayed, select the desired NE, select the port
as the sink port of the E2E trail, and click OK.
In the Route Calculation area, select Auto Calculate.
After route calculation is successful, the working route between the source and sink NEs is
displayed in blue. If the automatically calculated route is not the planned route, use one
of the methods described in Step 8-10 to restrict the route.
(Optional) Set explicit links. Click an OCh server link between the source and sink
NEs.
In the dialog box that is displayed, specify the explicit server link for the service.
After selecting the Select Channel check box, you can select the channels of the
explicit link.
(Optional) Set explicit nodes. If the calculated route is used, right-click an NE and
choose Set Explicit Node > NE or Set Explicit Node > Board/Port from the shortcut
menu to set an NE, board, or port as the explicit node of the trail to be created.
Indicates whether an NE is displayed. Double-click the NE again to deselect the
NE.
(Optional) Set excluded nodes. Right-click an NE and choose Set Excluded Node >
NE or Set Excluded Node > Board/Port from the shortcut menu to set an NE,
board, or port as the excluded node of the trail to be created. Indicates whether
an NE is displayed. Double-click the NE again to deselect the NE.
After route calculation is successful, the server-layer route information of the trail
to be created, the list of new dynamic cross-connections, and the list of port
attributes are displayed at the bottom of the topology view.
Click Apply. The Create Trail dialog box is displayed, showing the path creation
progress. After the trail is created successfully, a dialog box is displayed, indicating
that the operation is successful.
2.1.3 Create OTN Service Station by Station

Double-click the optical NE OADM-A. Right-click the desired NE and choose NE
Explorer from the shortcut menu. In the NE Explorer, right-click the NE and
choose Configuration > WDM Service Management from the Function Tree.
Click the WDM Cross-Connection Configuration tab.
Click New. In the Create Cross-Connection Service dialog box, select ODU0 level,
tributary TTA, and line board UNQ2 (the line board that carries the 80th
wavelength) according to the planning in Table 2-1.
Click OK. The Operation Result dialog box is displayed, indicating that the
operation is successful. Click Close.
The created cross-connection is displayed in the WDM Cross-Connection

Configuration window.
In the NE Explorer, click 06-TTA and choose Configuration > WDM Interface from
the Function Tree.
In the right pane, set Service Type to GE for TX1/RX1 and click Apply.
Repeat the preceding steps to configure cross-connections on NE B.
Choose Service > View > WDM Trail from the main menu.
In the WDM Trail dialog box, click Search for WDM Trail.
In the WDM Trail Search dialog box, click Next.
After the search is complete, click Next.
If the fiber connections and NE parameters are correct, the Client trail is displayed
in the Searched Trails list.
Click Next. If the fiber connection or NE parameters are incorrect, the Client trail is
incomplete and displayed in the Discrete Service list.
Click Finish.
2.2 UNI-UNI E-Line service

In this experiment, Ethernet ports are configured on Ethernet boards to implement
Ethernet service communication between different customers.
2.2.1.1 Objectives
⚫ Understand the basic working principles of E-Line services.
⚫ Understand the types of E-Line services.
⚫ Master the configuration of the E-Line service.
⚫ Understand the functions of different types of Ethernet ports.
Networking diagram for configuring UNI-UNI E-Line

services

On the network shown in Figure 2-3, the service requirements of user A are as follows:
• UserA1 and UserA2 communicate with each other. The services of UserA1 are accessed
through port 5-EX10-1, and the services of UserA2 are accessed through port 5-EX10-1.
• The services between UserA1 and UserA2 are classified into DCI service. The DCI service can
occupy 50M bit/s bandwidth at a burst. Table 2-2 describes the service requirements.
Table 2-2 E-Line Service Requirements
Service Type Service requirements
DCI CIR = 10 Mbit/s, PIR = 50 Mbit/s

Table 2-3 UNI-UNI E-Line service planning
Parameter Value Description
The value of ID can be manually

Service ID. 1
entered.
This topic describes how to create a

Direction UNI-UNI
UNI-UNI Ethernet service.
5-EX10-1 is connected to UserA1 and

NE A: 5-EX10-1, 3-UNQ2-2 UserA2, and 3-UNQ2-1 & 3-UNQ2-2
UNI
NE B: 5-EX10-1, 3-UNQ2-1 for NE A and NE B to connect each
other.
VLANs -
QoS for DCI CIR = 10048 kbit/s,

-
Services PIR = 50048 kbit/s
2.2.2 Configuration Procedure

Configure the Ethernet interface in NE A and NE B.
In the NE Explorer, select 3-UNQ2 and choose Configuration > Virtual Port
Mapping Management from the Function Tree.
Set Port Type: ”ETH”, Bandwidth: ”GE”, Quanity: ”1”, and Mapped
ODUk: ”2(IN2/OUT2)-OCh:1-ODU2-ODU0:1” according to the service plan, and
click Add.
Remember Port name is “40001(V_ETH_1)”, then click Apply complete the

configuration.
In the NE Explorer, select NE A and choose Configuration > Packet Configuration >
Interface Management > Ethernet Interface from the Function Tree.
Select 5-EX10-1 and 3-UNQ2-40001 from port list, and set Basic Attributes as
planned.
Procedure Description
• For used ports, set Enable Port to Enabled. For unused ports,
set Enable Port to Disabled.
• Set Encapsulation Type to Null.
• For an Ethernet port that is connected to external equipment,
Setting
set Working Mode to be the same value as the external equipment
General
(the working mode of the external equipment is generally auto-
Attributes for
negotiation). For an Ethernet port within the network, set Working
Ethernet
Mode to Auto-Negotiation.
Ports
• When jumbo frames are transmitted, set Max Frame Length
(byte) according to the actual length of the jumbo frames.
Otherwise, it is recommended that you set Max Frame Length
(byte) to 1522.
Required when the flow control function is enabled on the external
equipment to which the Ethernet port is connected.
• When the external equipment uses the non-auto-negotiation flow
Configuring control function, set Non-Autonegotiation Flow Control
Flow Control Mode to Enable Symmetric Flow Control.
• When the external equipment uses the auto-negotiation flow
control function, set Negotiation Flow Control Mode to Enable
Symmetric Flow Control.
Click Apply complete the configuration. Refer to step 1-5 to configure the Ethernet
ports in NE B.
C Create an OCh between NE A and NE B. For details, see section 1.2.
Configure the ethernet service between UserA1 and UserA2.

Ethernet Service Management > E-Line Service from the Function Tree.
Click Create. The Create E-Line Service dialog box is displayed.
Set the parameters of the service between UserA1 and UserA2.
Parameter Value
Service ID. 2
Service Name E-Line-1
Direction UNI-UNI
Port 5-EX10-1(Port-1)
VLANs -
Port 3-UNQ2-40001
VLANs -
BPDU Not transparently transmitted
MTU(bytes) 1526
Click Configure QoS. The Configure QoS dialog box is displayed.
Click the UNI tab.

Set the QoS parameters of the service between UserA1 and UserA2.
Parameter Value
Interface 5-EX10-1 (port-1)
Direction Egress
Bandwidth limit Enable
Committed Information Rate (kbit/s) 10048
Peak Bandwidth (kbit/s) 50048
Other parameters Default Value
Refer to step 8-13 to configure the DCI service in NE B.
2.2.3 Verification
Verifying the Connectivity of E-Line Services Using the Ethernet Service OAM Function
Create MDs, MAs, and MEPs for the three Ethernet services.
After Ethernet service OAM is configured, activate the CC function for the Ethernet
services.
If the Ethernet service configuration is correct, no ETH_CFM_LOC alarm is reported at the
MEP site. You can also use the LB test to check the service connectivity.
E-Line service connectivity check
Item Description Status
ETH Service OAM

Set basic ETH OAM parameters. □ Yes □ No
Configuration
Activating the CC of the source and sink

CC test □ Yes □ No
Ethernet ports
LB test Executing LB □ Yes □ No
Whether the MEP reports the ETH_CFM_LOC

Service alarm □ Yes □ No
alarm
2.3 E-Line services carried by ports(Based on VLAN)

In this experiment, Ethernet private line services are configured to enable different
services at different sites to communicate through the same transport device port
through the Ethernet.
2.3.1.1 Objectives
⚫ Understand the basic working principles of E-Line services.
⚫ Master the configuration of the E-Line service.
⚫ Learn how to divide VLANs.
⚫ Understand the functions of different types of Ethernet ports.
Networking diagram of service configuration

UserA1 and UserA2 communicate with each other. The video service is transmitted
through port 5-EX10-1, and the data service is transmitted through port 5-EX10-2.
The video service need to be isolated from the data service.
The services between UserA1 and UserA2 include the video conference and data services.
The video services use fixed bandwidth, and the common DCI service can use all
bandwidth at a burst. Table 2-4 describes the service requirements.
Table 2-4 Service requirements
Service Type Service Requirements
Video service (VLAN ID = 100) Fixed bandwidth CIR = PIR = 40 Mbit/s
Data Service (VLAN ID = 200) CIR = 10 Mbit/s, PIR = 50 Mbit/s
Services between UserA1 and UserA2 are classified into video services, video services, and
common DCI services. The three types of services are differentiated by VLAN tags. In
addition, video and video services have fixed bandwidths, whereas common DCI services
can occupy bandwidths abruptly. Therefore, different QoS processing is required for
different services. Table 2-5 describes the service planning.
Table 2-5 Planning information about E-Line services

Parameter NE A NE B Description
The value of ID can be

Service ID 1, 2 1, 2
manually entered.
In this example, the UNI-

Direction UNI-UNI UNI-UNI UNI E-Line services are
created.
The 5-EX10-1 for video

UNI
5-EX10-1, 5-EX10-2 5-EX10-1, 5-EX10-2 service, and the 5-EX10-2
interface
for data service.
The VLAN ID of the video

service is 100.
VLANs 100,200 100,200
The VLAN ID of the data
service is 200.
BPDU packets are

processed as service
packets and must match
Not transparently Not transparently the port attribute. When
BPDU
transmitted transmitted the port attribute is Tag
Aware, BPDU packets are
discarded because they do
not carry VLAN tags.
This section describes how

Bearer to configure the UNI-UNI
Port Port
Type E-Line services carried by
ports.
UNI
3-UNQ2-1 3-UNQ2-1 -
interface
QoS for Fixed bandwidth:

Fixed bandwidth: CIR
video CIR = PIR, 40000 -
= PIR, 40000 kbit/s
Services kbit/s
QoS for
CIR = 0 kbit/s, PIR = CIR = 0 kbit/s, PIR =
Data -
50048 kbit/s 50048 kbit/s
Services
Table 2-6 Planning of Ethernet Ports

NE LSR ID Port Port Attribute Encapsulation Type
Port mode: Layer 2

5-EX10-1(PORT-1)
Tag identifier: Access 802.1Q
5-EX10-2(PORT-2)
Default VLAN: 100
NEA 130.0.0.1
Port mode: Layer 2
3-UNQ2-2(40002) Tag identifier: Tag 802.1Q
Aware
5-EX10-1(PORT-1) Port mode: Layer 2

802.1Q
5-EX10-2(PORT-2) Tag identifier: Access
NEB 130.0.0.2 Port mode: Layer 2
3-UNQ2-1(40001) Tag identifier: Tag 802.1Q
Aware

Configure Ethernet interface in NE A and NE B.
In NE A NE Explorer, select 3-UNQ2 and choose Configuration > Virtual Port

click Add.

configuration.
Select 5-EX10-1, 5-EX10-2 and 3-UNQ2-40001 from port list, and set Basic
Attributes as planned.
For used ports, set Enable Port to Enabled. For unused ports,
Set Encapsulation Type to 802.1Q.
For an Ethernet port that is connected to external equipment,
set Working Mode to be the same value as the external equipment
Setting General
Attributes for (the working mode of the external equipment is generally auto-
Ethernet Ports negotiation). For an Ethernet port within the network, set Working
When jumbo frames are transmitted, set Max Frame Length
(byte) to 1522.

When the external equipment uses the non-auto-negotiation flow
Configuring Flow control function, set Non-Autonegotiation Flow Control
Control Mode to Enable Symmetric Flow Control.
When the external equipment uses the auto-negotiation flow
Click Apply complete the configuration. Click the Layer2 Attributes tab. After
setting the parameter on this tab page, click Apply.
3-UNQ2-40001:Tag
Aware If TAG is set to Access for a port, only data
TAG frames carrying no VLAN tags can enter the
5-EX10-1: Access
port.
5-EX10-2: Access
According to the plan, the VLAN ID is set to 100

on the transmission network side for video
Default 5-EX10-1: 100
services.
VLAN ID 5-EX10-2: 200
The VLAN ID is set to 200 on the transmission
network side for data services.
VLAN
- This parameter is set to the default value.
Priority
Refer to step 1-7 to configure the Ethernet ports in NE B.
On NE A, configure the video service and data service between UserA1 and UserA2.
Click Create. The Create E-Line Service dialog box is displayed.

Set the parameters of the services between UserA1 and UserA2.
Parameter Value
Service ID. 1
Direction UNI-UNI
MTU(bytes) 1500
Source Port 5-EX10-1 (port-1)
Source VLANs 100
Sink Port 3-UNQ2-40001
Sink VLANs 100
Click the UNI tab.

Set the QoS parameters for the E-Line service between UserA1 and UserA2.
Parameter Value
Interface 5-EX10-1 (port-1)
Direction Egress
Bandwidth Limit Enable
Policy Note: Select a configured QoS policy.
Click Apply complete the configuration.
Refer to step 8-14, According to the “Table 2-5 Planning information about E-Line
services” to configure the data service in NE A.
Refer to the steps 8-15, configure the services on NE B.
2.3.3 Verification
Verifying the Connectivity of E-Line Services Using the Ethernet Service OAM Function
E-Line service connectivity check:
Item Description Status
ETH Service OAM Basic ETH OAM parameters have been

□ Yes □ No
Configuration configured.
Activating the CC of the source and sink

CC test □ Yes □ No
Ethernet ports
LB test Executing LB □ Yes □ No
Whether the MEP reports the ETH_CFM_LOC

Service alarm □ Yes □ No
alarm
2.4 E-Line services carried by QinQ

In this experiment, Ethernet private line services are configured to implement shared
transmission among different customers who may use the same VLAN ID.
2.4.1.1 Objectives
⚫ Understand the basic working principle of QinQ.
⚫ Understand how to configure QinQ bearer for E-Line services.
⚫ Master the method of dividing S-VLANs.
Example network of the E-Line services carried by QinQ

links

In the network shown in Figure 2-6, the service requirements of user A and user B are as
follows:
• User A1 and User B1 access NE A through 5-EX10-1 and 5-EX10-2 respectively.
• User A2 and User B2 are connected to NE B through 5-EX10-1 and 5-EX10-2 respectively.
• Services of user A and user B need to be isolated. The internal VLAN of user A is 100, and
the internal VLAN of user B is 1 to 100.
• Add different S-VLANs on the network side to isolate services. Add VLAN 30 for user A and
VLAN 40 for user B.
• The service between User A1 and User A2 is a DCI service. The CIR is 10 Mbit/s and the PIR
is 50 Mbit/s.
• The service between UserB1 and UserB2 is a data service. The CIR is 30 Mbit/s and the PIR is
50 Mbit/s.
Services need to be carried by QinQ links. Therefore, service planning also includes QinQ
link planning. The E-Line services carried by QinQ links include:
• Table 2-7 lists the planning of QinQ links that carry services.
• Table 2-8 provides the planning information about the UNI-NNI E-Line services carried by
QinQ links.
Table 2-7 Planning of QinQ links that carry services
Parameter UserA (NE A-NE B) UserB (NE A-NE B)
QinQLink ID 1 2
Board 3-UNQ2 3-UNQ2
NE A: port 40002 , NE A: port 40002

Port
NE B:port 40001 NE B:port 40001
S-VlanID 30 40
Bandwidth
Enable Enable
limit
CIR(kbit/s) 10048 30016
PIR(kbit/s) 50048 50048
Table 2-8 Planning of the UNI-NNI E-Line services carried by QinQ links
Parameter UserA UserB
Service ID. 1 2
Service Name E-Line-1 E-Line-2
Direction UNI-NNI UNI-NNI
UNI 5-EX10-1 5-EX10-2
VLANs 100 100
Bearer type QinQLink QinQLink
QinQLinkID 1 2
Not transparently Not transparently

BPDU
transmitted transmitted
MTU(bytes) 1526 1526

The engineering information for configuring the E-Line services carried by QinQ links
includes the engineering information for configuring the QinQ links that carry services
and the engineering information for configuring the UNI-NNI E-Line services carried by
QinQ links.
Configure Ethernet interface in NE A and NE B.

click Add.

configuration.
Select 5-EX10-1, 5-EX10-2 and 3-UNQ2-40001 from port list, and set Basic
Attributes as planned.
For used ports, set Enable Port to Enabled. For unused ports,
3-UNQ2-40001 Set Encapsulation Type to QinQ.
5-EX10-1 and 5-EX10-2 Set Encapsulation Type to 802.1Q.
For an Ethernet port that is connected to external equipment,
Setting General set Working Mode to be the same value as the external equipment
Attributes for (the working mode of the external equipment is generally auto-
Ethernet Ports negotiation). For an Ethernet port within the network, set Working
When jumbo frames are transmitted, set Max Frame Length
(byte) to 1522.

When the external equipment uses the non-auto-negotiation flow
Configuring control function, set Non-Autonegotiation Flow Control
Flow Control Mode to Enable Symmetric Flow Control.
When the external equipment uses the auto-negotiation flow
Click Apply complete the configuration. Click the Layer2 Attributes tab. After
setting the parameter on this tab page, click Apply.
5-EX10-1: Tag Aware If TAG is set to Tag Aware for a port, only data
TAG
5-EX10-2: Tag Aware frames carrying VLAN tags can enter the port.
Default
- -
VLAN ID
VLAN
- This parameter is set to the default value.
Priority
Refer to step 1-7 to configure the Ethernet ports in NE B.

QinQ links need to be configured on NE A, and NE B.
In the NE A’s NE Explorer, select the 3-UNQ2 board and choose Interface
Management > Ethernet Interface from the Function Tree.
Select port 3-UNQ2-1 and set Encapsulation Type to QinQ.
Click Apply.
In NE A NE Explorer, select the NE and choose Configuration > Packet

Configuration > Ethernet Service Management > QinQ Link from the Function
Tree.
Click Create. The Create QinQ Link dialog box is displayed.
Click the Basic Attributes tab, and then set QinQ Link ID, Board, Port, and S-Vlan
ID base on Table 2-8.
Refer to steps 11-13, create QinQ Link 1 and 2 base on Table 2-7 on NE A and NE B.
On NE A, configure the E-Line service of UserA1:
Click New. In the Create E-Line Service dialog box, set the parameters of the E-
Line service of UserA1.
Parameter Value
Service ID. 1
Direction UNI-NNI
MTU(bytes) 1526
Source Port 5-EX10-1
Source VLANs 100
Bearer type QinQLink
QinQLinkID 1
Click the UNI tab and set QoS parameters for UserA1.
Parameter Value
Interface 5-EX10-1(Port-1)
Direction Egress
On NE A, configure the E-Line service of UserB1:
Repeat Step 14-17 to configure the E-Line service for UserB1.
Set the parameters of the E-Line services carried by the QinQ link of UserB1:
Parameter Value
Service ID. 2
Direction UNI-NNI
MTU(bytes) 1526
Port 5-EX10-2
VLANs 100
Bearer type QinQLink
QinQLinkID 2
Configure QoS parameters for UserB1.

Parameter Value
Direction Egress
On NE B, configure the E-Line services of UserA2 and UserB2:

Repeat Step 14-20 to configure E-Line services for UserA2 and UserB2.
2.4.3 Verification
The connectivity of the UNI-UNI Ethernet service does not need to be verified by 802.1ag
OAM. By default, the connectivity of the UNI-UNI Ethernet service is correct. For UNI-NNI
Ethernet services carried by ports, QinQ links, and PWs, the verification methods of
802.1ag OAM are similar. To verify the correctness of service configurations, you need to
configure Ethernet OAM.
Procedure
On NE A and NE B, create an MD for the service between UserA1 and UserA2.
The parameters of the MD are as follows:
Parameter NE A NE B
MD Name MD MD
MD level 4 4
The names and levels of the MDs created on NE A and NE B must be the same so
that NE A and NE B belong to the same MD.
On NE A and NE B, create a maintenance association for the services between

UserA1 and UserA2.
The parameters of the MA are as follows:
Parameter NE A NE B
MD Name MD MD
Maintenance Association
MA MA
Name
Related Services 1-E-Line-1 1-E-Line-1
CC Test Sending Period

3.33 ms 3.33 ms
(ms)
Create MEPs on NE A and NE B.
MEP parameters are as follows:
Parameter NE A NE B
MD Name MD MD
MA MA
Name
Board 5-EX10 5-EX10

Port 1 (port-1) 1 (port-1)
VLAN 100 100
MPID 1 2
Direction Ingress Ingress
CC Status Activation Activation
On NE A and NE B, create remote MEPs and perform the CC test.
• If the MEP of NE B does not receive the CC packets from the MEP of NE A within a period of
time (for example, 3.25 times the transmission period), the MEP of NE B automatically
reports the ETH_CFM_LOC alarm. If the alarm is not reported, it indicates that the
connectivity of the service from NE A to NE B is normal.
• If the MEP of NE A does not receive the CC packets from the MEP of NE B within a period of
time (for example, 3.25 times the transmission period), the MEP of NE A automatically
connectivity of the service from NE B to NE A is normal.
2.5 E-Line services carried by PWs (VPWS)

In this experiment, E-Line services are configured to enable transmission devices to
transmit Ethernet services in packet mode.
2.5.1.1 Objectives
⚫ Understand the basic working principles of E-Line services carried by packets.
⚫ Learn how to configure the E-Line service carried by packets.
Networking diagram

In the network shown in Figure 2-5, the service requirements of user A and user B are as
follows:
• User A1 and User B1 access NE A through 5-EX10-1 and 5-EX10-2 respectively.
• User A2 and User B2 access NE B through 5-EX10-1 and 5-EX10-2 respectively.
• The DCI service between UserA1 and UserA2 is a common service. The CIR is 10 Mbit/s and
the PIR is 30 Mbit/s.
• Data services are transmitted between UserB1 and UserB2. The CIR is 30 Mbit/s and the PIR
is 50 Mbit/s.
• The two PWs carry the services of user A and user B respectively.
• Two PWs share the bandwidth of one tunnel.
Table 2-9 LSR ID and port planning
NE Port IP IP Mask LSRID
NE A 3-UNQ2-2(Virtual Port:40002) 10.0.1.1 255.255.255.252 130.0.0.1
NE B 3-UNQ2-1(Virtual Port:40001) 10.0.1.2 255.255.255.252 130.0.0.2
The IP addresses of Ethernet ports on the same NE must be on different network

segments.
The IP addresses of the ports at both ends of a link must be on the same network
segment.
PWs that carry Ethernet services are carried by tunnels. Therefore, you need to plan
tunnels during service planning. Therefore, the planning of E-Line services carried by PWs
includes the following:
• Table 2-10 and Table 2-11 describe the planning of tunnels that carry PWs.
• Table 2-12 lists the MPLS tunnel OAM planning.
• Table 2-13describes the PW planning.
• Table 2-14 provides the planning information about the UNI-NNI E-Line services carried by
PWs.
Table 2-10 Planning of basic attributes of MPLS tunnels
Parameter Value
Tunnel Name Automatic allocation
Protocol Type MPLS
Signaling Type Static CR
Direction Bidirectional
Protection Type Null
Table 2-11 MPLS Tunnel Planning
Rev Rev
Inb
Inco erse Out Out ers
Tun No oun Outb Ne
min inco goin goin e
Tun N de d ound xt No No
nel g min g g Ne
nel E Ty inte Inter Ho de de
ID labe g labe labe xt
pe rfac face p
l labe l l Ho
e
l p
Auto 3-
Wor 13
mati Ing UNQ 10.
king N 0.0
c res - - 102 2- 100 - 0.1. - -
tun EA .0.
alloc s 4000 2
nel 2
atio 2
n 3-
13
UN 10.
N Egr 0.0
Q2- 101 - - - 103 - 0.1. -
EB ess .0.
400 1
1
01
• In E2E mode, Tunnel ID, Incoming label, Outgoing label, Reverse incoming label, and Reverse
outgoing label can be automatically allocated.
Table 2-12 MPLS tunnel OAM parameters
Parameter Planning
Attribute
Source Sink
Enable the receiving and sending Enable the receiving and

OAM Status
functions. sending functions.
Detection Mode Manual Manual
FFD
Detection
This parameter can be set only when FFD
Packet Type
Detection Packet Type is set to FFD.
3.3
Detection Generally, OAM packets are reported

Packet Period after three periods. If Detection 3.3
Packet Period (ms) is set to 3.3, the
(ms)
switching time is less than 50 ms after
a fault occurs.
CV/FFD status Start Start
Table 2-13 PW Planning

Parameter User A PW User B PW
PW signaling type Static Static
PW Type Ethernet tag mode Ethernet tag mode
Direction Bidirectional Bidirectional
PW ingress label 20 30
PW egress label 20 30
NE A 130.0.0.1 130.0.0.2
Peer LSR ID
NE B 130.0.0.2 130.0.0.2
MPLS Tunnel Name NE A_NE B NE A_NE B

Bandwidth limit Enable Enable
CIR(kbit/s) 10048 30016
PIR(kbit/s) 30016 50048
Request VLAN 10 20
Table 2-14 Planning of the UNI-NNI E-Line services

Parameter UserA UserB
Service ID. 1 2
Service Name E-Line-1 E-Line-2
Direction UNI-NNI UNI-NNI
UNI 5-EX10-1 5-EX10-2
VLANs 100 100
Bearer type PW PW
PWID 35 45
Not transparently Not transparently

BPDU
transmitted transmitted
MTU(bytes) 1500 1500

The engineering information for configuring the PW-carried E-Line service includes the
engineering information for configuring the tunnel that carries the PW, the engineering
information for configuring the PW, and the engineering information for configuring the
UNI-NNI E-Line service carried by the PW.
Set the LSR ID of each NE according to Table 2-6.
In NE A NE Explorer, select the desired NE and choose Configuration > Packet

Configuration > MPLS Management > Basic Configuration from the Function Tree.
Set LSR ID.

Refer to steps 1-2 to configure the LSR ID for the MPLS tunnels of NE B according to
Table 2-9.

click Add.
In NE A NE Explorer, click an NE and choose Configuration > Packet

Configuration > Interface Management > Ethernet Interface from the Function
Tree.
Click the Basic Attributes tab, and then set the parameters of the port.
Set the parameters related to the basic attributes of the port as follows:
• Port Enabled: Enabled

• Port mode: Layer 3
Click Apply.
Click the Layer 3 Attributes tab.
Select the desired port, set Enable Tunnel to Enabled, set specify IP to Manual,
and set IP Address and IP Mask according to the service plan.
Refer to steps 3 to 10 to configure ports on NE B.

Configuring Tunnels to Carry Services
Choose Service > Create > Static Tunnel from the main menu.
Configure the tunnel according to the parameter planning.
Table 2-15 Planning of basic attributes of MPLS tunnels
Attribute Parameter Planning
Tunnel Name NE A_NE B
Protection Tunnel Name Automatic allocation
Protocol Type MPLS
Signaling Type Static CR
Protection Type 1+1
Protection group name. Automatic allocation
Switching Mode Single-ended switching
Table 2-16 MPLS Tunnel Planning

Rev
Ou Reve ers
Tu Inbo Outb Ne Sour Sin
Nod Inco Reverse tgo rse e
nn N und ound xt ce k
e ming incomin ing outg Ne
elI E inter Interf Ho Nod No
Type label g label lab oing xt
D face ace p e de
el label Ho
p
3-
N 10. 13
Ingre UNQ2 10
E - - 102 - 0.1. - - 0.0.
ss - 0
A 2 0.2
40002
Au
to 3-
N UNQ 10.
Egre 130.
E 2- 101 - - - 103 - 0.1. -
ss 0.0.1
B 4000 1
1
Table 2-17 MPLS tunnel OAM parameters

Parameter Planning
Attribute
Source Sink
Enable the receiving and sending Enable the receiving and

OAM Status
functions. sending functions.
Detection Mode Manual Manual
Detection Packet FFD FFD

Type This parameter can be set only when
Detection Packet Type is set to FFD.
3.3
Generally, OAM packets are reported
Detection Packet after three periods. If Detection 3.3
Period (ms) Packet Period (ms) is set to 3.3, the
switching time is less than 50 ms
after a fault occurs.
CV/FFD status Start Start
Configure the common DCI service between UserA1 and UserA2 in end-to-end mode:
Choose Service > Create > PWE3 Service from the main menu.
Set the basic attributes of the common DCI service between UserA1 and UserA2.
Table 2-18 Parameters of the E-Line services between UserA1 and UserA2
Parameter Value
Service Type ETH
Service ID. 1
Protection Type unprotected
Configure the source and sink NEs of the PWE3 service:
On the Node List tab page, click Configure Source and Sink. The Configure Source
and Sink dialog box is displayed.
Select the source and sink NEs in the Physical Root navigation tree on the left.
In the SAI Configuration dialog box, set the attributes of the SAI for the Ethernet
service and click Add Node.
Parameter Value
Port 1
Source
VLANID 100
Port 1
Sink
VLANID 100
Click the PW tab and set the basic attributes of the PW.
Parameter Value
PWID 35
Signaling Type Static
Forward label 20
Reverse label 20
Forward Type Static binding
Forward Tunnel NE A_NE B
Reverse Type Static binding
Reverse Tunnel NE A_NE B

Encapsulation type MPLS
Click Detail and configure advanced PW attributes.
Click the PW QoS tab and set PW QoS parameters.
Parameter Value
Committed Information
Forward 10000
Rate (kbit/s)
Reverse 10000
Rate (kbit/s)
Click the PW Advanced Parameters tab and set the advanced attributes of the PW.
Parameter Value
PW Type Ethernet tag mode
Request VLAN 10
If you need to configure alarms along with services, select Ethernet OAM CC in the lower
left corner to enable the function of continuously detecting device connectivity faults.
Click OK.
Repeat steps 1-20 to configure the data service between UserB1 and UserB2 in
end-to-end mode.
Parameters of the E-Line service between UserB1 and UserB2:
Parameter Value
Service Type ETH
Service ID. 2
Protection Type unprotected
Configure the parameters of the service interface between UserB1 and UserB2.
Parameter Value
ID 2
Source
VLANID 100
ID 2
sup
VLANID 100
Basic attributes of the PW between UserB1 and UserB2:

Parameter Value
PWID 45
Signaling Type Static
Forward label 30
Reverse label 30
Forward Type Static binding
Forward Tunnel NE A_NE B
Reverse Type Static binding
Reverse Tunnel NE A_NE B
Encapsulation type MPLS
Service bandwidth parameters between UserB1 and UserB2:

Parameter Value
Forward 30000
Rate (kbit/s)
Reverse 30000
Rate (kbit/s)
Advanced parameters of the PW between UserB1 and UserB2:

Parameter Value
PW Type Ethernet tag mode
Request VLAN 20
2.5.3 Verification
Open the Network Management app and choose Service > View > PWE3 Service
from the main menu.
In the dialog box that is displayed, set filter criteria (for example, set Protection
Type to PWAPS) and click Filter to query all PWE3 services that meet the filter
criteria.
Right-click an Ethernet service carried by a PW and choose Ethernet OAM >

Ethernet OAM Test from the shortcut menu.
In the dialog box that is displayed, set Test Type to LB.
Click Run.
After the test is complete, click the LB Statistics tab to check the service
connectivity.
If the number of sent packets is the same as the number of received packets, the service
connectivity is normal.
2.6 E-LAN services Based on the 802.1d Bridge

In this experiment, E-LAN services are configured to implement multi-point
communication between different branches at different locations.
2.6.1.1 Objectives
⚫ Understand the basic working principles of E-LAN services.
⚫ Understand the types of E-LAN services.
⚫ Configure E-LAN services.
Networking diagram for configuring E-LAN services

On the network shown in Figure 2-8, the service requirements of Customer Edges (CEs)
are as follows:
• CE1, CE2, and CE3 are connected to NE A, NE B, and NE C respectively through 5-EX10-1.
• There is a data services between CE networks.
• The data service has a fixed bandwidth, that is, CIR = PIR = 40 Mbit/s.
When configuring Ethernet services carried by ports, you need to plan the following data:
• Table 2-20 provides the planning information about the E-LAN services carried by ports.
• Table 2-21 lists the UNI planning of each NE.
• Table 2-22 lists the QoS planning of each NE.
Table 2-19 Planning information about E-LAN services carried by ports
Parameter NE A
Service ID. 1
Service Name E-LAN
Tag Type Tag-Transparent
Self-learning MAC address Enable
MAC address learning mode IVL
MTU(bytes) 1526
According to the planning, UNI-UNI E-Line services should be created on NE B and NE C.
Table 2-20 UNI port planning

Parameter NE A NE B NE C
5-EX10-1
5-EX10-1 5-EX10-1
Port 3-UNQ2-1(40001)
3-UNQ2-1(40001) 3-UNQ2-1(40001)
3-UNQ2-2(40002)
Encapsulation Type Null Null Null
Table 2-21 QoS Planning

Parameter Data service
CIR(kbit/s) 40000
PIR(kbit/s) 40000

Services are carried by ports on the network. Therefore, you need to plan the parameters
related to port bearing.
Configure Ethernet ports on NEs A, B, and C according to the port planning in Table 2-20.
For details, see steps 1 to 5 in section 2.2.2.
Configure E-LAN services on NE A:
Ethernet Service Management > E-LAN Service from the Function Tree.
Click New. In the Create E-LAN Service dialog box, set the parameters of the E-
LAN service carried by ports.
Parameter Value
Service ID. 1
Service Name E-LAN
Tag Type Tag-Transparent
Self-learning MAC address Enable
MAC Address Learning Mode IVL
MTU(bytes) 1526
Click the UNI tab and click Configure. In the Configure Port dialog box that is
displayed, set UNI parameters. After setting the parameters, click OK.
Parameter Value
Port 5-EX10-1, 3-UNQ2-40001,3-UNQ2-40002
VLANs -
Click the UNI tab, and then set the QoS parameters of the E-LAN services carried
by ports.
Parameter Value
Direction Egress
Configure E-Line services on NE B and NE C, for details, see section 2.2.
2.6.3 Verification
For UNI-NNI Ethernet services carried by ports, QinQ links, and PWs, the verification
methods of 802.1ag OAM are similar. To verify the correctness of service configurations,
you need to configure Ethernet OAM.
On NE A and NE B, create an MD for the service between CE1 and CE2.
Parameter NE A NE B
MD Name MD1 MD1
MD level 4 4
On NE A and NE B, create a maintenance association for the service between CE1

and CE2.
Parameter NE A NE B
MD Name MD1 MD1
MA1 MA1
Name
Related Services 1-E-Lan-1 1-E-Lan-1

3.33 ms 3.33 ms
(ms)
Parameter NE A NE B
MD Name MD1 MD1
MA1 MA
Name
Board 5-EX10 5-EX10
VLAN 100 100
MPID 1 2
Note:
• If the MEP of NE B does not receive the CC packets from the MEP of NE A within a period of
time (for example, 3.25 times the transmission period), the MEP of NE B automatically
• If the MEP of NE A does not receive the CC packets from the MEP of NE B within a period of
time (for example, 3.25 times the transmission period), the MEP of NE A automatically
2.7 E-LAN services Based on the 802.1q Bridge

In this experiment, E-LAN services are configured to implement multi-point
communication between different branches at different locations.
2.7.1.1 Objectives
⚫ Understand the basic working principles of E-LAN services.
⚫ Configure E-LAN services.
Networking diagram for configuring E-LAN services

are as follows:
• User A and User B are connected to NE A, NE B, and NE C respectively through 5-EX10-1
and 5-EX10-2.
• There are two types of services in this networks. The services are video services (VLAN 100)
for User A and data services (VLAN 200) for User B in descending order.
• The video service has a fixed bandwidth, that is, CIR = PIR = 10 Mbit/s.
• The data service has a fixed bandwidth, that is, CIR = PIR = 40 Mbit/s.
When configuring Ethernet services carried by ports, you need to plan the following data:
• Table 2-23 provides the planning information about the E-LAN services.
• Table 2-24 lists the UNI planning of each NE.
• Table 2-25 lists the UNI planning for each NE.
• Table 2-26 lists the QoS planning of each NE.
Note:
• You can set a split horizon group for an E-LAN service. One E-LAN service can have only one
split horizon group.
• In a split horizon group, the network-side interface of each NE needs to be configured as a
split horizon group to prevent broadcast storms caused by mutual forwarding of network-
side port data.
• Unknown frames can be broadcast.
Table 2-22 Planning information about E-LAN services
Parameter NE A
Service ID. 1
Service Name E-LAN
Tag Type C-Aware
MAC address self-learning capability Enable
MTU(bytes) 1526

5-EX10-1(VLAN:100) 5-EX10-1(VLAN:100) 5-EX10-1(VLAN:100)

Port
5-EX10-2(VLAN:200) 5-EX10-2(VLAN:200) 5-EX10-2(VLAN:200)
Default VLAN 100,200 100,200 100,200
Encapsulation
802.1Q 802.1Q 802.1Q
Type
Tag Access Access Access

3-UNQ2-1(40001)
Port 3-UNQ2-1(40001) 3-UNQ2-1(40001)
3-UNQ2-2(40002)
Encapsulation Type 802.1Q 802.1Q 802.1Q
Tag Tag Aware Tag Aware Tag Aware

Parameter Video service Data service
CIR(kbit/s) 10048 40000
PIR(kbit/s) 10048 40000

The engineering information for configuring the E-LAN services carried by ports includes
the engineering information for configuring the UNIs and the engineering information
for configuring the NNIs.
Services are carried by ports on the network. Therefore, you need to plan the parameters
related to port bearing.
Configure Ethernet ports on NEs A, B, and C according to the port planning in Table 2-24
and 2-25. For details, see steps 1 to 5 in section 2.2.2.
Configure E-LAN services on NE A:
Ethernet Service Management > E-LAN Service from the Function Tree.
Click New. In the Create E-LAN Service dialog box, set the parameters of the E-
LAN service carried by ports.
Parameter Value
Service ID. 1
Service Name E-LAN
Tag Type C-Aware
MAC address self-learning capability Enable
MTU(bytes) 1526
Click the UNI tab and click Configure. In the Configure Port dialog box that is
displayed, set UNI parameters. After setting the parameters, click OK.
Parameter Value
Port 5-EX10-1 3-UNQ2-40001 3-UNQ2-40002
VLANs 100 - -
Click the Split Horizon Group tab and click Create. In the Create Split Horizon
Group dialog box that is displayed, set split horizon group parameters. After
setting the parameters, click OK.
Parameter Value
3-UNQ2-40001
Selected Interfaces
3-UNQ2-40002
Click the UNI tab, and then set the QoS parameters of the E-LAN services carried
by ports.
Parameter Value
Direction Egress
Configure E-LAN services for UserB
Repeat Step 1-7 to configure the E-LAN services for UserB base on information in
chapter 2.7.1.3.
Configure VLAN-based E-Line Services on NE B and NE C for service access.

2.7.3 Verification
For UNI-NNI Ethernet services carried by ports, QinQ links, and PWs, the verification
methods of 802.1ag OAM are similar. To verify the correctness of service configurations,
you need to configure Ethernet OAM.
On NE A and NE B, create an MD for the services.
Parameter NE A NE B
MD Name MD1 MD1
MD level 4 4
On NE A and NE B, create a maintenance association for the service between CE1

and CE2.
Parameter NE A NE B
MD Name MD1 MD1
MA1 MA1
Name
Related Services 1-E-Lan-1 1-E-Lan-1

3.33 ms 3.33 ms
(ms)
Parameter NE A NE B
MD Name MD1 MD1
MA1 MA
Name
Board 5-EX10 5-EX10
VLAN 100 100
MPID 1 2
Note:
If the MEP of NE B does not receive the CC packets from the MEP of NE A within a period
of time (for example, 3.25 times the transmission period), the MEP of NE B automatically
If the MEP of NE A does not receive the CC packets from the MEP of NE B within a period
of time (for example, 3.25 times the transmission period), the MEP of NE A automatically
2.8 E-LAN services carried by PWs(VPLS)

In this experiment, E-LAN services are configured so that transport devices can
communicate with each other in packet mode.
2.8.1.1 Objectives
⚫ Understand the basic working principles of the E-LAN service packet bearer.
⚫ Learn how to configure packet bearer for E-LAN services.
Networking diagram for configuring E-LAN services carried by PWs

are as follows:
CE1, CE2, and CE3 are connected to NE A, NE B, and NE C respectively through 5-EX10-1.
There are three types of services between CE networks. The services are video services
(VLAN 100) and data services (VLAN 200) in descending order.
The video service has a fixed bandwidth, that is, CIR = PIR = 10 Mbit/s.
The data service has a fixed bandwidth, that is, CIR = PIR = 40 Mbit/s.
CIR = 0 Mbit/s, PIR = 100 Mbit/s.
Services are carried by PWs on the network. Therefore, you need to plan parameters
related to PWs and MPLS tunnels.
When configuring E-LAN services carried by PWs, you need to plan the following data:
Table 2-17 describes the planning of tunnels that carry PWs.
Table 2-28 provides the planning information about E-LAN services carried by PWs.
Table 2-29 lists the UNI planning of each NE.
Table 2-30 lists the PW planning at the NNI of each NE.
Table 2-31 describes the QoS planning for each NE.
Note:
You can set a split horizon group for an E-LAN service. One E-LAN service can have only
one split horizon group.
In a split horizon group, the network-side interface of each NE needs to be configured as
a split horizon group to prevent broadcast storms caused by mutual forwarding of
network-side port data.
Unknown frames can be broadcast.
Table 2-26 Planning of the tunnel that carries the PW
Parameter Tunnel 1 Tunnel 2 Tunnel 3
Tunnel ID 1 2 3
Tunnel Name NE A-NE B NE B-NE C NE C-NE A
Bandwidth 100 Mbit/s
Ingress Board 3-UNQ2-40002 3-UNQ2-40002 3-UNQ2-40001
Egress board 3-UNQ2-40001 3-UNQ2-40002 3-UNQ2-40001
Source Node 130.0.0.1 130.0.0.2 130.0.0.3
Sink Node 130.0.0.2 130.0.0.3 130.0.0.1
Table 2-27 Planning information about E-LAN services carried by PWs

Service ID. 1 2 3
Service Name E-LAN-1 E-LAN-2 E-LAN-3
Tag Type C-Aware C-Aware C-Aware
MAC address self-

Enable Enable Enable
learning capability
MAC address
IVL IVL IVL
learning mode
MTU(bytes) 1526 1526 1526

Port 5-EX10-1 5-EX10-1 5-EX10-1
VLAN ID 100,200 100,200 100,200

Paramet
NE A NE B NE C
er
PWID 10 11 20 21 30 31
PW
signaling Static Static Static Static Static Static
type
Ethernet Ethernet Ethernet Ethernet Ethernet Ethernet

PW Type
tag mode tag mode tag mode tag mode tag mode tag mode
Bidirection Bidirection Bidirection Bidirection Bidirection Bidirection

Direction
al al al al al al
PW
ingress 20 30 20 40 40 30
label
PW
egress 20 30 20 40 40 30
label
Peer LSR
130.0.0.2 130.0.0.3 130.0.0.1 130.0.0.3 130.0.0.2 130.0.0.1
ID
Tunnel Tunnel1 Tunnel3 Tunnel1 Tunnel2 Tunnel2 Tunnel3
Request
10 30 10 20 20 30
VLAN

Parameter Video service Data service
CIR(kbit/s) 10048 40000
PIR(kbit/s) 10048 40000

The engineering information for configuring the E-LAN services carried by PWs includes
the engineering information for configuring the tunnels that carry the PWs, the
engineering information for configuring the UNIs, the engineering information for
configuring the PWs, and the engineering information for configuring the E-LAN services
carried by the PWs.
Choose Service > Create > VPLS Service from the main menu.
In the basic attribute list, set the basic attributes of the VPLS service.
Parameter Value
Service Name E-LAN
Signaling Type LDP/Static
Networking Mode Full-MeshVPLS
Service Type Service VPLS
Select a VPLS service node.
Choose Add > NPE on the right of NE List. The NPE dialog box is displayed.
Select NE A, NE B, and NE C from the Physical Topology Tree.
Set the parameters of the VPLS service node.
In the NE List area, select NEs and click Details.
Click the VSI Configuration tab and set the parameters of the VPLS service node.
Parameter Value
MTU 1526
Tag Type C-Aware
MAC address learning Enable
Learning Mode Unquality(IVL)
Enable transparent transmission of

Not transparently transmitted
BPDUs.
Manually select the tunnel that carries the VPLS service.
Click the PW Configuration tab and select the PW between NE A and NE B.

Value
Parameter
NE A-NE B NE B-NE C NE A-NE C
PWID 10 21 31
Basic
Forward label 20 40 30
attributes
Reverse label 20 40 30
Tunnel Tunnel1 Tunnel2 Tunnel3
Encapsulation Ethernet tag

Ethernet tag mode Ethernet tag mode
type mode
Advanced
Attributes Request VLAN
10 20 30
ID
Other
Default Value
parameters
Click Modify. In the dialog box that is displayed, set PW parameters.
Set the PWs between NE B and NE C and between NE A and NE C by referring to

steps 1 and 2.
Configure SAIs.
Click the SAI Configuration tab and select NE A from the NE List on the left.
Click Create. In the dialog box that is displayed, set service interface parameters.
Value
Parameter
NE A NE B NE C
Interface 5-EX10-1 5-EX10-1 5-EX10-1
VLANID 100,200,300 100,200,300 100,200,300
Refer to Steps 1 and 2 to set the parameters of the service interfaces on NE B and
NE C.
Configure service QoS.
Click the SAI QoS tab.
Select the interfaces for which you want to set QoS parameters.
Value
Parameter
NE A NE B NE C
Interface 5-EX10-1 5-EX10-1 5-EX10-1
Direction Ingress Ingress Ingress
Global QoS
Note: Select the configured global QoS policy template.
policy template
Bandwidth limit Enable Enable Enable
Committed
Information 50000 50000 50000
Rate (kbit/s)
Peak
Bandwidth 100000 100000 100000
(kbit/s)
2.8.3 Verification
Only one RMEP can be configured for an E-LAN service during an ETHOAM LB test.
Procedure
Open the Network Management app and choose Service > View > VPLS Service
from the main menu.
In the dialog box that is displayed, set filter criteria (for example, set Service Type
to Service VPLS) and click Filter to query all E-LAN services that meet the filter
criteria.
Right-click an Ethernet service carried by a PW and choose Ethernet OAM >

Ethernet OAM Test from the shortcut menu.
In the dialog box that is displayed, set filter criteria and click Filter.
Click Run.
After the test is complete, click the LB Statistics tab to check the service
connectivity.
If the number of sent packets is the same as the number of received packets, the service
connectivity is normal.
3 MS-OTN Protection
3.1 Equipment-level protection

OTN equipment supports 1+1 backup of input power supplies, 1+1 protection of system
control boards, clock boards, and cross-connect boards, and FAN redundancy.
3.1.1.1 Objective
⚫ Learn how to query the active/standby status of board 1+1 protection.
⚫ Master how to perform active/standby switching of board 1+1 protection.
Board 1+1 hot backup

The 1+1 backup of PIU boards does not support configuration on the NMS. PIU boards
work in load balancing mode.
In normal mode, the cross-connect module supports only 1+1 hot backup. The active and
standby cross-connect modules are working at the same time and data is consistent. The
switchover takes a short period of time.
The active/standby switchover and status of the system control, clock, and cross-connect
boards can be performed and queried on NCE.

Select an NE and double-click it to open the NE Panel.
In the NE Panel, the board marked with S in the lower right corner is the standby board,
and the board without S is the active board.
In the NE Panel, right-click an NE and choose NE Explorer from the shortcut

menu.
In the NE Explorer, choose Configuration > Board 1+1 Protection from the
Function Tree.
In the right pane, you can view the status of the working and protection boards of the
system control, clock, and cross-connect boards and the current board.
If protection switching is required, click Restore Working/Protection in the lower

right corner to perform manual switching.
3.2 1+1 optical line protection

Optical line protection refers to the protection of line fibers by using separate routes
between adjacent sites. The protection span varies according to the position of the OLP
board on the network, including 1+1 OMS trail protection and 1+1 OTS trail protection.
3.2.1.1 Objective
⚫ Understand the working principles of OLP protection.
⚫ Understand how to configure OLP protection.

1+1 optical line protection supports multiple deployment scenarios.
1+1 OTS Trail Protection - Two-Fiber Bidirectional

Monitoring Signals
1+1 OTS Trail Protection - Single-Fiber Bidirectional

Monitoring Signals
1+1 OMS trail protection

The configuration methods of OLP protection are basically the same regardless of the
type of OLP protection to be deployed.
In this example, 1+1 OTS Trail Protection - Single-Fiber Bidirectional Monitoring Signals is
deployed between OADM A and OADM B.

Before configuring protection, you can connect fibers on the equipment side and modify
logical fiber connections on the NMS based on actual fiber connections. However, the
protection configuration and status are not affected even if the logical fiber connections
are not modified.
Double-click the optical NE OADM A. Right-click the NE to be configured and

choose NE Explorer from the shortcut menu.
In the NE Explorer, select the OLP board and choose WDM Interface from the
Function Tree. In the WDM Interface window, set Initial Difference Between Active
and Standby Input Optical Power (dB) and Difference Threshold Between Active
and Standby Input Optical Power (dB) as required.
In the NE Explorer, select an NE and choose Configuration > Port Protection from
the Function Tree. Click New in the lower right corner.
The Create Protection Group dialog box is displayed. Select Optical Line Protection
from the Protection Type drop-down list and set other parameters for the
protection group.
Select the OLP board as the board where the working channel and protection channel
reside. The default working channel is RI1/TO1, and the default protection channel is
RI2/TO2. The board cannot be modified. The revertive mode can be set to non-revertive
or revertive. If the revertive mode is set to revertive, the WTR time can be set to 5 to 12
minutes.
Click OK. In the Information dialog box, click Close. The created protection group
is displayed.
Repeat the preceding steps to configure the protection group on OADM B.
3.2.3 Verification
Select a protection group and click Query on the right to query the status of the
protection group. Click Function and select a proper switching mode to test the switching
status.
After the switchover, query alarms and performance events on NCE to ensure that
services are normal. If the services are normal and no new alarms or performance events
are reported, the switchover is successful.
3.3 Intra-board 1+1 protection

Intra-board 1+1 protection uses the dual fed and selective receiving function of OTU/OLP
boards to protect services using separate routes.
3.3.1.1 Objective
⚫ Understand the working principles of intra-board 1+1 protection.
⚫ Understand how to configure intra-board 1+1 protection.

Select any wavelength in the topology view and complete fiber connection planning and
physical fiber connection according to the board configuration mode shown in the
following figure.

logical fiber connections on the NMS based on actual fiber connections. However, the
protection configuration and status are not affected even if the logical fiber connections
are not modified.

protection group.
RI2/TO2. The board cannot be modified. The revertive mode can be set to Non-Revertive
or Revertive. If the revertive mode is set to Revertive, the WTR time can be set to 5 to 12
minutes.
is displayed.

3.3.3 Verification
status.
3.4 Client 1+1 protection

The client 1+1 protection uses the dual fed and selective receiving function of the SCS/Y-
Cable or OLP board to protect services in the case of an OTU line-side fault, board fault,
or subrack fault.
3.4.1.1 Objective
⚫ Understand the working principles of client 1+1 protection.
⚫ Understand how to configure client 1+1 protection.

In the topology view, set up client 1+1 protection between NE A and NE B, and plan and
connect physical fibers according to the board configuration mode shown in the
following figure.

logical fiber connections and optical-layer service configurations on the NMS based on
actual fiber connections. However, the protection configuration and status are not
affected even if logical fiber connections are not modified.

protection group.
RI2/TO2. The board cannot be modified. The revertive mode can be set to Non-Revertive
or Revertive. If the revertive mode is set to Revertive, the WTR time can be set to 5 to 12
minutes.
is displayed.
3.4.3 Verification
status.
3.5 ODUk SNCP protection

ODUk SNCP protects ODUk services on an OTN network. ODUk SNCP protection is
implemented by using the dual fed and selective receiving function.
3.5.1.1 Objective
⚫ Learn how to configure ODUk SNCP on the NMS.
⚫ Understand the differences between different sub-types of ODUk SNCP.
Wavelength diagram
ODUk SNCP planning (ODU0 level)

4- 4-
UN UN
Q2 Q2
-2 -1
TT TT
A XCS XCS A
5- 5-
UN UN
Q2 Q2
-2 -2
NE A NE B
Working Protection

In the Main Topology, right-click in the blank area and choose Create Trail >
Create WDM Trail from the shortcut menu.
Configure the client service at the GE rate between OADM A and OADM B according to
Step 2-12 in section 2.1.2.
Click the Protection Settings tab and set the SNCP protection route.
Right-click OADM A and choose Set Dual-Fed Point from the shortcut menu.
Right-click OADM B and choose Set Selective Receiving Point from the shortcut
menu.
In the Node List window, right-click and choose Set SNCP Parameters from the
shortcut menu. In the Set SNCP Parameters dialog box, set SNCP Type to SNC/N
for optical NEs A and C and click OK.
Constrain the route of the protection path by referring to steps 8 to 11 in section 2.1.2.
Click Apply. The ODUk SNCP trail is created.
3.5.3 Verification
In the NE Explorer, choose Configuration > WDM Service Management from the main
menu. Click the SNCP Service Control tab. Select an SNCP protection group and click
Query in the right pane to query the status of the protection group. Click Function and
select a proper switching mode to test the switching status.
3.6 Tributary SNCP protection

Tributary SNCP protects client-side services accessed by tributary boards on an OTN
network. Tributary SNCP is implemented by using the dual fed and selective receiving
function.
3.6.1.1 Objective
⚫ Learn how to configure tributary SNCP on the NMS.
⚫ Understand the differences between sub-types of tributary SNCP.
1- 1-
TTA TTA
-1 -1
4- 4-
XCS UN UN XCS
Q2- Q2-
6- 2 1 6-
TTA TTA
-1 -1
NE A NE B
Tributary SNCP Planning (ODU0 Level)
Table 3-1 Protection Attribute
Protection Information GE services between site A and site B
Protection Type ODUk SNCP
SNCP Type SNC/I
Service type ODU1
OTN level PM
Revertive Mode Non-revertive
Table 3-2 NE A to be configured
Service information ODU0 SNCP
Information Working business Protection service

Source Slot 1-TTA 6-TTA
Source optical port 1(RX1/TX1) 1(RX1/TX1)
Source optical
1 1
channel
Sink Slot 4-UNQ2
Sink optical port 1(IN1/OUT1)
Sink optical channel OCh:1-ODU2:1-ODU1:1-ODU0:1
Table 3-3 NE B to be configured

Service information ODU0 SNCP
Information Working business Protection service
Source Slot 1-TTA 6-TTA
Source optical port 1(RX1/TX1) 1(RX1/TX1)
Source optical
1 1
channel
Sink Slot 4-UNQ2
Sink optical port 2(IN2/OUT2)
Sink optical channel OCh:1-ODU2:1-ODU1:1-ODU0:1

In the NE Explorer, select NE A and choose Configuration > WDM Service

Management from the Function Tree.
In the WDM Cross-Connection Configuration window, click Create SNCP Service.

The Create SNCP Service dialog box is displayed.
Set the protection parameters of NE A according to the planned parameters in

Table 3-1 and Table 3-2. Set Protection Type to ODUk SNCP and Service Type.
Click OK. In the Operation Result dialog box, click Close. The created protection
group is displayed.
Set the service type of the TTA board to GE by referring to steps 6 to 7 in section
2.1.3.
Configure tributary SNCP protection for NE B based on the data planned in Table
3-2 to create the selective receiving and reverse electrical cross-connections.
3.6.3 Verification
In the NE Explorer, choose Configuration > WDM Service Management from the main
menu. Click the SNCP Service Control tab. Select an SNCP protection group and click
Query in the right pane to query the status of the protection group. Click Function and
select a proper switching mode to test the switching status.
3.7 LAG protection

Link aggregation can bundle multiple Ethernet interfaces into a logical interface without
hardware upgrade to increase link bandwidth. In addition, link backup improves link
reliability between devices.
3.7.1.1 Objective
⚫ Learn how to configure LAG protection.
⚫ Understand different types of LAG protection.
LAG networking

The load-sharing LAG scheme is used. Two 10GE physical links are bundled into one
20GE logical link. The 20GE service data is transmitted on the tw0 10GE links at the same
time, meeting the service bandwidth requirements between NE A and the HQ.
Parameter Value
Indicates the aggregation

Automatically Assigned (Default)
group ID.
Indicates the name of the

LAG1
aggregation group.
LAG Type Static aggregation (default)
Link detection protocol Null (default value)

Load Balancing Type Load Balancing
Load balancing hash

Auto (default)
algorithm
System priority 32768 (default value)
Packet receiving timeout

Long period (default value)
period
Minimum number of
1 (default value)
activated links in a LAG
Master board 5-EX10
Master port 1(PORT-1)
Standby ports 5-EX10-2(PORT-2)
5-EX10-1(PORT-1): 32768 (default value)

Port Priority
5-EX10-2(PORT-2): 32768 (default value)

In the physical topology view, click the NE icon and choose NE Explorer from the
shortcut menu in the right pane.
Interface Management > Link Aggregation Group Management from the Function
Tree.
Click the Link Aggregation Group Management tab.
Click New. The Create Link Aggregation Group dialog box is displayed.
In the Attribute Settings dialog box, set the attributes of the LAG.
In the Port Settings dialog box, configure the master and slave ports of the LAG.
Set Master Board and Master Port.
Select the board where the Standby port is located from the Available Standby
Port drop-down list.
Select a slave port from the Port drop-down list box and click.
Click Apply. In the Danger dialog box that is displayed, select the operation
instructions and click Yes.
Click the Link Aggregation Parameters tab and set the port priority.
Click Apply. In the Danger dialog box that is displayed, select the operation
instructions and click Yes.
In the Operation Result dialog box that is displayed, click Close.
3.7.3 Verification
In the physical topology view, click the NE icon and choose NE Explorer from the shortcut
menu in the right pane.
In the NE Explorer, select an NE and choose Configuration > Packet Configuration >
Interface Management > Link Aggregation Group Management from the Function Tree.
Click the LAG Management tab, select one or more LAGs, and click Query. The queried
LAG configuration information is consistent with the network plan.
3.8 Tunnel APS protection

Tunnel APS protects tunnels based on the APS protocol. When the working tunnel fails,
services can be switched to the preset protection tunnel to protect services. Tunnel APS
can be classified into 1+1 protection and 1:1 protection based on the protection
mechanism.
3.8.1.1 Objective
⚫ Learn how to use the NMS to create NEs and optical NEs.
⚫ Master how to configure NE data.
Networking diagram
Table 3-4 Tunnel planning
Site Working Tunnel Protection Tunnel
Ingress Tunnel ID Egress Tunnel ID Ingress Tunnel ID Egress Tunnel ID

NE A
1 1 2 2
Positive Transit Reverse Transit

- -
NE C Tunnel ID Tunnel ID
- - 2 2
Ingress Tunnel ID Egress Tunnel ID Ingress Tunnel ID Egress Tunnel ID

NE B
1 1 2 2
Table 3-5 MPLS-TP Tunnel OAM Planning
Parameter NE A (Tunnel ID: 1 and 2) NE B (Tunnel ID: 1 and 2)
OAM status Enable Enable
MEG ID type IP Based IP Based

MEG Level 7 7
Detection Mode Adaptive Adaptive
CC packet priority 7 7
CC Packet Period
3.33 3.33
(ms)
AIS alarm enable forbid forbid
SD threshold (%) 0 0
SF threshold (%) 0 0
Table 3-6 Tunnel APS Planning
Parameter NE A NE B
Protection Type 1:1 1:1
Switching Mode dual-ended dual-ended
Working Tunnel Type MPLS Tunnel MPLS Tunnel
Working Ingress Tunnel ID 1 1
Working Egress Tunnel ID 1 1
Indicates the protection

2 2
ingress tunnel ID.
Protection Egress Tunnel ID 2 2
Revertive Mode Revertive Revertive
WTR Time (min) 5 5
Hold-off time (100 ms) 0 0
Protocol status Enable Enable

According to the tunnel planning in Table 3-4, create tunnel (NE A- NE B) and tunnel
(NE A-NE C- NE B) by referring to section 2.5.’
Create Tunnel APS protection:
Choose Service > View > Static Tunnel from the main menu.
In the Static Tunnel window, choose Protection Group Configuration > Create
Protection Group.
In the Create Protection Group dialog box, configure the basic information about
the protection group.
In the Create Protection Group area, click Add. In the Filter Criteria dialog box, set
filter criteria and click Filter.
In the Select Tunnel dialog box, select working tunnel and protection tunnel and
click OK.
In the tunnel list, set the tunnel type as working and protection.
In the lower right pane, set MPLS tunnel APS attributes.

Click OK.
3.8.3 Verification
In the NE Explorer, select an NE and choose Configuration > Packet
Configuration > APS Protection Management from the Function Tree.
Click the Tunnel APS Management tab.
Select the protection group to be verified, click Clear in the Function column, and
then click Query Switching Status in the Function column to check whether the
command is successfully issued.
Repeat the preceding steps to check whether manual switching commands such
as forced switching, manual switching to working, manual switching to protection,
exercise switching, and protection locking can be successfully issued.
3.9 PW APS/FPS protection

PW APS/PW FPS protects PWs. When the working PW fails, services can be switched to
the preset protection PW. This protects important services and improves the reliability of
PW transmission.
3.9.1.1 Objective
Networking diagram of PW APS protection

Table 3-7 Planning of Ethernet Ports
Port IP
NE LSR ID Port Port Attribute
Address/Mask
UNI Port mode: Layer 2

5-EX10-1(PORT-1) -
Tag identifier: Tag Aware
NE
1.0.0.1
A NNI Port mode: Layer 3
3-UNQ2-2(40002) 10.0.1.1/24
UNI Port mode: Layer 2

5-EX10-1(PORT-1) -
NEB 1.0.0.2
NNI Port mode: Layer 3
3-UNQ2-1(40001) 10.0.1.2/24
Table 3-8 Planning of tunnels carrying PWs
Parameter Tunnel where PW1_1 resides Tunnel where PW1_2 resides
Tunnel ID 1 2
Tunnel Name tunnel_1 tunnel_2
Signaling Type Static Static
Scheduling E-LSP E-LSP

Type
Bandwidth Unlimited Unlimited
Parameter PW1_1 PW1_2
PW ID 11 12
Name E-Line-1 working PW E-Line-1 protection PW
PW Signaling Type Static Static
PW Type etheric etheric
Direction Bidirectional Bidirectional
PW Incoming Label 20 30
PW outgoing label 20 30
Ingress Tunnel 100 (NE A-NE B) 200 (NE A-NE B)
Peer LSR ID 1.0.0.1 1.0.0.1
Egress Tunnel 100 (NE A-NE B) 200 (NE A-NE B)
Table 3-10 PW APS Planning
Parameter E-Line-1 Service Protection
Protection Type PW APS
Indicates the protection

1
group ID.
Working PW ID 11
Protection PW ID 12

Configure Ethernet ports and create tunnels based on the information planned in
the Table 3-7 and 3-8. For details, see section 2.3.
According to the Table 3-9, create an E-Line service on NE A. Click the UNI tab
and click New to create an E-Line service and set service attributes.
According to the Table 3-9, create working and protection PWs and configure
basic PW attributes.
According to the Table 3-10, configure a PW APS protection group.

Configure MPLS-TP OAM.
Switches the PW OAM standard. PW APS supports MPLS-TP OAM. Therefore, you need to
switch the OAM mode to Y.1731 before configuring PW APS.
Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
In the dialog box that is displayed, set filter criteria (for example, set Protection
Type to PW APS) and click Filter to query all PWE3 services that meet the filter
criteria.
Select the PWE3 service to be switched.
Right-click and choose PW OAM > Switch to Y.1731 Mode from the shortcut
menu.
Click Close.
3.9.3 Verification
In the NE Explorer, select an NE and choose Configuration > Packet
Configuration > APS Protection Management from the Function Tree.
Click the PW APS Management tab.
Select the protection group to be verified, click Clear in the Function column, and
then click Query Switching Status in the Function column to check whether the
command is successfully issued.
Repeat the preceding steps to check whether manual switching commands such
as forced switching, manual switching to working, manual switching to protection,
exercise switching, and protection locking can be successfully issued.
3.10 ERPS protection

Ethernet Ring Protection Switching (ERPS) is an Ethernet ring protection protocol based
on the Automatic Protection Switching (APS) protocol and protection switching
mechanism. ERPS protects the Ethernet LAN services on the Ethernet ring topology at
Layer 2.
3.10.1.1 Objective
Networking diagram

A ring network consists of NE A, NE B, and NEC. ERPS is used to protect Ethernet services
on the ring network.
After ERPS is deployed on a ring network, the RPL owner node (NE A) blocks the east
RPL port and transmits all services through the west port. When a link or an NE on the
ring is faulty, NE A unblocks the east RPL port so that services with interrupted routes
can be transmitted through the east RPL port.
Table 3-11 Ethernet ring protection instance configuration information

ERPS ID 1 1 1
East port 3-UNQ2-2(40002) 3-UNQ2-2(40002) 3-UNQ2-1(40001)
West port 3-UNQ2-1(40001) 3-UNQ2-1(40001) 3-UNQ2-2(40002)
ERP ring node ID RPL port None None
Identifying a port 3-UNQ2-2(40002) - -
Revertive Mode Non-Revertive - -
Control VLAN 4093 4093 4093
Table 3-12 Parameters of the Ethernet ring protocol
Hold-off time (ms) 0 0 0
Guard Time (ms) 500 500 500
WTR time (mm:ss) 10:00 10:00 10:00
Packet sending
5 5 5
interval (s)

In NE A NE Explorer, select an NE from the Object Tree and choose
Configuration > Packet Configuration > Ethernet Protection > ERPS Management
from the Function Tree.
Click New. The Create Ethernet Ring Protection Protocol Instance dialog box is
displayed.
Set the parameters of the ERPS instance according to the data plan listed in Table
3-10.
Click OK.
Repeat the preceding steps to configure NE B and NE C.
In the NE Explorer, select an NE from the Object Tree and choose Configuration >
Packet Configuration > Ethernet Protection > ERPS Management from the
Function Tree.
Set Ethernet ring protocol parameters.

Click Apply.
3.10.3 Verification
Query the working status of the protection group on NE C before the switching.
In the NE Explorer of NE C, select the NE from the Object Tree and choose
Configuration > Packet Configuration > Ethernet Protection > ERPS Management
from the Function Tree.
Select an ERPS protection group and click Query.
State Machine Status must be Idle.
Test the availability of Ethernet services. The value of LossRate in the detection
result should be 0.

HCIP-Transmission V2.5 Lab Guide

Uploaded by

Document Information

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

HCIP-Transmission V2.5 Lab Guide

Uploaded by

Copyright:

Available Formats

Huawei Transmission Certification Training

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Certificate System

About This Document

Background Knowledge Required

Experiment Environment Overview

Device Name Device Model Software Version

NG WDM E6608 V100R019C10SPC600

NCE server TaiShan 2280 V100R019C00

Experiment Environment Preparation

Device Quantity Remarks

E6616 3 Shared by all lab groups

E6608 3 Shared by all lab groups

E6608T 6 Shared by all lab groups

NCE server 1 Shared by all lab groups

The PC must be connected

⚫ One laptop or desktop

About This Document...............................................................................................................3

2.2.2 Configuration Procedure .......................................................................................................................................... 74

3.4.1 About this Experiment .............................................................................................................................................. 44

1 NG WDM System Commissioning

1.1 NG WDM Common Data Configuration

1.1.1.2 Networking and Service Description

NG WDM network topology

1.1.1.3 Networking Design

Table 1-1 Site planning and design

E6616 Master subrack

E6608 184 223 Slave subrack 1 Gateway 10.154.184.223

E6608 184 226 Master subrack Gateway 10.154.184.226

E6616 Master subrack

E6608 184 227 Master subrack Gateway 10.154.184.227

E6616 184 225 Master subrack Gateway 10.154.184.225

E6608T Master subrack Non-

E6608 184 229 Master subrack Gateway 10.154.184.229

Create other NEs in the same way.

2) Creating NEs in batches

1.1.3 Configuring NE Data

Table 1-2 Recommended Configuration

Site NE Recommended Configuration

1) Initialize and Manually configure NE data

Double-click the unconfigured NE in the Main Topology. The NE Configuration

Click Next. The NE Slot page is displayed.

Configure other NEs in the same way.

In the Main Topology, double-click an optical NE that contains unconfigured NEs.

Configure other NEs in the same way.

3) Upload NEs in batches

Choose Configuration > NE Configuration Data Management from the main

Click Upload. The Confirm dialog box is displayed. Click OK.

1.1.4 Creating an Optical NE

Table 1-3 Optical NE planning table

Create other optical NEs in the same way.

1.1.5 Set the Wavelength of an OTU/LU Board Port

Table 1-4 Port wavelength planning table

Site Board NE Subrack Slot Port Planning

In the Main Topology, double-click NE A. In the NE Panel, right-click the UNQ2

Change the wavelengths of all OTU/LU boards in the same way.

Modify the wavelengths of all OTU/LU boards in the same way.

1.1.6 Creating Fiber Connections

Inter-site fiber connection diagram

Internal fiber connections of NE A

Internal fiber connections of NE B

Internal fiber connections of NE C