Professional Documents
Culture Documents
RTN 900 V100R009C00 Configuration Guide 02 PDF
RTN 900 V100R009C00 Configuration Guide 02 PDF
V100R009C00
Configuration Guide
Issue 02
Date 2016-08-15
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.
Website: http://www.huawei.com
Email: support@huawei.com
Related Versions
The following table lists the product versions related to this document.
Intended Audience
This document describes how to configure various services on the OptiX RTN 900 series.
This document describes the basic information and configuration process, and uses
configuration examples to show how to set specific parameters.
NOTE
This manual is for the entire OptiX RTN 900 series. The configuration examples for services in the manual
are based on a specific product, but are applicable to other OptiX RTN 900 products that support the services.
For example, the configuration example for CES services is based on OptiX RTN 980, but is applicable to
OptiX RTN 905, 910A, 950, 950A.
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Symbol Description
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
Change History
Updates between document issues are cumulative. Therefore, the latest document issue
contains all updates made in previous issues.
Change Description
Contents
6.3 Configuration Example (Radio Links on the Hybrid Radio Chain Network).............................................................. 62
6.3.1 Networking Diagram................................................................................................................................................. 62
6.3.2 Configuration Procedure............................................................................................................................................64
6.4 Configuration Example (Microwave Links on a Hybrid Microwave Ring Network)..................................................68
6.4.1 Networking Diagram................................................................................................................................................. 68
6.4.2 Configuration Procedure............................................................................................................................................71
6.5 Configuration Example (Microwave Links on a Packet Network).............................................................................. 75
6.5.1 Networking Diagram................................................................................................................................................. 75
6.5.2 Configuration Procedure............................................................................................................................................77
B Parameters Description..........................................................................................................1163
B.1 Parameters for Network Management..................................................................................................................... 1164
B.1.1 Parameters for NE Management........................................................................................................................... 1164
B.1.1.1 Parameter Description: NE Searching (U2000).................................................................................................1164
B.1.1.2 Parameter Description: NE Searching (Web LCT)............................................................................................ 1168
B.1.1.3 Parameter Description: NE Creation (U2000)................................................................................................... 1169
B.1.1.4 Parameter Description: NE Creation (Web LCT).............................................................................................. 1173
B.1.1.5 Parameter Description: Login to an NE (Web LCT)..........................................................................................1174
B.1.1.6 Parameter Description:Changing NE IDs.......................................................................................................... 1175
B.1.1.7 Parameter Description: NE Time Synchronization (U2000)............................................................................. 1176
B.1.1.8 Parameter Description: NE Time Synchronization (Web LCT)........................................................................ 1179
B.1.1.9 Parameter Description: Localization Management of the NE Time.................................................................. 1184
B.1.1.10 Parameter Description: Standard NTP Key Management............................................................................... 1185
B.1.1.11 Parameter Description: License Management..................................................................................................1187
B.1.1.12 Parameter Description: Automatic Disabling of the Functions of NEs........................................................... 1188
B.1.2 Parameters for Communications Management..................................................................................................... 1189
B.1.2.1 Parameter Description: NE Communication Parameter Setting........................................................................ 1189
B.1.2.2 Parameter Description: DCC Management_DCC Rate Configuration..............................................................1190
B.1.2.3 Parameter Description: DCC Management_DCC Transparent Transmission Management............................. 1192
B.1.2.4 Parameter Description: ECC Management_Ethernet Port Extended ECC........................................................ 1194
B.1.2.5 Parameter Description: NE ECC Link Management......................................................................................... 1196
B.1.2.6 Parameter Description: ECC Link Management_Availability Test................................................................... 1197
B.1.2.7 Parameter Description: IP Protocol Stack Management_IP Route Management..............................................1198
B.1.2.8 Parameter Description: IP Protocol Stack Management_IP Route Management Creation............................... 1199
B.1.2.9 Parameter Description: IP Protocol Stack Management_Availability Test....................................................... 1200
B.1.2.10 Parameter Description: IP Protocol Stack Management_OSPF Parameter Settings....................................... 1201
B.1.2.11 Parameter Description: IP Protocol Stack_Proxy ARP................................................................................... 1207
B.6.3.10 Parameter Description: Ethernet Port OAM Management_OAM Error Frame Monitoring........................... 1547
B.6.3.11 Parameter Description: Ethernet OAM Management_Configuring Bandwidth Notification..........................1548
B.6.4 QoS Parameters.....................................................................................................................................................1549
B.6.4.1 Parameter Description: DiffServ Domain Management.................................................................................... 1549
B.6.4.2 Parameter Description: DiffServ Domain Management_Create....................................................................... 1555
B.6.4.3 Parameter Description: DiffServ Domain Applied Port_Modification............................................................. 1561
B.6.4.4 Parameter Description: Policy Management..................................................................................................... 1562
B.6.4.5 Parameter Description: Port Policy....................................................................................................................1566
B.6.4.6 Parameter Description: Port Policy_Traffic Classification Configuration........................................................ 1574
B.6.4.7 Parameter Description: Port Shaping Management_Creation........................................................................... 1584
B.6.4.8 Parameter Description: Port WRED Policy_Create.......................................................................................... 1585
B.6.4.9 Parameter Description: Service WRED Policy_Create..................................................................................... 1586
B.6.4.10 Parameter Description: WRR Scheduling Policy_Create................................................................................1588
B.6.4.11 Parameter Description: V-UNI Egress Policy..................................................................................................1589
B.6.4.12 Parameter Description: PW Policy.................................................................................................................. 1597
B.6.4.13 Parameter Description: QinQ Policy............................................................................................................... 1605
B.6.5 Parameter Description: IP Packet Marking and Statistics Collection...................................................................1613
B.7 Parameters for Ethernet Services and Ethernet Features on the EoS/EoPDH Plane............................................... 1618
B.7.1 Parameters for Ethernet Services.......................................................................................................................... 1618
B.7.1.1 Parameter Description: Ethernet Line Service_Creation................................................................................... 1618
B.7.1.2 Parameter Description: Ethernet Line Service_Creating QinQ-Based Ethernet Line Services.........................1622
B.7.1.3 Parameter Description: Ethernet Line Service...................................................................................................1633
B.7.1.4 Parameter Description: Ethernet LAN Service_Creation of Ethernet LAN Services Based on IEEE 802.1d/
802.1q Bridge................................................................................................................................................................. 1636
B.7.1.5 Parameter Description: Ethernet LAN Service_Creating IEEE 802.1ad Bridge-Based Ethernet LAN Service
........................................................................................................................................................................................ 1639
B.7.1.6 Parameter Description: Ethernet LAN Service..................................................................................................1644
B.7.1.7 Parameter Description: VLAN Filtering Table_Creation.................................................................................. 1651
B.7.1.8 Parameter Description: Aging Time of MAC Address Table Entries................................................................1652
B.7.2 Parameters for Ethernet Protocols........................................................................................................................ 1652
B.7.2.1 Parameter Description: ERPS Management_Creation...................................................................................... 1652
B.7.2.2 Parameter Description: ERPS Management...................................................................................................... 1655
B.7.2.3 Parameter Description: Spanning Tree_Protocol Enabling............................................................................... 1664
B.7.2.4 Parameter Description: Spanning Tree_Bridge Parameters...............................................................................1665
B.7.2.5 Parameter Description: Spanning Tree_Port Parameters...................................................................................1666
B.7.2.6 Parameter Description: Spanning Tree_Bridge Running Information...............................................................1668
B.7.2.7 Parameter Description: Spanning Tree_Port Running Information...................................................................1669
B.7.2.8 Parameter Description: Spanning Tree_Point-to-Point Attribute...................................................................... 1670
B.7.2.9 Parameter Description: IGMP Snooping Protocol_Enabling............................................................................ 1671
B.7.2.10 Parameter Description: IGMP Snooping Protocol_Creation of Static Multicast Table Entries...................... 1672
B.7.2.11 Parameter Description: IGMP Snooping Protocol_Aging Time of Multicast Table Entries........................... 1673
B.7.2.12 Parameter Description: Ethernet Link Aggregation_Creation of LAGs..........................................................1674
B.7.2.13 Parameter Description: Ethernet Link Aggregation_Link Aggregation.......................................................... 1676
C Glossary.................................................................................................................................... 1967
The U2000 quick start guide helps to learn about basic operations on the U2000 client.
For details, see A.1 U2000 Quick Start.
You can select the proper configuration procedure according to the actual configuration
scenarios.
Context
NOTE
l Different RTN 900 series products are used in different RTN 900 V100R008C10 microwave solutions. In
this document, descriptions are applicable to all RTN 900 series.
Initial Configuration
Initial configuration of a radio network refers to configuring network-wide service data by
using the NMS for the first time after the NE commissioning is complete. Figure 2-1 shows
the configuration procedure.
Start
End
Required
Optional
NOTE
Operation Description
8 Configuring Native Ethernet Services Required when Native Ethernet services need
to be transmitted.
11 Configuring
ETH PWE3
Services
12 Configuring
CES Services
13 Configuring
ATM Services
NOTE
The configuration sequence provided in Table 2-1 is for reference only and needs to be adjusted as required
in actual application scenarios.
Network Adjustment
Network adjustment involves adding and adjusting configuration data in the equipment
commissioning and operation phases. You can find the corresponding configuration
operations according to the actual network adjustment requirements in Table 2-2.
16.2 Common Task Collection (Radio This common task collection lists
Links) configuration operations associated with radio
links, including changing the working mode of
a TDM radio link and changing the number of
E1s on a Hybrid radio link.
16.3 Common Task Collection (TDM This common task collection lists
Services) configuration operations associated with TDM
services, including deleting TDM services and
upgrading a normal service to an SNCP
service.
16.4 Common Task Collection (Native This common task collection lists
Ethernet Services) configuration operations associated with
Native Ethernet services, including setting or
modifying Ethernet port parameters and
deleting Ethernet services.
16.6 Common Task Collection (MPLS/ This common task collection lists
PWE3 Services) configuration operations associated with
packet services, including setting or modifying
packet service parameters and deleting packet
services.
To better describe the initial configuration method for OptiX RTN 900, most configuration
examples in this document are based on the following three networking scenarios. The other
configuration examples are based on special networking scenarios and are for special
application scenarios.
BTS13
E1
FE NE14
BTS12 RTN 905 2E GE+E1 E1
GE
NE13 NE12 FE NE11
RNC
RTN 950A RTN 950A RTN 980
BTS11
NE16 NE15 E1
RTN 905 1E FE RTN 950A
BTS14
BTS15
NE15 RNC
NE16 CSHO
ISV3
RTN 905 1E NE6
ISV3 ISV3
E1
R99
FE RTN 950A BTS14
R4
BTS15
U2000
E1 BSC
LAN switch
GE
RNC
NE21
R4 FE
RTN 950A
BTS21 FE
R4
E1 NE25 BTS24
NE22
RTN 905 2E RTN 910A
BTS22
NE23 NE24
RTN 905 1E RTN 905 1E
FE
R4
BTS23
Figure 3-4 Board configuration of NEs on the Hybrid microwave ring network
CSHO BSC
NE6
ISV3 ISV3
NE21 RNC
RTN 950A
FE
R4
BTS21
RTN 905 2E NE22 NE25 CSHR(ISM6)
RTN 910A
E1
BTS22 FE R4
BTS24
NE23 NE24
FE
R4
BTS23
R4
FE
GE
NE32
RTN 980
NE33 NE31
RTN 950 NMS
RTN 980
NE34 E1
RTN 980
E1
E1
+G
BSC
E
RNC
NOTE
l NE31 is an OptiX PTN NE on an actual network because it does not support any microwave links. In this
document, NE31 is configured as an IDU to comprehensively describe the configurations of packet
services.
l NE33 receives services from BTS33 using Factional E1s.
l NE34 receives services from BTS34 using Factional E1s.
Figure 3-6 provides the board configuration of each NE on the packet network.
NE35
RTN 950A
BTS32 NE36 CSHO
FE FE ISV3
RTN 905 1E NE6
ISV3 ISV3
R4
NE32
RTN 980
PIU PIU
NE33
RTN 980 CSHN
GE
PIU PIU ISV3
ISV3 NE31
EG4 RTN 950
CSH CSH
NE6
NE34
CSHN RTN 980 EG4 ML1
PIU PIU GE
ML1
E1
NOTE
l On the network, NE32, NE33, and NE34 use OptiX RTN 980, NE31 uses OptiX RTN 950, NE35 uses
OptiX RTN 950A, and NE36 uses OptiX RTN 905 1E. To provide the complete configurations of packet
services, this document describes the configurations of all NEs.
l A LAG in configured for the GE port connected to the RNC for protection.
Configuration examples in this manual cover all initial configuration operations mentioned in
Networking Scenarios of Configuration Examples, as well as the special configuration
examples, which are based on special configuration scenarios.
This table lists the configuration examples related to each scenario, to facilitate querying of
the mapping between configuration examples and scenarios in this manual.
Configuring - - - Configuring
Native Ethernet point-to-point
services transparently
transmitted E-
Line services
Configuring - - -
VLAN-based
E-Line services
Configuring - - -
QinQ-based E-
Line services
- Configuring - -
IEEE 802.1D
bridge-based
E-LAN
services
Configuring - - -
IEEE 802.1q
bridge-based
E-LAN
services
- Configuring - -
802.1ad
bridge-based
E-LAN
services
Configuring - - - Configuring
Ethernet Ethernet
services on the services
EoS/EoPDH transmitted
boards over TDM
NOTE microwave
OptiX RTN
905/910A does - - - Configuring
not support this Ethernet
configuration. Services
Traversing a
TDM Network
Configuring - - Configuring -
MPLS tunnels MPLS tunnels
with MPLS AP
protection
- - Configuring -
unprotected
MPLS tunnels
- - - Configuring
MPLS tunnels
traversing a
Layer 2
network
- - - Configuring
MPLS tunnels
traversing a
TDM network
Configuring - - Configuring E- -
ETH PWE3 Line services
services carried by SS-
PWs
- - Configuring E- -
Line services
carried by MS-
PWs
- - Configuring E- -
Line and E-
LAN services
carried by
PWs
- - Configuring E- -
Aggr services
carried by
PWs
Configuring - - Configuring -
CES services CES services
based on
CESoPSN
encapsulation
- - Configuring -
CES services
based on
SAToP
encapsulation
- - - Configuring
CES services
that
transparently
transmit
STM-1s
Configuring - - Configuring -
ATM services ATM services
NOTE based on ATM
OptiX RTN 905 connections
does not support
this - - Configuring -
configuration. ATM ports to
transparently
transmit
services
- Configuring - -
clock for a
Hybrid
microwave
ring network
- - Configuring -
clock for a
packet
network
Configuring - - - Configuring
auxiliary ports orderwire
and NOTE
environment OptiX RTN 905
monitoring does not support
functions this
configuration.
- - - Configuring
synchronous
data services
NOTE
OptiX RTN 905
does not support
this
configuration.
- - - Configuring
asynchronous
data services
- - - Configuring
bypass E1
services
- - - Configuring
external
alarms
- - - Configuring
the monitoring
of outdoor
cabinets
You can manage a transport network by using the U2000 only after configuring the network
topology on the network.
5.1.1 DCN
To manage and maintain an NE, the U2000 needs to communicate with the NE through the
data communication network (DCN).
On a DCN, the NMS and all the NEs are considered as nodes. The DCN between the NMS
and all the NEs is considered as the external DCN, and the DCN between the NEs is
considered as the internal DCN. The OptiX RTN 900 supports the HWECC and IP DCN
solutions. IP DCN is the commonest DCN solution.
IP DCN is a DCN solution provided by Huawei. In this solution, DCN packets are
encapsulated using the standard IP protocol stack and transmitted over DCN channels
between NEs as IP packets, so that the NMS can manage the NEs.
Figure 5-1 shows how DCN packets are transmitted in the IP DCN solution. Different
vendors' DCN packets can be transmitted over the following DCN channels:
3rd-party Msg
OptiX Msg 3rd-party Msg
IP stack
IP stack IP stack
3rd-party Msg NM-ETH
DCC DCC
IP stack
NM-ETH
Third-party NMS NM
NM
NM
OptiX Msg
OptiX Msg GE
OptiX NMS IP stack GE
IP stack OptiX Msg
NM-ETH
Inband DCN IP stack
OptiX Msg
Inband DCN
IP stack
Inband DCN
GNE
Generally, a GNE is connected to the NMS through a local area network (LAN) or wide area
network (WAN). Its application layer can directly communicate with the NMS application
layer. One set of NMS needs to be connected to one or more GNEs.
Non-GNE
A non-GNE communicates with the GNE through the DCN channels between NEs.
NE ID
At the application layer of each DCN solution, an OptiX NE uses its NE ID as the NE
address. Therefore, each NE must have a unique NE ID on the DCN and all these NE IDs
must be planned in a unified manner.
The NE ID has 24 bits. The most significant eight bits represent the subnet ID (or the
extended ID) and the least significant 16 bits represent the basic ID. For example, if an NE ID
is 0x090001, the subnet ID is 9 and the basic ID is 1.
NE IP Address
An NE uses an IP address as its unique identifier during TCP/IP communication.
In the HWECC solution, the IP addresses of the NEs on the DCN are used in the following
scenarios:
l A gateway NE (GNE) communicates with the U2000 over TCP/IP. The IP address of the
GNE must be planned as required by the external DCN.
l Different NEs communicate with each other over extended ECC channels. In this
scenario, NE IP addresses must be on the same network segment. By default, NE IP
addresses are on the 129.9.0.0 network segment.
In the DCN solution (for example, IP DCN) where network management messages are
transmitted over TCP/IP, an NE IP address is used as the NE address at the network layer.
Therefore, each NE IP address on the DCN must be unique and all these NE IP addresses
must be planned in a unified manner.
By default (which indicates that an NE IP address is never manually changed), this NE IP
address is automatically changed to 0x81000000 + ID if the NE ID is changed. For example,
if an NE IP address is never manually changed, this NE IP address is automatically changed
to 129.9.0.1 when the NE ID is changed to 0x090001. Once an NE IP address is manually
changed, the interlocking relationship between the NE ID and NE IP address no longer takes
effect.
NOTE
On RTN 950A, a logical board SL1D can be switched to a logical board CD1, and a logical board SP3S can
be switched to a logical board MP1.
On RTN 950A, an MN1 board must be installed before CES services are configured on a logical board MP1
or CD1.
Figure 5-2 Logical board layout of the OptiX RTN 905 IDU
IDU 905 1E
VS2/
PIU ISV3 CSHP AUX EG6 MP1 CD1 MN1 FAN
EG2
Slot 5 Slot 3 Slot 1 Slot 10 Slot 7 Slot 8 Slot 9 Slot 15 Slot 16 Slot 6
IDU 905 2E
VS2/
PIU ISV3 ISV3 CSHP AUX EG6 MP1 CD1 MN1 FAN
EG2
Slot 5 Slot 4 Slot 3 Slot 1 Slot 10 Slot 7 Slot 8 Slot 9 Slot 15 Slot 16 Slot 6
The slot ID for the logical board of an ODU equals 20 plus the slot ID of the IF board
connected to the ODU.
By default, slot 8 of an OptiX RTN 905 IDU is configured with a VS2 logical board. If the
COMBO interface functions as a GE interface, the VS2 board must be changed into an EG2
board.
NOTE
Fibers and cables are topological objects on the U2000. Hence, operations on the fibers or cables do not affect
the normal running of the NEs.
5.1.6 Subnet
NEs in a same domain or with similar attributes can be allocated to a same subnet. In this
way, they can be displayed as a whole on the U2000, thus facilitating the NE management.
The subnets are topological objects on the U2000. Hence, operations on the subnets do not
affect the normal running of the NEs. In the case of a large number of topological objects,
subnets that contain multiple NEs simplify the topology view on the U2000.
Start
Creating NEs
Configuring NE attributes
Configuring DCCs
Synchronizing NE time
Optional End
NOTE
l If the NE ID and NE name are changed in the NE commissioning process and if the NE communication
parameters, logical boards, VLAN IDs and bandwidth of the inband DCN are set during the per-NE
commissioning, the configuration data is automatically synchronized onto the NMS in the NE data
uploading process. Therefore, you do not need to perform the preceding operations again.
l This section describes the typical IP DCN solution configuration process. If an IP DCN solution
containing special requirements or another DCN solution is used, perform the configurations by referring
to the Feature Description.
l If the Web LCT is used, fibers/cables do not need to be created.
2 A.3.2.1 Uploading the NE Data If you select Upload after create during A.
(U2000) 3.1.1 Creating NEs by Using the Search
Method (U2000), skip this operation.
NOTE
The NE creation steps on the Web LCT are different from those on the U2000.
1. Operations in A.3.2.1 Uploading the NE Data (U2000) are not necessary.
2. If an NE is created but has not been logged in to, perform operations in A.3.1.5 Logging In to an NE
(Web LCT).
1 A.3.1.9 Required.
Changing
the NE ID
2 A.3.1.10 Optional.
Changing
the NE
Name
3 A.3.1.6 Required. Set a logical board for the ODU based on the
Configuring ODU connections.
the Logical For OptiX RTN 980, manually set the SFP module type for
Board the SL4D board (a logical board) according to the actual
board.
4 Configuring Required.
an SFP Port It is recommended that you delete the SFP port for which
no SFP module is installed. If the type of the installed SFP
module differs from the default module type of the port,
delete the port, and add a new port for which the SFP
module type is set to the actual module type. The default
SFP module type for an Ethernet port is a Gigabit Ethernet
(GE) optical module and the default SFP module type for an
SDH port is a Synchronous Transport Module level 1
(STM-1) optical module.
1 A.3.7.1 Required.
Setting NE NOTE
IP If the IP address of an NE has not been changed manually, the IP
Communica address changes according to the NE ID and is always 0x81000000
tion + NE ID. In this case, the IP address of a non-gateway NE does not
need to be changed manually.
Parameters
2 A.3.7.2 Optional.
Configuring
DCCs
A.3.6.2 Optional.
Copying
Topology
Objects
A.3.6.3 Optional.
Moving
Topology
Objects
BTS13
E1
FE NE14
BTS12 RTN 905 2E GE+E1 E1
GE
NE13 NE12 FE NE11
RNC
RTN 950A RTN 950A RTN 980
BTS11
NE16 NE15 E1
RTN 905 1E FE RTN 950A
BTS14
BTS15
NE15 RNC
NE16 CSHO
ISV3
RTN 905 1E NE6
ISV3 ISV3
E1
R99
FE RTN 950A BTS14
R4
BTS15
Data Preparation
Item Value in This Example Planning Principle
Gateway NE NE11 -
9-14
129.9.0.14
0.0.0.0
NE14 9-13 9-12 9-11
129.9.0.13 129.9.0.12 10.0.0.11
0.0.0.0 0.0.0.0 0.0.0.0
NE13 NE12 NE11
9-15
9-16 129.9.0.15
129.9.0.16 0.0.0.0
0.0.0.0
NE15 Extended ID-Basic ID
NE16 IP address
Gateway
Context
NOTE
In the case of NE commissioning, if the NE ID and the values of NE communication parameters have been
changed and the logical boards have been configured, skip the operations.
Procedure
Step 1 Create NEs using the search method.
NOTE
In this example, the IP address of the gateway NE has been modified to the planned value during NE
commissioning.
Normally, the icons of NE11 to NE16 should be displayed on the main topology and all the
NE data should be uploaded successfully.
Step 2 Change an NE ID.
Take NE11 as an example.
Normally, all Ethernet links involving NE11 to NE16 should be displayed on the main
topology.
Step 6 Search for Ethernet links.
Take the Ethernet link between NE12 and NE13 as an example.
1. Search for the link.
Normally, all Ethernet links involving NE11 to NE16 should be displayed on the main
topology.
----End
Figure 5-6 shows topology of the Hybrid microwave ring network which is configured
according to the following requirements:
l In this example, the Hybrid microwave chain network comprises of only OptiX RTN
equipment which are managed by the U2000 in unified manner.
l NE21 is a gateway NE and the other NEs access the U2000 through NE21.
l The Hybrid microwave ring receives various base station services.
l NE23 and NE24 are interconnected through GE ports.
U2000
E1 BSC
LAN switch
GE
RNC
NE21
R4 FE
RTN 950A
BTS21 FE
R4
E1 NE25 BTS24
NE22
RTN 905 2E RTN 910A
BTS22
NE23 NE24
RTN 905 1E RTN 905 1E
FE
R4
BTS23
Figure 5-7 Board configuration of NEs on the Hybrid microwave ring network
CSHO BSC
NE6
ISV3 ISV3
NE21 RNC
RTN 950A
FE
R4
BTS21
RTN 905 2E NE22 NE25 CSHR(ISM6)
RTN 910A
E1
BTS22 FE R4
BTS24
NE23 NE24
FE
R4
BTS23
Data Preparation
Item Value in This Example Planning Principle
Gateway NE NE21 -
9-21
129.9.0.21
0.0.0.0
NE21 9-25
9-22
129.9.0.22 129.9.0.25
0.0.0.0 0.0.0.0
NE22 NE25
9-23 9-24
129.9.0.23 129.9.0.24
0.0.0.0 0.0.0.0
NE23 NE24
Extended ID-Basic ID
IP address
Gateway
Context
NOTE
In the case of NE commissioning, if the NE ID and the values of NE communication parameters have been
changed and the logical boards have been configured, skip the operations.
Procedure
Step 1 Create NEs using the search method.
NOTE
In this example, the IP address of the gateway NE has been modified to the planned value during NE
commissioning.
Normally, the icons of NE21 to NE25 should be displayed on the main topology and all the
NE data should be uploaded successfully.
Step 2 Change an NE ID.
Take NE21 as an example.
Normally, all Ethernet links involving NE21 to NE25 should be displayed on the main
topology.
Step 6 Search for Ethernet links.
Take the Ethernet link between NE21 and NE22 as an example.
1. Search for the link.
Normally, all Ethernet links involving NE21 to NE25 should be displayed on the main
topology.
----End
NE31 is an OptiX PTN NE on an actual network because it does not support any microwave links.
In this document, NE31 is configured as an IDU to comprehensively describe the configurations of
packet services.
l NE31 is a gateway NE and the other NEs access the U2000 through NE31.
l NEs on the packet ring are interconnected through GE optical links and packet chains are
interconnected through pack microwave links.
R4
FE
GE
NE32
RTN 980
NE33 NE31
RTN 950 NMS
RTN 980
NE34 E1
RTN 980
E1
E1
+G
BSC
E
RNC
This figure provides the board configuration of each NE on the packet network.
NE35
RTN 950A
BTS32 NE36 CSHO
FE FE ISV3
RTN 905 1E NE6
ISV3 ISV3
R4
NE32
RTN 980
PIU PIU
NE33
RTN 980 CSHN
GE
PIU PIU ISV3
ISV3 NE31
EG4 RTN 950
CSH CSH
NE6
NE34
CSHN RTN 980 EG4 ML1
PIU PIU GE
ML1
E1
Data Preparation
Item Value in This Example Planning Principle
Gateway NE NE31 -
9-36 9-35
129.9.0.36 129.9.0.35
0.0.0.0 0.0.0.0
NE36 NE35
9-32
GE 129.9.0.32
0.0.0.0 GE
NE32
9-33 9-31
129.9.0.33 10.0.0.31
0.0.0.0 0.0.0.0
NE33 NE31
9-34 GE
GE 129.9.0.34
0.0.0.0
NE34
Extended ID-Basic ID
IP address
Gateway
Context
NOTE
In the case of NE commissioning, if the NE ID and the values of NE communication parameters have been
changed and the logical boards have been configured, skip the operations.
Procedure
Step 1 Create NEs using the search method.
NOTE
In this example, the IP address of the gateway NE has been modified to the planned value during NE
commissioning.
Normally, the icons of NE31 to NE36 should be displayed on the main topology and all the
NE data should be uploaded successfully.
Step 2 Change an NE ID.
Take NE31 as an example.
Normally, the microwave links between NE32 and NE35 and between NE35 and NE36
should be displayed on the main topology.
Step 6 Search for Ethernet links.
Take the Ethernet link between NE32 and NE35 as an example.
1. Search for the link.
Normally, all Ethernet links involving NE31 to NE36 should be displayed on the main
topology.
----End
Before configuring services on a radio link, you need to configure the radio link.
NOTE
The non-protection configuration indicates that there is no protection channel. In practice, services on an
unprotected microwave link can still be protected, for example, E1 services can be configured with SNCP
protection and Ethernet services can be configured with air interface link aggregation and ERPS protection.
The 1+1 protection mode is classified into 1+1 HSB, 1+1 FD, and 1+1 SD.
l In 1+1 HSB protection mode, the system provides a 1+1 hot standby configuration for
the IF board and ODU at both ends of each hop of microwave link to provide protection.
l In 1+1 FD protection mode, the system uses two channels with a specific frequency
interval to transmit and receive the same service signal. The opposite end selects from
the two received signals. With the 1+1 FD protection, the impact of the fading on signal
transmission is reduced.
The 1+1 FD protection mode also supports the 1+1 HSB protection function.
l In 1+1 SD protection mode, the system uses two antennas with a space distance to
receive the same RF signal. The equipment selects from the two received signals. With
the 1+1 SD protection, the impact of the fading on signal transmission is reduced.
The 1+1 SD protection mode also supports the 1+1 HSB protection function.
NOTE
OptiX RTN 905 1E NEs are stacked to implement 1+1 protection.
The OptiX RTN 900 supports N+1 protection for only STM-1 microwave and Integrated IP
microwave. The protection mechanism is similar to 1:N linear MSP which uses the N+1
protection protocol.
NOTE
OptiX RTN 905 does not support N+1 protection.
XPIC Mode
The XPIC mode indicates that a microwave link transmits two channels of signals over the
horizontally polarized wave and the vertically polarized wave in the same channel. Therefore,
the microwave link capacity in XPIC configuration is double the microwave link capacity in
1+0 non-protection configuration.
NOTE
OptiX RTN 905 1E NEs are stacked to implement XPIC.
l PLA (also called L1 LAG). PLA can aggregate multiple integrated microwave links. To
implement the sharing of load and balance the Ethernet bandwidth utilization on the
microwave links, Ethernet traffic is allocated based on the Ethernet bandwidth of each
microwave link.
PLA is available in four modes, conventional mode, enhanced mode, super mode, and
Super Dual Band mode.
– Conventional PLA has IF boards allocate traffic. Only two radio links share load.
Generally, conventional PLA is called PLA.
– Enhanced PLA (EPLA) has packet switching units for allocating traffic. For OptiX
RTN 905 1E, EPLA supports load-sharing among a maximum of two microwave
links. For OptiX RTN 905 2E, 910A, 950, and 950A, EPLA supports load-sharing
among a maximum of four microwave links. For OptiX RTN 980, EPLA supports
load-sharing among a maximum of 12 microwave links.
NOTE
OptiX RTN 905 1E, OptiX RTN 905 2E, OptiX RTN 910A, OptiX RTN 950A, OptiX RTN 950
using CSHU/CSHUA boards and OptiX RTN 980 using CSHNA board support EPLA.
– The PLA in super mode has the packet switching unit to distribute traffic to the
dual-IF board. Then, the dual-IF board distributes traffic to the IF ports. For OptiX
RTN 910A, this mode supports the load sharing of a maximum of six microwave
links. For OptiX RTN 950A and 950, this mode supports the load sharing of a
maximum of eight microwave links. Therefore, this super mode is called EPLA+.
NOTE
Only OptiX RTN 910A, OptiX RTN 950A and OptiX RTN 950 using CSHU/CSHUA boards
support EPLA+.
– The PLA in Super Dual Band mode binds links at common bands and E-Band links
to implement long-distance large-bandwidth transmission. The EM6D board is used
to distribute traffic to the two types of links according to service priorities. The PLA
in Super Dual Band Mode is called Super EPLA.
NOTE
Only OptiX RTN 950A and OptiX RTN 950 using CSHU/CSHUA boards support Super EPLA.
For more details about Super EPLA, see the Super Dual Band User Manual.
l Air-interface LAG, also called L2 LAG. Air-interface LAG aggregates multiple
integrated microwave links based on IEEE 802.3ad. To implement the sharing of load,
Ethernet traffic is allocated based on the HASH algorithm which is based on packet
headers (IP addresses, MAC addresses, or MPLS labels).
Radio link 2
Microwave link aggregation can increase the bandwidth and improve the reliability for
Ethernet services on integrated IP microwave links.
NOTE
For OptiX RTN 905 1E NEs that require improved bandwidth utilization and transmission reliability for
Ethernet services, PLA is a must because air-interface LAG is not supported. Two OptiX RTN 905 1E
NEs are stacked to implement PLA.
End
Optional
NOTE
l OptiX RTN 905 is an integrated chassis device and does not support inserted boards.
l OptiX RTN 910A supports only ISV3 and ISM6 boards.
l OptiX RTN 950A does not support IF1/IFX2 boards.
l For OptiX RTN 910A/950/950A/980, when XPIC and IF 1+1 protection are coupled, IF 1+1 protection is
not configured on the Microwave Link Configuration tab.
A.8.10.7 Changing the Running Mode of The working modes of IF ports at both ends
an IF Port of a microwave link must be the same.
A.8.10.6 Changing the IF Service Type Required if the IF service type is not Native
E1+Ethernet.
Operation Remarks
A.3.5.1 Creating Optical Fibers by Using Required when microwave links needs to be
the Search Method created on the U2000.
In normal cases, the main topology displays
the previously created microwave links.
NOTE
Skip this step if microwave links have been
created during per-NE commissioning or the
creation of network topology.
A.8.10.3 Optional.
Setting When E1 priority is enabled, you can
Advanced AM perform this operation to change the number
Attributes of E1s in intermediate modulation mode.
Operation Remarks
Configuring Optional.
enhanced If enhanced Ethernet frame compression is
Ethernet enabled for a QoS queue at an IF port,
frame Ethernet frame header compression (L2+L3)
compression is automatically enabled for the IF port.
Number of 0 0 1 2 0
high-
priority E1s
Number of 0 0 0 2 0
low-priority
E1s
Capacity of 10 5 3 1 5
high-
priority
Ethernet
services
(Mbit/s)
Capacity of 35 15 24 20 19
low-priority
Ethernet
services
(Mbit/s)
NOTE
High-priority services are services that require transmission guarantees. High-priority services must not
be discarded in modulation scheme shifts. Low-priority services are services that do not require
transmission guarantees. Low-priority services can be discarded in modulation scheme shifts. The
common service priorities are provided in this table.
BTS13
E1
FE NE14
BTS12 RTN 905 2E GE+E1 E1
GE
NE13 NE12 FE NE11
RNC
RTN 950A RTN 950A RTN 980
BTS11
NE16 NE15 E1
RTN 905 1E FE RTN 950A
BTS14
BTS15
NE15 RNC
NE16 CSHO
ISV3
RTN 905 1E NE6
ISV3 ISV3
E1
R99
FE RTN 950A BTS14
R4
BTS15
Data Preparation
Item Value in This Example Planning Principle
Number of E1s 3 1 2 0
in AM
guaranteed
capacity mode
Number of E1s 5 - 4 -
in AM full
capacity mode
Capacity of 24 8 6 5
high-priority
Ethernet
services
(Mbit/s)
Capacity of 113 39 39 19
high-priority
Ethernet
services
(Mbit/s)
Automatic - - - -
ATPC threshold
setting
Upper threshold - - - -
of ATPC
adjustment
(dBm)
Lower - - - -
threshold of
ATPC
adjustment
(dBm)
Maximum - - - -
transmit power
(dBm)
Procedure
Step 1 Configure one hop of microwave link.
Link 101 between NE11 and NE12 is taken as an example. For details, see
.
NOTE
In this example, an IF board with a smaller slot ID is configured as the working board and an IF board with a
larger slot ID is configured as the protection board. In actual situations, refer to the the network plan.
----End
Number of 0 2 0 0
high-priority
E1s
Number of 0 0 0 0
low-priority
E1s
Capacity of 8 4 8 8
high-priority
Ethernet
services
(Mbit/s)
Capacity of 10 10 10 10
low-priority
Ethernet
services
(Mbit/s)
NOTE
High-priority services are services that require transmission guarantees. High-priority services must not
be discarded in modulation scheme shifts. Low-priority services are services that do not require
transmission guarantees. Low-priority services can be discarded in modulation scheme shifts. The
common service priorities are provided in Table 6-7.
U2000
E1 BSC
LAN switch
GE
RNC
NE21
R4 FE
RTN 950A
BTS21 FE
R4
E1 NE25 BTS24
NE22
RTN 905 2E RTN 910A
BTS22
NE23 NE24
RTN 905 1E RTN 905 1E
FE
R4
BTS23
Figure 6-7 Board configuration of NEs on the Hybrid microwave ring network
CSHO BSC
NE6
ISV3 ISV3
NE21 RNC
RTN 950A
FE
R4
BTS21
RTN 905 2E NE22 NE25 CSHR(ISM6)
RTN 910A
E1
BTS22 FE R4
BTS24
NE23 NE24
FE
R4
BTS23
Data Preparation
Item Value in This Example Planning Principle
201 204
14930M 14958M
14510M 14538M
420M 420M
14M NE21 14M
1+0 1+0
V-polarization V-polarization
Tx high Tx high
Tx low Tx low
Tx low Tx low
NE22 NE25
Tx high Tx high
202 203
14958M 14930M
14538M 14510M
420M 420M
14M 14M
1+0 NE23 NE24 1+0
H-polarization H-polarization
Link ID
Tx high site Tx Freq.
Tx low site Tx Freq.
T/R spacing
Channel spacing
RF configuarion
Polarization
Number of E1s 2 2 2 2
in AM
guaranteed
capacity mode
Number of E1s - - - -
in AM full
capacity mode
Capacity of 28 28 28 28
high-priority
Ethernet
services
(Mbit/s)
Capacity of 40 40 40 40
high-priority
Ethernet
services
(Mbit/s)
Automatic - - - -
ATPC threshold
setting
Upper threshold - - - -
of ATPC
adjustment
(dBm)
Lower - - - -
threshold of
ATPC
adjustment
(dBm)
Maximum - - - -
transmit power
(dBm)
Procedure
Step 1 Configure one hop of microwave link.
Link 201 between NE21 and NE22 is taken as an example. For details, see
NOTE
Configure the running mode for the ISM6 board on NE25 to IS3 so that the ISM6 board can interconnect with
the ISV3 board.
----End
Based on 5.5 Configuration Example (Network Topology for a Packet Network), the
microwave links need to be configured according to the following requirements:
NOTE
High-priority services are services that require transmission guarantees. High-priority services must not
be discarded in modulation scheme shifts. Low-priority services are services that do not require
transmission guarantees. Low-priority services can be discarded in modulation scheme shifts.
R4
FE
GE
NE32
RTN 980
NE33 NE31
RTN 950 NMS
RTN 980
NE34 E1
RTN 980
E1
E1
+G
BSC
E
RNC
This figure provides the board configuration of each NE on the packet network.
NE35
RTN 950A
BTS32 NE36 CSHO
FE FE ISV3
RTN 905 1E NE6
ISV3 ISV3
R4
NE32
RTN 980
PIU PIU
NE33
RTN 980 CSHN
GE
PIU PIU ISV3
ISV3 NE31
EG4 RTN 950
CSH CSH
NE6
NE34
CSHN RTN 980 EG4 ML1
PIU PIU GE
ML1
E1
Data Preparation
Item Value in This Example Planning Principle
Basic information about See Figure 6-11. The XPIC On microwave networks,
microwave links link between NE32 and TX high sites and TX low
NE35 uses dual-polarized sites are arranged
antennas and the alternately.
unprotected link between
NE35 and NE36 uses single-
polarized antennas.
303
14930M
14510M
420M
7M
1+0 301,302
H- polarzation 14967M
NE36 14547M
RTN 905 1E NE35
420M
RTN 950A
14M
XPIC
Tx high PLA
Tx low Dual - polarization
Tx low
Tx high
GE
NE32
RTN 980
NE33 NE31
RTN 980 RTN 950
NE34
RTN 980
Link ID
Tx high station Tx Freq.
Tx low station Tx Freq.
T/R spacing
Channel spacing
RF configuarion
Polarization
Capacity of high- 5 5 5
priority services
(Mbit/s)
Capacity of low- 24 24 24
priority services
(Mbit/s)
Automatic ATPC - - -
threshold setting
Upper threshold of - - -
ATPC adjustment
(dBm)
Lower threshold of - - -
ATPC adjustment
(dBm)
Maximum transmit - - -
power (dBm)
Procedure
Step 1 Configure one hop of microwave link.
Take the XPIC link between NE32 and NE35 as an example.
NOTE
In this example, an IF board with a smaller slot ID is configured to vertically polarized and an IF board with a
larger slot ID is configured to horizontally polarized. In actual situations, refer to the the network plan.
NOTE
In this example, an IF board with a smaller slot ID is configured as the working board and an IF board
with a larger slot ID is configured as the protection board. In actual situations, refer to the the network
plan.
2. Set Minimum Active Links.
----End
The key to configuring TDM services is configuring the corresponding service cross-
connections.
Linear MSP
Linear MSP applies to point-to-point networks. MSP provides protection for the services
between two multiplex section termination (MST) modules. That is, when an MSP switching
occurs, the services are switched from the working section to the protection section. For
OptiX RTN 900, linear MSP provides protection for TDM services that are transmitted over
SDH fibers.
Linear MSP includes 1+1 linear MSP and 1:N linear MSP.
l 1+1 linear MSP
In the case of 1+1 linear MSP, one protection channel protects one working channel, and
the protection channel does not transmit extra services. When the working channel
becomes unavailable, services are switched to the protection channel for transmission, as
shown in Figure 7-1. 1+1 linear MSP is classified into dual-ended revertive, dual-ended
non-revertive, single-ended revertive, and single-ended non-revertive modes. The single-
ended non-revertive mode is the most common linear MSP mode.
Protection
channel
Protection switching
Working
NE A NE B
channel
Protection
channel
Protection switching
NE A Working NE B
channel 1
Normal Normal
service 1 service1
... Working ...
channel N
Normal Normal
service N service N
Protection
channel
Extra Extra
service service
NOTE
OptiX RTN 910A supports only 1:1 protection for channelized STM-1 services. In 1:1 protection mode, one
working channel exclusively uses one protection channel, and the protection channel cannot carry extra
services. 1:1 protection for channelized STM-1 services is available only in dual-ended revertive mode.
SNCP
In the case of SNCP, the protection subnet connection takes over when the working subnet
connection fails or deteriorates. For OptiX RTN 900, SNCP provides protection for TDM
services on STM-1 fiber ring networks, TDM microwave ring networks, Hybrid microwave
ring networks, STM-1 fiber ring networks, or Hybrid ring networks.
SNCP is based on dual feed and selective receiving and requires a working subnet and a
protection subnet. When the working subnet fails or deteriorates, services are transmitted over
the protection subnet, as shown in Figure 7-3.
Working SNC
NE A NE B
Protection SNC
Protection switching
Working SNC
NE A NE B
Protection SNC
OptiX RTN 900 supports the coexistence of 1+1 protection, N+1 protection, and SNCP. In
this case, you can set the hold-off time for SNCP so that the microwave link protection
switching is performed preferentially, therefore preventing circular switchovers.
NOTE
OptiX RTN 905 does not support N+1 protection.
West East
STM-4 two-fiber
NE B bidirectional MSP ring NE D
East
West
West East
NE C
Protection swicthing
NE A
East West
West East
STM-4 two-fiber
NE B bidirectional MSP ring NE D
East West
East
West
NE C
E1
If an IF board transmits E1s and the E1 capacity is nxE1, the first to nth VC-12 timeslots on
the IF board are available and correspond to the first to nth E1 timeslots that are transmitted
over microwave. For example, if the E1 capacity is 75xE1, only the first to sixty-third VC-12
timeslots in VC4-1 and the first to twelfth VC-12 timeslots in VC4-2 on the IF board are
available. If a cross-connection is configured between an E1 port on a service board and the
second VC-12 timeslot in VC4-2 on the IF board, the E1 services that are accessed through
the E1 port are sent to the 65th E1 timeslot that is transmitted over microwave.
STM-1
If an IF board transmits STM-1s and the STM-1 capacity is nxSTM-1, the first to nth VC-4
timeslots on the IF board are available and correspond to the first to nth STM-1s that are
transmitted over microwave. For example, if the STM-1 capacity is 2xSTM-1, VC4-1 and
VC4-2 on the IF board are available. If a cross-connection is configured between an E1 port
on a service board and the second VC-12 timeslot in VC4-2 on an IF board, the E1 services
that are accessed through the E1 port are sent to the second VC-12 in the second STM-1 that
is transmitted over microwave.
NOTE
An OptiX RTN 905 2E or an ISM6 board can transmit a maximum of two VC-4 TDM services.
l Interleaved scheme
This timeslot numbering scheme is also considered as line scheme. The numbering
formula is as follows: VC-12 number = (TUG-3 number - 1) x 21 + (TUG-2 number -1)
x 3 + TU-12 number.
The OptiX equipment can adopt this scheme when it interconnects with the equipment
that adopts the interleaved scheme or when a specific timeslot numbering scheme is
required.
1 4 7 10 13 16 19 1
1
{ 22
43
25
46
28
49
31
52
34
55
37
58
40
61
2
3
1
{
2 5 8 11 14 17 20
TUG-3 TU-12
2 23 26 29 32 35 38 41 2
44 47 50 53 56 59 62 3
3 6 9 12 15 18 21 1
3
{ 24
45
27
48
30
51
33
54
36
57
39
60
42
63
2
3
1 4 7 10 13 16 19 1
1
{ 2
3
5
6
8
9
11
12
14
15
17
18
20
21
2
3
1
{
22 25 28 31 34 37 40
TUG-3 TU-12
2 23 26 29 32 35 38 41 2
24 27 30 33 36 39 42 3
43 46 49 52 55 58 61 1
3
{ 44
45
47
48
50
51
53
54
56
57
59
60
62
63
2
3
VC4-2 ......
As shown in Figure 7-7, the timeslot allocation diagram contains three areas, namely, site
area, timeslot area, and timeslot assignment area.
The site area contains the NE icons and interface boards that carry microwave links.
l Each of the first NE and last NE has only one interface board and an intermediate NE
has two interface boards which are at both sides of the vertical line under the
intermediate NE icon.
l The interface board on the left side of the vertical line under an intermediate NE icon is
connected to the interface board on the right side of the vertical line under its upstream
NE icon. The interface board on the right side of the vertical line under an intermediate
NE icon is connected to the interface board on the left side of the vertical line under its
downstream NE icon.
l In the case of a ring link, before planning the site area, you need to break the ring link
into a chain link and ensure that the start and end NEs are the same one.
The timeslot area represents the VC-4 timeslot resources. For example, in the case of a
microwave link, timeslots occupied by an STM-1 service are all in the first VC-4.
In the timeslot assignment area, each straight line represents a service and the numeric above
the straight line represents the timeslot occupied by this service.
l A black dot indicates that services are added to or dropped from the NE. The board
under a black dot indicates the board and corresponding ports on the board that are used
for adding or dropping services.
l An arrow indicates that services are transferred on the NE.
l If a straight line passes a vertical line without any arrow or black dot, it indicates that
services pass through the NE.
l In the case of protection configuration (for example, 1+1 HSB protection) wherein the
working service and protection service have the same route, you only need to draw a
solid line to represent the working service. In the case of protection configuration (for
example, SNCP) wherein the working service and protection service have different
routes, you need to draw a solid line to represent the working service and a dotted line to
represent the protection service.
1. Select the chain that contains the most hops as the main chain. Then, divide the chain
network into several sub-chains by taking the main chain as the reference. Consider the
E1 channels or fiber connections that are used for transferring services between NEs as
links.
2. Assign the timeslots for the added, dropped, or pass-through services on the NEs of the
main chain one after another, in the descending order of distance. Assign the smallest
VC-12 timeslot number to the service on the farthest NE. The number of the timeslot
each service occupies does not change on the chain network.
3. Repeat the previous step to configure timeslots for the services on all the sub-chains.
This timeslot assignment method ensures that only the numbers of timeslots that services on
the nodes of the aggregation sub-chain occupy may change.
The principles for obtaining the timeslot cross-connection configurations from the non-SNCP
service timeslot assignment diagram are as follows:
For details, see 7.4 Configuration Example (TDM Services on a Hybrid Microwave
Chain Network).
1. Assign the timeslots to added or dropped services on the NEs in anti-clockwise order.
Assign the smallest VC-12 timeslot number to the service on the nearest NE. The
number of the timeslot each service occupies does not change on the ring network.
2. Repeat the previous step to configure timeslots for the services on all the sub-chains.
This timeslot assignment method ensures that only the numbers of timeslots that services on
the nodes of the aggregation sub-chain occupy may change.
The principles for obtaining the timeslot cross-connection configurations from the SNCP
service timeslot assignment diagram are as follows:
For details, see 7.5 Configuration Example (TDM Services on a Hybrid Microwave Ring
Network).
l If the system control board is SLF2CSHO, the PDH ports of SP3S and SP3D boards and
the PDH port integrated on SLF2CSHO boards can work in T1 mode.
l A T1 service occupies 24x64 kbit/s timeslots, an E1 service occupies 32x64 kbit/s
timeslots, and therefore a T1 service can be carried over an E1 channel with the
remaining 8x64 kbit/s timeslots stuffed.
l When transmitting T1 services, each E1 channel corresponds to a T1 service.
l When configuring T1 services, retain the original configurations of the TDM cross-
connect mode and Hybrid microwave. Only the service types carried over PDH ports are
different.
This figure shows the flowchart for configuring TDM services in end-to-end mode.
Start
Optional End
Table 7-1 Process for configuring the TDM service port working mode
Process of configuring
Process of configuring
common services or
added/dropped SNCP services
SNCP pass-through services
Start Start
Configuring the TDM service port Configuring the TDM service port
working mode working mode
Start Optional
Table 7-4 Process for configuring TDM services (added/dropped SNCP services)
Step Operation Remarks
3 A.7.2 Creating Cross- Required when the TDM services are SNCP
Connections of SNCP services.
Servicesa The parameters need to be set according to the
service plan.
4 A.7.5 Configuring the Optional when the TDM services are SNCP
Automatic Switching services.
of SNCP Services
6 Testing E1 Services The test results should show that each E1 service
Using PRBS contains no bit errors.
1 A.8.2 Setting Working Required for OptiX RTN 905 and OptiX RTN
Modes of E1 Ports 950A on which an MP1 or a CD1 board provides a
TDM port.
Set Port Working Mode to PDH or SDH.
3 A.7.1 Creating the Required when the TDM services are point-to-
Cross-Connections of point services.
Point-to-Point The parameters need to be set according to the
Servicesa service plan.
4 Testing E1 Services The test results should show that each E1 service
Using PRBS contains no bit errors.
NOTE
a: In the case of 1+1 protection configuration or 1+1 linear MSP, you need to configure TDM services on the
working channel only. In the case of N+1 protection configuration, two-fiber bidirectional ring MSP
configuration (for OptiX RTN 980 only) or 1:N linear MSP configuration, you also need to configure the
extra services on the protection channel if required.
Number of high-priority 1 2
E1s
Number of low-priority 0 2
E1s
Figure 7-10 Networking diagram (TDM services on a Hybrid microwave chain network)
Packet
E1 network
1xE1 NE14
BTS13
NE13 NE12 NE11
4xE1
NE16 NE15
BTS14
NE15 RNC
NE16 CSHO
ISV3
RTN 950 1E NE6
ISV3 ISV3
E1
R99
RTN 950A BTS14
Data Preparation
This figure shows timeslot assignment for TDM services on a network.
VC12: 1-2
19-SP3S: 1-2
VC12: 3-4
19-SP3S: 3-4
VC12: 5
VC4-1
Links-2: NE13-NE14
Site NE13 NE14
Timeslot 19-SP3S 3-ISV3 3-ISV3
VC12: 5 VC12: 1
VC4-1
9-SP3S:1
/ Pass-through (low/high)
/ Add/Drop (low/high)
/ Forward (low/high)
Procedure
Step 1 Create an SDH service trail.
The high-priority E1 service trail between port 2-SP3S-1 of NE11 and port 19-SP3S-1 of
NE15 is taken as an example.
1. Set the basic service information and the E1 priority.
2. Set the source and sink nodes for the service trail.
----End
Data Preparation
This figure shows timeslot assignment for TDM services on a network.
VC12: 1-2
19-SP3S: 1-2
VC12: 3-4
19-SP3S: 3-4
VC12: 5
VC4-1
Links-2: NE13-NE14
Site NE13 NE14
Timeslot 19-SP3S 3-ISV3 3-ISV3
VC12: 5 VC12: 1
VC4-1
9-SP3S:1
/ Pass-through (low/high)
/ Add/Drop (low/high)
/ Forward (low/high)
Procedure
Step 1 Create a cross-connection between an E1 and a VC-12.
Take NE11 as an example.
----End
E1 capacity 2
Figure 7-14 Networking diagram (TDM services on a Hybrid microwave ring network)
2*E1 BSC
NE21
RTN 950A
2*E1 NE25
NE22
RTN 905 2E RTN 910A
BTS22
NE23 NE24
RTN 905 1E RTN 905 1E
CSHO BSC
NE6
ISV3 ISV3
NE21
RTN 950A
E1
BTS22
NE23
NE23
Data Preparation
This figure shows timeslot assignment for TDM services on a network.
Procedure
Step 1 Create an SDH service trail.
1. Set basic service information.
2. Set the source and sink nodes for the service trail.
----End
Data Preparation
This figure shows timeslot assignment for TDM services on a network.
Procedure
Step 1 Create a cross-connection between an E1 and a VC-12.
Take NE21 as an example.
----End
Native Ethernet services are categorized into two types: E-Line and E-LAN.
L2 network
FE/GE/Microwave
link
Ethernet header
Data
NOTE
Native Ethernet services can also be configured for EoS or EoPDH boards. The configuration method is
similar as that for Ethernet services on EoS or EoPDH boards, but different from that for common Native
Ethernet services. Therefore, the Native Ethernet services described here do not include Native Ethernet
services on EoS or EoPDH boards.
8.1.3 Auto-negotiation
The auto-negotiation function enables one network device to transmit information about its
supported working modes to the remote end on the network and to receive corresponding
information from the remote end on the network.
NOTE
If auto-negotiating equipment does not support the half-duplex mode, the auto-negotiation result will be a
full-duplex mode at the corresponding rate level.
Table 8-1 Auto-negotiation rules for FE electrical ports (when the local port works in the
auto-negotiation mode)
NOTE
As provided in Table 8-1, when the remote port works in 10M full-duplex or 100M full-duplex mode, auto-
negotiation cannot match the working modes between the local port and the remote port; as a result, packets
may still be lost. Therefore, if the remote port works in 10M full-duplex or 100M full-duplex mode, configure
the local port to work in the same mode.
When both the local FE interface and the remote FE interface work in auto-negotiation mode,
they can auto-negotiate flow control.a
Table 8-2 Auto-negotiation rules for GE electrical ports (when the local port works in the
auto-negotiation mode)
NOTE
As provided in Table 8-2, when the remote port works in 10M full-duplex or 100M full-duplex mode, auto-
negotiation cannot match the working modes between the local port and the remote port; as a result, packets
may still be lost. Therefore, if the remote port works in 10M full-duplex or 100M full-duplex mode, configure
the local port to work in the same mode.
When the GE electrical ports on both ends are working in the auto-negotiation mode, the
equipment on both ends can negotiate the flow control function through the auto-negotiation
function.a
NOTE
a: OptiX RTN 950A supports the flow control function only for point-to-point transparently transmitted E-
Line services.
On the NMS, OptiX RTN 900 only supports two auto-negotiation flow control modes: Disabled and
Symmetric PAUSE.
l Send only
In case of congestion, a port in this mode can send PAUSE frames but cannot process
received PAUSE frames.
l Receive only
In case of congestion, a port in this mode can process received PAUSE frames but cannot
send PAUSE frames.
l Symmetric
A port in this mode can send and processes PAUSE frames.
l Disabled
An port in this mode does not send or process PAUSE frames.
NOTE
On the NMS, OptiX RTN 900 only supports two auto-negotiation flow control modes: Disabled and Enable
Symmetric Flow Control (symmetric).
On the mobile backhaul network shown in Figure 8-2, the VLANs ID that are carried by base
station services are planned in a unified manner and are unique globally. The base station
services need to share the Ethernet service bandwidth on the Hybrid microwave network
(NE1 to NE5) and be isolated from each other using VLAN IDs. The base station services are
aggregated at NE1 and then transmitted through the regional backhaul network to the BSC.
Therefore, in this example, services on the Hybrid microwave network of the mobile backhaul
network are configured as VLAN-based E-Line services.
FE
BTS
VLAN 1 NE3
FE
NE2 Regional
BTS Hybrid microwave transmission network Backhaul Network
VLAN 2 GE
NE1 BSC
FE
BTS
VLAN 3 NE4
NE5
FE
BTS
VLAN 4
NOTE
IEEE 802.1d bridge-based service packets are forwarded based on MAC addresses and may be broadcast
among all ports connected to the IEEE 802.1d bridge. Therefore, isolate the ports that do not need to
communicate with each other by adding the ports into a split horizon group.
FE
BTS
NE3
FE
NE2
Regional backhaul
BTS Hybrid microwave transmission network network GE
NE1 BSC
FE
BTS
NE5 NE4
FE
BTS NE6
NOTE
IEEE 802.1q bridge-based E-LAN service packets can be broadcast within each domain. Therefore, isolate
the ports that do not need to communicate with each other by adding the ports into a split horizon group.
FE
BTS
VLAN 1 NE3
FE
NE2 Domain 1
BTS VLAN 1 Regional backhaul
VLAN 1 network
Domain 2 GE
VLAN 2 NE1 BSC
Hybrid radio
network
FE
BTS
NE5 NE4
VLAN 2
FE
BTS
VLAN 2 NE6
Networking This l The VLAN IDs that High l Extre l Service l Network
of VLAN- networking are carried by the mely s with expansion
based E-Line mode is received base station high a is difficult.
services applicable to services are planned in l Servi certain l When a
all network a unified manner and ces VLAN new base
scale. are unique globally. from ID are station is
l Base station services differ transmi added to
need to share physical ent tted the
Ethernet service base over a network,
bandwidths and need statio fixed E-Line
to be isolated by ns are service services on
means of VLAN IDs. isolat trail. all NEs
ed l The that the
from OAM base
each capabil station
other. ity is services
strong traverse
and need to be
only reconfigur
point- ed to add
to- the VLAN
point ID of the
config new base
uration station.
is
support
ed.
NOTE
a: For IEEE 802.1d bridge-based and IEEE 802.1q bridge-based E-LAN services, to block communication
between certain ports connected to a bridge, you need to add the ports into a split horizon group.
ERPS
If a ring network is configured with ERPS, the RPL owner node blocks its port on one side so
that services are transmitted only through its port on the other side. This can prevent service
loops. When a ring link fails or an NE becomes faulty, the RPL owner node unblocks the RPL
port. Then, services are transmitted through the RPL port, to achieve ring network protection.
OptiX RTN 900 supports ERPS V1 and ERPS V2, which can protect Ethernet services on
single-ring networks and multi-ring networks. a
Figure 8-5 shows a single-ring network using ERPS V2.
l Normally, the RPL owner node NE4 blocks the port connected to the RPL neighbor node
NE1, and NE1 also blocks the port connected to NE4.b Services are transmitted along the
route NE1 -> NE2 -> NE3 -> NE4.
l When the link between NE1 and NE2 fails, NE4 and NE1 unblock their ports so that
services can be transmitted along the route NE1 -> NE4 -> NE3 -> NE2.
NOTE
a:
ERPS V1 cannot protect Ethernet services on multi-ring networks.
b:
If ERPS V1 is used, NE1 does not block the port connected to NE4.
Ethernet service
direction
NE3
Blocked port
Protection
switching
NE1
Ethernet service
direction
Ethernet service
direction
Figure 8-6 shows a multi-ring Ethernet network using ERPS V2. NE1, NE2, NE3, and NE4
form a major ring with NE4 being the RPL owner node. NE2, NE6, NE5, and NE3 form a
sub-ring with NE6 being the RPL owner node.
l Normally, NE4 blocks the port connected to the neighbor node NE1, and NE1 also
blocks the port connected to NE4. NE6 blocks the port connected to the neighbor node
NE5, and NE5 also blocks the port connected to NE6. The blocking mechanism prevents
service loops on the major ring and sub-ring.
l When the link between NE3 and NE5 on the sub-ring fails, NE5 and NE6 unblock their
ports so that services can be transmitted along the route NE2 -> NE6 -> NE5 on the sub-
ring. NE4 and NE1 on the major ring do not unblock their ports. The service route on the
major ring remains the same.
l When the link between NE1 and NE2 on the major ring fails, NE4 and NE1 unblock
their ports so that services can be transmitted along the route NE2 -> NE3 -> NE4 ->
NE1 on the major ring. NE6 and NE5 on the sub-ring do not unblock their ports. The
service route on the sub-ring remains the same.
NE1 NE4
1 4
Major ring
topology
2 3
NE3
NE2
2 3
GE Sub-ring
GE
topology
6 5
Ethernet service
direction
Blocked port NE6 NE5
1 4 1 4
Major
Major ring
ring
topology topology
2 3 2 3
NE3 NE3
NE2 NE2
2 3 2 3
GE Sub-ring GE Sub-ring
GE GE
topology topology
6 5 6 5
LAG
Link aggregation enables one or multiple links that are connected to the same equipment to be
aggregated into a LAG. The aggregated links are considered as a single logical link by
customers.
l Increasing bandwidth
A LAG provides users with a cost-effective method for increasing the link bandwidth.
Users obtain data links with higher bandwidths by combining multiple physical links
into one logical link without upgrading the existing equipment. The bandwidth of the
logical link is equal to the sum of the bandwidths of the physical links. The aggregation
module distributes the traffic to different members by using the load sharing algorithm,
therefore achieving the load sharing function at the link level.
l Improving link availability
The links in a LAG back up each other dynamically. When a link fails, another link in
the LAG takes it over immediately. The process of starting the backup link is only
related to the links in the same LAG.
Link 1
Link 2
Ethernet Ethernet
packet packet
Link aggregation
group
MSTP
OptiX RTN 900 supports only the MSTP protocol that uses the common and internal
spanning tree (CIST). The MSTP that uses the CIST can be used as a rapid spanning tree
protocol (RSTP). The RSTP is used in the network loop. This protocol adopts certain
algorithms to break a loop network into a loop-free tree network and therefore prevents
packets from increasing and cycling in an endless manner on the loop network.
For OptiX RTN 900, the MSTP is used to prevent a network loop on the access side.
As shown in Figure 8-8, when the user equipment accesses the OptiX RTN 900 through two
different trails, you can configure the ports on the OptiX RTN 900 that are connected to the
user network into a port group. This port group, together with the switch on the user network,
can run the MSTP. If an service access link becomes faulty, the MSTP enables a re-
configuration and therefore the spanning tree topology is generated to provide protection for
the user network that is configured with multiple access points.
Root Root
Port group
CIST
Blocked Port
Model References
Flowchart
Flowchart for configuring Native Ethernet E-Line services from end to end is shown in this
figure.
Optional
Configuring Ethernet ports
Configuring LAGs
Configuring QoS
End
Operation Remarks
A.9.2.1 Required if the LAG function needs to be used for an FE/GE port.
Creating a
LAG
NOTE
For an Ethernet link for which a LAG is configured, configure parameters only for the main port. The
following operations described in this section are also applicable to the main port only.
A.3.5.1 Perform this task to create microwave links for the service trails if they
Creating have not been created on the main topology of the U2000.
Optical Fibers
by Using the
Search
Method
Creating a Required to create Ethernet fibers/cables for the service trails if they
Fiber/Cable by have not been created on the main topology of the U2000.
Using the During the creation, do not use the automatically allocated IP addresses.
Search
Method
A.15.3.2 Required.
Creating E-
Line Services
over Native
Ethernet
A.9.3.12 Required if VLAN ID swapping is required at the source and sink of the
Creating a E-Line service.
VLAN NOTE
Forwarding Configure the VLAN forwarding table items separately for the source port and
Table for an E- sink port.
Line Service
Configuring QoS
For details about the QoS configuration procedure, seeConfiguration Process (QoS/HQoS).
A.15.3.5 Required.
Verifying The LB test result should show that no packet loss occurs.
Native
Ethernet
Services
Model References
NOTE
IEEE 802.1q and IEEE 802.1ad bridges are recommended. The two types of bridges can isolate broadcast
domains through VLANs, minimizing the possibility of loops. Do not use IEEE 802.1d bridges if possible.
Flowchart
Flowchart for configuring Native Ethernet E-LAN services from end to end is shown in this
figure.
Optional
Configure LAGs.
Configure QoS
End
Operation Remarks
A.9.2.1 Required if the LAG function needs to be used for an FE/GE port.
Creating a
LAG
NOTE
For an Ethernet link for which a LAG is configured, configure parameters only for the main port. The
following operations described in this section are also applicable to the main port only.
Operation Remarks
A.3.5.1 Creating Optical Fibers by Using Perform this task to create microwave links
the Search Method for the service trails if they have not been
created on the main topology of the U2000.
NOTE
If the network carries both E-LAN and E-Line services, configure end-to-end hybrid services instead of end-
to-end E-LAN services.
Configuring QoS
For details about the QoS configuration procedure, seeConfiguration Process (QoS/HQoS).
A.15.3.5 Required.
Verifying The LB test result should show that no packet loss occurs.
Native
Ethernet
Services
Model References
Flowchart
Flowchart for configuring Native Ethernet E-Line services is shown in this figure.
Optional
Configuring Ethernet ports
Configuring LAGs
Configuring QoS
End
Operation Remarks
A.8.8.3 Required.
Setting the
Layer 2
Attributes
of Ethernet
Ports
A.8.9.2 Required.
Setting the
Layer 2
Attributes
of IF_ETH
Ports
A.9.2.1 Required if the LAG function needs to be used for an FE/GE port.
Creating a
LAG
NOTE
For an Ethernet link for which a LAG is configured, configure parameters only for the main port. The
following operations described in this section are also applicable to the main port only.
A.9.3.3 Required.
Configuring
UNI-UNI E-
Line Services
(U2000) or A.
9.3.4
Configuring
UNI-UNI E-
Line
Services(Web
LCT)
A.9.3.12 Required if VLAN ID swapping is required at the source and sink of the
Creating a E-Line service.
VLAN Set parameters according to the network plan.
Forwarding
NOTE
Table for an E- Configure the VLAN forwarding table items separately for the source port and
Line Service sink port.
Configuring QoS
For details about the QoS configuration procedure, seeConfiguration Process (QoS/HQoS).
A.15.3.5 Required.
Verifying The LB test result should show that no packet loss occurs.
Native
Ethernet
Services
Model References
NOTE
IEEE 802.1q and IEEE 802.1ad bridges are recommended. The two types of bridges can isolate broadcast
domains through VLANs, minimizing the possibility of loops. Do not use IEEE 802.1d bridges if possible.
Flowchart
Flowchart for configuring Native Ethernet E-LAN services is shown in this figure.
Optional
Configure Ethernet ports.
Configure LAGs.
Configure QoS
End
A.8.8.3 Required.
Setting the
Layer 2
Attributes
of Ethernet
Ports
A.8.8.5 Required.
Setting the
Advanced
Attributes
of Ethernet
Ports
A.8.9.2 Required.
Setting the
Layer 2
Attributes
of IF_ETH
Ports
A.8.9.4 Required.
Setting the
Advanced
Attributes
of IF_ETH
Ports
A.9.2.1 Required if the LAG function needs to be used for an FE/GE port.
Creating a
LAG
NOTE
For an Ethernet link for which a LAG is configured, configure parameters only for the main port. The
following operations described in this section are also applicable to the main port only.
Configuring ERPS
A.9.1.2 Setting Required when the ERPS protocol parameters need to be modified
Global ERPS according to the network plan.
Protocol
Parameters
1 A.9.1.1 Required.
Creating
Ethernet Ring
Protection
Instances
Managing A.9.4.2 Required when you need to disable NEs with certain MAC
the MAC Creating a addresses from using E-LAN services.
address table Blacklist
Entry of
MAC
Addresses
Configuring QoS
For details about the QoS configuration procedure, seeConfiguration Process (QoS/HQoS).
A.15.3.5 Required.
Verifying The LB test result should show that no packet loss occurs.
Native
Ethernet
Services
Backhaul network
NE1 BSC
NE2
NodeB
NE1 (RTN 905 1E)
7-EG6–1 (to NodeB)
3-ISV3-1 (to NE2)
Data Preparation
Item Value in This Example Planning Principle
Procedure
Step 1 Set the basic attributes of Ethernet ports.
----End
Data Preparation
Item Value in This Example Planning Principle
Service ID 1 -
Direction UNI-UNI -
Procedure
Step 1 Configure E-Line services.
----End
Data Preparation
Item Value in This Example Planning Principle
Backhaul network
NE1 BSC
NE2
NodeB
Procedure
Step 1 Query the mapping in the DiffServ domain to ensure that the default setting is the same as the
planned setting.
This figure shows ingress mapping.
NOTE
l AF2 has three sub-classes: AF21, AF22, and AF23. In this example, AF21 is used. The same goes with
AF3.
l The mapping of the default DiffServ domain complies with the network planning requirements and
therefore does not need to be modified.
Step 2 Modify the trusted packet type to DSCP for E-Line service ports in the default DiffServ
domain.
----End
Procedure
Step 1 Create an MD.
Step 5 Verify Ethernet services by using the LB function. For details, see A.9.9.7 Performing an LB
Test.
Perform an LB test by considering the MP whose ID is 101 as the source MP and the MP
whose ID is 102 as the sink MP.
----End
Based on 6.3 Configuration Example (Radio Links on the Hybrid Radio Chain
Network), configure Ethernet services according to the following requirements:
l BTS11, BTS12, and BTS15 provide FE ports whose port rate is 100 Mbit/s.
l Services transmitted by each BTS must carry VLAN IDs, and VLAN IDs on the entire
network must be planned in a unified manner.
l VLAN priorities have been configured on each BTS according to service types.
To meet the preceding requirements, VLAN-based E-Line services are configured for each
NE; in addition, corresponding QoS policies are configured.
Data Preparation
Item Value in This Example Planning Principle
C:100
RNC to BTS11
17-EG2D-1(C:100) 7-EG6-1(C:100)
C:120 C:120 C:120 C:120
RNC to BTS15
17-EG2D-1(C:120) 7-EG6-1(C:120)
C:110 C:110
RNC to BTS12
17-EG2D-1(C:110)
Links-2: NE13-NE14
NE13 NE14
17-EG6-1 3-ISV3-1 3-ISV3-1
C:110 C:110
RNC to BTS12
7-EG6-1(C:110)
C: C-VLAN S: S-VLAN
Pass through
Add/Drop
Foward
Prerequisites
Ethernet fibers/cables have been searched out in Creating the Network Topology.
Procedure
Step 1 Create a VLAN-based E-Line service.
The E-Line service between port 17-EG2D-1 of NE11 and port 7-EG6-1 of NE14 is taken as
an example.
----End
Data Preparation
Item Value in This Example Planning Principles
Procedure
Step 1 Query the mapping in the DiffServ domain to ensure that the default setting is the same as the
planned setting.
This figure shows ingress mapping.
NOTE
l AF2 has three sub-classes: AF21, AF22, and AF23. In this example, AF21 is used. The same goes with
AF3.
l The mapping of the default DiffServ domain complies with the network planning requirements and
therefore does not need to be modified.
----End
Procedure
Step 1 Verify Ethernet services.
1. Manage Native Ethernet services.
2. Start an LB test.
----End
Data Preparation
Item Value in This Example Planning Principle
Procedure
Step 1 Set the basic attributes of Ethernet ports.
Take NE14 as an example.
Step 2 Query the Layer 2 attributes of the Ethernet port and ensure that the Tag attribute is Tag
Aware.
Take NE14 as an example.
Step 4 Query the Layer 2 attributes of the IF_ETH port and ensure that the Tag attribute is the default
value Tag Aware.
Take NE14 as an example.
----End
Data Preparation
Item Value in This Example Planning Principle
Service information See the following figure. Set IDs and names for
network-wide E-Line
services according to the
network plan.
C:100
RNC to BTS11
17-EG2D-1(C:100) 7-EG6-1(C:100)
C:120 C:120 C:120 C:120
RNC to BTS15
17-EG2D-1(C:120) 7-EG6-1(C:120)
C:110 C:110
RNC to BTS12
17-EG2D-1(C:110)
Links-2: NE13-NE14
NE13 NE14
17-EG6-1 3-ISV3-1 3-ISV3-1
C:110 C:110
RNC to BTS12
7-EG6-1(C:110)
C: C-VLAN S: S-VLAN
Pass through
Add/Drop
Foward
Procedure
Step 1 Configure VLAN-based E-Line services.
Take NE14 as an example.
----End
Data Preparation
Item Value in This Example Planning Principles
Procedure
Step 1 Query the mapping in the DiffServ domain to ensure that the default setting is the same as the
planned setting.
This figure shows ingress mapping.
NOTE
l AF2 has three sub-classes: AF21, AF22, and AF23. In this example, AF21 is used. The same goes with
AF3.
l The mapping of the default DiffServ domain complies with the network planning requirements and
therefore does not need to be modified.
----End
Procedure
Step 1 Create a maintenance domain (MD) for NE11, NE12, NE14, and NE16.
Take NE14 as an example.
Step 2 Create a maintenance association (MA) for NE11, NE12, NE14, and NE16.
Take NE14 as an example.
Step 3 Create maintenance points (MPs) for NE11, NE12, NE14, and NE16.
Take NE14 as an example.
NOTE
l On port 17-EG2D-1 of NE11, create three MPs with the IDs of 101, 102, and 103 respectively.
l On port 7-EG6-1 of NE12, create an MP with the ID of 201.
l On port 7-EG6-1 of NE16, create an MP with the ID of 601.
Step 4 Create remote MPs for NE11, NE12, NE14, and NE16.
Take NE14 as an example.
NOTE
l For NE11, create three remote MPs with the IDs of 201, 401, and 601 respectively.
l For NE12, create a remote MP with the ID of 101.
l For NE16, create a remote MP with the ID of 103.
----End
NOTE
In this example, the BTS/RNC is capable of processing S-VLAN IDs.
Data Preparation
Item Value in This Example Planning Principle
S: 200
RNC to BTS11
17-EG2D-1(S: 200) 7-EG6-1(S: 200l)
S: 202 S: 202 S: 202 S: 202
RNC to BTS15
17-EG2D-1(S: 202) 7-EG6-1(S: 202)
S: 201 S: 201
RNC to BTS12
17-EG2D-1(S: 201)
Links-2: NE13-NE14
NE13 NE14
17-EG6-1 3-ISV3-1 3-ISV3-1
S: 201 S: 201
RNC to BTS12
7-EG6-1(S: 201)
C: C-VLAN
S: S-VLAN
Pass through
Add/Drop
Foward
Prerequisites
Ethernet fibers/cables have been searched out in Creating the Network Topology.
Procedure
Step 1 Create an S-VLAN-based E-Line service.
The E-Line service between port 17-EG2D-1 of NE11 and port 7-EG6-1 of NE14 is taken as
an example.
1. Set basic service information.
----End
Data Preparation
Item Value in This Example Planning Principle
Procedure
Step 1 Query the mapping in the DiffServ domain to ensure that the default setting is the same as the
planned setting.
This figure shows ingress mapping.
NOTE
l AF2 has three sub-classes: AF21, AF22, and AF23. In this example, AF21 is used. The same goes with
AF3.
l The mapping of the default DiffServ domain complies with the network planning requirements and
therefore does not need to be modified.
----End
Procedure
Step 1 Verify Ethernet services.
1. Manage Native Ethernet services.
2. Start an LB test.
----End
Data Preparation
Item Value in This Example Planning Principle
Procedure
Step 1 Set the basic attributes of Ethernet ports.
Take NE14 as an example.
----End
Data Preparation
Item Value in This Example Planning Principle
Service information See the following figure. Set IDs and names for
network-wide E-Line
services according to the
network plan.
S: 200
RNC to BTS11
17-EG2D-1(S: 200) 7-EG6-1(S: 200l)
S: 202 S: 202 S: 202 S: 202
RNC to BTS15
17-EG2D-1(S: 202) 7-EG6-1(S: 202)
S: 201 S: 201
RNC to BTS12
17-EG2D-1(S: 201)
Links-2: NE13-NE14
NE13 NE14
17-EG6-1 3-ISV3-1 3-ISV3-1
S: 201 S: 201
RNC to BTS12
7-EG6-1(S: 201)
C: C-VLAN
S: S-VLAN
Pass through
Add/Drop
Foward
Procedure
Step 1 Configure a QinQ link.
Take NE14 as an example.
----End
Data Preparation
Item Value in This Example Planning Principle
Procedure
Step 1 Query the mapping in the DiffServ domain to ensure that the default setting is the same as the
planned setting.
This figure shows ingress mapping.
NOTE
l AF2 has three sub-classes: AF21, AF22, and AF23. In this example, AF21 is used. The same goes with
AF3.
l The mapping of the default DiffServ domain complies with the network planning requirements and
therefore does not need to be modified.
----End
Procedure
Step 1 Create a maintenance domain (MD) for NE11, NE12, NE14, and NE16.
Take NE14 as an example.
Step 2 Create a maintenance association (MA) for NE11, NE12, NE14, and NE16.
Take NE14 as an example.
Step 3 Create maintenance points (MPs) for NE11, NE12, NE14, and NE16.
Take NE14 as an example.
NOTE
l On port 17-EG2D-1 of NE11, create three MPs with the IDs of 101, 102, and 103 respectively.
l On port 7-EG6-1 of NE12, create an MP with the ID of 201.
l On port 7-EG6-1 of NE16, create an MP with the ID of 601.
Step 4 Create remote MPs for NE11, NE12, NE14, and NE16.
Take NE14 as an example.
NOTE
l For NE11, create three remote MPs with the IDs of 201, 401, and 601 respectively.
l For NE12, create a remote MP with the ID of 101.
l For NE16, create a remote MP with the ID of 103.
----End
FE FE
R4 R4
BTS21 NE22 NE25 BTS24
802.1d bridge 802.1d bridge
Data Preparation
Item Value in This Example Planning Principle
FE FE
R4 R4
BTS21 NE22 NE25 BTS24
802.1d bridge 802.1d bridge
FE FE
R4 R4
BTS21 NE22 NE25 BTS24
7-ISM6-2 (East)
7-ISM6-1 (West)
FE
Control VLAN: 4094
NE23 NE24
R4
BTS23
3-ISV3-1 (East)
7-EG6–1 (East) 7-EG6–1 (West, RPL next
3-ISV3-1 (West, RPL neighbor port)
neighbor port) Control VLAN: 4094
Control VLAN: 4094
Procedure
Step 1 Configure ERPS.
NOTE
Broadcast packet suppression needs to be enabled for ports mounted to all bridges. In the preceding
figure, port 3–ISV3–1 is taken as an example.
----End
Data Preparation
Item Value in This Example Planning Principle
Procedure
Step 1 Query the mapping in the DiffServ domain to ensure that the default setting is the same as the
planned setting.
This figure shows ingress mapping.
NOTE
l AF2 has three sub-classes: AF21, AF22, and AF23. In this example, AF21 is used. The same goes with
AF3.
l The mapping of the default DiffServ domain complies with the network planning requirements and
therefore does not need to be modified.
----End
Procedure
Step 1 Verify Ethernet services.
1. Manage Native Ethernet services.
2. Start an LB test.
----End
Data Preparation
Item Value in This Example Planning Principle
FE FE
R4 R4
BTS21 NE22 NE25 BTS24
802.1d bridge 802.1d bridge
Procedure
Step 1 Set the basic attributes of Ethernet ports.
Take NE22 as an example.
----End
Data Preparation
Item Value in This Example Planning Principle
FE FE
R4 R4
BTS21 NE22 NE25 BTS24
7-ISM6-2 (East)
7-ISM6-1 (West)
FE
Control VLAN: 4094
NE23 NE24
R4
BTS23
3-ISV3-1 (East)
7-EG6–1 (East) 7-EG6–1 (West, RPL next
3-ISV3-1 (West, RPL neighbor port)
neighbor port) Control VLAN: 4094
Control VLAN: 4094
Procedure
Step 1 Configure ERPS.
Take NE23 as an example.
----End
Data Preparation
Item Value in This Example Planning Principle
FE FE
R4 R4
BTS21 NE22 NE25 BTS24
802.1d bridge 802.1d bridge
Procedure
Step 1 Configure E-LAN services.
Take NE21 as an example.
----End
Data Preparation
Item Value in This Example Planning Principle
Procedure
Step 1 Query the mapping in the DiffServ domain to ensure that the default setting is the same as the
planned setting.
This figure shows ingress mapping.
NOTE
l AF2 has three sub-classes: AF21, AF22, and AF23. In this example, AF21 is used. The same goes with
AF3.
l The mapping of the default DiffServ domain complies with the network planning requirements and
therefore does not need to be modified.
----End
Procedure
Step 1 Create a maintenance domain (MD) for NE21, NE22, NE23, and NE25.
Take NE23 as an example.
Step 2 Create a maintenance association (MA) for NE21, NE22, NE23, and NE25.
Take NE23 as an example.
Step 3 Create maintenance points (MPs) for NE21, NE22, NE23, and NE25.
Take NE23 as an example.
NOTE
l On port 17-EG6-1 of NE21, create three MPs with the IDs of 102, 103, and 105 respectively.
l On port 7-EG6-1 of NE22, create an MP with the ID of 201.
l On port 7-EG6-1 of NE25, create an MP with the ID of 501.
Step 4 Create remote MPs for NE21, NE22, NE23, and NE25.
Take NE23 as an example.
NOTE
l For NE21, create three remote MPs with the IDs of 201, 301, and 501 respectively.
l For NE22, create a remote MP with the ID of 102.
l For NE25, create a remote MP with the ID of 105.
l BTS11, BTS12, and BTS15 provide FE ports whose port rate is 100 Mbit/s.
l BTS11 and BTS12 belong to domain 1; BTS15 belongs to domain 2. The BTSs in one
domain have the same VLAN ID and the services from different domains are isolated
from each other by using the VLAN IDs.
l VLAN priorities have been configured on each BTS according to service types.
l The network should be able to suppress broadcast packets.
To meet the preceding requirements, IEEE 802.1q bridge-based E-LAN services are
configured for each NE; in addition, broadcast packet suppression and QoS policies are
configured.
R4 FE
NE14 (RTN 905 2E) GE
7-EG6–1 (to BTS12) NE14
3-ISV3-1 (to NE13) RNC
NE13 NE12 NE11 VLAN 100, 110
Data Preparation
Item Value in This Example Planning Principle
R4 FE
NE14 (RTN 905 2E) GE
7-EG6–1 (to BTS12) NE14
3-ISV3-1 (to NE13) RNC
NE13 NE12 NE11 VLAN 100, 110
Procedure
Step 1 Create an IEEE 802.1q bridge-based E-LAN service.
1. Set basic service information.
NOTE
Broadcast packet suppression needs to be enabled for ports mounted to all bridges. In the preceding
figure, port 3–ISV3–1 is taken as an example.
----End
Procedure
Step 1 Query the mapping in the DiffServ domain to ensure that the default setting is the same as the
planned setting.
NOTE
l AF2 has three sub-classes: AF21, AF22, and AF23. In this example, AF21 is used. The same goes with
AF3.
l The mapping of the default DiffServ domain complies with the network planning requirements and
therefore does not need to be modified.
----End
Procedure
Step 1 Create a maintenance domain (MD) for NE11, NE12, NE14, and NE16.
Take NE14 as an example.
Step 2 Create a maintenance association (MA) for NE11, NE12, NE14, and NE16.
Take NE14 as an example.
Step 3 Create maintenance points (MPs) for NE11, NE12, NE14, and NE16.
Take NE14 as an example.
NOTE
l On port 17-EG2D-1 of NE11, create three MPs with the IDs of 101, 102, and 103 respectively.
l On port 7-EG6-1 of NE12, create an MP with the ID of 201.
l On port 7-EG6-1 of NE16, create an MP with the ID of 601.
Step 4 Create remote MPs for NE11, NE12, NE14, and NE16.
Take NE14 as an example.
NOTE
l For NE11, create three remote MPs with the IDs of 201, 401, and 601 respectively.
l For NE12, create a remote MP with the ID of 101.
l For NE16, create a remote MP with the ID of 103.
----End
Data Preparation
Item Value in This Example Planning Principle
R4 FE
NE14 (RTN 905 2E) GE
7-EG6–1 (to BTS12) NE14
3-ISV3-1 (to NE13) RNC
NE13 NE12 NE11 VLAN 100, 110
Procedure
Step 1 Set the basic attributes of Ethernet ports.
Take NE14 as an example.
Step 2 Query the Layer 2 attributes of the Ethernet port and ensure that the Tag attribute is Tag
Aware.
Take NE14 as an example.
Step 5 Query the Layer 2 attributes of the IF_ETH port and ensure that the Tag attribute is the default
value Tag Aware.
Take NE14 as an example.
----End
Data Preparation
Item Value in This Example Planning Principle
R4 FE
NE14 (RTN 905 2E) GE
7-EG6–1 (to BTS12) NE14
3-ISV3-1 (to NE13) RNC
NE13 NE12 NE11 VLAN 100, 110
Procedure
Step 1 Configure E-LAN services.
Take NE14 as an example.
NOTE
For OptiX RTN 950 using CSHU/CSHUA boards and OptiX RTN 950A, the total number of VLANs
configured for Ethernet services must not exceed 1024. To avoid this restriction, do as follows:
1. Retain VLANs/CVLAN of some ports to null.
2. Set VLAN Filtering Table to the desired VLANs for the ports.
In this case, the VLANs configured in VLAN Filtering Table will not be counted in the VLANs configured
for Ethernet services. However, theses ports cannot participate in other Ethernet services.
----End
Procedure
Step 1 Query the mapping in the DiffServ domain to ensure that the default setting is the same as the
planned setting.
NOTE
l AF2 has three sub-classes: AF21, AF22, and AF23. In this example, AF21 is used. The same goes with
AF3.
l The mapping of the default DiffServ domain complies with the network planning requirements and
therefore does not need to be modified.
----End
Procedure
Step 1 Create a maintenance domain (MD) for NE11, NE12, NE14, and NE16.
Take NE14 as an example.
Step 2 Create a maintenance association (MA) for NE11, NE12, NE14, and NE16.
Take NE14 as an example.
Step 3 Create maintenance points (MPs) for NE11, NE12, NE14, and NE16.
Take NE14 as an example.
NOTE
l On port 17-EG2D-1 of NE11, create three MPs with the IDs of 101, 102, and 103 respectively.
l On port 7-EG6-1 of NE12, create an MP with the ID of 201.
l On port 7-EG6-1 of NE16, create an MP with the ID of 601.
Step 4 Create remote MPs for NE11, NE12, NE14, and NE16.
Take NE14 as an example.
NOTE
l For NE11, create three remote MPs with the IDs of 201, 401, and 601 respectively.
l For NE12, create a remote MP with the ID of 101.
l For NE16, create a remote MP with the ID of 103.
----End
FE FE
R4
R4
BTS21 BTS24
NE22 NE25
CVLAN 100 802.1ad bridge CVLAN 100
802.1ad bridge
SVLAN 200 SVLAN 201
Data Preparation
Item Value in This Example Planning Principle
Ports mounted to a bridge See the following figure. In this example, base station
l The encapsulation type is services carry C-VLAN IDs.
set to 802.1Q for UNIs. However, because the C-
VLAN IDs of BTS21 and
l The encapsulation type is BTS24 conflict with each
set to QinQ for NNIs. other, S-VLAN IDs are
planned for the backhaul
network for distinguishing.
Therefore, the encapsulation
type is set to 802.1Q for
UNIs.
FE FE
R4
R4
BTS21 BTS24
NE22 NE25
CVLAN 100 802.1ad bridge CVLAN 100
802.1ad bridge
SVLAN 200 SVLAN 201
FE FE
R4 R4
BTS21 NE22 NE25 BTS24
7-ISM6-2 (East)
7-ISM6-1 (West)
FE
Control VLAN: 4094
NE23 NE24
R4
BTS23
3-ISV3-1 (East)
7-EG6–1 (East) 7-EG6–1 (West, RPL next
3-ISV3-1 (West, RPL neighbor port)
neighbor port) Control VLAN: 4094
Control VLAN: 4094
Procedure
Step 1 Configure ERPS.
NOTE
Broadcast packet suppression needs to be enabled for ports mounted to all bridges. In the preceding
figure, port 3–ISV3–1 is taken as an example.
----End
Data Preparation
Item Value in This Example Planning Principle
Procedure
Step 1 Query the mapping in the DiffServ domain to ensure that the default setting is the same as the
planned setting.
This figure shows ingress mapping.
NOTE
l AF2 has three sub-classes: AF21, AF22, and AF23. In this example, AF21 is used. The same goes with
AF3.
l The mapping of the default DiffServ domain complies with the network planning requirements and
therefore does not need to be modified.
----End
Procedure
Step 1 Verify Ethernet services.
1. Manage Native Ethernet services.
2. Start an LB test.
----End
Data Preparation
Item Value in This Example Planning Principle
Ports mounted to a bridge See the following figure. l In this example, base
l The encapsulation type is station services carry C-
set to 802.1Q for UNIs. VLAN IDs. However,
because the C-VLAN
l The encapsulation type is IDs of BTS21 and
set to QinQ for NNIs. BTS24 conflict with
each other, S-VLAN IDs
are planned for the
backhaul network for
distinguishing.
Therefore, the
encapsulation type is set
to 802.1Q for UNIs.
FE FE
R4
R4
BTS21 BTS24
NE22 NE25
CVLAN 100 802.1ad bridge CVLAN 100
802.1ad bridge
SVLAN 200 SVLAN 201
Procedure
Step 1 Set the basic attributes of Ethernet ports.
Take NE22 as an example.
----End
Data Preparation
Item Value in This Example Planning Principle
FE FE
R4 R4
BTS21 NE22 NE25 BTS24
7-ISM6-2 (East)
7-ISM6-1 (West)
FE
Control VLAN: 4094
NE23 NE24
R4
BTS23
3-ISV3-1 (East)
7-EG6–1 (East) 7-EG6–1 (West, RPL next
3-ISV3-1 (West, RPL neighbor port)
neighbor port) Control VLAN: 4094
Control VLAN: 4094
Procedure
Step 1 Configure ERPS.
Take NE23 as an example.
----End
Data Preparation
Item Value in This Example Planning Principle
Ports mounted to a bridge See the following figure. In this example, base station
l The encapsulation type is services carry C-VLAN IDs.
set to 802.1Q for UNIs. However, because the C-
VLAN IDs of BTS21 and
l The encapsulation type is BTS24 conflict with each
set to QinQ for NNIs. other, S-VLAN IDs are
planned for the backhaul
network for distinguishing.
Therefore, the encapsulation
type is set to 802.1Q for
UNIs.
FE FE
R4
R4
BTS21 BTS24
NE22 NE25
CVLAN 100 802.1ad bridge CVLAN 100
802.1ad bridge
SVLAN 200 SVLAN 201
Procedure
Step 1 Configure E-LAN services.
Take NE21 as an example.
1. Configure the basic service information and ports mounted to UNIs.
NOTE
For OptiX RTN 950 using CSHU/CSHUA boards and OptiX RTN 950A, the total number of
VLANs configured for Ethernet services must not exceed 1024. To avoid this restriction, do as
follows:
1. Retain VLANs/CVLAN of some ports to null.
2. Set VLAN Filtering Table to the desired VLANs for the ports.
In this case, the VLANs configured in VLAN Filtering Table will not be counted in the VLANs
configured for Ethernet services. However, theses ports cannot participate in other Ethernet
services.
2. Configure ports mounted to NNIs.
----End
Data Preparation
Item Value in This Example Planning Principle
Procedure
Step 1 Query the mapping in the DiffServ domain to ensure that the default setting is the same as the
planned setting.
This figure shows ingress mapping.
NOTE
l AF2 has three sub-classes: AF21, AF22, and AF23. In this example, AF21 is used. The same goes with
AF3.
l The mapping of the default DiffServ domain complies with the network planning requirements and
therefore does not need to be modified.
----End
Procedure
Step 1 Create a maintenance domain (MD) for NE21, NE22, NE23, and NE25.
Take NE23 as an example.
Step 2 Create a maintenance association (MA) for NE21, NE22, NE23, and NE25.
Take NE23 as an example.
Step 3 Create maintenance points (MPs) for NE21, NE22, NE23, and NE25.
Take NE23 as an example.
NOTE
l On port 17-EG6-1 of NE21, create two MPs with the IDs of 102 and 103 respectively.
l On port 17-EG6-2 of NE21, create an MP with the ID of 105.
l On port 7-EG6-1 of NE22, create an MP with the ID of 201.
l On port 7-EG6-1 of NE25, create an MP with the ID of 501.
Step 4 Create remote MPs for NE21, NE22, NE23, and NE25.
Take NE23 as an example.
NOTE
l For NE21, create three remote MPs with the IDs of 201, 301, and 501 respectively.
l For NE22, create a remote MP with the ID of 102.
l For NE25, create a remote MP with the ID of 105.
----End
Ethernet services based on EoS/EoPDH boards are classified into EPL services, EVPL
services, EPLAN services, and EVPLAN services.
NOTE
OptiX RTN 905/910A does not support the configuration of Ethernet services on EoS/EoPDH boards.
9.1.1 EoS/EoPDH
Ethernet over SDH (EoS) enables Ethernet services to be transmitted over an SDH network
by encapsulating and mapping Ethernet services into one or more virtual containers (VCs).
Ethernet over PDH (EoPDH) enables Ethernet services to be transmitted over an SDH/PDH
network by encapsulating and mapping Ethernet services to one ore more PDH payloads.
The EoS/EoPDH feature is applicable to the following scenarios:
Ethernet frame
SDH/PDH container
Figure 9-2 Scenario 2: transmitting Native Ethernet services from a Hybrid microwave
network across a leased TDM network
Hybrid microwave
network Hybrid microwave
TDM network network
TDM link
Ethernet frame
SDH/PDH container
9.1.2 VCTRUNK
When Ethernet services need to be transmitted in EoS/EoPDH mode, you need to configure
the Ethernet services between Ethernet ports and VCTRUNKs on the EoS/EoPDH boards.
During the application of the EoS, the rate of the Ethernet service does not adapt to the rate of
the standard VC container of the SDH. Hence, if you directly map the Ethernet service data
into a standard VC container, the transmission bandwidth is lavishly wasted. To solve this
problem, the virtual concatenation technology is used to concatenate standard VC to a VCG
that adapts to the rate of Ethernet services. Similarly, the EoPDH also requires to use the
virtual concatenation technology to concatenate PDHs to a VCG that adapts to the rate of the
Ethernet service.
EMS6 is an EoS board and support VCTRUNKsa binding VC-3 or VC-12 channels.
NOTE
a: For EMS6, if VC-12 channels need to be bound with a VCTRUNK, only VC-12s in VC4-4 are available.
b: On the NMS, VCTRUNKs that bind E1 channels are displayed as VCTRUNKs that bind VC-12 channels.
Flowchart
This figure shows the flowchart for configuring EPL/EVPL services.
Required Start
Optional
Configuring Ethernet Ports
Configuring LAGs
Configuring QoS
End
A.10.5.1 Required.
Configuring
External
Ethernet Ports
A.10.5.2 Required.
Configuring
VCTRUNKs
on an Ethernet
Board
A.10.2.1 Required when a LAG needs to be configured. Set the major parameters
Creating a as follows:
LAG l Set LAG Type to the same value as the opposite equipment. LAG
Type is generally set to Static for the equipment at both ends.
l Set Load Sharing to the same value as the opposite equipment. If
the LAG is configured only to implement protection, it is
recommended that you set Load Sharing to Non-Sharing for the
equipment at both ends. If the LAG is configured to increase the
bandwidth, it is recommended that you set Load Sharing to Sharing
for the equipment at both ends.
l Set Revertive Mode to the same value as the opposite equipment.
Generally, set Revertive Mode to Revertive for the equipment at
both ends. This parameter is valid to only LAGs whose Load
Sharing is set to Non-Sharing.
l Set Sharing Mode to the same value as the opposite equipment.
Unless otherwise specified, this parameter takes the default value.
This parameter is valid to only LAGs whose Load Sharing is set to
Sharing.
l Set Main Port and Selected Standby Ports according to the
network plan. It is recommended that the main and slave ports at
both ends adopt the same settings.
A.10.2.2 Optional.
Setting
Parameters for
LAGs
A.10.3.1 Required.
Creating
Ethernet
Private Line
Services
A.10.8.1 Required when you need to perform CAR or CoS operations. Before
Creating a performing any CAR or CoS operations, you need to create flows.
Flow Set the relevant parameters according to the network plan.
A.10.8.2 Required if you need to perform CAR or CoS operations for a specific
Creating the flow over a port.
CAR Set CAR or CoS parameters and bind the configured CARs or CoSs to
A.10.8.3 the corresponding flows according to the network plan.
Creating the
CoS
A.10.8.4
Binding the
CAR/CoS
A.10.8.5 Required if you need to perform queue scheduling over an egress port or
Configuring limit the bandwidth of queues over an egress port.
Traffic Set the relevant parameters according to the network plan.
Shaping for
Egress Queues
It is recommended that you use standard maintenance points (MPs) for testing Ethernet services. The
following table only provides the description about standard MPs.
A.10.9.1 Creating Required for NEs where the two Ethernet ports involved in the service test are located.
MDs Set the parameters as follows:
l Set Maintenance Domain Name and Maintenance Domain Level to the same
values for the two NEs.
l For an Ethernet service between two edge nodes on the transport network, it is
recommended that Maintenance Domain Level take the default value 4. In the
test for an Ethernet service between two internal NEs on the transport network, set
Maintenance Domain Level to a value smaller than 4. In the test for an Ethernet
service between two Ethernet ports on the same NE, set Maintenance Domain
Level to a value smaller than the value that is set in the test for an Ethernet service
between two internal NEs on the transport network.
Operation Description
A.10.9.2 Creating Required for NEs where the two Ethernet ports involved in the service test are located.
MAs Set the parameters as follows:
l Set Maintenance Domain Name to the value of Maintenance Domain Name that
is set in the preceding step.
l Set Maintenance Association Name to the same value for the two NEs.
A.10.9.3 Creating Required for NEs where the two Ethernet ports involved in the service test are located.
MPs Set the major parameters as follows:
l Set Maintenance Association Name to the value of Maintenance Association
Name that is set in the preceding step.
l Set Node to the Ethernet ports that are involved in the service test.
l Set MEP ID to different values for MEPs in the same MD.
l If the OAM information initiated by the MEP travels through the Ethernet
switching unit on the EMS6 or EFP8 board, set Direction of the MEP to SDH.
Otherwise, set Direction to IP.
l If the MP ID is used to identify an MEP, set CC Status to Active.
l It is recommended that you set CCM Sending Period(ms) to 1000 ms.
Performing an LB Required.
test to test the The LB test result should show that the test is successful.
Ethernet service
configurations
EPLAN services based on the 802.1d bridge 802.1D Bridge-based EPLAN Services in
the Feature Description
Flowchart
This figure shows the flowchart for configuring EPLAN/EVPLAN services.
Required Start
Optional
Configuring Ethernet Ports
Configuring LAGs
Configuring QoS
End
Operation Remarks
A.10.5.1 Required.
Configuring
External
Ethernet Ports
A.10.5.2 Required.
Configuring
VCTRUNKs
on an Ethernet
Board
A.10.2.1 Required when a LAG needs to be configured. Set the major parameters
Creating a as follows:
LAG l Set LAG Type to the same value as the opposite equipment. LAG
Type is generally set to Static for the equipment at both ends.
l Set Load Sharing to the same value as the opposite equipment. If
the LAG is configured only to implement protection, it is
recommended that you set Load Sharing to Non-Sharing for the
equipment at both ends. If the LAG is configured to increase the
bandwidth, it is recommended that you set Load Sharing to Sharing
for the equipment at both ends.
l Set Revertive Mode to the same value as the opposite equipment.
Generally, set Revertive Mode to Revertive for the equipment at
both ends. This parameter is valid to only LAGs whose Load
Sharing is set to Non-Sharing.
l Set Sharing Mode to the same value as the opposite equipment.
Unless otherwise specified, this parameter takes the default value.
This parameter is valid to only LAGs whose Load Sharing is set to
Sharing.
l Set Main Port and Selected Standby Ports according to the
network plan. It is recommended that the main and slave ports at
both ends adopt the same settings.
A.10.2.2 Optional.
Setting
Parameters for
LAGs
Table 9-8 Configuring EVPLAN services based on the IEEE 802.1q bridge
Operation Remarks
Operation Remarks
A.10.3.3 Changing the Required if you need to change a port connected to a VB,
Ports Connected to a VB enabled status of a port connected to a VB, or Hub/Spoke
attribute of a port connected to a VB.
A.10.8.1 Required when you need to perform CAR or CoS operations. Before
Creating a performing any CAR or CoS operations, you need to create flows.
Flow Set the relevant parameters according to the network plan.
A.10.8.2 Required if you need to perform CAR or CoS operations for a specific
Creating the flow over a port.
CAR Set CAR or CoS parameters and bind the configured CARs or CoSs to
A.10.8.3 the corresponding flows according to the network plan.
Creating the
CoS
A.10.8.4
Binding the
CAR/CoS
Operation Description
A.10.8.5 Required if you need to perform queue scheduling over an egress port or
Configuring limit the bandwidth of queues over an egress port.
Traffic Set the relevant parameters according to the network plan.
Shaping for
Egress Queues
It is recommended that you use standard maintenance points (MPs) for testing Ethernet services. The
following table only provides the description about standard MPs.
A.10.9.1 Creating Required for NEs where the two Ethernet ports involved in the service test are located.
MDs Set the parameters as follows:
l Set Maintenance Domain Name and Maintenance Domain Level to the same
values for the two NEs.
l For an Ethernet service between two edge nodes on the transport network, it is
recommended that Maintenance Domain Level take the default value 4. In the
test for an Ethernet service between two internal NEs on the transport network, set
Maintenance Domain Level to a value smaller than 4. In the test for an Ethernet
service between two Ethernet ports on the same NE, set Maintenance Domain
Level to a value smaller than the value that is set in the test for an Ethernet service
between two internal NEs on the transport network.
A.10.9.2 Creating Required for NEs where the two Ethernet ports involved in the service test are located.
MAs Set the parameters as follows:
l Set Maintenance Domain Name to the value of Maintenance Domain Name that
is set in the preceding step.
l Set Maintenance Association Name to the same value for the two NEs.
A.10.9.3 Creating Required for NEs where the two Ethernet ports involved in the service test are located.
MPs Set the major parameters as follows:
l Set Maintenance Association Name to the value of Maintenance Association
Name that is set in the preceding step.
l Set Node to the Ethernet ports that are involved in the service test.
l Set MEP ID to different values for MEPs in the same MD.
l If the OAM information initiated by the MEP travels through the Ethernet
switching unit on the EMS6 or EFP8 board, set Direction of the MEP to SDH.
Otherwise, set Direction to IP.
l If the MP ID is used to identify an MEP, set CC Status to Active.
l It is recommended that you set CCM Sending Period(ms) to 1000 ms.
Operation Description
Performing an LB Required.
test to test the The LB test result should show that the test is successful.
Ethernet service
configurations
l In this example, few Ethernet services are transmitted only on BTS13 and BTS14. To
meet the service requirements, the TDM microwave network doe not need to be
upgraded and Ethernet services are transmitted in EoS mode.
l The Ethernet services from BTS13 occupy a 4 Mbit/s bandwidth and the Ethernet
services from BTS14 occupy a 10 Mbit/s bandwidth.
l Ethernet services from BTS13 and BTS14 carry VLAN IDs, and VLAN IDs on the
entire network are planned in a unified manner.
l FE links to the BSC are configured with link aggregation group (LAG) protection.
l QoS processing is not required.
E1
BTS12
STM-1
FE+E1 NE14 FE+STM-1
BTS13
4 Mbit/s E1
VLAN 120
NE13 NE12 NE11
BSC
FE+E1 BTS11
E1
NE16 NE15
BTS14
BTS15 10 Mbit/s
VLAN 130
CSHO CSHO
ISU2
NE6
ISU2 NE6
ISU2 ISU2
SP3S EMS6 SP3S
NE16 NE15 FE E1
E1
BTS14
BTS15
Data Preparation
LCAS Enabled -
STM-1
FE+E1 NE14 FE+STM-1
BTS13
4 Mbit/s E1
VLAN 120
NE13 NE12 NE11
BSC
FE+E1 BTS11
E1
NE16 NE15
BTS14
BTS15 10 Mbit/s
NE15 (RTN 950A) VLAN 130
1-EMS6–PORT1 (to BTS14)
1-EMS6-VCTRUNK1 (to NE13)
VC4-4-VC12(1-5)
Procedure
Step 1 Configure external ports.
Take NE11 as an example.
1. Set basic attributes.
2. Query tag attributes and ensure that the tag attributes are the same as planned.
3. Query network attributes and ensure that network attributes are the same as planned.
2. Query network attributes and ensure that network attributes are the same as planned.
3. Enable LCAS.
4.
----End
Data Preparation
Item Value in This Example Planning Principle
Procedure
Step 1 Configure a LAG on NE11.
----End
Data Preparation
Ethernet services from each BTS carry a specific VLAN ID. Therefore, you need to configure
VLAN-based EVPL services in this example. The following tables provide the planning
information.
Board 4-EMS6
Direction Bidirectional
Board 1-EMS6
Direction Bidirectional
Procedure
Step 1 Configure Ethernet services.
Take the service between 4-EMS6-1 to VCTRUNK1 on NE11 as an example.
----End
Data Preparation
Item Value in This Example Planning Principle
VC12:1-5
4-EMS6-1(VCTRUNK2)
VC4-4:VC12:6-7
Links-2: NE13-NE14
Station NE13 NE14
Timeslot 1-SL1D-1 3-IF1 3-IF1
4-EMS6 -1(VCTRUNK1)
VC4-4:VC12:1-2
Pass through
Add/Drop
Foward
Procedure
Step 1 Configure cross-connections.
Take the cross-connection between VCTRUNK1 to 3-ISU2 on NE11 as an example.
----End
Procedure
Step 1 Create a maintenance domain (MD) for NE11, NE14, and NE15.
Take NE14 as an example.
Step 2 Create a maintenance association (MA) for NE11, NE12, NE14, and NE16.
Take NE14 as an example.
Step 3 Create maintenance points (MPs) for NE11, NE12, NE14, and NE16.
Take NE14 as an example.
NOTE
l NE11 and NE17 use the EoPDH technology, wherein Ethernet services are encapsulated
into E1 services so that Ethernet services traverse the TDM network successfully.
NOTE
To facilitate description of service configurations in this example, NE17 is an IDU that supports the
EoPDH function. In addition to an IDU, NE17 can also be an MSTP device that provides the EoPDH
function.
l Each BTS is allocated with a specific Ethernet bandwidth and a total of 40 Mbit/s
bandwidth is required. Therefore, 20 E1 lines need to be leased.
l The services from each BTS carry VLAN IDs, and VLAN IDs on the entire network are
planned in a unified manner. Therefore, VLAN-based E-Line services are configured for
service transmission in this example.
l VLAN priorities have been configured for base stations based on service types. In
addition, QoS processing is required.
NOTE
In this example, service configurations only on NE11 and NE17 are described. For service configuration
details on NE12 to NE16, see 8.7 Configuration Example (VLAN-based E-Line Services).
FE
GE
NE14 TDM
FE E1 network
NE13 NE12 NE11
E1
FE
BTS11
FE 10 Mbti/s
NE16 NE15 VLAN 100 NE17
BSC
BTS15
10 Mbit/s
VLAN 120
E1
CSHO
CSHO CSHO
ISU2 NE6
NE6
ISU2 NE6
ISU2 ISU2
EFP8
SP3D
EG4P SP3S EG4P SP3S
NE16 NE15 NE17 FE
FE E1
BTS15 BSC
Data Preparation
4-EFP8-PORT10
4-EFP8-PORT10
Data Preparation
Service ID 1
Direction UNI-UNI
Procedure
Step 1 Configure E-Line services.
----End
Data Preparation
Item Value in This Example Planning Principle
Procedure
Step 1 Query the mapping in the DiffServ domain to ensure that the default setting is the same as the
planned setting.
This figure shows ingress mapping.
NOTE
l AF2 has three sub-classes: AF21, AF22, and AF23. In this example, AF21 is used. The same goes with
AF3.
l The mapping of the default DiffServ domain complies with the network planning requirements and
therefore does not need to be modified.
----End
Data Preparation
LCAS Enabled -
FE
GE
NE14 TDM
FE E1 network
NE13 NE12 NE11
E1
FE
BTS11
FE 10 Mbti/s
NE16 NE15 VLAN 100 NE17
BSC
BTS15
10 Mbit/s NE17 (RTN 950A)
VLAN 120
4-EFP8-PORT1 (to BSC)
4-EFP8-VCTRUNK1 (to NE11)
VC4-1-VC12(1-10)
4-EFP8-VCTRUNK2 (to NE11)
VC4-1-VC12(11-20)
Procedure
Step 1 Configure external ports.
In this example, you only need to enable port 4-EFP8-PORT1; the other parameters take their
default values.
----End
Data Preparation
Item Value in This Example Planning Principle
(NE11 and NE17)
Reversion mode - -
Procedure
Step 1 Configure a LAG.
Take NE11 as an example.
----End
Data Preparation
Parameter NE11
Board 4-EFP8
Direction Bidirectional
Procedure
Step 1 Configure Ethernet services.
Take the service between 4-EFP8-1 to VCTRUNK1 on NE11 as an example.
----End
Data Preparation
Parameter Value
Direction Bidirectional
Source port 1
Sink port -
Sink VC-4 -
Parameter Value
Direction Bidirectional
Source port 1
Sink port -
Sink VC-4 -
Procedure
Step 1 Configure cross-connections.
Take the cross-connection between 4-EFP8-1 and 2-SP3D on NE11 as an example.
----End
Data Preparation
Parameter Value
Bound CAR ID - - - -
Bound CoS ID 1 1 1 1
Parameter Value
Parameter Value
Bound CAR ID - - - -
Bound CoS ID 1 1 1 1
NOTE
According to the service classes of BTS services, CoS with an ID 1 schedules BTS services with different
VLAN priorities into egress queues with different forwarding priorities.
In this example, BTS services are configured with VLAN priorities or DSCPs based on
service types. The EFP8 board performs CoS processing for BTS services based on VLAN
priorities or DSCPs.
In this example, BTSs allocate VLAN priorities to their services based on service types. CoS
needs to be configured based on service VLAN priorities on Ethernet ports that receive
services from or transmit services to the BTSs.
Parameter Value
CoS ID 1
Table 9-28 CoS parameters and corresponding BTS service types of EFP8 (NE11 and NE17)
NOTE
Queue 8 (namely, CoS priority 7) is an SP queue and queues 1 to 7 (namely, CoS priorities 0 to 6) are WRR
queues. Therefore, you need to map all high-priority services into queue 8 to ensure that high-priority
services can be scheduled in time.
Procedure
Step 1 Create flows.
Take the Port+VLAN (150) flow on NE11 as an example.
----End
Procedure
Step 1 Create a maintenance domain (MD) for NE11 and NE17.
Take NE11 as an example.
NOTE
Over port 1-EFP8-1 on NE15, create an MEP with an MP ID 201 for each service with a VLAN ID 150.
----End
Configuring MPLS tunnels, to be specific, static LSPs, is a prerequisite for configuring PWE3
services.
Flowchart
NOTE
l For MPLS tunnels that have been configured on a per-NE basis, follow instructions in A.15.4 Searching
for MPLS Tunnels and PWE3 Services to synchronize the MPLS tunnels to the network layer of the
U2000. This enables end-to-end management of the MPLS tunnels. For MPLS APS protection groups
that have also been configured on a per-NE basis, follow instructions in A.15.5.8 Searching for MPLS
APS Protection Groups to synchronize the protection groups to the network layer of the U2000.
NOTE
l When OptiX RTN 905 transmits MPLS tunnel services through ML-PPP ports, the working modes
of the E1, channelized STM-1, and cascading ports must be set to CES.
l When OptiX RTN 950A housing an MN1 board transmits MPLS tunnel services through ML-PPP
ports, the working modes of the E1 and STM-1 ports on the MP1 and CD1 boards must be set to
CES.
For details, see A.8.2 Setting Working Modes of E1 Ports.
Operation Remarks
NOTE
a:
l For an OptiX RTN 905E 2E-provided microwave link for which 1+1 protection or link aggregation
group (LAG) is configured, set parameters only for the main IF_ETH port. The following operations
described in this section are also applicable only to the main port.
l For OptiX RTN 905E 1Es that are stacked to implement physical link aggregation/ (PLA), Enhanced
physical link aggregation(EPLA), 1+1 hot standby (HSB), 1+1 frequency diversity (FD), or 1+1
space diversity (SD), set parameters only for IF_ETH ports on main NEs. The following operations
described in this section are also applicable only to main NEs.
Operation Remarks
NOTE
a:
l For an OptiX RTN 905E 2E-provided microwave link for which 1+1 protection or link aggregation
group (LAG) is configured, set parameters only for the main IF_ETH port. The following operations
described in this section are also applicable only to the main port.
l For OptiX RTN 905E 1Es that are stacked to implement physical link aggregation/ (PLA), Enhanced
physical link aggregation(EPLA), 1+1 hot standby (HSB), 1+1 frequency diversity (FD), or 1+1
space diversity (SD), set parameters only for IF_ETH ports on main NEs. The following operations
described in this section are also applicable only to main NEs.
Operation Remarks
Table 10-4 Configuring ML-PPP (E1s in channelized STM-1s being MP group members)
Operation Remarks
Operation Remarks
A.8.7.2 Required.
Setting
Basic
Attributes
of Serial
Ports
A.9.2.1 Required if the LAG function needs to be used for an FE/GE port.
Creating a
LAG
NOTE
For an Ethernet link for which a LAG is configured, configure parameters only for the main port. The
following operations described in this section are also applicable to the main port only.
A.11.1.1 Creating Required when the dynamic ARP protocol cannot obtain the next-
ARP Static Entries hop MAC address (for example, when packets traverse a Layer 2
network).
Operation Remarks
Searching for Layer If the NEs at both ends of an MPLS tunnel can be managed on the
2 Links U2000, a Layer 2 link needs to be created for the MPLS tunnel.
Then, the automatic route computation function can be used to
create the MPLS tunnel.
You can create Ethernet fibers/cables when searching for Layer 2
links.
A.11.2.7 Changing Perform this operation to set a VLAN ID for related MPLS nodes
MPLS Tunnel if packets on a segment of an MPLS tunnel need to traverse a
Information Layer 2 network.
Configuring QoS
For details about the QoS configuration procedure, seeConfiguration Process (QoS/HQoS).
A.15.5.5 Verifying Required. It is recommended that you perform an LSP ping test to
MPLS Tunnels in an verify the connectivity of an MPLS tunnel.
End-to-End Mode
Start Start
Set MPLS port attributes (not Set MPLS port attributes Configure ML PPP (Smart Configure ML PPP (E1s in
using VLAN sub-interfaces) (using VLAN sub-interfaces) E1s being MP group channelized STM-1s being
members) MP group members)
Create MPLS
Create MPLS tunnels
protection groups
Optional End
NOTE
l When OptiX RTN 905 transmits MPLS tunnel services through ML-PPP ports, the working modes
of the E1, channelized STM-1, and cascading ports must be set to CES.
l When OptiX RTN 950A housing an MN1 board transmits MPLS tunnel services through ML-PPP
ports, the working modes of the E1 and STM-1 ports on the MP1 and CD1 boards must be set to
CES.
For details, see A.8.2 Setting Working Modes of E1 Ports.
Table 10-8 Setting attributes of MPLS ports (not using VLAN sub-interfaces)
Operation Remarks
Operation Remarks
NOTE
a:
l For an OptiX RTN 905E 2E-provided microwave link for which 1+1 protection or link aggregation
group (LAG) is configured, set parameters only for the main IF_ETH port. The following operations
described in this section are also applicable only to the main port.
l For OptiX RTN 905E 1Es that are stacked to implement physical link aggregation/ (PLA), Enhanced
physical link aggregation(EPLA), 1+1 hot standby (HSB), 1+1 frequency diversity (FD), or 1+1
space diversity (SD), set parameters only for IF_ETH ports on main NEs. The following operations
described in this section are also applicable only to main NEs.
Operation Remarks
NOTE
a:
l For an OptiX RTN 905E 2E-provided microwave link for which 1+1 protection or link aggregation
group (LAG) is configured, set parameters only for the main IF_ETH port. The following operations
described in this section are also applicable only to the main port.
l For OptiX RTN 905E 1Es that are stacked to implement physical link aggregation/ (PLA), Enhanced
physical link aggregation(EPLA), 1+1 hot standby (HSB), 1+1 frequency diversity (FD), or 1+1
space diversity (SD), set parameters only for IF_ETH ports on main NEs. The following operations
described in this section are also applicable only to main NEs.
Table 10-11 Configuring ML-PPP (E1s in channelized STM-1s being MP group members)
Operation Remarks
A.8.7.2 Required.
Setting
Basic
Attributes
of Serial
Ports
A.9.2.1 Required if the LAG function needs to be used for an FE/GE port.
Creating a
LAG
NOTE
For an Ethernet link for which a LAG is configured, configure parameters only for the main port. The
following operations described in this section are also applicable to the main port only.
A.11.1.1 Creating ARP Static Required when the dynamic ARP protocol cannot
Entries obtain the next-hop MAC address (for example, when
packets traverse a Layer 2 network).
Perform the following operations only on ingress and egress nodes, but not on transit nodes.
OptiX RTN 910A does not support Y.1711-compliant MPLS OAM.
Configuring A.11.2.3 Required if the tunnel OAM standard is not the default
Y.1711- Changing the value Y.1711.
based MPLS MPLS
OAM Tunnel/PW
OAM Standard
A.11.3.1 Creating an MPLS Required when you need to configure protection for
APS Protection Group services carried on an MPLS tunnel.
A.11.2.3 Required.
Changing the
MPLS
Tunnel/PW
OAM Standard
A.11.3.1 Creating an MPLS Required when you need to configure protection for
APS Protection Group services carried on an MPLS tunnel.
Configuring QoS
For details about the QoS configuration procedure, seeConfiguration Process (QoS/HQoS).
A.11.2.9 Setting MPLS OAM Required when you need to enable the MPLS OAM
(Y.1711) Parameters function to detect the tunnel status before creating an
MPLS APS protection group.
All base station services need to be transmitted through a PSN to the BSC and RNC. Based on
6.5 Configuration Example (Microwave Links on a Packet Network), configure MPLS
tunnels on the packet ring according to the following actual requirements:
l Bidirectional MPLS tunnels are configured between NE31 and NE11, between NE31
and NE21, and between NE31 and NE32.
l MPLS APS protection is configured for each tunnel on the packet ring to ensure service
availability upon a tunnel fault.
l MPLS interfaces used on the packet ring are shown in Figure 10-3.
2-EG4-1(to NE11)
2-EG4-2(to NE31)
GE GE
NE32 RTN950
RTN980
NE11 NE31 1-EG4-1(to NE32)
2-EG4-1(to NE21) GE NE21 GE
1-EG4-2(to NE21)
2-EG4-2(to NE32)
RTN980
1-EG4-1(to NE31)
1-EG4-2(to NE11)
Data Preparation
l IP address resources: allocated to ports at both ends of manually created fibers/cables
l Ethernet port attributes: Working Mode, Max Frame Length (bytes), Enable Bit
Error Detection and Enable Switching Triggered by Bit Error.
Procedure
Step 1 Configure port IP address resources.
Configuring port IP address resources is a prerequisite for automatically allocating IP
addresses to MPLS ports.
l Because IP addresses cannot be automatically allocated to some MPLS ports, the
configured IP address resources must not include the IP address resources that have been
allocated to these ports.
l If the IP address resources to be configured are inconsecutive, you can configure
multiple IP address resources.
l The configured IP address resources must not contain 192.168.0.0/16, 192.169.0.0/16, or
network segments to which LSR IDs and NE IP addresses belong.
This table provides parameter values for configuring port IP address resources.
NOTE
After fibers/cables are created, query port attributes. Port Mode is Layer 3, Enable Tunnel is Enabled, and
IP Address is the allocated network segment with the length of 30 bits.
Figure 10-6 Setting attribute for the Ethernet port that NE31 uses to connect to NE21
----End
Data Preparation
l Basic MPLS attributes: LSR ID and start of global label space
l End-to-end MPLS tunnel with MPLS APS protection: source and sink boards, explicit
boards, revertive mode, and WTR time
l Y.1731-compliant tunnel OAM parameters or Y.1711-compliant tunnel OAM parameters
Procedure
Step 1 Set the basic attributes of MPLS.
Set the basic attributes LSR ID and Start of Global Label Space for each NE.
NE32
NE31
LSR ID: 130.0.0.1
NE11
LSR ID: 130.0.0.3
NE21
NOTE
After Layer 2 links are searched out, you do not need to create fibers/cables.
Step 4 Create end-to-end MPLS tunnels with MPLS APS protection between NE31 and NE11.
Figure 10-8 Plan of 1:1 MPLS APS for the MPLS tunnels between NE31 and NE11
Transmit Transmit
Board:2-EG4-1 Board:2-EG4-2
IP: 46.1.64.5 IP: 46.1.64.2
Incoming Lable:1511 Incoming Lable:1501
Outgoing Lable:1511 Outgoing Lable:1501
Egress Ingress
Board:2-EG4-2 Board:1-EG4-1
IP: 46.1.64.6 NE32
IP: 46.1.64.1
Incoming Lable:1511 Incoming Lable:1501
Outgoing Lable:1511 Outgoing Lable:1501
NE31
Egress NE11 Ingress
Board:2-EG4-1
IP: 46.1.64.9 Board:1-EG4-2
NE21
IncomingLable:1512 IP: 46.1.64.14
Outgoing Lable:1512 Incoming Lable:1502
Outgoing Lable:1502
Transmit Transmit
Board:1-EG4-2 Board:1-EG4-1
IP: 46.1.64.10 IP: 46.1.64.13 Working Tunnel
Incoming Lable:1512 Incoming Lable:1502
Protection Tunnel
Outgoing Lable:1512 Outgoing Lable:1502
2 NE( 32)
NE( 31)
Select “Auto-
NE(31) Calculate route”.
NE(32) 3
NE(11)
4
Select source:
NE(31) Double-click the
NE(32)
source node.
5
Select sink: Double-
NE(11)
click the sink node.NE(21)
7
NE(31 The interfaces are displayed.
)
NE(32 Configure labels.
)
NE(11
)
NE(31
Node information is ) 1501 1-EG4-1(Port-1)
NE(32
displayed. ) 2-EG4-2(Port-2) 1501 1511 2-EG41(Port-1)
NE(11
6 2-EG4-2(Port-2) 1511
)
Or click Auto-
8 Assign Label.
NE( 31)
NE( 32)
4. Configure constraints for the tunnels. If the tunnels that are automatically calculated are
not the planned tunnels, you can configure constraints for them manually.
NE(31)
2-EG4-2(Port-2) 46.1.64.2
Right-click the explicit 2-EG4-1(Port-1) 46.1.64.5
node to display the
Select the explicit port.
shortcut menu.
12 13
14
NE(11) NE(21)
16
NE(31)
NE(32)
NE(11)
17
15
NE(31) NE(11)
11
19
1501 1-EG4-1(Port-1)
2-EG4-2(Port-2)
20 1501 1511 2-EG4-1(Port-1)
2-EG4-2(Port-2) 1511 18
NE(31)
NE(32)
NE(11)
22
23
21
NOTE
Either Y.1731-compliant OAM or Y.1711-compliant OAM is used at a time.
Step 5 Create MPLS tunnels with MPLS APS protection between NE31 and NE32 and end-to-end
MPLS tunnels with MPLS APS protection between NE31 and NE21.
Figure 10-9 Plan of 1:1 MPLS APS for the MPLS tunnels between NE31 and NE32
Egress Egress
Board:2-EG4-2 Board:2-EG4-2
IP: 46.1.64.6 IP: 46.1.64.6
Incoming Lable:1622 Incoming Lable:1601
Outgoing Lable:1622 Outgoing Lable:1601
Ingress
Transmit
Board:1-EG4-1
IP: 46.1.64.1
Board:2-EG4-2 Incoming Lable:1601
IP: 46.1.64.6 NE32 Outgoing Lable:1601
Incoming Lable:1622
Outgoing Lable:1622
NE31 Ingress
Transmit NE11
Board:1-EG4-2
Board:2-EG4-1 IP: 46.1.64.14
IP: 46.1.64.9 Incoming Lable:1602
NE21
Incoming Lable:1612 Outgoing Lable:1602
Outgoing Lable:1612
Transmit Transmit
Board:1-EG4-2 Board:1-EG4-1
IP: 46.1.64.10 IP: 46.1.64.13
Incoming Lable:1612 Incoming Lable:1602 Working Tunnel
Outgoing Lable:1612 Outgoing Lable:1602 Protection Tunnel
Figure 10-10 Plan of 1:1 MPLS APS for the MPLS tunnels between NE31 and NE21
Transmit Transmit
Board:2-EG4-2 Board:2-EG4-2
IP: 46.1.64.6 IP: 46.1.64.6
Incoming Lable:1712 Incoming Lable:1702
Outgoing Lable:1712 Outgoing Lable:1702
Transmit Ingress
Board:2-EG4-2 Board:1-EG4-1
IP: 46.1.64.6 IP: 46.1.64.1
NE32
Incoming Lable:1712 Incoming Lable:1702
Outgoing Lable:1712 Outgoing Lable:1702
NE31
Transmit NE11 Ingress
Board:2-EG4-1
Board:1-EG4-2
IP: 46.1.64.9 NE21 IP: 46.1.64.14
Incoming Lable:1722
Incoming Lable:1701
Outgoing Lable:1722
Outgoing Lable:1701
Egress Egress
Board:1-EG4-2 Board:1-EG4-1
IP: 46.1.64.10 IP: 46.1.64.13
Working Tunnel
Incoming Lable:1722 Incoming Lable:1701
Outgoing Lable:1722 Outgoing Lable:1701 Protection Tunnel
Configure the two protection groups according to the configuration of the protection group
between NE31 and NE11.
----End
Data Preparation
Traffic carried on tunnels need to be classified based on the MPLS EXP field in packets. In
this example, the mapping in the default DiffServ domain is used for simple traffic
classification.
l Mapping in the default DiffServ domain
CS7 7 –
CS6 6 –
AF4 4 –
AF1 1 –
Procedure
Step 1 Apply the mapping in the default DiffServ domain to target NNIs to implement simple traffic
classification.
Each NE uses mapping in the default DiffServ domain. The packet type for traffic
classification needs to be changed to mpls-exp for NNIs of All Tunnels.
Figure 10-11 Applying the mapping in the default DiffServ domain to NNIs
4
2
1 3
----End
Procedure
Step 1 Use the LSP Ping function in Diagnose > Test and Check to verify the connectivity of
MPLS tunnels.
6 7
NOTE
To verify the service availability at different packet lengths, you can set Packet Size to 128, 256, 512, 1024,
or 1280 bytes as desired.
After the verification, query the verification result of each MPLS tunnel. Packet Loss Ratio (%) of each
tunnel should be zero.
----End
Data Preparation
Board:2-EG4-2 Board:1-EG4-1
IP: 46.1.64.6/30 NE32 IP: 46.1.64.1/30
NE31
NE11
NE21 Board:1-EG4-2
Board:2-EG4-1 IP: 46.1.64.14/30
IP: 46.1.64.9/30
Board:1-EG4-2 Board:1-EG4-1
IP: 46.1.64.10/30 IP: 46.1.64.13/30
Procedure
Step 1 Set attributes of Ethernet ports.
Set basic attributes and Layer 3 attributes for Ethernet ports between NEs. The Ethernet port
that NE31 uses to connect to NE21 is used as an example.
Figure 10-14 Setting attribute for the Ethernet port that NE31 uses to connect to NE21
----End
Data Preparation
l Basic MPLS attributes: LSR ID and start of global label space
l MPLS tunnels with MPLS APS protection: source and sink board, explicit boards, and
ingress and egress labels
Procedure
Step 1 Set the basic attributes of MPLS.
Set the basic attributes LSR ID and Start of Global Label Space for each NE.
NE32
NE31
LSR ID: 130.0.0.1
NE11
LSR ID: 130.0.0.3
NE21
Step 2 Create bidirectional MPLS tunnels (working and protection tunnels in the APS protection
group between NE31 and NE11).
Transmit Transmit
Board:2-EG4-1 Board:2-EG4-2
IP: 46.1.64.5 IP: 46.1.64.2
Incoming Lable:1511 Incoming Lable:1501
Outgoing Lable:1511 Outgoing Lable:1501
Egress Ingress
Board:2-EG4-2 Board:1-EG4-1
IP: 46.1.64.6 NE32
IP: 46.1.64.1
Incoming Lable:1511 Incoming Lable:1501
Outgoing Lable:1511 Outgoing Lable:1501
NE31
Egress NE11 Ingress
Board:2-EG4-1
IP: 46.1.64.9 Board:1-EG4-2
NE21
IncomingLable:1512 IP: 46.1.64.14
Outgoing Lable:1512 Incoming Lable:1502
Outgoing Lable:1502
Transmit Transmit
Board:1-EG4-2 Board:1-EG4-1
IP: 46.1.64.10 IP: 46.1.64.13 Working Tunnel
Incoming Lable:1512 Incoming Lable:1502
Protection Tunnel
Outgoing Lable:1512 Outgoing Lable:1502
1-EG4
1(Port-1)
2-EG4
2(Port-2)
2-EG4
1(Port-1)
3
1511
2-EG4
1511
1511
Figure 10-19 Plan of 1:1 MPLS APS for the MPLS tunnels between NE31 and NE32
Egress Egress
Board:2-EG4-2 Board:2-EG4-2
IP: 46.1.64.6 IP: 46.1.64.6
Incoming Lable:1622 Incoming Lable:1601
Outgoing Lable:1622 Outgoing Lable:1601
Ingress
Transmit
Board:1-EG4-1
IP: 46.1.64.1
Board:2-EG4-2 Incoming Lable:1601
IP: 46.1.64.6 NE32 Outgoing Lable:1601
Incoming Lable:1622
Outgoing Lable:1622
NE31 Ingress
Transmit NE11
Board:1-EG4-2
Board:2-EG4-1 IP: 46.1.64.14
IP: 46.1.64.9 Incoming Lable:1602
NE21
Incoming Lable:1612 Outgoing Lable:1602
Outgoing Lable:1612
Transmit Transmit
Board:1-EG4-2 Board:1-EG4-1
IP: 46.1.64.10 IP: 46.1.64.13
Incoming Lable:1612 Incoming Lable:1602 Working Tunnel
Outgoing Lable:1612 Outgoing Lable:1602 Protection Tunnel
Figure 10-20 Plan of 1:1 MPLS APS for the MPLS tunnels between NE31 and NE21
Transmit Transmit
Board:2-EG4-2 Board:2-EG4-2
IP: 46.1.64.6 IP: 46.1.64.6
Incoming Lable:1712 Incoming Lable:1702
Outgoing Lable:1712 Outgoing Lable:1702
Transmit Ingress
Board:2-EG4-2 Board:1-EG4-1
IP: 46.1.64.6 IP: 46.1.64.1
NE32
Incoming Lable:1712 Incoming Lable:1702
Outgoing Lable:1712 Outgoing Lable:1702
NE31
Transmit NE11 Ingress
Board:2-EG4-1
Board:1-EG4-2
IP: 46.1.64.9 NE21 IP: 46.1.64.14
Incoming Lable:1722
Incoming Lable:1701
Outgoing Lable:1722
Outgoing Lable:1701
Egress Egress
Board:1-EG4-2 Board:1-EG4-1
IP: 46.1.64.10 IP: 46.1.64.13
Working Tunnel
Incoming Lable:1722 Incoming Lable:1701
Outgoing Lable:1722 Outgoing Lable:1701 Protection Tunnel
Configure tunnels in the two protection groups according to the configuration of tunnels in the
protection group between NE31 and NE11.
----End
Data Preparation
l Y.1731 tunnel OAM parameters
l MPLS APS protection group parameters: working tunnel, protection tunnel, recovery
mode, and WTR time
Procedure
Step 1 Switch the OAM standard.
The default standard is Y.1711. If the standard needs to be switched to Y.1731, switch the
OAM standard to Y.1731 on the first node and last node of each tunnel. This figure shows the
procedure.
Configure the first node and last node for each tunnel according to the following figure.
3
1
NOTE
After OAM has been configured for working and protection tunnels, APS protection groups can be created.
Step 4 Create an MPLS APS protection group between NE31 and NE11.
When configuring the protection group on the first node and last node, select the working and
protection tunnels and set the protection group attributes.
NOTE
During creation of the APS protection group, set the protocol status to disabled. After the protection
group has been created at the first node and last node, enable the protocol respectively.
l NE11 is the last node and needs to be configured consistently with the first node.
Step 5 Create MPLS APS protection groups between NE31 and NE11 and between NE31 and NE21.
The configuration procedure is the same as that for the MPLS ASP protection group between
NE31 and NE11.
Step 6 Start the PW APS protection protocol.
After the protection groups are created, enable the APS protocol in sequence. If the protocol
has been enabled after the creation, it is recommended that you disable and then enable the
protocol. This figure shows the procedure.
----End
Data Preparation
Traffic carried on tunnels need to be classified based on the MPLS EXP field in packets. In
this example, the mapping in the default DiffServ domain is used for simple traffic
classification.
l Mapping in the default DiffServ domain
CS7 7 –
CS6 6 –
AF4 4 –
AF1 1 –
Procedure
Step 1 Apply the mapping in the default DiffServ domain to target NNIs to implement simple traffic
classification.
Each NE uses mapping in the default DiffServ domain. The packet type for traffic
classification needs to be changed to mpls-exp for NNIs of All Tunnels.
Figure 10-25 Applying the mapping in the default DiffServ domain to NNIs
4
2
1 3
----End
Data Preparation
To use the LB function of MPLS-TP OAM to verify tunnel connectivity, prepare the
following data:
l RMEP IP Address: Because MEG IDs are based on IP addresses, a remote MEP IP
address, that is an LSR ID, is used during an LB test.
Procedure
Step 1 Start an LB test of MPLS-TP PW OAM.
On the first node and last node of each tunnel, select a tunnel for test and perform the test as
shown in the following figure. The test result is displayed in the Test Result tab.
3
Enter the LSR ID of
the remote node.
----End
l Figure 10-27 shows information about NNIs used on the packet microwave links.
RTN 950
3-ISV3-1(to NE34)
4-ISV3-1(to NE32)
RTN 905 NE34
NE33 RTN 980
3-ISV3-1(to NE33)
3-ISV3-1(to NE33)
GE GE
NE32
NE11 NE31
GE NE21 GE
Data Preparation
l IP address resources: allocated to ports at both ends of manually created fibers/cables
l Ethernet port attributes: Working Mode and Max Frame Length (bytes)
Procedure
Step 1 Configure port IP address resources.
Configuring port IP address resources is a prerequisite for automatically allocating IP
addresses to MPLS ports.
l Because IP addresses cannot be automatically allocated to some MPLS ports, the
configured IP address resources must not include the IP address resources that have been
allocated to these ports.
Figure 10-29 Manually creating a microwave fiber/cable between NE32 and NE33
NOTE
After fibers/cables are created, query port attributes. Port Mode is Layer 3, Enable Tunnel is Enabled, and
IP Address is the allocated network segment with the length of 30 bits.
----End
Data Preparation
l Basic MPLS attributes: LSR ID and start of global label space
l End-to-end MPLS tunnel: source and sink boards and explicit boards
Procedure
Step 1 Set the basic attributes of MPLS.
Set the basic attributes LSR ID and Start of Global Label Space for each NE.
NE34 NE33
LSR ID: 130.0.0.2
NE32
NE31
NE11
NE21
NOTE
After Layer 2 links are searched out, you do not need to create fibers/cables.
Board:4-ISV3-1 Board:3-ISV3-1
IP: 46.1.64.18/30 IP: 46.1.64.17/30
Incoming Lable:1801 Incoming Lable:1801
Outgoing Lable:1801 Outgoing Lable:1801
Tunnel
2
Set the basic
attributes.
4 5
Double-click an
Double-click an
NE to set it as the
NE to set it as
NE(33)
sink NE.
the source NE. NE(32)
2. Configure constraints for the tunnels. If the tunnels that are automatically calculated are
not the planned tunnels, you can configure constraints for them manually.
NE(31)
2-EM6F-2(Port-2) 46.1.64.2
Right-click the explicit 46.1.64.
2-EM6F-1(Port-1)
node to display the 5
8 Select the explicit port.
shortcut menu. 9
10
NE(11) NE(21)
Tunnel
The configuration method is the same as that for the tunnel between NE32 and NE33.
----End
Data Preparation
Traffic carried on tunnels need to be classified based on the MPLS EXP field in packets. In
this example, the mapping in the default DiffServ domain is used for simple traffic
classification.
l Mapping in the default DiffServ domain:
CS7 7 –
CS6 6 –
AF4 4 –
AF1 1 –
Procedure
Step 1 Apply the mapping in the default DiffServ domain to target NNIs to implement and simple
traffic classification.
Each NE uses the mapping in the default DiffServ domain. The packet type for traffic
classification needs to be changed to mpls-exp for NNIs of All Tunnels.
Figure 10-36 Applying the mapping in the default DiffServ domain to NNIs
4 2
1 3
----End
Procedure
Step 1 Use the LSP Ping function in Diagnose > Test and Check to verify the connectivity of
MPLS tunnels.
6 7
NOTE
To verify the service availability at different packet lengths, you can set Packet Size to 128, 256, 512, 1024,
or 1280 bytes as desired.
After the verification, query the verification result of each MPLS tunnel. Packet Loss Ratio (%) of each
tunnel should be zero.
----End
Data Preparation
Procedure
Step 1 Set microwave port attributes.
Basic attributes and Layer 3 attributes need to be configured for microwave ports between
NEs. A microwave port is taken as an example in the following figure.
----End
Data Preparation
l Basic MPLS attributes: LSR ID and start of global label space
l MPLS tunnel: source and sink boards, explicit boards, and ingress and egress labels
Procedure
Step 1 Set the basic attributes of MPLS.
Set the basic attributes LSR ID and Start of Global Label Space for each NE.
NE34 NE33
LSR ID: 130.0.0.2
NE32
NE31
NE11
NE21
Tunnel
1901
3-ISV3
1(RTNIF-1)
1901
1901
1 46.1.64.18
3
1901
4-ISV3
1(RTNIF-1)
1901
1901
3-ISV3
1(RTNIF-1)
1902
1902
1 46.1.64.22
46.1.64.17
130.0.0.6
130.0.0.2
3
1901
3-ISV3
1(RTNIF-1)
1902
1902
1
46.1.64.21
130.0.0.2
Board:4-ISV3-1 Board:3-ISV3-1
IP: 46.1.64.18/30 IP: 46.1.64.17/30
Incoming Lable:1801 Incoming Lable:1801
Outgoing Lable:1801 Outgoing Lable:1801
Tunnel
The configuration method is the same as that for the bidirectional MPLS tunnel between
NE32 and NE34.
----End
Data Preparation
Traffic carried on tunnels need to be classified based on the MPLS EXP field in packets. In
this example, the mapping in the default DiffServ domain is used for simple traffic
classification.
l Mapping in the default DiffServ domain:
CS7 7 –
CS6 6 –
AF4 4 –
AF1 1 –
Procedure
Step 1 Apply the mapping in the default DiffServ domain to target NNIs to implement and simple
traffic classification.
Each NE uses the mapping in the default DiffServ domain. The packet type for traffic
classification needs to be changed to mpls-exp for NNIs of All Tunnels.
Figure 10-44 Applying the mapping in the default DiffServ domain to NNIs
4 2
1 3
----End
Procedure
Step 1 Perform MPLS Ping tests to verify the connectivity of MPLS tunnels.
Initiate a ping test on the first node of a tunnel.
2
Right-click the target tunnel and choose
Ping Test from the shortcut menu.
Set Response Mode to Application
Control Channel and retain the 4
default values for the other
parameters. 3
NOTE
To verify the service availability at different packet lengths, you can set Packet Size to
128/256/512/1024/1280 bytes as desired.
After the verification, query the verification result of each MPLS tunnel. Packet Loss Ratio (%) of each
tunnel should be zero.
----End
L2 network BTS1
VLAN=4060
VL NE2 NE3
BSC NE1 A N=
40
90
NE4
MPLS Tunnel 2
Figure 10-47 shows information about the MPLS ports on the network. The VLAN sub-ports
of ports for carrying the MPLS tunnels on NE1, NE2, and NE4 are enabled so that the MPLS
tunnels can traverse the Layer 2 network.
RTN 950
VLAN=4060
VL NE2 NE3
NE1 AN
=4
09
0
RTN 950
RTN 950
NE5
3-ISU2-1 (to NE5)
MPLS Tunnel 1
MPLS Tunnel 2
Equipment type
Data Preparation
Figure 10-48 Data plan for microwave ports and Ethernet sub-ports
Board: 3-EM6T-1 Board: 4-EM6T-1
Virtual Interface: 1 Virtual Interface: 1
IP:46.1.64.6/30 IP:46.1.64.5/30 Board: 3-ISU2-1 Board: 3-ISU2-1
VLAN: 4060 VLAN: 4060 IP:46.1.64.2/30 IP:46.1.64.1/30
L2 network
VLAN=4060
NE1 VL NE2 NE3
AN
=4
0 90
Board: 3-EM6T-1
Virtual Interface: 2
NE4
IP:46.1.64.9/30
VLAN: 4090
Board: 4-EM6T-1 NE5
Virtual Interface: 1
IP:46.1.64.10/30 Board: 3-ISU2-1
VLAN: 4090 IP:46.1.64.13/30
Board: 3-ISU2-1
IP:46.1.64.14/30
Tunnel
Tunnel
Procedure
Step 1 Set microwave port attributes.
Basic attributes and Layer 3 attributes need to be configured for microwave ports between
NEs. A microwave port is taken as an example in the following figure.
6
4
----End
Data Preparation
l Basic MPLS attributes: LSR ID and start of global label space
l End-to-end MPLS tunnels with MPLS APS protection: source and sink boards and
explicit boards
Procedure
Step 1 Set the basic attributes of MPLS.
Set the basic attributes LSR ID and Start of Global Label Space for each NE.
NE4
NOTE
After Layer 2 links are searched out, you do not need to create fibers/cables.
L2 network
VLAN=4060
NE1 VL NE2 NE3
AN
=4
09
Board:L 3-EM6T-1 0
Virtual Interface: 2
IP: 46.1.64.9/30 NE4
Incoming Label: 1003
Outgoing Label: 1003Board: 4-EM6T-1
NE5
Virtual Interface: 1
IP: 46.1.64.10/30 Board: 3-ISU2-1
Incoming Label: 1003 IP: 46.1.64.13/30
Outgoing Label: 1003 Incoming Label: 1004
Outgoing Label: 1004 Board: 3-ISU2-1
IP: 46.1.64.14/30
Incoming Label: 1004
Tunnel Outgoing Label: 1004
Tunnel
2
Set the basic attributes.
5 4
Double-click an Double-click an
NE to set it as NE to set it as
NE(1) NE(2) NE(3)
the sink NE. the source NE.
6
The calculation result is displayed.
You can manually adjust the explicit
Select Auto-Calculate route. boards and configure labels.
NE(3) 3
NE(2)
NE(1) NE(3)
NE(2)
NE(1)
7
Labels can also be
automatically assigned.
– Configure constraints for the tunnels. If the tunnels that are automatically calculated
are not the planned tunnels, you can configure constraints for them manually.
NE(31)
2-EM6F-2(Port-2) 46.1.64.2
Right-click the explicit 46.1.64.
2-EM6F-1(Port-1)
node to display the 5
8 Select the explicit port.
shortcut menu. 9
10
NE(11) NE(21)
----End
Data Preparation
Traffic carried on tunnels need to be classified based on the MPLS EXP field in packets. In
this example, the mapping in the default DiffServ domain is used for simple traffic
classification.
l Mapping in the default DiffServ domain
CS7 7 –
CS6 6 –
AF4 4 –
AF1 1 –
l NNI: microwave port and Ethernet port (for an Ethernet subinterface, the mapping needs
to be applied to its host Ethernet port.)
Procedure
Step 1 Apply the mapping in the default DiffServ domain to target NNIs to implement and simple
traffic classification.
Each NE uses the mapping in the default DiffServ domain. The packet type for traffic
classification needs to be changed to mpls-exp for NNIs of All Tunnels.
Figure 10-55 Applying the mapping in the default DiffServ domain to NNIs
4 2
1 3
----End
Procedure
Step 1 Use the LSP Ping function in Diagnose > Test and Check to verify the connectivity of
MPLS tunnels.
6 7
NOTE
To verify the service availability at different packet lengths, you can set Packet Size to 128, 256, 512, 1024,
or 1280 bytes as desired.
After the verification, query the verification result of each MPLS tunnel. Packet Loss Ratio (%) of each
tunnel should be zero.
----End
Data Preparation
Figure 10-57 Data plan for microwave ports and Ethernet sub-ports
Board: 3-EM6T-1 Board: 4-EM6T-1
Virtual Interface: 1 Virtual Interface: 1
IP:46.1.64.6/30 IP:46.1.64.5/30 Board: 3-ISU2-1 Board: 3-ISU2-1
VLAN: 4060 VLAN: 4060 IP:46.1.64.2/30 IP:46.1.64.1/30
L2 network
VLAN=4060
NE1 VL NE2 NE3
AN
=4
0 90
Board: 3-EM6T-1
Virtual Interface: 2
NE4
IP:46.1.64.9/30
VLAN: 4090
Board: 4-EM6T-1 NE5
Virtual Interface: 1
IP:46.1.64.10/30 Board: 3-ISU2-1
VLAN: 4090 IP:46.1.64.13/30
Board: 3-ISU2-1
IP:46.1.64.14/30
Tunnel
Tunnel
Procedure
Step 1 Set microwave port attributes.
Basic attributes and Layer 3 attributes need to be configured for microwave ports between
NEs. A microwave port is taken as an example in the following figure.
6
4
----End
Data Preparation
l Basic MPLS attributes: LSR ID and start of global label space
l MPLS tunnel: source and sink boards, explicit boards, and ingress and egress labels
Procedure
Step 1 Set the basic attributes of MPLS.
Set the basic attributes LSR ID and Start of Global Label Space for each NE.
NE4
L2 network
VLAN=4060
NE1 VL NE2 NE3
AN
=4
09
Board:L 3-EM6T-1 0
Virtual Interface: 2
IP: 46.1.64.9/30 NE4
Incoming Label: 1003
Outgoing Label: 1003Board: 4-EM6T-1
NE5
Virtual Interface: 1
IP: 46.1.64.10/30 Board: 3-ISU2-1
Incoming Label: 1003 IP: 46.1.64.13/30
Outgoing Label: 1003 Incoming Label: 1004
Outgoing Label: 1004 Board: 3-ISU2-1
IP: 46.1.64.14/30
Incoming Label: 1004
Tunnel Outgoing Label: 1004
Tunnel
1001
3-ISU2
1(RTNIF-1)
1001
1001
1 46.1.64.2
130.0.0.1
3
1001
3-ISU2
1(RTNIF-1)
1001
1001
Virtual Ethernet
1(VEther-1)
1002
1002
1 46.1.64.6
46.1.64.1
130.0.0.3
130.0.0.1
3
1001
Virtual Ethernet
1(VEther-1)
1002
1002
1
46.1.64.5
130.0.0.3
----End
Data Preparation
Traffic carried on tunnels need to be classified based on the MPLS EXP field in packets. In
this example, the mapping in the default DiffServ domain is used for simple traffic
classification.
l Mapping in the default DiffServ domain
CS7 7 –
CS6 6 –
AF4 4 –
AF1 1 –
l NNI: microwave port and Ethernet port (for an Ethernet subinterface, the mapping needs
to be applied to its host Ethernet port.)
Procedure
Step 1 Apply the mapping in the default DiffServ domain to target NNIs to implement and simple
traffic classification.
Each NE uses the mapping in the default DiffServ domain. The packet type for traffic
classification needs to be changed to mpls-exp for NNIs of All Tunnels.
Figure 10-63 Applying the mapping in the default DiffServ domain to NNIs
4 2
1 3
----End
Procedure
Step 1 Perform MPLS Ping tests to verify the connectivity of MPLS tunnels.
2
Right-click the target tunnel and choose
Ping Test from the shortcut menu.
Set Response Mode to Application
Control Channel and retain the 4
default values for the other
parameters. 3
NOTE
To verify the service availability at different packet lengths, you can set Packet Size to
128/256/512/1024/1280 bytes as desired.
After the verification, query the verification result of each MPLS tunnel. Packet Loss Ratio (%) of each
tunnel should be zero.
----End
ML-PPP (2E1)
NE2 NE3
NE1 ML
BSC -PP
P(
4V
C1
2 )
NE4
MPLS Tunnel 1
RTN 950
MPLS Tunnel 2 3-ISU2-1 (to NE5) NE5 BTS2
1-CQ1-1-VC12:1~4 (to
RTN 950
NE1)
3-ISU2-1 (to NE4)
Data Preparation
Figure 10-66 Data plan for microwave ports and Ethernet sub-ports
Board: 2-ML1-1~2 Board: 1-ML1-1~2 Board: 3-ISU2-1 Board: 3-ISU2-1
MP Group2 IP: 46.1.64.6/30 MP Group1 IP: 46.1.64.5/30 IP: 46.1.64.2/30 IP: 46.1.64.1/30
TDM network
ML-PPP(2E1)
Tunnel
Tunnel
Procedure
Step 1 Set microwave port attributes.
Basic attributes and Layer 3 attributes need to be configured for microwave ports between
NEs. A microwave port is taken as an example in the following figure.
1
5
1
Select a board.
4
1
After the configuration, change Encapsulation Type to PPP and Port Level to Layer 3.
3. Configure the MP group.
3
Set the parameters. The tunnel needs to be
enabled. Sequence Number Type needs to
be set consistently for the first and last nodes.
1-CQ1
1-CQ1-1(Serial-1)
1-CQ1-1(Serial-2)
1-CQ1-1(Serial-3)
1-CQ1-1(Serial-4)
1
5
----End
Data Preparation
l Basic MPLS attributes: LSR ID and start of global label space
l End-to-end MPLS tunnels with MPLS APS protection: source and sink boards and
explicit boards
Procedure
Step 1 Set the basic attributes of MPLS.
Set the basic attributes LSR ID and Start of Global Label Space for each NE.
NE4
NOTE
After Layer 2 links are searched out, you do not need to create fibers/cables.
TDM network
ML-PPP(2E1)
Tunnel
2
Set the basic attributes.
5 4
Double-click an Double-click an
NE to set it as NE to set it as
NE(1) NE(2) NE(3)
the sink NE. the source NE.
6
The calculation result is displayed.
You can manually adjust the explicit
Select Auto-Calculate route. boards and configure labels.
NE(3) 3
NE(2)
NE(1) NE(3)
NE(2)
NE(1)
7
Labels can also be
automatically assigned.
– Configure constraints for the tunnels. If the tunnels that are automatically calculated
are not the planned tunnels, you can configure constraints for them manually.
NE(31)
2-EM6F-2(Port-2) 46.1.64.2
Right-click the explicit 46.1.64.
2-EM6F-1(Port-1)
node to display the 5
8 Select the explicit port.
shortcut menu. 9
10
NE(11) NE(21)
----End
Data Preparation
Traffic carried on tunnels need to be classified based on the MPLS EXP field in packets. In
this example, the mapping in the default DiffServ domain is used for simple traffic
classification.
l Mapping in the default DiffServ domain:
CS7 7 –
CS6 6 –
AF4 4 –
AF1 1 –
Procedure
Step 1 Apply the mapping in the default DiffServ domain to target NNIs to implement and simple
traffic classification.
Each NE uses the mapping in the default DiffServ domain. The packet type for traffic
classification needs to be changed to mpls-exp for NNIs of All Tunnels.
Figure 10-72 Applying the mapping in the default DiffServ domain to NNIs
4 2
1 3
----End
Procedure
Step 1 Use the LSP Ping function in Diagnose > Test and Check to verify the connectivity of
MPLS tunnels.
6 7
NOTE
To verify the service availability at different packet lengths, you can set Packet Size to 128, 256, 512, 1024,
or 1280 bytes as desired.
After the verification, query the verification result of each MPLS tunnel. Packet Loss Ratio (%) of each
tunnel should be zero.
----End
Data Preparation
Figure 10-74 Data plan for microwave ports and Ethernet sub-ports
Board: 2-ML1-1~2 Board: 1-ML1-1~2 Board: 3-ISU2-1 Board: 3-ISU2-1
MP Group2 IP: 46.1.64.6/30 MP Group1 IP: 46.1.64.5/30 IP: 46.1.64.2/30 IP: 46.1.64.1/30
TDM network
ML-PPP(2E1)
Tunnel
Tunnel
Procedure
Step 1 Set microwave port attributes.
Basic attributes and Layer 3 attributes need to be configured for microwave ports between
NEs. A microwave port is taken as an example in the following figure.
1
5
1
Select a board.
4
1
After the configuration, change Encapsulation Type to PPP and Port Level to Layer 3.
3. Configure the MP group.
3
Set the parameters. The tunnel needs to be
enabled. Sequence Number Type needs to
be set consistently for the first and last nodes.
1-CQ1
1-CQ1-1(Serial-1)
1-CQ1-1(Serial-2)
1-CQ1-1(Serial-3)
1-CQ1-1(Serial-4)
1
5
----End
Data Preparation
l Basic MPLS attributes: LSR ID and start of global label space
l MPLS tunnel: source and sink boards, explicit boards, and ingress and egress labels
Procedure
Step 1 Set the basic attributes of MPLS.
Set the basic attributes LSR ID and Start of Global Label Space for each NE.
NE4
TDM network
ML-PPP(2E1)
Tunnel
1001
3-ISU2
1(RTNIF-1)
1001
1001
1 46.1.64.2
130.0.0.1
3
1001
3-ISU2
1(RTNIF-1)
1001
1001
ML-PPP
1(MP-1)
1002
1002
1 46.1.64.6
46.1.64.1
130.0.0.3
130.0.0.1
3
1001
ML-PPP
2(MP-1)
1002
1002
1
46.1.64.5
130.0.0.3
----End
Data Preparation
Traffic carried on tunnels need to be classified based on the MPLS EXP field in packets. In
this example, the mapping in the default DiffServ domain is used for simple traffic
classification.
l Mapping in the default DiffServ domain:
CS7 7 –
CS6 6 –
AF4 4 –
AF1 1 –
Procedure
Step 1 Apply the mapping in the default DiffServ domain to target NNIs to implement and simple
traffic classification.
Each NE uses the mapping in the default DiffServ domain. The packet type for traffic
classification needs to be changed to mpls-exp for NNIs of All Tunnels.
Figure 10-79 Applying the mapping in the default DiffServ domain to NNIs
4 2
1 3
----End
Procedure
Step 1 Perform MPLS Ping tests to verify the connectivity of MPLS tunnels.
Initiate a ping test on the first node of a tunnel.
2
Right-click the target tunnel and choose
Ping Test from the shortcut menu.
Set Response Mode to Application
Control Channel and retain the 4
default values for the other
parameters. 3
NOTE
To verify the service availability at different packet lengths, you can set Packet Size to
128/256/512/1024/1280 bytes as desired.
After the verification, query the verification result of each MPLS tunnel. Packet Loss Ratio (%) of each
tunnel should be zero.
----End
ETH PWE3 services are available in E-Line services carried by PWs, E-Aggr services carried
by PWs, and E-LAN services (VPLS) carried by PWs.
In this example, a combination of PW-carried E-Line and E-LAN services is configured for
Ethernet service convergence.
11.9 Configuration Example (E-Aggr Services Carried by PWs)
This example assumes that MPLS tunnels have been configured.
Flowchart
Figure 11-1 Flowchart for configuring E-Line services carried by PWs in end-to-end mode
Required Start
Optional
Configure Ethernet ports.
Configure LAGs.
Configure a PW APS
protection group.
Configure QoS.
End
NOTE
For PWE3 services that have been configured on a per-NE basis, follow instructions in A.15.4 Searching for
MPLS Tunnels and PWE3 Services to synchronize the services to the network layer of the NMS. This
enables end-to-end management of the PWE3 services.
A.8.8.1 Setting Required if UNIs are Ethernet ports. Basic attributes include the port
the Basic mode, encapsulation type, and maximum frame length.
Attributes of
Ethernet Ports
A.8.8.3 Setting Required if UNIs are Ethernet ports. Layer 2 attributes of Ethernet ports
the Layer 2 define link-layer information, including TAG attributes and port
Attributes of attributes.
Ethernet Ports
A.8.8.5 Setting Required when you need to enable the port self-loop test function, the
the Advanced automatic loopback shutdown function, or the broadcast packet
Attributes of suppression function.
Ethernet Ports
A.8.9.1 Setting Required if UNIs are IF_ETH ports. Basic attributes of an IF_ETH port
the Basic specify the basic information, including the port mode and encapsulation
Attributes of mode.
IF_ETH Ports
A.8.9.2 Setting Required if UNIs are IF_ETH ports. Layer 2 attributes of the IF_ETH
the Layer 2 port specify link-layer information, including the TAG attribute and
Attributes of QinQ type domain.
IF_ETH Ports
A.9.2.1 Required if the LAG function needs to be used for an FE/GE port.
Creating a
LAG
NOTE
For an Ethernet link for which a LAG is configured, configure parameters only for the main port. The
following operations described in this section are also applicable to the main port only.
Operation Remarks
Configuring PW Protection
Normally, PW APS is configured to work with other equipment configured with MC-PW
APS, therefore achieving dual-homing protection. You can configure dual-homing services in
end-to-end mode on the NMS. For details, see the Configuration Guide of the equipment
where MC-PW APS is configured or the U2000 Online Help.
Configuring QoS
For details about the QoS configuration procedure, seeConfiguration Process (QoS/HQoS).
Operation Remarks
Flowchart
Required Start
Optional
Configure Ethernet ports.
Configure LAGs.
Configure a PW APS
protection group.
Configure QoS.
End
A.8.8.1 Setting Required if UNIs are Ethernet ports. Basic attributes include the port
the Basic mode, encapsulation type, and maximum frame length.
Attributes of
Ethernet Ports
A.8.8.3 Setting Required if UNIs are Ethernet ports. Layer 2 attributes of Ethernet ports
the Layer 2 define link-layer information, including TAG attributes and port
Attributes of attributes.
Ethernet Ports
A.8.8.5 Setting Required when you need to enable the port self-loop test function, the
the Advanced automatic loopback shutdown function, or the broadcast packet
Attributes of suppression function.
Ethernet Ports
A.8.9.1 Setting Required if UNIs are IF_ETH ports. Basic attributes of an IF_ETH port
the Basic specify the basic information, including the port mode and encapsulation
Attributes of mode.
IF_ETH Ports
A.8.9.2 Setting Required if UNIs are IF_ETH ports. Layer 2 attributes of the IF_ETH
the Layer 2 port specify link-layer information, including the TAG attribute and
Attributes of QinQ type domain.
IF_ETH Ports
A.8.9.4 Setting Required when you need to enable the port self-loop test function, the
the Advanced automatic loopback shutdown function, or the broadcast packet
Attributes of suppression function.
IF_ETH Ports
Operation Remarks
A.9.2.1 Required if the LAG function needs to be used for an FE/GE port.
Creating a
LAG
NOTE
For an Ethernet link for which a LAG is configured, configure parameters only for the main port. The
following operations described in this section are also applicable to the main port only.
Operation Remarks
A.9.3.21 Optional.
Configuring Perform this operation to change the T-PID value of the S-VLAN tag
Global Attributes carried in PW-carried QinQ services.
of VPLS Services
Configuring PW Protection
For details about how to configure PW protection, see Configuration Procedure (PW APS) in
PW APS/FPS of the Feature Description.
Configuring QoS
For details about the QoS configuration procedure, seeConfiguration Process (QoS/HQoS).
Flowchart
Optional
Configure Ethernet ports.
Configure LAGs.
Configure a PW APS
protection group.
Configure QoS.
End
Operation Remarks
A.8.8.1 Setting Required if UNIs are Ethernet ports. Basic attributes include the port
the Basic mode, encapsulation type, and maximum frame length.
Attributes of
Ethernet Ports
A.8.8.3 Setting Required if UNIs are Ethernet ports. Layer 2 attributes of Ethernet ports
the Layer 2 define link-layer information, including TAG attributes and port
Attributes of attributes.
Ethernet Ports
Operation Remarks
A.8.8.5 Setting Required when you need to enable the port self-loop test function, the
the Advanced automatic loopback shutdown function, or the broadcast packet
Attributes of suppression function.
Ethernet Ports
A.8.9.1 Setting Required if UNIs are IF_ETH ports. Basic attributes of an IF_ETH port
the Basic specify the basic information, including the port mode and encapsulation
Attributes of mode.
IF_ETH Ports
A.8.9.2 Setting Required if UNIs are IF_ETH ports. Layer 2 attributes of the IF_ETH
the Layer 2 port specify link-layer information, including the TAG attribute and
Attributes of QinQ type domain.
IF_ETH Ports
A.9.2.1 Required if the LAG function needs to be used for an FE/GE port.
Creating a
LAG
NOTE
For an Ethernet link for which a LAG is configured, configure parameters only for the main port. The
following operations described in this section are also applicable to the main port only.
A.9.3.9 Required.
Configuring
UNI-NNI E-
Line Services
(Carried by
PWs)(U2000)
or A.9.3.10
Configuring
UNI-NNI E-
Line Services
(Carried by
PWs)(Web
LCT)
Configuring PW Protection
For details about how to configure PW protection, see Configuration Procedure (PW APS) in
PW APS/FPS of the Feature Description.
Configuring QoS
For details about the QoS configuration procedure, seeConfiguration Process (QoS/HQoS).
Flowchart
Start
Required
Configure LAGs.
Configure a PW APS
protection group.
Configure QoS.
End
A.8.8.1 Setting Required if UNIs are Ethernet ports. Basic attributes include the port
the Basic mode, encapsulation type, and maximum frame length.
Attributes of
Ethernet Ports
A.8.8.3 Setting Required if UNIs are Ethernet ports. Layer 2 attributes of Ethernet ports
the Layer 2 define link-layer information, including TAG attributes and port
Attributes of attributes.
Ethernet Ports
A.8.8.5 Setting Required when you need to enable the port self-loop test function, the
the Advanced automatic loopback shutdown function, or the broadcast packet
Attributes of suppression function.
Ethernet Ports
A.8.9.1 Setting Required if UNIs are IF_ETH ports. Basic attributes of an IF_ETH port
the Basic specify the basic information, including the port mode and encapsulation
Attributes of mode.
IF_ETH Ports
A.8.9.2 Setting Required if UNIs are IF_ETH ports. Layer 2 attributes of the IF_ETH
the Layer 2 port specify link-layer information, including the TAG attribute and
Attributes of QinQ type domain.
IF_ETH Ports
A.9.2.1 Required if the LAG function needs to be used for an FE/GE port.
Creating a
LAG
NOTE
For an Ethernet link for which a LAG is configured, configure parameters only for the main port. The
following operations described in this section are also applicable to the main port only.
A.9.3.11 Required.
Creating E- NOTE
AGGR On a packet switched network (PSN), if Ethernet services carried on PEs are end-
Services to-end services from one UNI to a PW and require no VLAN ID swapping,
configure the Ethernet services as E-Line services carried by PWs on a per-NE
basis.
Configuring PW Protection
For details about how to configure PW protection, see Configuration Procedure (PW APS) in
PW APS/FPS of the Feature Description.
Configuring QoS
For details about the QoS configuration procedure, seeConfiguration Process (QoS/HQoS).
groups (LAGs), configuring QoS policies, configuring PW protection, and verifying the E-
LAN configurations.
Flowchart
Figure 11-5 Flowchart for configuring E-LAN services carried by PWs on a Per-NE basis
Required Start
Optional
Configure Ethernet ports.
Configure LAGs.
Configure a PW APS
protection group.
Configure QoS.
End
A.8.8.1 Setting Required if UNIs are Ethernet ports. Basic attributes include the port
the Basic mode, encapsulation type, and maximum frame length.
Attributes of
Ethernet Ports
A.8.8.3 Setting Required if UNIs are Ethernet ports. Layer 2 attributes of Ethernet ports
the Layer 2 define link-layer information, including TAG attributes and port
Attributes of attributes.
Ethernet Ports
A.8.8.5 Setting Required when you need to enable the port self-loop test function, the
the Advanced automatic loopback shutdown function, or the broadcast packet
Attributes of suppression function.
Ethernet Ports
A.8.9.1 Setting Required if UNIs are IF_ETH ports. Basic attributes of an IF_ETH port
the Basic specify the basic information, including the port mode and encapsulation
Attributes of mode.
IF_ETH Ports
A.8.9.2 Setting Required if UNIs are IF_ETH ports. Layer 2 attributes of the IF_ETH
the Layer 2 port specify link-layer information, including the TAG attribute and
Attributes of QinQ type domain.
IF_ETH Ports
A.9.2.1 Required if the LAG function needs to be used for an FE/GE port.
Creating a
LAG
NOTE
For an Ethernet link for which a LAG is configured, configure parameters only for the main port. The
following operations described in this section are also applicable to the main port only.
Operation Remarks
A.9.3.21 Optional.
Configuring Perform this operation to change the T-PID value of the S-VLAN tag
Global carried in PW-carried QinQ services.
Attributes of
VPLS Services
A.9.3.20 Required.
Configuring NOTE
PW-Carried On a packet switched network (PSN), if Ethernet services carried on PEs are end-
E-LAN to-end services from one UNI to a PW, configure the Ethernet services as E-Line
Services services carried by PWs on a per-NE basis.
(U2000)
Configuring PW Protection
For details about how to configure PW protection, see Configuration Procedure (PW APS) in
PW APS/FPS of the Feature Description.
Configuring QoS
For details about the QoS configuration procedure, seeConfiguration Process (QoS/HQoS).
Operation Remarks
Figure 11-6 Networking diagram (E-Line services carried by PWs, a simple example)
NE34
BTS33 NE33
FE
BTS31
R4
R4
Working tunnel
(ID=1601)
GE NE32 GE
RTN 980
Hybrid microwave chain
NE11 NE31
network RTN 950
GE
NE21 GE
RNC
Table 11-26 provides the UNI information about the E-Line services carried by PWs.
Procedure
Step 1 Configure the interface attributes.
----End
Data Preparation
Figure 11-7 Data plan for PWE3 E-Line services between NE31 and NE32
PW ID:303
PW Incoming Label:40
UNI:2-EG4-3 PW Outgoing Label:40
VLAN:310 Tunnel ID:1601
BTS31 PW ID:303
PW Incoming Label:40
PW Outgoing Label:40
Tunnel ID:1601
GE NE32 GE
UNI:1-EG4-3
VLAN:310
NE31
NE11
GE RNC
NE21 GE
Tunnel
Ethernet services (VLAN ID: 310) from BTS31 are received by NE32 and need to be
transmitted to the RNC. A bidirectional tunnel (ID: 1601) with protection is available between
NE32 and NE31. Ethernet services carried by PWs connected to BTSs are transparently
transmitted over the tunnel.
Procedure
Step 1 Configure UNIs.
NE(32) NE(31)
8
NE(31) NE(32)
6
9
10
7
11
12
NE(32) NE(31)
NE(31)-1-EG4-3(Port-3)
NE(32)-2-EG4-3(Port-3) 15
16
14
Configure a PW, and select the forward
NE(31) NE(32) and reverse tunnels.
A PW label can be automatically allocated
or manually specified.
17
----End
Data Preparation
On UNIs, traffic carried on tunnels need to be classified based on the C-VLAN priority field
in packets. On NNIs, traffic carried on tunnels need to be classified based on the MPLS EXP
field in packets. In this example, the mapping in the default DiffServ domain is used for
simple traffic classification.
l Mapping in the default DiffServ domain
CS7 7 7 –
CS6 6 6 –
EF 5 5 Real-time voice
service and
signaling service
AF4 4 4 –
AF1 1 1 –
BE 0 0 HSDPA data
services
Procedure
Step 1 Apply the mapping in the default DiffServ domain to target UNIs to implement simple traffic
classification.
Each NE uses the mapping in the default DiffServ domain, performing traffic classification
based on the C-VLAN priority field in the packets. The mapping is applied over UNIs and the
UNI port type needs to be changed to CVLAN.
Figure 11-8 Applying the mapping in the default DiffServ domain to UNIs
1 3
Step 2 Apply the mapping in the default DiffServ domain to target NNIs to implement simple traffic
classification.
Each NE uses the mapping in the default DiffServ domain, performing traffic classification
based on the Tunnel EXP field in the packets. The mapping is applied over NNIs and the NNI
port type needs to be changed to mpls-exp. For details, refer to tunnel QoS configurations.
----End
Procedure
Step 1 Use the VCCV Ping function in Test and Check to verify the connectivity of PWs.
4
Select the application control
channel.
NOTE
To verify the service availability at different packet lengths, you can set Packet Size to 128, 256, 512, 1024,
or 1280 bytes as desired.
After the verification, view the detailed results to check whether the number of received packets and the
number of transmitted packets are the same.
If a VCCV ping test result shows that the PW is unavailable, perform an LSP ping test to check the
connectivity of the MPLS tunnel.
----End
Procedure
Step 1 Set Ethernet port attributes for UNIs on NE31 and NE32.
Set Encapsulation Type to 802.1Q, set Tag to Tag Aware, and set Max Frame
Length(bytes) based on live network conditions. UNI configuration on NE31 is used as an
example.
----End
Procedure
Step 1 Configure the interface attributes.
----End
Data Preparation
Figure 11-9 Data plan for PWE3 E-Line services between NE31 and NE32
PW ID:303
PW Incoming Label:40
UNI:2-EG4-3 PW Outgoing Label:40
VLAN:310 Tunnel ID:1601
BTS31
PW ID:303
PW Incoming Label:40
PW Outgoing Label:40
Tunnel ID:1601
GE NE32 GE
UNI:1-EG4-3
VLAN:310
NE31
NE11
GE RNC
NE21 GE
Tunnel
Ethernet services (VLAN ID: 310) from BTS31 are received by NE32 and need to be
transmitted to the RNC. A bidirectional tunnel (ID: 1601) with protection is available between
NE32 and NE31. Ethernet services carried by PWs connected to BTSs are transparently
transmitted over the tunnel.
Procedure
Step 1 Configure PWE3 E-Line services on NE31.
4
1 8
9
Step 2 Configure PWE3 E-Line services on NE32 by referring to the service configuration on NE31.
----End
Data Preparation
On UNIs, traffic carried on tunnels need to be classified based on the C-VLAN priority field
in packets. On NNIs, traffic carried on tunnels need to be classified based on the MPLS EXP
field in packets. In this example, the mapping in the default DiffServ domain is used for
simple traffic classification.
l Mapping in the default DiffServ domain
CS7 7 7 –
CS6 6 6 –
EF 5 5 Real-time voice
service and
signaling service
AF4 4 4 –
AF1 1 1 –
BE 0 0 HSDPA data
services
Procedure
Step 1 Apply the mapping in the default DiffServ domain to target UNIs to implement simple traffic
classification.
Each NE uses the mapping in the default DiffServ domain, performing traffic classification
based on the C-VLAN priority field in the packets. The mapping is applied over UNIs and the
UNI port type needs to be changed to CVLAN.
Figure 11-10 Applying the mapping in the default DiffServ domain to UNIs
1 3
Step 2 Apply the mapping in the default DiffServ domain to target NNIs to implement simple traffic
classification.
Each NE uses the mapping in the default DiffServ domain, performing traffic classification
based on the Tunnel EXP field in the packets. The mapping is applied over NNIs and the NNI
port type needs to be changed to mpls-exp. For details, refer to tunnel QoS configurations.
----End
Procedure
Step 1 Perform ping tests at the first and last nodes of the PW to check the connectivity of the PW.
3
Select the application
control channel.
Select the PW to be checked, right-click,
and choose Ping Test from the drop-
down menu.
2
When the service is available, the packet loss ratio should be zero.
----End
l The information about the tunnels between NE34 and NE31 is as follows:
– A bidirectional tunnel (ID: 1901) with no protection is available between NE34 and
NE32.
– A bidirectional tunnel (ID: 1601) with protection is available between NE32 and
NE31.
– Ethernet services from BTSs are carried by PWs on the two tunnels, and PW labels
and tunnel labels are swapped on NE32.
l Ethernet services from all BTSs have been configured with VLAN priorities based on
the service types (real-time voice services, HSDPA real-time services, R99 non-real-time
services, and HSDPA data services). The transmission network provides end-to-end QoS
control based on the VLAN priorities.
l NE31's GE ports, which are connected to the RNC, need to be protected by a link
aggregation group (LAG).
Figure 11-11 Networking diagram (E-Line services carried by PWs, configured for
transmitting Ethernet services aggregated converged from a Hybrid microwave network)
NE34
BTS33 RTN 905
NE33
BTS31
R4
Tunnel
(ID=1901)
R4
FE Working tunnel
GE (ID=1601)
NE32 GE
RTN 980
Hybrid microwave chain NE31
network NE11 RTN 950
GE
NE21 GE RNC
Table 11-29 provides the UNI information about the E-Line services carried by PWs.
Procedure
Step 1 Configure the interface attributes.
----End
Data Preparation
Figure 11-12 Data plan for PWE3 E-Line services between NE31 and NE34
PW ID:305
PW Incoming Label:20
PW Outgoing Label:20
NE34 Tunnel ID:1901
UNI:7-EG6-1 NE33
BTS33 VLAN:330 PW ID:305
PW Incoming Label:20
PW Outgoing Label:20
Tunnel ID:1901
R4 PW ID:304
PW Incoming Label:30
PW Outgoing Label:30
Tunnel ID:1601
PW ID:304
PW Incoming Label:30
GE PW Outgoing Label:30
Tunnel ID:1601
NE32 GE
NE31
NE11
GE UNI:4-EG4-3
NE21 GE RNC
VLAN:330
Ethernet services (VLAN ID: 330) from BTS33 are received by NE34 and need to be
transmitted to the RNC. A bidirectional tunnel (ID: 1901) with no protection is available
between NE34 and NE32. A bidirectional tunnel (ID: 1601) with protection is available
between NE32 and NE31. Ethernet services from BTSs are carried by PWs on the two
tunnels, and PW labels and tunnel labels are swapped on NE32.
Procedure
Step 1 Configure UNIs.
13
Double-click the NE to make it the sink
node. You can configure UNIs by
referring the configuration procedure
applied to the source node.
NE(31)
8
NE(31) NE(32) NE31_NE32
NE(31)
NE(32) NE(34)
NE(32) NE32_NE34
6 9
NE31_NE32
NE32_NE34
10
7 11
12
Step 2 Configure the MS-PW between NE31 and NE34 in end-to-end mode.
NE(34)
NE(32)
16
NE(31)-1-EG4-3(Port-3)
NE(32)
NE(34)-7-EG6-1(Port-1) 17
15
NE(31) NE(32) NE31_NE32 Select tunnel segments.
PW labels can be automatically allocated
NE(32) NE(34) NE32_NE34 or manually specified.
NE31_NE32
NE32_NE34
18
----End
Data Preparation
On UNIs, traffic carried on tunnels need to be classified based on the C-VLAN priority field
in packets. On NNIs, traffic carried on tunnels need to be classified based on the MPLS EXP
field in packets. In this example, the mapping in the default DiffServ domain is used for
simple traffic classification.
l Mapping in the default DiffServ domain
CS7 7 7 –
CS6 6 6 –
EF 5 5 Real-time voice
service and
signaling service
AF4 4 4 –
AF1 1 1 –
BE 0 0 HSDPA data
services
Procedure
Step 1 Apply the mapping in the default DiffServ domain to target UNIs to implement simple traffic
classification.
Each NE uses the mapping in the default DiffServ domain, performing traffic classification
based on the C-VLAN priority field in the packets. The mapping is applied over UNIs and the
UNI port type needs to be changed to CVLAN.
Figure 11-13 Applying the mapping in the default DiffServ domain to UNIs
1 3
Step 2 Apply the mapping in the default DiffServ domain to target NNIs to implement simple traffic
classification.
Each NE uses the mapping in the default DiffServ domain, performing traffic classification
based on the Tunnel EXP field in the packets. The mapping is applied over NNIs and the NNI
port type needs to be changed to mpls-exp. For details, refer to tunnel QoS configurations.
----End
Procedure
Step 1 Use the VCCV Ping function in Test and Check to verify the connectivity of PWs.
4
Select the application control
channel.
NOTE
To verify the service availability at different packet lengths, you can set Packet Size to 128, 256, 512, 1024,
or 1280 bytes as desired.
After the verification, view the detailed results to check whether the number of received packets and the
number of transmitted packets are the same.
If a VCCV ping test result shows that the PW is unavailable, perform an LSP ping test to check the
connectivity of the MPLS tunnel.
----End
Procedure
Step 1 Set Ethernet port attributes for UNIs on NE31 and NE34.
Set Encapsulation Type to 802.1Q, set Tag to Tag Aware, and set Max Frame
Length(bytes) based on live network conditions. UNI configuration on NE31 is used as an
example.
----End
Procedure
Step 1 Configure the interface attributes.
----End
Data Preparation
Figure 11-14 Data plan for PWE3 E-Line services between NE31 and NE34
PW ID:305
PW Incoming Label:20
PW Outgoing Label:20
NE34 Tunnel ID:1901
UNI:7-EG6-1 NE33
BTS33 VLAN:330 PW ID:305
PW Incoming Label:20
PW Outgoing Label:20
Tunnel ID:1901
R4 PW ID:304
PW Incoming Label:30
PW Outgoing Label:30
Tunnel ID:1601
PW ID:304
PW Incoming Label:30
GE PW Outgoing Label:30
Tunnel ID:1601
NE32 GE
NE31
NE11
GE UNI:4-EG4-3
NE21 GE RNC
VLAN:330
Ethernet services (VLAN ID: 330) from BTS33 are received by NE34 and need to be
transmitted to the RNC. A bidirectional tunnel (ID: 1901) with no protection is available
between NE34 and NE32. A bidirectional tunnel (ID: 1601) with protection is available
between NE32 and NE31. Ethernet services from BTSs are carried by PWs on the two
tunnels, and PW labels and tunnel labels are swapped on NE32.
Procedure
Step 1 Configure PWE3 E-Line services on NE34.
304
BTS34_RNC
4
1 8
9
6
304
BTS34_RNC
330 7
Step 2 Configure PWE3 E-Line services on NE31 by referring to service configurations on NE34.
1601 1901
1601 1901
Step 4 Configure UNI-NNI E-Line services carried by PWs. For details, see A.9.3.9 Configuring
UNI-NNI E-Line Services (Carried by PWs)(U2000).
----End
Data Preparation
On UNIs, traffic carried on tunnels need to be classified based on the C-VLAN priority field
in packets. On NNIs, traffic carried on tunnels need to be classified based on the MPLS EXP
field in packets. In this example, the mapping in the default DiffServ domain is used for
simple traffic classification.
l Mapping in the default DiffServ domain
CS7 7 7 –
CS6 6 6 –
EF 5 5 Real-time voice
service and
signaling service
AF4 4 4 –
AF1 1 1 –
BE 0 0 HSDPA data
services
Procedure
Step 1 Apply the mapping in the default DiffServ domain to target UNIs to implement simple traffic
classification.
Each NE uses the mapping in the default DiffServ domain, performing traffic classification
based on the C-VLAN priority field in the packets. The mapping is applied over UNIs and the
UNI port type needs to be changed to CVLAN.
Figure 11-15 Applying the mapping in the default DiffServ domain to UNIs
1 3
Step 2 Apply the mapping in the default DiffServ domain to target NNIs to implement simple traffic
classification.
Each NE uses the mapping in the default DiffServ domain, performing traffic classification
based on the Tunnel EXP field in the packets. The mapping is applied over NNIs and the NNI
port type needs to be changed to mpls-exp. For details, refer to tunnel QoS configurations.
----End
Procedure
Step 1 Perform ping tests at the first and last nodes of the PW to check the connectivity of the PW.
3
Select the application
control channel.
Select the PW to be checked, right-click,
and choose Ping Test from the drop-
down menu.
2
When the service is available, the packet loss ratio should be zero.
----End
Figure 11-16 Networking diagram (hybrid configuration of E-Line and E-LAN services
carried by PWs)
Working tunnel
(ID=1501)
NNI UNI
BTS11
NE32
VLAN 100
GE
NE31
NE11 RTN 950
RTN 980 NE21
R4 E-Line RTN 980 VPLS RNC
E-Line
Working tunnel
(ID=1701)
R4
BTS21
VLAN 100
Table 11-32 provides the information about ports of E-Line and E-LAN services carried by
PWs.
Procedure
Step 1 Set Ethernet port attributes for UNIs on NE31, NE11, and NE21.
Set Encapsulation Type to 802.1Q, set Tag to Tag Aware, and set Max Frame
Length(bytes) based on live network conditions. UNI configuration on NE31 is used as an
example.
----End
Data Preparation
Figure 11-17 Data plan for E-Line and E-LAN services carried by PWs
VSI ID:100
PW ID:301,302
PW Incoming Lable:60,50
PW Outgoing Lable:60,50 UNI:1-EG4-3
PW ID:301 Tunnel ID:1501,1701 VLAN:100
PW Incoming Lable:60
BTS11 PW Outgoing Lable:60
Tunnel ID:1501
NNI UNI
VLAN 100 NE32
NE31
NE11
R4
E-Line NE21 VPLS
UNI:2-EG4-3 RNC
VLAN:100
E-Line
PW ID:302
UNI:1-EG4-3 PW Incoming Lable:50
R4 VLAN:100 PW Outgoing Lable:50
Tunnel ID:1701
BTS21
VLAN 100
Tunnel (ID=1501)
Tunnel (ID=1701)
l Ethernet services (VLAN ID: 100) from BTS11 are received by NE11 and need to be
transmitted to the RNC. A bidirectional tunnel (ID: 1501) with protection is available
between NE11 and NE31.
l Ethernet services (VLAN ID: 100) from BTS21 are received by NE21 and need to be
transmitted to the RNC. A bidirectional tunnel (ID: 1701) with protection is available
between NE21 and NE31.
l NE31 functions as a VPLS node, converging services carried by PWs from NE11 and
NE21.
Procedure
Step 1 Configure hybrid E-Line services and E-LAN services carried by PWs in end-to-end mode.
Figure 11-18 Configuring hybrid E-Line services and E-LAN services carried by PWs in end-
to-end mode
NOTE
For OptiX RTN 950A, OptiX RTN 910A, OptiX RTN 905 or OptiX RTN 950 that uses a CSHU/CSHUA
board, MAC Address Learning Mode can be set to IVL.
----End
Data Preparation
On UNIs, traffic carried on tunnels need to be classified based on the C-VLAN priority field
in packets. On NNIs, traffic carried on tunnels need to be classified based on the MPLS EXP
field in packets. In this example, the mapping in the default DiffServ domain is used for
simple traffic classification.
l Mapping in the default DiffServ domain
CS7 7 7 –
CS6 6 6 –
EF 5 5 Real-time voice
service and
signaling service
AF4 4 4 –
AF1 1 1 –
BE 0 0 HSDPA data
services
Procedure
Step 1 Apply the mapping in the default DiffServ domain to target UNIs to implement simple traffic
classification.
Each NE uses the mapping in the default DiffServ domain, performing traffic classification
based on the C-VLAN priority field in the packets. The mapping is applied over UNIs and the
UNI port type needs to be changed to CVLAN.
Figure 11-20 Applying the mapping in the default DiffServ domain to UNIs
1 3
Step 2 Apply the mapping in the default DiffServ domain to target NNIs to implement simple traffic
classification.
Each NE uses the mapping in the default DiffServ domain, performing traffic classification
based on the Tunnel EXP field in the packets. The mapping is applied over NNIs and the NNI
port type needs to be changed to mpls-exp. For details, refer to tunnel QoS configurations.
----End
Procedure
Step 1 Use the VCCV Ping function in Test and Check to verify the connectivity of PWs.
4
Select the application control
channel.
NOTE
To verify the service availability at different packet lengths, you can set Packet Size to 128, 256, 512, 1024,
or 1280 bytes as desired.
After the verification, view the detailed results to check whether the number of received packets and the
number of transmitted packets are the same.
If a VCCV ping test result shows that the PW is unavailable, perform an LSP ping test to check the
connectivity of the MPLS tunnel.
----End
Procedure
Step 1 Set Ethernet port attributes for UNIs on NE31, NE11, and NE21.
Set Encapsulation Type to 802.1Q, set Tag to Tag Aware, and set Max Frame
Length(bytes) based on live network conditions. UNI configuration on NE31 is used as an
example.
----End
Data Preparation
Figure 11-21 Data plan for E-Line and E-LAN services carried by PWs
VSI ID:100
PW ID:301,302
PW Incoming Lable:60,50
PW Outgoing Lable:60,50 UNI:1-EG4-3
PW ID:301 Tunnel ID:1501,1701 VLAN:100
PW Incoming Lable:60
BTS11 PW Outgoing Lable:60
Tunnel ID:1501
NNI UNI
VLAN 100 NE32
NE31
NE11
R4
E-Line NE21 VPLS
UNI:2-EG4-3 RNC
VLAN:100
E-Line
PW ID:302
UNI:1-EG4-3 PW Incoming Lable:50
R4 VLAN:100 PW Outgoing Lable:50
Tunnel ID:1701
BTS21
VLAN 100
Tunnel (ID=1501)
Tunnel (ID=1701)
l Ethernet services (VLAN ID: 100) from BTS11 are received by NE11 and need to be
transmitted to the RNC. A bidirectional tunnel (ID: 1501) with protection is available
between NE11 and NE31.
l Ethernet services (VLAN ID: 100) from BTS21 are received by NE21 and need to be
transmitted to the RNC. A bidirectional tunnel (ID: 1701) with protection is available
between NE21 and NE31.
l NE31 functions as a VPLS node, converging services carried by PWs from NE11 and
NE21.
Procedure
Step 1 Configure PWE3 E-Line services on NE21.
302
BTS21_RNC
4
1 8
9
6
302
BTS21_RNC
100 7
Step 2 Configure PWE3 E-Line services on NE11 by referring to service configurations on NE21.
NOTE
For OptiX RTN 950A, OptiX RTN 910A, OptiX RTN 905 or OptiX RTN 950 that uses a CSHU/
CSHUA board, MAC Address Learning Mode can be set to IVL.
NOTE
For OptiX RTN 950 using CSHU/CSHUA boards and OptiX RTN 950A, the total number of VLANs
configured for Ethernet services must not exceed 1024. To avoid this restriction, do as follows:
1. Retain VLANs/CVLAN of some ports to null.
2. Set VLAN Filtering Table to the desired VLANs for the ports.
In this case, the VLANs configured in VLAN Filtering Table will not be counted in the VLANs
configured for Ethernet services. However, theses ports cannot participate in other Ethernet services.
The number of VLANs connected to a V-UNI is restricted when VPLS services are configured on
OptiX RTN 980and OptiX RTN 950 using CSH boards. Users can use the preceding method to break
through this restriction or decrease the number of V-UNIs supported by an NE to increase the number
of VLANs that can be connected to a V-UNI.
2. Configure services carried by PWs to NE11 on the NNI side.
13
10 14
Configure a PW-carried
service to NE11.
12
1501
1501
15
11
18
19
Configure a PW-carried
service on NE21.
17
1701
1701
20
16
23
25
24
26
21
22
27
----End
Data Preparation
On UNIs, traffic carried on tunnels need to be classified based on the C-VLAN priority field
in packets. On NNIs, traffic carried on tunnels need to be classified based on the MPLS EXP
field in packets. In this example, the mapping in the default DiffServ domain is used for
simple traffic classification.
l Mapping in the default DiffServ domain
CS7 7 7 –
CS6 6 6 –
EF 5 5 Real-time voice
service and
signaling service
AF4 4 4 –
AF1 1 1 –
BE 0 0 HSDPA data
services
Procedure
Step 1 Apply the mapping in the default DiffServ domain to target UNIs to implement simple traffic
classification.
Each NE uses the mapping in the default DiffServ domain, performing traffic classification
based on the C-VLAN priority field in the packets. The mapping is applied over UNIs and the
UNI port type needs to be changed to CVLAN.
Figure 11-22 Applying the mapping in the default DiffServ domain to UNIs
1 3
Step 2 Apply the mapping in the default DiffServ domain to target NNIs to implement simple traffic
classification.
Each NE uses the mapping in the default DiffServ domain, performing traffic classification
based on the Tunnel EXP field in the packets. The mapping is applied over NNIs and the NNI
port type needs to be changed to mpls-exp. For details, refer to tunnel QoS configurations.
----End
Procedure
Step 1 Perform ping tests at the first and last nodes of the PW to check the connectivity of the PW.
3
Select the application
control channel.
Select the PW to be checked, right-click,
and choose Ping Test from the drop-
down menu.
2
When the service is available, the packet loss ratio should be zero.
----End
Ethernet services from BTSs (with conflicting VLAN IDs) need to be converged to an RNC
through PWs based on MPLS tunnel plan and configuration. The specific service
requirements are as follows:
l Ethernet services from BTS11, BTS12, and BTS13, which respectively carry VLAN ID
100, VLAN ID 110, and VLAN ID 120, need to be transmitted to NE11 through a
Hybrid microwave chain network and then to the RNC. A bidirectional tunnel (ID: 1501)
with protection is available between NE11 and NE31. Ethernet services carried by PWs
from BTS11, BTS12, and BTS13 are transparently transmitted over the tunnel.
l Ethernet services from BTS21, BTS22, and BTS23, which respectively carry VLAN ID
100, VLAN ID 110, and VLAN ID 120, need to be transmitted to NE21 through a
Hybrid microwave ring network and then to the RNC by means of VLAN forwarding. A
bidirectional tunnel (ID: 1701) with protection is available between NE21 and NE31.
Ethernet services carried by PWs from BTS21, BTS22, and BTS23 are transparently
transmitted over the tunnel.
l Ethernet services at all preceding BTSs have already been configured with
corresponding VLAN priorities based on service types (real-time voice services, HSDPA
real-time services, R99 non-real-time services, and HSDPA data services), and the
transmission network is required to provide end-to-end QoS control based on the VLAN
priorities.
l NE31's GE ports, which are connected to the RNC, need to be protected by a link
aggregation group (LAG).
NNI UNI
R4 NE32
RTN 980 GE
Hybrid microwave chain NE31
network NE11 RTN 950
RTN 980 NE21
E-Line RTN 980 E-Aggr RNC
R4
E-Line Working tunnel
BTS12
VLAN 110 (ID=1701)
Hybrid microwave ring
R4
network
BTS13
VLAN 120 R4
1 BTS21
VLAN 100
R4
R4
2 BTS22
3 BTS23
VLAN 110
VLAN 120
1 2 3 VLAN IDs conflict.
Table 11-35 provides the port information about the E-Line and E-Aggr services carried by
PWs.
Procedure
Step 1 Set Ethernet port attributes for UNIs on NE31, NE11, and NE21.
Set Encapsulation Type to 802.1Q, set Tag to Tag Aware, and set Max Frame
Length(bytes) based on live network conditions. UNI configuration on NE31 is used as an
example.
----End
Data Preparation
NNI UNI
R4 NE32
GE
Hybrid microwave chain NE31
network NE11
NE21
E-Aggr RNC
R4
Hybrid microwave ring
BTS12
network
VLAN 110
UNI NNI
R4 PW ID:302
R4 UNI:1-EG4-3
BTS13 PW Incoming Label:50
VLAN:100,110,120
VLAN 120 BTS21 PW Outgoing Label:50
VLAN 100 Tunnel ID:1701
R4
R4
BTS22
VLAN 110 BTS23
VLAN 120
Tunnel (ID=1501)
Tunnel (ID=1701)
l Ethernet services from BTS11, BTS12, and BTS13, which respectively carry VLAN ID
100, VLAN ID 110, and VLAN ID 120, need to be transmitted to NE11 through a
Hybrid microwave chain network and then to the RNC. A bidirectional tunnel (ID: 1501)
with protection is available between NE11 and NE31. Ethernet services carried by PWs
from BTS11, BTS12, and BTS13 are transparently transmitted over the tunnel.
l Ethernet services from BTS21, BTS22, and BTS23, which respectively carry VLAN ID
100, VLAN ID 110, and VLAN ID 120, need to be transmitted to NE21 through a
Hybrid microwave ring network and then to the RNC by means of VLAN forwarding. A
bidirectional tunnel (ID: 1701) with protection is available between NE21 and NE31.
Ethernet services carried by PWs from BTS21, BTS22, and BTS23 are transparently
transmitted over the tunnel.
l Services carried by PWs converge at NE31.
Procedure
Step 1 Configure PWE3 E-Line services on NE21.
302
NE21_RNC
4
1 8
9
6
302
NE21_RNC
100,110,120 7
Step 2 Configure PWE3 E-Line services on NE11 by referring to service configurations on NE21.
1
5
13
12
14
10
15
11
19
20
16
21
Create the third VLAN forwarding
table item for the PW whose ID is
301.
23
27
----End
Data Preparation
On UNIs, traffic carried on tunnels need to be classified based on the C-VLAN priority field
in packets. On NNIs, traffic carried on tunnels need to be classified based on the MPLS EXP
field in packets. In this example, the mapping in the default DiffServ domain is used for
simple traffic classification.
l Mapping in the default DiffServ domain
CS7 7 7 –
CS6 6 6 –
EF 5 5 Real-time voice
service and
signaling service
AF4 4 4 –
AF1 1 1 –
BE 0 0 HSDPA data
services
Procedure
Step 1 Apply the mapping in the default DiffServ domain to target UNIs to implement simple traffic
classification.
Each NE uses the mapping in the default DiffServ domain, performing traffic classification
based on the C-VLAN priority field in the packets. The mapping is applied over UNIs and the
UNI port type needs to be changed to CVLAN.
Figure 11-25 Applying the mapping in the default DiffServ domain to UNIs
1 3
Step 2 Apply the mapping in the default DiffServ domain to target NNIs to implement simple traffic
classification.
Each NE uses the mapping in the default DiffServ domain, performing traffic classification
based on the Tunnel EXP field in the packets. The mapping is applied over NNIs and the NNI
port type needs to be changed to mpls-exp. For details, refer to tunnel QoS configurations.
----End
Procedure
Step 1 Perform ping tests at the first and last nodes of the PW to check the connectivity of the PW.
3
Select the application
control channel.
Select the PW to be checked, right-click,
and choose Ping Test from the drop-
down menu.
2
When the service is available, the packet loss ratio should be zero.
----End
CES services allow TDM E1s to be encapsulated to PWs and further transmitted over a packet
switched network (PSN).
NOTE
OptiX RTN 905 does not support the configuration of CES services.
Flowchart
Configure PW APS
End
NOTE
l For PWE3 services that have been configured on a per-NE basis, follow instructions in A.15.4 Searching
for MPLS Tunnels and PWE3 Services to synchronize the services to the network layer of the NMS.
This enables end-to-end management of the PWE3 services.
l Currently, a CES service transparently transmitting SDH overhead bytes cannot be configured in end-to-
end mode.
l For OptiX RTN 905, ensure that the working mode of E1 ports, channelized STM-1 ports, and multi-
functional cascading ports is CES. For OptiX RTN 950A that houses an MN1 board, ensure that the
working mode of E1 ports and STM-1 ports on the CSHO board is CES. For details, see A.8.2 Setting
Working Modes of E1 Ports.
NOTE
When E1 ports on the MP1 board are used as Smart E1 port for transmitting packet services, ensure that
Service Mode of the E1 ports is CES Mode.
Changing the E1 Frame Format and Frame Mode for a Channelized STM-1
Table 12-2 Changing the E1 frame format and frame mode for a channelized STM-1
Operation Remarks
A.11.6.2 Modifying CES Service Perform this task to change the PHB of a CES service
Parameters if a value other than the default value EF is required.
Configuring PW Protection
Normally, PW APS is configured to work with other equipment configured with MC-PW
APS, therefore achieving dual-homing protection. You can configure dual-homing services in
end-to-end mode on the NMS. For details, see the Configuration Guide of the equipment
where MC-PW APS is configured or the U2000 Online Help.
Testing E1 Services by Using a A CES service that uses fewer than 31 timeslots can
BER Tester or Testing E1 Services be tested only by means of a BER tester that supports
Using PRBS Nx64 kbit/s service tests.
Flowchart
Configure PW APS
End
NOTE
l If all clocks on the PSN are synchronous, configure CES service clocks in retiming mode. If not all
clocks on the PSN are synchronous, configure CES service clocks in CES ACR mode. (ACR stands
for adaptive clock recovery.)
l For OptiX RTN 905, ensure that the working mode of E1 ports, channelized STM-1 ports, and
multi-functional cascading ports is CES. For OptiX RTN 950A that houses an MN1 board, ensure
that the working mode of E1 ports and STM-1 ports on the CSHO board is CES. For details, see A.
8.2 Setting Working Modes of E1 Ports.
Operation Remarks
NOTE
When E1 ports on the MP1 board are used as Smart E1 port for transmitting packet services, ensure that
Service Mode of the E1 ports is CES Mode.
Changing the E1 Frame Format and Frame Mode for a Channelized STM-1
Table 12-6 Changing the E1 frame format and frame mode for a channelized STM-1
Operation Remarks
Operation Remarks
A.11.6.2 Modifying Required when you need to create a CES service for
CES Service transparently transmitting overhead bytes.
Parameters After creating the CES service at both ends, specify the
overhead bytes as planned.
Configuring PW Protection
For details about how to configure PW protection, see Configuration Procedure (PW APS) in
PW APS/FPS of the Feature Description.
Testing E1 Services by Using a A CES service that uses fewer than 31 timeslots can
BER Tester or Testing E1 Services be tested only by means of a BER tester that supports
Using PRBS Nx64 kbit/s service tests.
Working tunnel
(ID=1509)
GE GE
NE32
NE11 NE31
E1
GE GE
NE21 BSC
E1
BTS36 BTS35
Procedure
Step 1 Set E1 port attributes on the UNI side of NE31.
NE31 uses two E1 ports for receiving and transmitting services.
4
Set Frame Format to a framed format.
The default value is CRC-4 Multiframe.
NOTE
When E1 ports 1 and 16 are used, the DCN function needs to be disabled.
Step 2 Set E1 port attributes on the UNI side of NE11, by referring to configurations on the UNI side
of NE31.
----End
Data Preparation
NE32
NE31
NE11
E1
NE21
BSC
E1
BTS36 BTS35
Procedure
Step 1 Configure a CESoPSN service for the PW whose PW ID is 203.
NE(11) NE(31)
3
Respectively double-click the source and sink nodes in
the physical topology to select UNIs.
When configuring the UNIs, select “Channeled” and
NE(31)-2-ML-1(Port-1) configure 64 kbit/s timeslots.
NE(11)-4-ML-1(Port-1)
5
NE31_NE11
Step 2 Configure a CESoPSN service for the PW whose PW ID is 204, by referring to configurations
for the PW whose PW ID is 203.
----End
Procedure
Step 1 Use the VCCV Ping function in Test and Check to verify the connectivity of PWs.
4
Select the application control
channel.
NOTE
To verify the service availability at different packet lengths, you can set Packet Size to 128, 256, 512, 1024,
or 1280 bytes as desired.
After the verification, view the detailed results to check whether the number of received packets and the
number of transmitted packets are the same.
If a VCCV ping test result shows that the PW is unavailable, perform an LSP ping test to check the
connectivity of the MPLS tunnel.
----End
Procedure
Step 1 Set E1 port attributes on the UNI side of NE31.
4
Set Frame Format to a framed format.
The default value is CRC-4 Multiframe.
NOTE
When E1 ports 1 and 16 are used, the DCN function needs to be disabled.
Step 2 Set E1 port attributes on the UNI side of NE11, by referring to configurations on the UNI side
of NE31.
----End
Data Preparation
NE32
NE31
NE11
E1
NE21
BSC
E1
BTS36 BTS35
Procedure
Step 1 Create two CESoPSN services on NE31.
1. Create the service for the PW whose ID is 203.
1
4
2. Create the service for the PW whose ID is 204, by referring to configuration for the PW
whose ID is 203.
Step 2 Create two CESoPSN services on NE11, by referring to configurations on NE31.
----End
Procedure
Step 1 Perform ping tests at the first and last nodes of the PW to check the connectivity of the PW.
3
Select the application
control channel.
Select the PW to be checked, right-click,
and choose Ping Test from the drop-
down menu.
2
When the service is available, the packet loss ratio should be zero.
----End
GE GE
NE32
E1
NE11 NE31
GE GE
NE21 BSC
E1
BTS22
NOTE
If E1 services are locally accessed, they can be received by Smart E1 ports. Therefore, cross-connect loops
between PDH ports and Smart E1 ports are not required.
Procedure
Step 1 Set E1 port attributes on the UNI side of NE31.
NOTE
When E1 ports 1 and 16 are used, the DCN function needs to be disabled.
Step 2 Set E1 port attributes on the UNI side of NE21, by referring to configurations on the UNI side
of NE31.
----End
Data Preparation
NE32
E1
NE31
NE11
NE21
BSC
Working tunnel
(ID=1701)
Hybrid microwave ring network
UNI NNI
UNI:6-ML1-3 PW ID:201
E1
Unframe PW Incoming Label:203
PW Outgoing Label:203
Tunnel ID:1701
UNI NNI
BTS22 PW ID:202
UNI:6-ML1-4
Unframe PW Incoming Label:204
PW Outgoing Label:204
Tunnel ID:1701
Procedure
Step 1 Configure SAToP services for PWs whose IDs are 201 and 202 in end-to-end mode.
NE(21) NE(31)
3
Respectively double-click the source and sink nodes in the physical
topology to select UNIs numbered 9 and 10 (configure two services
at the same time).
When configuring UNIs, do not select Channeled and do not
NE(31)-2-ML-9(Port-9) configure 64 kbit/s timeslots.
NE(31)-2-ML-10(Port-10) 5
NE(21)-6-ML-3(Port-3)
NE(21)-6-ML-4(Port-4)
4
Specify PW ID, Forward Label and Reverse
Label for the two services separately, or select
Auto-Assign.
NE31_NE21
----End
Procedure
Step 1 Use the VCCV Ping function in Test and Check to verify the connectivity of PWs.
4
Select the application control
channel.
NOTE
To verify the service availability at different packet lengths, you can set Packet Size to 128, 256, 512, 1024,
or 1280 bytes as desired.
After the verification, view the detailed results to check whether the number of received packets and the
number of transmitted packets are the same.
If a VCCV ping test result shows that the PW is unavailable, perform an LSP ping test to check the
connectivity of the MPLS tunnel.
----End
Procedure
Step 1 Set E1 port attributes on the UNI side of NE31.
NE31 uses two E1 ports for receiving and transmitting services.
NOTE
When E1 ports 1 and 16 are used, the DCN function needs to be disabled.
Step 2 Set E1 port attributes on the UNI side of NE21, by referring to configurations on the UNI side
of NE31.
----End
Data Preparation
NE32
E1
NE31
NE11
NE21
BSC
Working tunnel
(ID=1701)
Hybrid microwave ring network
UNI NNI
UNI:6-ML1-3 PW ID:201
E1
Unframe PW Incoming Label:203
PW Outgoing Label:203
Tunnel ID:1701
UNI NNI
BTS22 PW ID:202
UNI:6-ML1-4
Unframe PW Incoming Label:204
PW Outgoing Label:204
Tunnel ID:1701
Procedure
Step 1 Create two SAToP services on NE31.
1. Create the service for the PW whose ID is 201.
1
4
2. Create the service for the PW whose ID is 202, by referring to configuration for the PW
whose ID is 201.
Step 2 Create two SAToP services on NE21, by referring to configurations on NE31.
----End
Procedure
Step 1 Perform ping tests at the first and last nodes of the PW to check the connectivity of the PW.
3
Select the application
control channel.
Select the PW to be checked, right-click,
and choose Ping Test from the drop-
down menu.
2
When the service is available, the packet loss ratio should be zero.
----End
Packet microwave can be used to transparently transmit STM-1s from an SDH network across
special terrains such as lakes and swamps.
Configure CES services on NE11 and NE12 in Figure 12-9 according to the following
requirements:
Procedure
Step 1 Set port attributes for the CQ1 board on the UNI side of NE11.
For the CQ1 board, the default port mode is Layer 1 and only VC-12 path parameters need to
be set.
NOTE
When VC-12s 1, 17, 33, and 49 are used, the DCN function needs to be disabled.
Step 2 Set port attributes for the CQ1 board on the UNI side of NE12, referring to configurations on
NE11.
----End
Data Preparation
Procedure
Step 1 Configure SAToP services for PWs whose IDs are 101 and 102 in end-to-end mode.
NE(11) NE(12)
3
Respectively double-click the source and sink nodes in the
physical topology to select UNIs numbered 1 and 2
(configure two services at the same time).
When configuring UNIs, do not select Channeled and do
not configure 64 kbit/s timeslots.
NE(12)-3-CQ1-1(Port-1)
NE(11)-3-CQ1-1(Port-1)
5
4
Specify PW ID, Forward Label and Reverse
Label for the two services separately, or select
Auto-Assign.
NE11_NE12
----End
Data Preparation
Figure 12-11 Data plan for CES services transmitting SDH overhead bytes
UNI NNI NNI UNI
UNI:3-CQ1-1 PW ID:103 PW ID:103 UNI:3-CQ1-1
Serive Type:SOH only PW Incoming Label:103 PW Incoming Label:103 Serive Type:SOH only
PW Outgoing Label:103 Working tunnel PW Outgoing Label:103
Tunnel ID:1501 (ID=1501) Tunnel ID:1501
Procedure
Step 1 Create a CES service transmitting SDH overhead bytes on NE11.
3
Set “Service Type”
to “SOH only”.
1
4
Step 2 Create the CES service transmitting SDH overhead bytes on NE12, by referring to
configurations on NE11.
----End
Procedure
Step 1 Use the VCCV Ping function in Test and Check to verify the connectivity of PWs.
4
Select the application control
channel.
NOTE
To verify the service availability at different packet lengths, you can set Packet Size to 128, 256, 512, 1024,
or 1280 bytes as desired.
After the verification, view the detailed results to check whether the number of received packets and the
number of transmitted packets are the same.
If a VCCV ping test result shows that the PW is unavailable, perform an LSP ping test to check the
connectivity of the MPLS tunnel.
----End
Procedure
Step 1 Set port attributes for the CQ1 board on the UNI side of NE11.
For the CQ1 board, the default port mode is Layer 1 and only VC-12 path parameters need to
be set.
NOTE
When VC-12s 1, 17, 33, and 49 are used, the DCN function needs to be disabled.
Step 2 Set port attributes for the CQ1 board on the UNI side of NE12, referring to configurations on
NE11.
----End
Data Preparation
Procedure
Step 1 Create two SAToP services on NE11.
3
When configuring two CES services,
you need to specify two Service ID and
Source Low Channel values.
1
4
7
You need to specify two PW
Incoming Label and PW
Outgoing Label values.
6
----End
Data Preparation
Figure 12-13 Data plan for CES services transmitting SDH overhead bytes
UNI NNI NNI UNI
UNI:3-CQ1-1 PW ID:103 PW ID:103 UNI:3-CQ1-1
Serive Type:SOH only PW Incoming Label:103 PW Incoming Label:103 Serive Type:SOH only
PW Outgoing Label:103 Working tunnel PW Outgoing Label:103
Tunnel ID:1501 (ID=1501) Tunnel ID:1501
Procedure
Step 1 Create a CES service transmitting SDH overhead bytes on NE11.
3
Set “Service Type”
to “SOH only”.
1
4
Step 2 Create the CES service transmitting SDH overhead bytes on NE12, by referring to
configurations on NE11.
----End
Procedure
Step 1 Perform ping tests at the first and last nodes of the PW to check the connectivity of the PW.
3
Select the application
control channel.
Select the PW to be checked, right-click,
and choose Ping Test from the drop-
down menu.
2
When the service is available, the packet loss ratio should be zero.
----End
ATM services allow ATM cells to be encapsulated to PWs and further transmitted over a
packet switched network (PSN).
NOTE
OptiX RTN 905 does not support the configuration of ATM services.
Flowchart
Figure 13-1 shows the flowchart for configuring ATM/IMA E1 services and fractional
ATM/IMA services. The procedure for configuring ATM/IMA E1 services is different from
the procedure for configuring fractional ATM/IMA services.
NOTE
End End
NOTE
For PWE3 services that have been configured on a per-NE basis, follow instructions in A.15.4 Searching for
MPLS Tunnels and PWE3 Services to synchronize the PWE3 services to the network layer of the U2000.
This enables end-to-end management of the PWE3 services.
Operation Remarks
NOTE
When E1 ports on the MP1 board are used as Smart E1 port for transmitting packet services, ensure that
Service Mode of the E1 ports is CES Mode.
Operation Remarks
Operation Remarks
NOTE
When E1 ports on the MP1 board are used as Smart E1 port for transmitting packet services, ensure that
Service Mode of the E1 ports is CES Mode.
Operation Remarks
Operation Remarks
Configuring PW Protection
Normally, PW APS is configured to work with other equipment configured with MC-PW
APS, therefore achieving dual-homing protection. You can configure dual-homing services in
end-to-end mode on the NMS. For details, see the Configuration Guide of the equipment
where MC-PW APS is configured or the U2000 Online Help.
Flowchart
Figure 13-2 shows the flowchart for configuring ATM/IMA E1 services and fractional
ATM/IMA services. The procedure for configuring ATM/IMA E1 services is different from
the procedure for configuring fractional ATM/IMA services.
Optional
Set UNI port attributes of Set UNI port attributes of
ATM/IMA E1 services Fractional E1 services
End End
Operation Remarks
NOTE
When E1 ports on the MP1 board are used as Smart E1 port for transmitting packet services, ensure that
Service Mode of the E1 ports is CES Mode.
Operation Remarks
Operation Remarks
NOTE
When E1 ports on the MP1 board are used as Smart E1 port for transmitting packet services, ensure that
Service Mode of the E1 ports is CES Mode.
A.11.9.3 Creating an ATM Policy Required for services that are not
transparently transmitted ATM services.
A.11.8.1 Creating ATM Setting service attributes Set the basic attributes for
Services ATM services. Required.
Configuring PW Protection
For details about how to configure PW protection, see Configuration Procedure (PW APS) in
PW APS/FPS of the Feature Description.
Working tunnel
(ID=1501)
GE GE
NE32
RTN980
E1
NE11 NE31
RTN980 RTN950 RNC
Hybrid radio chain network NE21
GE
RTN980 GE
E1 loop
E1 E1
R99
BTS13 R99
BTS14
NOTE
If E1 services are received directly from Smart E1 ports, you do not need to connect the Smart E1 ports
and corresponding PDH ports with E1 cables.
Procedure
Step 1 Configure attributes of UNIs on NE31.
Configure attributes of E1 ports 2-MP1-10 to 2-MP1-14.
2
1
4 5
When setting Frame Format and Frame Mode, ensure
that Frame Mode is set to the same value for the local
and peer ends. Normally, the CRC-4 multi-frame format
and the PCM30 frame mode are used.
----End
Data Preparation
GE GE
NE32
E1
NE11 NE31
RNC
Hybrid radio chain network NE21
GE
GE
E1 loop
E1 E1
R99
BTS13 R99
BTS14
Procedure
Step 1 Create IMA groups on NE11.
1. Create IMA Group 1.
10
Step 2 Configure data about IMA group management on NE31 by referring to the configuration
procedure applied to NE11.
----End
Data Preparation
l Prepare data for creating two ATM policies for four types of ATM services: a policy for
one E1 and a policy for four E1s.
Policy ID 1 2 3 4
Table 13-11 Data required for configuring a policy for four E1s
Parameter CBR Service rt-VBR nrt-TVBR UBR Service
(4xE1s) Service Service (4xE1s)
(4xE1s) (4xE1s)
Policy ID 5 6 7 8
Procedure
Step 1 Create end-to-end ATM policies. Use the creation of 1e1_cbr as an example to describe how
to create an end-to-end ATM policy.
1. Create a global ATM policy.
----End
Data Preparation
GE GE
NE32
E1
NE11 NE31
RNC
Hybrid radio chain network NE21
GE
GE
E1 loop
E1 E1
R99
BTS13 R99
BTS14
Procedure
Step 1 Create ATM services.
1. Create the source and sink nodes, and PW services.
Double-click the
Double-click the desired source and
desired sink and select Trunk-1.
select Trunk-1. NE(31) 3
4 NE(11)
Display source and 6
sink info. Right-click the sink and
choose Select Sink and select
Trunk-2.
5
NE(31)-2-ML-1(Trunk-1)
NE(11)-4-ML-1(Trunk-1)
NE(11)-4-ML-2(Trunk-2) 8
7
Configure PW info.
9
NE(31) NE(11) NE31_NE11
NE31_NE11
N
E
( NE(11) NE(31)
1
1
) Select created ATM policies, apply 1e1_cbr to the first 12
- Link and 4e1_cbr to the second Link and assign VPI and
4 VCI for them.
NE(31)-2-ML-1(Trunk-1)
-
NE(11)-4-ML-1(Trunk-1)
M 5
L
NE(31)-2-ML-1(Trunk-1) 30
- 32 NE(31)[Ingress:1e1_cbr,Egress:... NE(11)-4-ML-1(Trunk-1) 30 32
NE(31)-2-ML-1(Trunk-1) 2
30 33 NE(31)[Ingress:4e1_cbr,Egress:... NE(11)-4-ML-2(Trunk-2) 30 33
(
T
r
u NE(11)[Ingress:1e1_cbr,Egress:... 30 32
n NE(11)[Ingress:4e1_cbr,Egress:... 30 33
k
NE(31) NE(11) - NE31_NE11
2
)
NE31_NE11
11
13
10
NE(11) NE(31)
NE(31)-2-ML-1(Trunk-1)
NE(11)-4-ML-1(Trunk-1) 14
NE(11)-4-ML-2(Trunk-2)
15
16
Select the default ATM CoSMap template
NE(31) NE(11) NE31_NE11
or a customized template for the source
and sink nodes.
NE31_NE11
17
----End
Procedure
Step 1 Use the VCCV Ping function in Test and Check to verify the connectivity of PWs.
4
Select the application control
channel.
NOTE
To verify the service availability at different packet lengths, you can set Packet Size to 128, 256, 512, 1024,
or 1280 bytes as desired.
After the verification, view the detailed results to check whether the number of received packets and the
number of transmitted packets are the same.
If a VCCV ping test result shows that the PW is unavailable, perform an LSP ping test to check the
connectivity of the MPLS tunnel.
----End
Procedure
Step 1 Configure attributes of UNIs on NE31.
Configure attributes of E1 ports 2-MP1-10 to 2-MP1-14.
2
1
4 5
When setting Frame Format and Frame Mode, ensure
that Frame Mode is set to the same value for the local
and peer ends. Normally, the CRC-4 multi-frame format
and the PCM30 frame mode are used.
----End
Data Preparation
GE GE
NE32
E1
NE11 NE31
RNC
Hybrid radio chain network NE21
GE
GE
E1 loop
E1 E1
R99
BTS13 R99
BTS14
Procedure
Step 1 Create IMA groups on NE11.
1. Create IMA Group 1.
10
Step 2 Configure data about IMA group management on NE31 by referring to the configuration
procedure applied to NE11.
----End
Data Preparation
l Prepare data for creating two ATM policies for four types of ATM services: a policy for
one E1 and a policy for four E1s.
Policy ID 1 2 3 4
Table 13-13 Data required for configuring a policy for four E1s
Parameter CBR Service rt-VBR nrt-TVBR UBR Service
(4xE1s) Service Service (4xE1s)
(4xE1s) (4xE1s)
Policy ID 5 6 7 8
Procedure
Step 1 Create an ATM policy on NE31. Use the creation of 1e1_cbr as an example to describe how
to create an ATM policy.
4 2
Step 2 Create a CoS mapping relationship on NE31. The default mapping "DefaultAtmCosMap" is
used. If another mapping relationship is required, use the following steps to create one.
3
2
5
1
----End
Data Preparation
GE GE
NE32
E1
NE11 NE31
RNC
Hybrid radio chain network NE21
GE
GE
E1 loop
E1 E1
R99
BTS13 R99
BTS14
Procedure
Step 1 Create ATM services on NE31.
5 2
2. Create a PW.
10
11
8
1501
1501
12
13
14
15
16
----End
Procedure
Step 1 Perform ping tests at the first and last nodes of the PW to check the connectivity of the PW.
3
Select the application
control channel.
Select the PW to be checked, right-click,
and choose Ping Test from the drop-
down menu.
2
When the service is available, the packet loss ratio should be zero.
----End
Working tunnel
(ID=1501)
NE32
E1
NE31
NE11 RNC
NE21
E1
E1
R99
BTS13 R99
BTS14
Procedure
Step 1 Configure attributes of UNIs on NE31.
Configure attributes of E1 ports 2-MP1-10 to 2-MP1-14.
2
1
4 5
When setting Frame Format and Frame Mode, ensure
that Frame Mode is set to the same value for the local
and peer ends. Normally, the CRC-4 multi-frame format
and the PCM30 frame mode are used.
----End
Data Preparation
GE GE
NE32
E1
NE11 NE31
RNC
GE NE21
GE
E1 E1
R99
BTS13 R99
BTS14
Procedure
Step 1 Create IMA groups on NE11.
1. Create IMA Group 1.
10
Step 2 Configure data about IMA group management on NE31 by referring to the configuration
procedure applied to NE11.
----End
Data Preparation
Table 13-15 Data plan for QoS of transparently transmitted ATM services
Parameter Value
PORT-TRANS EF
Procedure
Step 1 Create an end-to-end CoS mapping relationship.
1. Create a global ATM CoS mapping relationship.
NOTE
PHB service classes for other service types are invalid for transparently transmitted ATM services. It is
recommended that a transparently transmitted ATM service takes its default PHB service class.
2. Apply the mapping relationship to NEs.
Step 2 Configure an ATM QoS template in end-to-end mode and apply the template to services.
----End
Data Preparation
GE GE
NE32
E1
NE11 NE31
RNC
E1 NE21
GE
GE
E1
R99 E1 loop
BTS13
R99
BTS14
Procedure
Step 1 Configure transparently transmitted ATM services between NE11 and NE31 in end-to-end
mode. In this example, the PW ID 101 is used.
NE(11)-NE(12)
----End
Procedure
Step 1 Use the VCCV Ping function in Test and Check to verify the connectivity of PWs.
4
Select the application control
channel.
NOTE
To verify the service availability at different packet lengths, you can set Packet Size to 128, 256, 512, 1024,
or 1280 bytes as desired.
After the verification, view the detailed results to check whether the number of received packets and the
number of transmitted packets are the same.
If a VCCV ping test result shows that the PW is unavailable, perform an LSP ping test to check the
connectivity of the MPLS tunnel.
----End
Procedure
Step 1 Configure attributes of UNIs on NE31.
Configure attributes of E1 ports 2-MP1-10 to 2-MP1-14.
2
1
4 5
When setting Frame Format and Frame Mode, ensure
that Frame Mode is set to the same value for the local
and peer ends. Normally, the CRC-4 multi-frame format
and the PCM30 frame mode are used.
----End
Data Preparation
GE GE
NE32
E1
NE11 NE31
RNC
GE NE21
GE
E1 E1
R99
BTS13 R99
BTS14
Procedure
Step 1 Create IMA groups on NE11.
1. Create IMA Group 1.
10
Step 2 Configure data about IMA group management on NE31 by referring to the configuration
procedure applied to NE11.
----End
Data Preparation
Table 13-16 Data plan for QoS of transparently transmitted ATM services
Parameter Value
PORT-TRANS EF
Procedure
Step 1 Create a CoS mapping relationship on NE31.
4
2
1
NOTE
PHB service classes for other service types are invalid for transparently transmitted ATM services. It is
recommended that a transparently transmitted ATM service takes its default PHB service class.
----End
Data Preparation
GE GE
NE32
E1
NE11 NE31
RNC
E1 NE21
GE
GE
E1
R99 E1 loop
BTS13
R99
BTS14
Procedure
Step 1 Create ATM services on NE31. In this example, PW ID 101 is used.
1. Create an ATM connection.
3 5
4
1
2. Create a PW.
7
10
1501
1501
11
12
Step 2 Create ATM services on NE11 by referring to the configuration procedure applied to NE31.
----End
Procedure
Step 1 Perform ping tests at the first and last nodes of the PW to check the connectivity of the PW.
3
Select the application
control channel.
Select the PW to be checked, right-click,
and choose Ping Test from the drop-
down menu.
2
When the service is available, the packet loss ratio should be zero.
----End
To ensure that clocks of all the nodes on the transmission network are synchronized, configure
the clocks for these nodes according to a unified clock synchronization policy.
Start
Configure clock
sources.
Configure standard or
extended SSM
protection.
Configure standard or
extended SSM
protection.
Configure a clock
source group.
Modify parameters of
the output clock.
Optional End
A.12.1.2 Setting the E1 Clock Required when an E1 clock source needs to be set for a
Source for a Channelized channelized STM-1.
STM-1 Interface Board
Operation Remarks
A.15.8 Querying the Clock Generally, the clock tracing relationship is consistent
Tracing Relationship with that in the network plan.
Based on 6.3 Configuration Example (Radio Links on the Hybrid Radio Chain
Network), configure the clocks according to the following requirements:
l The microwave transmission network is synchronized with the clock of the BSC through
a link aggregation group (LAG) that consists of two GE links.
l Clock synchronization signals are transmitted to BTSs over FE signals.
FE
BTS2
GE GE
FE NE14
BTS3
FE
NE13 NE12 NE11 BSC
FE BTS1
FE
NE16 NE15
BTS5 BTS4
Data Preparation
Item Value in This Example Planning Principles
Clock source information See the following figure. You need to configure an
Ethernet clock source for
each link in an LAG.
3-ISV3-1/
4-ISV3-1
Internal GE
NE14 GE
RTN 905 2E
NE13 NE12 NE11
BSC
RTN 950A RTN 950A RTN 980
17-EG6–1 / 3-ISV3-1/ 17-EG2D–1 /
Internal 5-ISV3-1/ 17-EG2D-2/
Internal Internal
NE16 NE15
RTN 905 1E RTN 950A
3-ISV3-1/ 4-ISV3-1/
Internal 6-ISV3-1
Internal
Clock
Procedure
Step 1 Configure the priority of a clock source.
To configure the priority of a clock source on NE11, do as follows.
----End
BITS
R4
FE NE21
BTS21
FE
R4
BTS22
R4 NE23 NE24
BTS23
Data Preparation
Item Value in This Example Planning Principle
BITS
NE21
RTN 950A
External/
Internal
NE22 NE25
RTN 905 2E RTN 910A
7-ISM6-2/
4-ISV3-1/ 7-ISM6-1/
3-ISV3-1/ Internal
Internal
NE23 NE24
RTN 905 1E RTN 905 1E
3-ISV3-1/ 7-EG6-1/
7-EG6-1/ 3-ISV3-1/
Clock Internal Internal
Procedure
Step 1 Configure the priority of a clock source.
To configure the priority of a clock source on NE21, do as follows.
Generally, the clock tracing relationship is consistent with that in the network plan.
----End
Based on 3.3 Packet Network, configure the clocks according to the following requirements:
R4
FE
GE
NE32
RTN 980
NE33 NE31
RTN 980 RTN 950
NE34 E1
RTN 980
E1
E1
E1
+G
BSC
E
BTS33
R99
BTS34
RNC
Data Preparation
Item Value in This Example Planning Principles
Synchronization policy for The CES retiming function In this example, 2G base
2G base stations is used. stations need to extract
CES retiming is the default clock information through
clock recovery solution for E1 ports on the PSN.
PSNs and therefore does not The PSN implements the
need to be enabled following clock
manually. synchronization:
l Network-wide clock
synchronization
l Synchronization between
the network-wide clock
and the service clock
Therefore, the PSN can use
the CES retiming function
for clock synchronization.
That is, the PSN extracts
system clock information
from the E1 signal
converted from a CES
service and then provides
the clock synchronization
signal through E1 ports to
base stations.
BTS31
R4
FE
E1 FE R4
BTS32 GE GE
NE32
E1
GE E1
+G
BSC
E
BTS33
R99
BTS34
Clock RNC
Procedure
Step 1 Configure the priority of a clock source.
Take NE31 as an example.
----End
The product provides various auxiliary ports and the function of environment monitoring,
which require certain data configuration.
This example assumes that the outdoor cabinet monitoring port and the outdoor cabinet PMU
are correctly connected.
Orderwire
OptiX RTN 910A/950/950A/980 supports one orderwire phone so that operation or
maintenance engineers at different workstations can perform voice communication through
microwave or SDH overhead bytes.
l The orderwire phone numbers of all nodes on the network must be of the same length. A
3-digit number is recommended and all orderwire phone numbers on the entire network
must be unique.
l Dual tone multiple frequency is used as the dialing method of the orderwire phone on
each node.
l The call waiting time must be set to the same value for all nodes. It is recommended that
you set the call waiting time to 5s if fewer than 30 nodes exist on the orderwire subnet
and to 9s if more than 30 nodes exist on the orderwire subnet.
l The product supports the orderwire group call function. When the orderwire group call
number "888" is dialed on an OptiX RTN, orderwire phones of all OptiX RTN devices
on the orderwire subnet ring. When an orderwire phone receives the call, orderwire
phones on other NEs stop ringing. In this case, the orderwire point-to-multipoint group
call changes to a point-to-point common orderwire call.
l When orderwire signals are transmitted over a microwave link, they are always
transmitted through one customized overhead byte. When orderwire signals are
transmitted over SDH fibers, they are transmitted through the E1 or E2 byte.
l By default, all line ports, IF ports, and unconfigured synchronous data ports on an OptiX
RTN device function as orderwire ports. Therefore, in normal cases, orderwire ports
need to be configured only at the edge of an orderwire subnet.
l The equipment supports the transmission of orderwire overhead bytes through a 64 kbit/s
synchronous data port or an external clock port. If two pieces of equipment are
connected in back-to-back mode, they do not support the orderwire group call function
(orderwire group call number "888").
l If multiple microwave links or optical transmission lines exist between two NEs, ports
corresponding to these links must be configured as orderwire ports. When Hybrid
microwave links are not used in N+1 protection, orderwire signals can be normally
transmitted between two NEs as long as one of microwave links between the two NEs is
available. When orderwire signals are transmitted over Hybrid microwave links in N+1
protection, the protection link cannot transmit orderwire signals.
l For definitions of the pins on the ports, see the IDU Hardware Description.
transmitted between two NEs can be used for transmitting one 64 kbit/s synchronous data
service.
When using synchronous data services, note the following points:
l The synchronous data service is fully transparently transmitted, and the port transmission
rate is 64 kbit/s.
l The synchronous data service is clock-sensitive. If the clock is not synchronized, bit
errors occur.
l Ports on the equipment comply with ITU-T G.703.
l When synchronous data services are transmitted over a microwave link, they are always
transmitted through one customized overhead byte. When orderwire signals are
transmitted over SDH fibers, they are always transmitted through the F1 byte.
l The equipment supports the transmission of overhead bytes in the synchronous data
service through external clock ports to implement the service spanning function.
l When the synchronous data service is transmitted over protected microwave links or
optical transmission lines, the synchronous data service is also protected.
l For definitions of the pins on the ports, see the IDU Hardware Description.
l The asynchronous data service is fully transparently transmitted. The transmission rate
and transmission control protocol do not need to be configured. The port transmission
rate is 19.2 kbit/s.
l The asynchronous data service is clock-sensitive. If the clock is not synchronized, bit
errors occur.
l The equipment provides RS-232 electrical ports that comply with ITU-T V.24/V.28.
l The equipment supports only point-to-point communications.
l When asynchronous data services are transmitted over a microwave link, they are always
transmitted through one customized overhead byte. When orderwire signals are
transmitted over SDH fibers, they are transmitted through any of the SERIAL 1 to
SERIAL 4 bytes.
l The equipment supports the transmission of overhead bytes in the asynchronous data
service through external clock ports to implement the service spanning function.
l When the asynchronous data service is transmitted over protected microwave links or
optical transmission lines, the asynchronous data service is also protected.
l For definitions of the pins on the ports, see the IDU Hardware Description.
Wayside E1 Services
The OptiX RTN 905/910A/950/950A/980 supports one wayside E1 service. The transmitted
overhead bytes in STM-1 microwave signals can be used for transmitting one wayside E1
service between two sites in one hop of STM-1 microwave link.
External Alarms
External alarms are also called housekeeping alarms or relay alarms.
This figure shows the port circuits for external alarm input. When the external relay is
switched off, the port circuit generates a high-level signal. When the external relay is
switched on, the port circuit generates a low-level signal. The board generates an alarm based
on the level signal. External alarm input mainly achieves access of the relay alarms generated
by the environmental alarm generator.
The port circuit for external alarm output works in a similar manner as the external system
shown in the preceding figure. When the external alarm output conditions specified for the
NE are met, the NE drives the relay to turn on or off the switch according to the conditions
that result in the alarm. Otherwise, the NE drives the relay to change the switch to the reverse
status that results in the alarm. External alarm output helps to provide equipment alarms to the
centralized alarming device.
For definitions of the pins on the ports, see the IDU Hardware Description.
l APM30H: The advanced power module with heat exchanger cooler (APM30H) cabinet
supports alternating current (AC) power input and direct current (DC) power output. It
provides a 7U space for installing user equipment.
l TMC11H: The transmission cabinet of 11U high with heat exchanger (TMC11H) cabinet
supports DC power input and DC power output. It provides an 11U space for installing
user equipment.
l OMB: The outdoor mini box (OMB) cabinet supports AC or DC power input. It provides
a 2U space for installing user equipment.
NOTE
For details about outdoor cabinets, see the chapter that describes outdoor cabinets in the Site
Preparationoutdoor cabinet product description.
On the NMS, an outdoor cabinet is named based on its power input mode (the naming rule applies to the
document):
l An APM30H cabinet is named APM30 AC.
l A TMC11H cabinet is named APM30 DC.
l An OMB (AC power input) cabinet is named OMB AC, and an OMB (DC power input) cabinet is
named OMB DC.
This table describes the logical slots of outdoor cabinets supported by OptiX RTN 900 and
their functions.
l OptiX RTN 905 uses a CLK/TOD/MON port as the outdoor cabinet monitoring port.
l OptiX RTN 910A/950/950A/980 provides an outdoor cabinet monitoring port on its
system control, switching, and timing board.
l For definitions of the pins on the ports, see the IDU Hardware Description.
Flowchart
This figure shows the flowchart for configuring the function of monitoring an outdoor
cabinet.
Figure 15-2 Flowchart for configuring the function of monitoring an outdoor cabinet
Required
Start
Optional
Set the temperature and fan Set the information about the power Set the temperature and humidity
information of the outdoor cabinet. . system of the outdoor cabinet. thresholds of the PMU.
End
Each NE shown in the following networking diagram needs to be configured with the
orderwire. Only microwave links between NE1 and NE2 are configured with 1+1 protection.
Other microwave links use 1+0 non-protection.
1+0
1+1
64 kbit/s
NE4
RTN 980
1+0
NE2 NE1
1+0 NE3 RTN 980 RTN 980
RTN 980
NE6 NE5
RTN 980 RTN 980
Data Preparation
Item Value in This Example Planning Principle
Information about orderwire See the following table. l In this example, services
ports between NE2 and NE3
are forwarded through an
E1 line. Therefore,
service spanning is
required. A 64 kbit/s
synchronous data service
port is used for service
spanning. An external
clock port can also be
used to implement
service spanning
between NE2 and NE3.
In this case, the external
clock port needs to be
added to the orderwire
port on the NMS.
l NE2 to NE6 are located
on the orderwire subnet.
Therefore, NE2 to NE6
use the default orderwire
ports (all the IF ports,
line ports, and
unconfigured
synchronous data ports)
that are automatically
mapped by the
equipment.
l If NE1 is not located at
the edge of the orderwire
subnet, configure
orderwire ports for NE1
in the way orderwire
ports are configured for
NE2 to NE6. If NE1 is
located at the edge of the
orderwire subnet and if it
is connected to an IF port
or a line port on another
orderwire subnet, delete
the IF port or line port
from the orderwire ports
on the NMS.
1+0
104 1+1
NE4
1+0 E1
NE3 NE2 NE1
1+0
101
102
103
NE6 NE5
105
106
NE Orderwire Port
NE1 3-ISV3-1
5-ISV3-1
NE2 3-ISV3-1
5-ISV3-1
F1
NE3 3-ISV3-1
4-ISV3-1
F1
NE4 3-ISV3-1
NE Orderwire Port
NE5 3-ISV3-1
4-ISV3-1
NE6 3-ISV3-1
Procedure
Step 1 Configure the orderwire.
----End
The microwave network shown in the following networking diagram needs to transmit
network information about third-party equipment. Third-party equipment and NMS use
protocol converters to convert network management messages carried by the Ethernet
network into network management messages carried by the 64 kbit/s synchronous data
service. Therefore, the microwave network needs to transparently transmit the corresponding
synchronous data only.
l 64 kbit/s synchronous data services are added or dropped on NE1 and NE6, and passed
through NE2, NE3, and NE5.
l Only microwave links between NE1 and NE2 are configured with 1+1 protection. Other
microwave links use 1+0 non-protection.
1+0
1+1
Third-party 64 kbit/s ETH
equipment NE4 64 kbit/s
RTN 980
1+0
NE3 NE2 NE1 64K/ETH
1+0 RTN 980 RTN 980 RTN 980
ETH converter
64 kbit/s
NE5
64K/ETH NE6 RTN 980
converter RTN 980
Data Preparation
Item Value in This Example Planning Principle
NE Data Channel
NE1 F1 3-ISV3-1
NE2 3-ISV3-1 F1
NE3 F1 4-ISV3-1
NE6 3-ISV3-1 F1
Procedure
Step 1 Configure synchronous data services.
To configure synchronous data services for NE1, do as follows.
----End
1+0
1+1
Third-party RS-232 ETH
equipment NE4 RS-232
RTN 980
1+0
NE3 NE2 NE1 RS-232/ETH
1+0 RTN 980 RTN 980 RTN 980
ETH converter
RS-232
NE6 NE5
RS-232/ETH RTN 980 RTN 980
converter
Data Preparation
Item Value in This Example Planning Principle
Procedure
Step 1 Configure asynchronous data services.
To configure asynchronous data services for NE1, do as follows.
----End
Third-party Third-party
equipment NMS
Data Preparation
Item Value in This Example Planning Principle
Information about wayside See the following table. In the case of microwave
E1 services links configured with 1+1 or
N+1 protection, only the
active link is configured
with wayside E1 services.
Procedure
Step 1 Configure wayside E1 services.
----End
4-AUX
Input 1
Smoke sensor
Input 2
NE1 Output 1
Water sensor Input 3 RTN 980
Integrated
Door status switch
alarm box
sensor
Data Preparation
Item Value in This Example Planning Principle
Port 1 Used
Procedure
Step 1 Configure external alarms.
----End
As shown in this figure, the CLK/TOD/MON port on the OptiX RTN 905 is connected to the
COM_IN port in the APM30 DC cabinet. The OptiX RTN 905 supports the function of
monitoring the PMU temperature and humidity after the upper and lower thresholds for
temperature and humidity alarms of the PMU are configured.
Figure 15-9 Networking diagram (an OptiX RTN 905 outdoor cabinet)
PMU
COM_IN
IDU
CLK/TOD/
MON
Data Preparation
Item Value in This Example Planning Principles
Alarm thresholds for the Default value Generally, default values are
PMU recommended.
Procedure
Step 1 Query the CLK/TOD/MON port mode and ensure that the External clock (Hz mode) +
outdoor cabinet mode is used.
Step 4 In this example, the default PMU alarm thresholds are used. If the thresholds need to be
changes, follow instructions in A.14.6.6 Setting the Temperature and Humidity Alarm
Thresholds for the PMU.
----End
During the equipment commissioning and operating phases, you need to add or modify
certain configuration data according to the actual requirements.
Creating NEs When using the NMS A.3.1.1 Creating NEs l Generally, NEs
to perform centralized by Using the Search are created by
management of NEs, Method (U2000) or A. searching for the
create the icons of the 3.1.3 Creating NEs by NE on the NMS.
NEs to be managed at Using the Manual l The manual NE
corresponding Method (U2000) creation method
positions on the Main is applicable only
Topology. when several
NEs need to be
created on a large
radio
transmission
network.
NOTICE
When you add or modify the configurations of a radio link, you need to modify the
configurations of the NE that is located far from the NMS server and then modify the
configurations of the NE that is located near to the NMS server.
NOTE
l For 1+1 HSB/SD protection, you need to configure only the IF/ODU information of the main radio
link.
l For 1+1 FD protection, you need to configure the IF/ODU information of the main radio link and the
ODU information of the standby radio link.
l Before configuring XPIC workgroups, you need to set IF Service Type separately for IF boards in
the vertical polarization and those in horizontal polarization.
l For N+1 protection, you need to configure the IF/ODU information of the N+1 radio links
respectively.
l The MW_CFG_MISMATCH alarm is reported, if the E1 count, AM enabled status, 1588 timeslot
enabled status, STM-1 count, or modulation mode is set inconsistently for both ends of an Integrated
IP microwave link. This alarm should be cleared immediately. Otherwise, services may be
configured unsuccessfully or interrupted.
Changing the When the original A.8.10.9 l Before using the new
modulation modulation scheme Modifying the modulation scheme,
scheme of a does not meet the Hybrid/AM contact the network
Hybrid radio link service requirements, Attributes planning department to
you need to use confirm that the Hybrid
another modulation radio link supports the
scheme. new Modulation Mode
of the Guarantee AM
Capacity and
Modulation Mode of
the Full AM Capacity.
l Ensure that the
parameter values are
the same at both ends
of the Hybrid radio
link.
Changing the You can change the A.7.3 Modifying l When you change the
priority of E1 priority of E1 the Priorities of priority of an E1, the
services on a services on a Hybrid E1 Services E1 is interrupted
Hybrid radio link radio link. transiently.
l If the number of E1s
with high priorities
exceeds the value of
Modulation Mode of
the Guarantee AM
Capacity, you need to
increase the value of
Modulation Mode of
the Guarantee AM
Capacity before
changing the priorities.
NOTE
OptiX RTN 905/910A does not support the configuration of Ethernet services on EoS/EoPDH boards.
Table 16-5 Common task collection (Ethernet services on the EoS/EoPDH plane)
Task Application Configuration Operation Remarks
Scenario
Changing The Ethernet LAN A.10.3.3 Changing the Ports You need to
logical ports service requirements Connected to a VB add or delete
connected to change. As a result, the the logical port
a VB logical ports connected connected to a
to the VB need to be VB, or modify
changed. attributes
associated with
the logical port
connected to
the VB
according to
the actual
planning
information.
Creating Create MPLS APS A.11.3 Managing MPLS APS When creating
MPLS APS protection groups to Protection Groups an MPLS APS
protection improve the reliability protection
groups of service transmission group, set
over tunnels. Protocol
Status to
Disabled. Start
the protocol
after an MPLS
APS protection
group has been
created on the
NEs at both
ends.
Adding CES Add CES services A.11.6.1 Creating CES l If new CES
services according to the Services services are
service plan. carried by
PCM
Adjusting Adjust QoS settings A.9.8 Managing the QoS Modify QoS
QoS settings when service parameters to
requirements change. adapt the QoS
to the service
requirement
changes.
Creating and Create and configure A.8.7 Setting Serial Port l Set Level to
configuring serial ports when Parameters 64K
serial ports fractional ATM/IMA Timeslot.
services need to be When the
used. E1 frame
mode is 30,
timeslot 0
and
timeslot 16
are
unavailable.
When the
E1 frame
mode is 31,
timeslot 0 is
unavailable.
l Set Port
Type to
Layer 2.
l Set
Encapsulat
ion Type to
ATM.
ATM/IMA
services,
select the
ports to be
bound in
Available
Resources
and the
timeslots to
be bound in
Available
Timeslots.
Managing Manage ATM port A.11.7.3 Setting ATM Port l Set Port
ATM ports parameters such as Parameters Type and
ATM trunk port type, ATM Cell
ATM cell payload Payload
scrambling, and Scramblin
loopback mode. g according
to the type
of access
equipment.
It is
recommend
ed that you
set the
parameters
to the
default
values.
l Retain the
default
values for
the other
parameters.
A Task Collection
To ensure the clock synchronization between transmission nodes on a transport network, you
need to manage the NE clock.
A.13 Ethernet Performance Query
This section describes operations related to Ethernet performance query.
A.14 Configuring Auxiliary Ports and Functions
The NE supports auxiliary ports and functions such as asynchronous data service port,
wayside service port, external alarm port, and outdoor cabinet monitoring port.
A.15 End-to-End Configuration Task Collection
End-to-end configuration is simpler than per-NE configuration.
Prerequisites
l The U2000 system has been started on the U2000 server.
l The IP address of the U2000 client is in the access control list (ACL) configured in the
U2000 system.
l The U2000 client has proper communication with the U2000 server.
NOTE
Procedure
Step 1 Double-click the U2000 client icon on the desktop.
Step 2 In the Login dialog box, set User Name and Password.
Step 3 Select the desired U2000 server from the Server drop-down list.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Procedure
Step 1 Choose File > Exit from the Main Menu.
The Confirm dialog box is displayed.
NOTE
If the main topology has changed but the changes have not been stored, a dialog box will be displayed
asking whether to update the main topology. The U2000 client is shut down after you determine whether
to update the main topology.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Procedure
Step 1 Choose Help > Help Topics from the Main Menu.
The Online Help page is displayed.
NOTE
When using the U2000client, press the F1 key to quickly display the related Online Help page.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Procedure
Step 1 Choose View > Main Topology from the Main Menu, or double-click the Main Topology
icon in Workbench.
The Main Topology view is displayed.
Step 2 Optional: Choose View > Display Settings > Filter from the Main Menu.
The Filter tab page is displayed on the right of the main topology.
NOTE
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Procedure
Step 1 Optional: In Main Topology, double-click the subnet to which the NE belongs.
Step 2 In Main Topology, right-click the icon of the desired NE and choose NE Explorer from the
shortcut menu.
The NE Explorer view is displayed.
NOTE
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Procedure
Step 1 Optional: In Main Topology, double-click the subnet to which the NE belongs.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Procedure
When using the Web LCT, press the F1 key to quickly display the related Online Help page.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Procedure
Step 1 In NE List, select the NE to which you are logged in and click NE Explorer at the lower
right corner.
The NE Explorer view is displayed.
NOTE
NOTE
You can also navigate to the NE Explorer view using the following methods:
l In NE List, right-click the NE to which you are logged in and choose NE Explorer from the shortcut
menu.
l In NE List, double-click the NE to which you are logged in.
----End
Prerequisites
l The NMS must have proper communication with NEs.
l You must be an NM user with NE operator authority or higher.
Procedure
Step 1 Choose File > Discovery > NE from the Main Menu.
NOTE
l If the U2000 server and the gateway NE are in the same network segment, it is recommended that you set
Search Mode to IP auto discovery.
l In other scenarios, it is recommended that you set Search Mode to Search for NE.
If... Then...
Search Mode is set to Search for NE Perform Step 4 to Step 7.
Search Mode is set to IP auto discovery Perform Step 8 to Step 10.
Step 4 If Search Mode is set to Search for NE, you need to add a search domain.
1. Click Add, and then the Input Search Domain dialog box is displayed.
2. Select an address type and enter the search address.
NOTE
– When Address Type is set to IP Address of GNE or IP Address Range of GNE, and the U2000
server and gateway NE are not in the same network segment, ensure that the IP routes of the
network segments to which the U2000 server and gateway NE belong are configured on the U2000
and related routers.
– The factory default user name is root, and its corresponding password is Changeme_123. If you
have changed the password, log in to the NE using the correct password.
3. Click OK.
Step 5 Repeat Step 4 to add several search domains.
Step 6 In the Search for NE dialog box, perform the operations described in the Note part.
NOTE
l If Create NE after search is selected, you need to specify NE User and Password.
l You can select either Create NE after search or Upload after Create or both Create NE after search
and Upload after Create. In this manner, after the NE searching is complete, the system automatically
creates an NE and uploads the NE.
Step 7 Click Next, and then the Transport NE Search dialog box is displayed.
After the search is complete, all the NEs that are found are displayed in the Result list.
Step 8 If Search Mode is set to IP auto discovery, enter NE User and Password.
NOTE
The factory default user name is root, and its corresponding password is Changeme_123. If you have
changed the password, log in to the NE using the correct password.
Step 10 After the NE to be created is displayed in Result, click Stop. In the dialog box that is
displayed, click Yes.
Step 12 Optional: Repeat Step 11 to create other NEs that are not created.
----End
Prerequisites
l The NMS must have proper communication with NEs.
l You must be an NM user with NE operator authority or higher.
Procedure
Step 1 Click NE Search in NE List and select a desired search type.
If... Then...
All NEs are directly connected to the NMS server through Perform Step 2 to Step 5.
Ethernet cables
Not all NEs are directly connected to the NMS server Perform Step 6 to Step 11.
through Ethernet cables
NOTE
The default user name is lct, and its corresponding password is Changeme_123.
Local IP Address indicates the IP address of an Ethernet port on the NMS server. There may be multiple
Local IP Address values because an NMS server may have multiple network adapters.
NE IP Address indicates the IP addresses of all NEs (searched out by the system automatically) that are
connected to the NMS server directly through Ethernet cables.
When NE Search is selected, the system can directly log in to NEs. You do not need to enter the user
name and password.
2. After the Web LCT finds the NEs to be managed, click End Search.
NOTE
In the IP auto discovery mode, the Web LCT searches for the gateway NE and non-gateway NEs that are
managed by the gateway NE in the network segment where the server resides.
During initial configuration, Manage Domain takes the default value of 129.9.255.255. After the IP
address of the gateway NE is changed, the value of Manage Domain also needs to be changed. The
default network segment cannot be modified or deleted.
Step 9 Select the NE that needs to be added and click Add NE.
A dialog box is displayed, indicating that the NE is added successfully.
Step 10 Click OK.
A new NE has been added to the NE list.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The NMS must have proper communication with the NE to be created.
Procedure
Step 1 Choose File > New > NE from the Main Menu.
The Create NE dialog box is displayed.
Step 2 Choose RTN Series from the Object Tree and select a desired product.
Step 3 Enter the following information: ID, Extended ID, Name, and Remarks.
If... Then...
The Gateway Type parameter is set to Proceed to the next step.
Gateway
The Gateway Type parameter is set to Non- Select the gateway to which the NE
Gateway belongs, and go to Step 6.
NOTE
Security SSL is recommended for communication.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The NMS must have proper communication with the NE to be created.
l If the NE to be created is a non-gateway NE, the gateway NE to which the NE to be
created belongs must be created.
Procedure
Step 1 In NE List, click Add NE. Then, select Europe.
NOTE
NOTE
l SSL is recommended for communication with NEs. Set the port number to 5432 and perform the
following steps to replace the SSL certificate:
1. a. Delete the WebLCT\conf\certificate directory on the Web LCT.
2. Copy the server\etc\ssl\nemanager\default directory on the U2000 to the path WebLCT\conf on the
Web LCT. Rename default to certificate. Note that the installation path on the Web LCT should not
contain Chinese characters, spaces, or special characters.
3. c. Restart the Web LCT.
l Install the SSL certificate to the NE using the U2000. For details, see the Security Configuration
Maintenance & Hardening.
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The NE to be managed is already created in NE List.
Procedure
Step 1 In the NE List, select the target NE and click NE Login.
NOTE
NOTE
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l All the boards must be installed correctly.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 Double-click the NE icon to open the NE layout diagram.
Based on the slot layout, the NE automatically configures the logical boards that are required
but still not be configured for certain physical boards.
NOTE
If you configure the logical board using the Web LCT, perform the following operations:
Click the Slot Layout tab and click Add Physical Boards.
Step 2 Optional: On the slot to which the board is to be added, right-click, and then choose Add
XXX.
NOTE
Step 3 Optional: On the slot to which the board is to be deleted, right-click, and then choose Delete.
1. In the displayed confirmation dialog box, click OK.
2. In the dialog box that is displayed again for confirmation, click OK.
NOTE
Before deleting the board, delete the data, such as the service, clock, and protection, on the board.
Before configuring the COMBO port on an OptiX RTN 905 to function as a GE port, delete the VS2
logical board and add the EG2 logical board.
For OptiX RTN 950A that houses an MN1 board, delete the logical boards SP3S and SL1D integrated
on the CSHO before configuring the logical boards MP1 and CD1 respectively. In this manner, ports on
the logical boards MP1 and CD1 can be configured as Smart E1 ports and channelized STM-1 ports.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l All the boards and their SFP modules have been installed correctly.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Context
The following table lists the boards and the supported SFP module types.
Procedure
Step 1 Double-click the icon of an NE to open its slot layout.
NOTE
If you configure the logical board using the Web LCT, perform the following operations:
Click the Slot Layout tab.
Step 2 Right-click the target board and choose Path View. The board's path view is displayed.
NOTE
l It is recommended that you delete the ports that have no SFP module, to prevent the NMS from reporting
alarms related to SFP modules.
l For an SDH port, you can set the SFP module type in Mo mode. For an Ethernet port, you need to delete
the port and add it again if you want to reset the SFP module type. Set the SFP module type when adding
the port.
l For an EG4/EG2D board, its SFP port and fixed GE port share a physical channel. Therefore, if the SFP
port has no SFP module, delete the port and add it again. When adding the port, set Type of the SFP
module to Electrical Port.
----End
Prerequisites
l Only OptiX RTN 950 supports this operation.
l You must be an NM user with NE operator authority or higher.
l All the boards have been installed correctly.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree and then choose
Configuration > NE Properties from the Function Tree.
Step 2 On the Advance Properties tab page, set the backplane bus rate in Backplane Bus Mode.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 In the Main Topology, right-click the NE whose ID needs to be changed. Choose Properties.
The Properties dialog box is displayed.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 In the Main Topology, select the NE whose name is to be changed. Right-click on this NE,
and then choose Properties from the shortcut menu. The Properties dialog box is displayed.
NOTE
If you change the NE name using the Web LCT, perform the following operations:
In the NE Explorer, select the NE from the Object Tree, and choose Configuration > NE Attribute from the
Function Tree.
NOTE
Skip this step when the Web LCT is used for configuration.
Step 4 Click OK. Close the dialog box indicating the operation result.
The new name of the NE is displayed below the NE icon in the Main Topology.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
NOTE
To perform batch NE configurations on the U2000, choose Configuration > NE Batch Configuration > Set
NE Auto Creation Attributes from the main menu.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > NMS
Server from the Function Tree.
Step 2 Double-click NE Automatic Reporting and select Enabled from the drop-down menu.
Step 3 Set the IP address for the U2000 server based on the network plan.
NOTE
l For a single NMS server, you only need to set Server IP1.
l For dual NMS servers, set Server IP1 and Server IP2.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l When you need to synchronize the NE time with the time on the NMS server, the time
zone and time must be set correctly on the PC or server running the NMS software.
l When you need to synchronize the NE time with the time on the NTP server, the time on
the NTP server must be set correctly and the NTP protocol must be normal.
Procedure
Step 1 Choose Configuration > NE Batch Configuration > NE Time Synchronization from the
Main Menu.
Step 2 Click the NE Time Synchronization tab.
Step 3 In the physical view, select the NE whose time needs to be synchronized, and then click
Step 4 After the operation is complete, a dialog box is displayed indicating that the operation is
successful. Click Close.
Step 5 When you need to synchronize the NE time with the NMS time, set the time synchronization
mode and the related parameters.
1. Optional: The NE time is synchronized with the NMS time immediately.
a. Right-click the NE whose time needs to be synchronized, and then choose
Synchronize with NM Time from the shortcut menu.
b. Click Apply.
c. In the displayed confirmation dialog box, click Yes.
d. Close the displayed operation result dialog box.
NOTE
l When you need to synchronize the NE time with the NMS time, set Synchronous Mode to NM.
l When you need to synchronize the NE time with the time on the NTP server, set Synchronous Mode to
Standard NTP. Configure Standard NTP Authentication according to the requirements of the NTP
server.
Step 6 When you need to synchronize the NE time with the time on the NTP server, set the time
synchronization mode and the related parameters.
1. Set Synchronous Mode to Standard NTP.
2. Configure Standard NTP Authentication according to the requirements of the NTP
server.
3. Click Apply.
4. Click Close. The dialog box that is displayed indicating the operation result is closed.
5. Configure the upper-layer NTP server.
a. Select the NE, right-click in the configuration box where the standard NTP server is
configured, and then choose New.
c. Click Apply.
d. Close the displayed operation result dialog box.
6. Optional: Copy the configuration of the upper-layer NTP server.
NOTE
Before the copy operation, set Synchronous Mode to Standard NTP for the source NE and the target
NE.
a. Select the NE to be copied, right-click, and then choose Copy Standard NTP
Server.
b. Select the NE to be pasted, right-click, and then choose Paste Standard NTP
Server.
c. In the displayed confirmation dialog box, click Yes.
d. Close the displayed operation result dialog box.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l When you need to synchronize the NE time with the time on the NMS server, the time
zone and time must be set correctly on the PC or server running the NMS software.
l When you need to synchronize the NE time with the time on the NTP server, the time on
the NTP server must be set correctly and the NTP protocol must be normal.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > NE
Time Synchronization from the Function Tree.
If... Then...
You set Synchronous Mode to NULL Set the relevant parameters, and then click Apply.
You set Synchronous Mode to NM Set the relevant parameters, and then click Apply
to perform Step 5.
You set Synchronous Mode to Set the related parameters, and then click Apply to
Standard NTP perform Step 3.
NOTE
If you only need to synchronize the NE time and do not need to change the type of synchronization or
parameters, select the synchronization option corresponding to the NE, right-click, and choose Synchronize
with NM Time.
l If the NE is a gateway NE, set the external NTP server as the standard NTP server.
l If the NE is a non-gateway NE, set the gateway NE as the standard NTP server.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Context
NOTE
To perform batch NE configurations on the U2000, choose Configuration > NE Batch Configuration > NE
Time Localization Management from the main menu.
Procedure
Step 1 Choose Configuration > NE Batch Configuration > NE Time Localization Management
from the Main Menu.
NOTE
If you localize the NE time using the Web LCT, perform the following operations:
In the NE Explorer, select the NE from the Object Tree and then choose Configuration > NE Time
Localization Management from the Function Tree.
Step 2 Select the NE for time localization management from the Object Tree, and then click
.
NOTE
Skip this step when the Web LCT is used for configuration.
Step 3 Click the Time Zone drop-down list, and then set the time zone of the NE.
Step 4 Optional: Click DST, and then configure the related parameters.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l Synchronous Mode must be set to Standard NTP and Standard NTP Authentication
must be set to Enabled.
l The NTP protocol must be running properly and the NTP identity authentication must be
enabled on the NTP server.
NOTE
Configuring standard NTP keys using the Web LCT is performed during A.3.1.13 Synchronizing the NE
Time (Web LCT).
Procedure
Step 1 Choose Configuration > NE Batch Configuration > NE Time Synchronization from the
Main Menu.
Step 2 Click the Standard NTP Key Management tab.
Step 3 In the physical view, select the NE whose NTP keys need to be configured, and then click
.
Step 4 Click Add.
The Add Key and Password dialog box is displayed.
----End
Prerequisites
l An NE must be logged in to successfully.
l You must be an NM user with NE operator authority or higher.
NOTE
Procedure
Step 1 Select the corresponding operation steps according to the NE status.
If... Then...
An NE is not configured and the NE data In the Main Topology, double-click the NE
needs to be uploaded. that is not configured, and then perform Step
2 through Step 4.
An NE is configured with data and NE Perform Step 5 through Step 8.
data needs to be uploaded.
Step 2 In the displayed NE Configuration Wizard dialog box, select Upload, and then click Next.
A dialog box is displayed for confirmation.
Step 5 Choose Configuration > NE Configuration Data Management from the Main Menu.
Step 6 Select the NE whose data needs to be uploaded from the Object Tree, and then click
Step 7 Select the NE, click Upload. In the displayed confirmation dialog box, click OK.
The uploading is started. After the uploading is complete, the Operation Result dialog box is
displayed.
----End
Prerequisites
l You must be an NM user with NE maintainer authority or higher.
l The NE is created.
l The NE is in unsynchronized state.
NOTE
When an NE is in unsynchronized state, it carries the mark.
NOTE
Procedure
Step 1 Method 1:
1. Choose Configuration > Synchronize NE Configuration Data from the Main Menu.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
NOTE
To perform batch NE configurations on the U2000, choose Performance > Set NE Performance
Monitoring Time from the main menu.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree, and then choose Performance > NE
Performance Monitoring Time from the Function Tree.
Step 2 Configure the performance monitoring parameters of the NEs.
1. Select 15-Minute or 24-Hour.
2. Select Enabled or Disabled in Set 15-Minute Monitoring or Set 24-Hour Monitoring.
3. Set the start time and end time of the performance monitoring of NEs.
NOTE
– Generally, both Set 15-Minute Monitoring and Set 24-Hour Monitoring are enabled.
– You can specify the start time of the performance monitoring function, only after selecting Enabled
in the Set 15-Minute Monitoring or Set 24-Hour Monitoring area.
– You can specify the end time of the performance monitoring function, only after selecting Enabled
and then selecting To in the Set 15-Minute Monitoring or Set 24-Hour Monitoring area.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 In the NE Explorer, select the desired board.
Step 2 Choose Alarm > Alarm Suppression from the Function Tree.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
NOTE
Procedure
Step 1 Choose File > Discovery > Fiber/Cable/Microwave Link from the Main Menu.
Step 2 Select the board of the NE on which the fiber needs to be searched for or the IF board of the
NE on which radio links need to be searched for from the Physical Root.
Step 3 Click Search.
NOTE
l If Do not search the ports with Fiber/Cable created on NMS is selected, the port whoseoptical
transmission line or radio link is created is not searched on the NMS.
l If you need to check whether the connection ofan optical transmission line or a radio link is the same
as the actual connection of theoptical transmission line or radio link, do not select Do not search the
ports with Fiber/Cable created on NMS.
l If Do not search the ports with Fiber/Cable created on NMS is selected and all the selected ports
are created withoptical transmission lines or radio links, a dialog box is displayed after the search,
indicating that the search domain is null.
Step 4 After the operation is complete, a dialog box is displayed indicating that the operation is
successful. Click Close.
Step 5 In Physical Fiber/Cable Link List, select one or multipleoptical transmission lines or radio
links, and then click Create Fiber/Cable.
NOTE
l When you select one or multipleoptical transmission lines or radio links from Physical Fiber/Cable
Link List, the conflictingoptical transmission lines or radio links are automatically displayed in
Logical Fiber/Cable Link List. In this manner, you need to delete these conflictingoptical
transmission lines or radio links by referring to Step 6, and then create the links.
l When you createoptical transmission lines or radio links, No fiber to create is displayed if the
selectedoptical transmission lines or radio links are in the Already created state.
Step 6 When you select one or multiple conflictingoptical transmission lines or radio links from
Logical Fiber/Cable Link List, click Delete Fiber/Cable.
----End
Follow-up Procedure
If the information about theoptical transmission lines or radio links that are created using the
search method is incomplete, you can supplement the information by changing the
information about theoptical transmission lines or radio links.
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The relevant boards of various NEs must be created on the NMS.
l The resources of port IP addresses must be created if the automatic allocation of port IP
addresses is enabled.
NOTE
Procedure
Step 1 In the Main Topology, select the icon . Then, the cursor is displayed as "+".
Step 3 In the Select Fiber/Cable Source dialog box, select the source board and source port.
Step 4 Click OK. In the Main Topology, the cursor is displayed as "+".
Step 6 In the Select Fiber/Cable Sink dialog box, select the sink board and sink port.
Step 7 Click OK. Set the attributes of the fiber in the Create Fiber/Cable dialog box.
Step 8 Click OK. Then, the created fiber is displayed between the source NE and the sink NE in the
Main Topology.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The boards of all NEs have been created on the NMS.
l All Ethernet links are functioning properly.
l Port Mode at both ends of each Ethernet link is Layer 2 or Layer 3.
NOTE
Context
A microwave link is generally not imported to fibers/cables unless IP addresses need to be
automatically assigned at both ends of the microwave link. After IP addresses are assigned,
you need to delete the fibers/cables that the microwave link is imported by choosing File >
Discovery > Fiber/Cable/Microwave Link from the main menu.
Procedure
Step 1 Choose File > Discovery > Link from the main menu.
Step 2 Select the NE for which Ethernet links need to be searched from the Function Tree on the left
Step 6 Select the target links from Available Link in the Import Link window and click .
The links are displayed in Selected Link.
OptiX RTN 905
Other NEs
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Procedure
Step 1 Choose File > Create > Link from the Main Menu. The Create Link dialog box is displayed.
Step 3 Configure the attributes of the created extended ECC according to the data plan.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding IF board must be added on the NE Panel.
NOTE
Procedure
Step 1 In the Main Topology, choose File > New > Link.
The Create Link dialog box is displayed.
Step 3 Select the source NE from the drop-down list of Source NE.
Step 4 Select the sink NE from the drop-down list of Sink NE.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Procedure
Step 1 In the Main Topology, right-click, and then choose New > Subnet.
The Create Subnet dialog box is displayed.
Step 4 Click the Select Object tab, select a created NE from Available Objects, and then click
NOTE
l Click to add the selected object in the left pane to the right pane.
l Click to add all the objects in the left pane to the right pane.
Step 6 In the Main Topology, click in a blank area, and then the created subnet is displayed in the
position where you click.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Procedure
Step 1 In the Main Topology, right-click the NE or subnet that needs to be copied.
Step 3 Select the subnet that the NE or subnet needs to be pasted to.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Procedure
Step 1 In the Main Topology, right-click the NE or subnet that needs to be moved.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
NOTE
l Do not use the default NE IP address to access the public network (such as Internet).
l The default NE IP address is a temporary address, and is only used for management DCN plug-and-play.
The IP address must be modified in a timely manner.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication >
Communication Parameters from the Function Tree.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCC
Management from the Function Tree.
Step 2 Click the DCC Rate Configuration tab.
Step 3 Optional: Change the enable status of the DCC.
1. Double-click the cell in the Enabled/Disabled column to which the DCC corresponds.
Select the required state from the drop-down list.
2. Click Apply.
Step 4 Optional: Change the protocol type of the DCC.
1. Double-click the cell in the Protocol Type column to which the DCC corresponds.
Select the required protocol type from the drop-down list.
2. Click Apply.
NOTE
– For OptiX RTN 905, the 16th E1 is configured as a 2 Mbit/s external clock port, and external clock
source 2 refers to this 2 Mbit/s external clock port. For OptiX RTN 950/980, external clock source 1
refers to the external clock port on the system control board with a smaller slot ID, and external
clock source 2 refers to the external clock port on the system control board with a larger slot ID.
– When Protocol Type is set to TCP/IP for a port that is an ABR's port in a non-backbone area, IP
Address and Subnet Mask must be specified for the port (ABR stands for area border router). In
addition, it is recommended that the IP address of the port and the IP address of the port-located NE
be on different network segments.
– When Protocol Type is TCP/IP for a port and the port does not belong to the default process, you
need to set IP Address, Subnet Mask, and OSPF Subnet to which the port belongs.
NOTE
Set Protocol Type based on the management protocol used by the DCN solution.
3. Click OK.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
The DCC bytes required by the transparent transmission function must not be used.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCC
Management from the Function Tree.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCN
Management from the Function Tree.
Step 2 Click the Bandwidth Management tab.
NOTE
l If the default VLAN ID of the inband DCN conflicts with the VLAN ID in the service, the Ethernet
Board VLAN ID of the inband DCN can be changed manually.
l Ethernet Board VLAN ID is an NE-level parameter and its priority is lower than that of the VLAN ID
configured for a specific port.
l Bandwidth(kbit/s) specifies the bandwidth for inband DCN messaging on the Ethernet link.
l IF Port Bandwidth(kbit/s) specifies the bandwidth for inband DCN messaging on the radio link.
l NMS Port VLAN ID is available only when an NE supports distinguish Huawei DCN packets from
third-party DCN packets by VLAN ID.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree and then choose
Communication > DCN Management from the Function Tree.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCN
Management from the Function Tree.
Step 2 Click the Port Settings tab.
Step 3 Optional: Select E1 and set port parameters for the ports that need to use inband DCN.
Step 4 Optional: Select CSTM-1 and set port parameters for the ports that need to use inband DCN.
Step 5 Optional: Select FE/GE, configure the port parameters for the inband DCN function.
Step 6 Optional: Select IF, configure the port parameters for the inband DCN function.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
NOTE
l Do not use the default NE IP address to access the public network (such as Internet).
l The default NE IP address is a temporary address, and is only used for management DCN plug-and-play.
The IP address must be modified in a timely manner.
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree and then choose
Communication > DCN Management from the Function Tree.
NOTE
l If the Enabled Status is set to Enabled, this port can be used to support access of the management
information from the NMS.
l If the Enabled Status is set to Disabled, this port cannot be used to support access of the management
information from the NMS.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
The default extended ECC mode is Autosensing mode.
Procedure
Step 1 Click an NE in the NE Explorer. Choose Communication > ECC Management from the
Function Tree.
Step 2 Optional: You can enable the Auto mode function of the extended ECC.
3. Click Apply.
A confirmation dialog box is displayed.
4. Click OK.
Step 4 Set parameters for the extended ECC function in Autosensing mode at the client end.
1. Set Extended ECC Mode to Autosensing mode.
2. Set related parameters for the client end.
3. Click Apply.
A confirmation dialog box is displayed.
4. Click OK.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP
Protocol Stack Management from the Function Tree.
Step 2 Click the IP Route Management tab.
The created static route has a lower priority than a dynamic route.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree. Choose Communication >
Static Route Entries in the Kernel Route Table from the Function Tree.
Step 2 Click Create.
The Create a Static Route Entry in the Kernel Route Table dialog box is displayed.
Step 3 Click New.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP
Protocol Stack Management from the Function Tree.
Step 2 Click the OSPF Parameter Settings tab.
NOTE
Set the parameters according to the network plan.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the desired NE and choose Communication > IP Protocol Stack
Management from the Function Tree.
NOTE
Set parameters according to network planning information.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the desired NE and choose Communication > IP Protocol Stack
Management from the Function Tree.
Step 2 Click the Multi-area OSPF Management tab.
Step 3 Optional: Add a Network to an OSPF area.
1. Select the OSPF area to add a Network.
2. In Network Segment, click Add.
The Add dialog box is displayed.
3. Set the IP address and subnet mask of the new Network.
NOTE
Set parameters according to network planning information.
4. Click OK.
Step 4 Optional: Change a Network of an OSPF area.
1. In Network Segment, change the IP address and subnet mask of the target Network.
2. Click Apply.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the desired NE and choose Communication > IP Protocol Stack
Management from the Function Tree.
Step 2 Click the Multi-OSPF Management tab.
Step 3 Disable the automatic route aggregation function in an area.
1. In OSPF Area, select the area where routes need to be manually aggregated and set
Automatic Route Aggregation to Disabled.
2. Click Apply.
Step 4 In Manual Route Aggregation, click Add.
The Add dialog box is displayed.
Step 5 Set the IP address and subnet mask of the Network where routes are manually aggregated.
NOTE
Set parameters according to network planning information.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP
Protocol Stack Management from the Function Tree.
Step 2 Set the OSPF authentication type.
1. Click the Multi-area OSPF Management tab.
2. In OSPF Area, change the value of Authentication Type of the desired OSPF area.
NOTE
none indicates no authentication.
3. Click Apply.
Step 3 Set the passwords used for different types of DCN ports when different OSPF authentication
types are used.
NOTE
l If Authentication Type is set to none, all preset authentication passwords are cleared.
l MD5 Key is available only when Authentication Type is MD5.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP
Protocol Stack Management from the Function Tree.
NOTE
l The proxy ARP enables the NEs in the same network segment but different domains to communicate with
each other.
l To realize communication between such NEs, the source NE sends the ARP broadcast packet to address
the route to the destination NE. The NE with the proxy ARP function enabled checks the routing table
after sensing the ARP broadcast packet. If the routing table contains the destination address that the ARP
broadcast packet looks for, the NE returns an ARP spoofing packet, which enables the NE that sends the
ARP broadcast packet to consider that the MAC address of the NE that returns the ARP spoofing packet
is the MAC address of the destination NE. In this manner, the packet that is to be sent to the destination
NE is first sent to the NE with the proxy ARP function enabled and then forwarded to the destination NE.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree and then choose
Communication > L2DCN Management from the Function Tree.
Step 2 Click Query.
Step 3 Set Configuration Status.
----End
Prerequisites
You must be an NM user with NE monitor authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > NE ECC
Link Management from the Function Tree.
Step 2 Check whether the ECC route and related parameters are set correctly in NE ECC Link
Management List.
----End
Prerequisites
You must be an NM user with NE monitor authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP
Protocol Stack Management from the Function Tree.
Step 4 Check whether the IP routes and related parameters in the routing table are in accordance with
the plan.
----End
Prerequisites
You must be an NM user with NE monitor authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > Core
Routing Table from the Function Tree.
Step 2 Click Query. Close the displayed operation result dialog box.
----End
Prerequisites
You must be an NM user with NE monitor authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP
Protocol Stack Management from the Function Tree.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree and then choose
Communication > NE ECC Link Management from the Function Tree.
Step 2 Click Reachability Test and choose Ping or Trace Route from the drop-down menu.
The Ping Test or Trace Route dialog box is displayed.
Ping
Trace Route
Prerequisites
You must be an NM user with NE maintainer authority or higher.
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree and then choose
Communication > IP Protocol Stack Management from the Function Tree.
Step 2 Click Reachability Test and choose Ping Test or Trace Route from the drop-down menu.
The Ping Test or Trace Route dialog box is displayed.
Step 3 Set test parameters.
Ping Test
Trace Route
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select an NE from the Object Tree and then choose Communication >
SNMP Communication Parameters from the Function Tree.
Step 3 Set SNMP communications parameters of the NE based on the SNMP server requirements.
NOTE
l Set NMS IP Address to the IP address of the SNMP server that uses these communications
parameters. If there are no restrictions on the IP address of the SNMP server that accesses the NE,
set this parameter to 0.0.0.0. However, setting the NMS IP address to 0.0.0.0 causes certain security
risks. Therefore, make sure that you know the security risks when setting the NMS IP address to
0.0.0.0.
l If the NMS IP Address is set to 0.0.0.0, the NE does not support the Trap function.
l Verify Read/Write Permissions, Read Community Name, and Write Community Name of the
SNMP server based on the network plan. Read/Write Permissions, Read Community Name, and
Write Community Nam must take the same values as the right parameters set on the SNMP server.
l Set Report SDH Performance Trap, Report IP Performance Trap, and Report Alarm Trap to
Report if an SNMP server is required to automatically report trap packets when the SDH
performance crosses the threshold, the data performance crosses the threshold, or an alarm is
generated on a NE.
l It is recommended that Port take the default value.
l Set the Report Traps Version parameter based on the SNMP protocol version running on the
SNMP server.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Procedure
Step 1 Choose Administration > DCN Management from the Main Menu.
The Filter dialog box is displayed.
Step 4 Select the NE for which the standby gateway NE needs to be configured, double-click GNE2,
and select the desired standby gateway NE from the drop-down list.
NOTE
l Alternatively, you can select the NE for which a standby gateway NE needs to be configured, right-
click the NE, and select the desired gateway NE from the drop-down list.
l You can select several NEs for which a standby gateway NE needs to be configured, right-click the
NE, and select the desired gateway NE from the drop-down list.
NOTE
l If more than one standby gateway NE is required, set GNE3 and GNE4.
l If the main gateway NE fails, GNE2 takes over. If GNE2 fails, GNE3 takes over. If GNE3 fails,
GNE4 takes over.
l During a switch between gateway NEs, communication may be interrupted but services are not
affected.
Step 5 Click Apply. Then, close the operation result dialog box that is displayed.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
Background Information
l It is recommended that the LCT accesses an NE through Ethernet ports.
l If you need to initialize an NE or perform software loading by using the LCT, the LCT
needs to access the NE through Ethernet ports.
l OptiX RTN 910A does not support the extended NMS port.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Communication >
Access Control from the Function Tree.
Step 2 Select Enable Ethernet Access. Then, the NE allows NMS access through its Ethernet ports.
NOTE
To disable the Ethernet port-based access function, deselect Enable Ethernet Access.
Step 4 Click OK. Close the displayed operation result dialog box.
Step 5 Set Work Mode and Enabled/Disabled of the Ethernet network management port and NE
cascading port on the system control, switching, and timing board.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
OptiX RTN 950 housing CSH boards does not support this operation.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCN
Management from the Function Tree.
----End
A.3.8.3 Changing the Encapsulation Type and QinQ Type Domain for the
Ethernet NMS Port
This operation needs to be performed if the NMS port functions as a QinQ port and third-
party packets are transmitted through service channels.
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
OptiX RTN 950 housing CSH boards does not support this operation.
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree and choose Configuration >
Interface Management > NMS Interface from the Function Tree.
Step 2 Click the Basic Attributes tab and set Encapsulation Type to QinQ.
Step 3 Click the Layer 2 Attributes tab and change the value of QinQ Type Domain.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
If the LCT cannot access an NE through serial ports when the Enable Serial Port Access
check box is selected, the LCT access function may be disabled.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Communication >
Access Control from the Function Tree.
Step 2 Select the Enable Serial Port Access check box and select Access NM.
Step 3 Click Apply. Close the displayed operation result dialog box.
Step 4 Optional: Select the baud rate of the serial port from the Baud Rate drop-down list. Click
Apply. Close the displayed operation result dialog box.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
This operation is supported only by OptiX RTN 980 (housing CSHNA), OptiX RTN 950
(housing CSHU/CSHUA) and OptiX RTN 905.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Communication >
Access Control from the Function Tree.
Step 2 Click the Access Control Tab.
Step 3 Select the Enable OAM Access Control check box and select Access NM.
Step 4 Click Apply. Close the displayed operation result dialog box.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l An online user can create a user at a lower level.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Background Information
l The default NE user is at the monitoring level.
l For security of NE data, NE users are assigned operation rights based on their
responsibilities.
Procedure
Step 1 Select the required NE from the Object Tree in the NE Explorer. Choose Security > NE User
Management from the Function Tree.A dialog box is displayed, indicating that the operation
is successful.
Step 2 Close the dialog box.
NOTE
Skip this step when the Web LCT is used for configuration.
NOTE
l A Debug Level NE user has all security and configuration authorities, and has the right to run
debugging commands.
l A System Level NE user has all security and configuration authorities.
l A Maintenance Level NE user has some security authorities, some configuration authorities, the
communication setting authority, and the log management authority.
l An Operation Level NE user has all fault performance authorities, some security authorities, and
some configuration authorities.
l A Monitor Level NE user has the right to use all query commands, to log in, to log out, and to
change its own password.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l The NE user is created.
l An online user can change the password of a user at a lower level.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Background Information
NOTE
Procedure
Step 1 Select the required NE from the Object Tree in the NE Explorer. Choose Security > NE User
Management from the Function Tree.A dialog box is displayed, indicating that the operation
is successful.
Skip this step when the Web LCT is used for configuration.
Step 3 Select the required NE user from the NE user management list, and click Set Password.
The Set Password of NE User dialog box is displayed.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l An NE user has been created.
l The current online NE user is of a higher level than the NE user whose additional user
information will be configured.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 Select the required NE from the Object Tree in the NE Explorer. Choose Security > NE User
Management from the Function Tree.A dialog box is displayed, indicating that the operation
is successful.
Skip this step when the Web LCT is used for configuration.
Step 4 Select the desired NE user and configure additional information for the NE user.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree. Choose Security > NE
Security Parameters from the Function Tree.
Step 2 Set Warning Screen Switching and Warning Screen Information according to the network
plan.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the desired NE from the Object Tree in the NE Explorer and choose Security > NE
User Group Management from the Function Tree.
Step 2 Click Query and close the dialog box that is displayed.
Step 3 Click the desired NE user group to display all NE users in the group.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the desired NE from the Object Tree in the NE Explorer and choose Security > Online
User Management from the Function Tree.
Step 2 Click Query and close the dialog box that is displayed. The current online NE user
information is displayed.
Step 3 Select the desired online NE user, click Force Logout and close the dialog box that is
displayed.
----End
Prerequisites
l An NE user is created.
NOTE
Background Information
An NE cannot be logged in to and managed by the same NE user from different servers at the
same time. If the same NE user from different servers logs in to an NE at different time, the
first online user will be forcibly logged out of the NE.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree. Choose Security > NE
Login Management from the Function Tree.
Step 2 Select the required NE, and click Switch NE User.
The Switch Current NE User dialog box is displayed.
Step 3 Set User and Password of the user to be switched.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
This operation is supported only by OptiX RTN 980 (housing CSHNA), OptiX RTN 910A
OptiX RTN 905, OptiX RTN 950A, and OptiX RTN 950 (housing CSHU/CSHUA).
Procedure
Step 1 Select the desired NE from the object tree in the NE Explorer, and choose Communication >
Access Control from the function tree.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Context
l If the LCT requests to log in to an NE to which the NMS has logged in, the NE
determines whether to permit the login of the LCT according to the status of LCT
Access Control Switch.
l If the LCT requests to log in to an NE to which the NMS has not logged in, the NE
permits the login of the LCT regardless of the status of LCT Access Control Switch.
The NMS, however, can log in to an NE to which the LCT has logged in. That is, the
login of the LCT does not affect the login of the NMS. After the NMS user logs in to the
NE successfully, the logged LCT user is not affected. If LCT Access Control Switch is
set to Disable Access, the logged LCT user is also not affected.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Security > LCT
Access Control from the Function Tree.
Step 2 Select the required NE from the list, and click Access Allowed to enable the LCT access
function.
NOTE
To disable the LCT access function, click Disable Access.
----End
Prerequisites
The connection mode of the U2000 server is set to SSL.
NOTE
Background Information
l Two connection modes are supported, which are Common and Security(SSL) and
which can be queried on the U2000 server by running a query command.
l The default connection mode is Common.
NOTE
l When the U2000 server and its client are deployed on the same host and the U2000 server uses the
SSL connection mode, the client can log in to the server by using the common or SSL connection
mode. When the U2000 server and its client are deployed on the same host and the U2000 server
uses the common connection mode, the client can log in to the server only by using the common
connection mode.
l When the U2000 server and its client are deployed on different hosts, the client can log in to the
U2000 server only by using the same connection mode as the U2000 server.
l Security SSL is recommended for communication.
Procedure
Step 1 Start the U2000 client.
----End
A.4.4.2 Configuring the Connection Mode Between a U2000 Client and Its
Gateway NE
Two connection modes are supported between a U2000 client and its gateway NE, namely
common connection mode and Secure Sockets Layer (SSL) connection mode.
Prerequisites
l You must be an NM user with NE maintainer authority or higher.
l SSL licenses have been deployed on the gateway NE and the U2000 client according to
the SSL loading guide.
NOTE
Procedure
Step 1 Configure the connection mode of the U2000 client.
1. Choose Administration > DCN Management from Main Menu.
The Filter dialog box is displayed.
2. Click Cancel and then click the GNE tab.
The Filter GNE dialog box is displayed.
3. Click , choose the required gateway NE, and then click OK.
4. Click OK.
5. Select the required NE, right-click the NE, and choose Modify GNE from the shortcut
menu.
The Modify GNE dialog box is displayed.
6. Change the value of Connection Mode to Security SSL.
NOTE
If Connection Mode is set to Common or Common + Security SSL and the U2000 logs in to an NE
in common mode, data is transmitted between the U2000 and NE in plaintext and there are security
risks. Security SSL is recommended for communication.
7. Click OK.
A warning dialog box is displayed.
8. Click OK. Close the displayed dialog box.
If Connection Mode of a gateway NE is Security SSL, tools (such as the Web LCT and DC) that use
the common connection mode cannot communicate with the gateway NE.
3. Click Apply.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
NOTE
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree and choose Security > NE
RADIUS Configuration from the Function Tree.
Step 2 Enable an NE to be a RADIUS client.
1. Double-click RADIUS Client and choose Open from the drop-down menu.
2. Click Apply. Then, close the operation result dialog box that is displayed.
Step 3 Optional: Enable an NE to be a proxy server.
1. Double-click Proxy Server and choose Open from the drop-down menu.
NOTE
– Proxy Server can be set to Open only if RADIUS Client is set to Open.
– When an NE uses RADIUS authentication in the proxy NAS mode, set Proxy Server to Close.
2. Click Apply. Then, close the operation result dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l The RADIUS function has been enabled for the NE.
NOTE
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree and choose Security > NE
RADIUS Configuration from the Function Tree.
Step 2 Click the RADIUS Server Configuration tab.
The RADIUS Server Information dialog box is displayed.
Step 3 Click New.
The New RADIUS Server Information dialog box is displayed.
Step 4 Configure information about the RADIUS server or RADIUS proxy server.
l If an NE uses RADIUS authentication in the NAS mode or functions as a proxy server,
set the parameters as follows:
NOTE
– For both NE RADIUS authentication and NE usage accounting, set this parameter to
Authentication + Accounting or Accounting (when the Authentication function has been
enabled).
– Set Server Type to RADIUS Server.
– Set Server ID to IP Address and specify the IP address of the RADIUS server.
l If an NE uses RADIUS authentication in the proxy NAS mode, set the parameters as
follows:
NOTE
– For both NE RADIUS authentication and NE usage accounting, set this parameter to
Authentication + Accounting or Accounting (when the Authentication function has been
enabled).
– Set Server Type to Proxy Server.
– It is recommended that you set Server ID to NE ID and set the gateway NE as a proxy server.
Step 5 Click OK. Then, close the operation result dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l The RADIUS server or RADIUS proxy server have been configured for the NE.
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree and choose Security > NE
RADIUS Configuration from the Function Tree.
Step 2 Click New.
The New RADIUS Server Information dialog box is displayed.
Step 3 Click .
The Select Server dialog box is displayed.
Step 4 Select a configured server and click OK. Then, the system automatically associates out the
values of Function, Server ID, and Server Type.
Step 5 Configure the RADIUS parameters.
l If an NE uses RADIUS authentication in the NAS mode or functions as a proxy server:
NOTE
Step 6 Click OK. Then, close the operation result dialog box that is displayed.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the desired NE from the object tree in the NE Explorer and choose Configuration >
LLDP Configuration from the function tree.
Step 2 Set packet transmit parameters on the Protocol Time Parameters tab page.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the desired NE from the object tree in the NE Explorer and choose Configuration >
LLDP Configuration from the function tree.
Step 2 Configure LLDP for an Ethernet port on the Port Parameters tab page.
NOTE
You can also configure LLDP for IF boards on an OptiX RTN 950 using CSHU/CSHUA boards and an
OptiX RTN 950A using SLF2CSHO board.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l LLDP has been enabled for related Ethernet ports.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the desired NE from the object tree in the NE Explorer and choose Configuration >
LLDP Configuration from the function tree.
Step 2 Click Query and view the neighbor NE information on the Neighboring Node Information
tab page.
NOTE
Alternatively, perform the following steps to query the neighbor NE information on the U2000:
1. Choose Inventory > Base Station Report from the main menu.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The IF boards and the ODUs/RFUs to which the IF boards are connected have been
added in NE Panel.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Background Information
l This task configures a 1+0 radio link, a cross polarization interference cancellation
(XPIC) radio link, or a 1+1 radio link. To configure N+0 radio links, they must be
configured as N 1+0 radio links.
l For OptiX RTN 905 1E, this task configures a 1+0 radio link or an XPIC radio link. The
method for configuring an XPIC radio is different from the method for configuring an
XPIC radio link between other OptiX RTN 900 products.
l To configure 1+1 radio links between interconnected OptiX RTN 905 1E, perform the
operation A.5.2 Creating an IF 1+1 Protection Group and then configure a 1+0 radio
link between the two main OptiX RTN 905 1Es and a 1+0 radio link between the two
standby OptiX RTN 905 1Es.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Radio Link
Configuration from the Function Tree.
NOTE
If you create an IF 1+1 protection group using the Web LCT, perform the following operations:
Select an NE from the Object Tree in the NE Explorer. Click the Radio Link Configuration tab.
Step 2 Select the IF board connected to the microwave link from the drop-down list.
The basic information of the radio link connected to the IF board is displayed.
NOTE
Click Open the Opposite NE Explorer to enter the NE Explorer of the peer NE.
NOTE
l If the radio link is in a 1+1 or XPIC group, select any IF board connected to the radio link.
l If the radio link is not working correctly, the basic information of the peer NE is not displayed.
l For an ISM6 board, select an IF port to which the radio link is connected.
Step 3 Configure the basic attributes for the local NE and the peer NE as required.
l To configure a 1+0 non-protected radio link:
a. Select 1+0, and deselect the XPIC check box.
NOTE
For RTN 905 1E, Protection is unavailable, therefore, deselect XPIC.
b. Configure the basic attributes of the radio links.
NOTE
After 1+0 is selected and the configuration takes effect, the IF 1+1 protection group or XPIC
workgroup is deleted if the radio link is configured with 1+1 protection or XPIC.
l To configure 1+1 protected radio links:
a. Select 1+1.
b. Configure the basic attributes of the radio links.
c. Optional: Click Advanced, and configure the advanced attributes of the radio
links.
l To configure XPIC radio links for OptiX RTN 905 1E:
a. Select XPIC.
b. Configure the basic attributes of the radio links.
NOTE
To configure XPIC radio links under 1+1 protection, first configure two XPIC radio links,
and then configure IF 1+1 protection by following the instructions in A.5.2 Creating an IF
1+1 Protection Group.
Step 4 Configure IF attributes for the local NE and the peer NE on the radio link.
NOTE
If two XPIC links in an XPIC group are in the same N+1 protection group, configure the E1 capacity
consistently for the two XPIC links.
Step 5 Configure RF attributes for the local NE and the peer NE on the radio link.
NOTE
In IS3 or IS6 runtime mode, the transmit power can reach the configured maximum value in the
corresponding modulation scheme only after the microwave link is available.
l Configure a 1+0 non-protected radio link.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The IF boards and the ODUs to which the IF boards are connected have been added on
the NE Panel.
l The IF boards of an IF 1+1 FD/SD protection group have been configured in two paired
slots.
l The two RTN 905 1Es are connected using a service cascade cable.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Background Information
When a 1+0 service is converted into a 1+1 HSB protection configuration by configuring the
IF 1+1 protection group, the original E1 service is not interrupted. The board that carries the
original service, however, needs to be set as the working board.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1
Protection from the Function Tree.
NOTE
If you create an IF 1+1 protection group using the Web LCT, perform the following operations:
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from
the Function Tree. Click the IF 1+1 Protection tab.
NOTE
l When Working Mode is set to HSB, the equipment provides a 1+1 hot standby configuration for
the IF board and ODU at both ends of each hop of a radio link to realize the protection.
l When Working Mode is set to FD, the system uses two channels that have a frequency spacing
between them, to transmit and receive the same signal. The remote end selects signals from the two
received signals. With FD protection, the impact of the fading on signal transmission is reduced.
l When Working Mode is set to SD, the system uses two antennas that have a space distance between
them, to receive the same signal. The equipment selects signals from the two received signals. With
SD protection, the impact of the fading on signal transmission is reduced.
l When Revertive Mode is set to Revertive Mode, the NE that is in the switching state releases the
switching and enables the former working channel to return to the normal state some time after the
former working channel is restored to normal. It is recommended that you set this parameter to
Revertive Mode.
l When Revertive Mode is set to Non-Revertive, the NE that is in the switching state keeps the
current state unchanged unless another switching occurs even though the former working channel is
restored to normal.
l You can set WTR Time(s) only when Revertive Mode is set to Revertive Mode. It is
recommended that you use the default value.
l Enable Reverse Switching is valid only when Working Mode is set to HSB or SD.
l Generally, it is recommended that you set Enable Reverse Switching to Enabled.
l Each of the parameters Working Mode, Revertive Mode, WTR Time(s),Anti-jitter Time(s), and
Enable Reverse Switching must be set to the same value at both ends of a radio hop.
l It is recommended that you set Alarm Report Mode to Only protection group alarms. In this
case, protection group alarms are reported to indicate radio link faults.
l It is recommended that Anti-jitter Time(s) take its default value.
Step 4 Click OK. Close the displayed operation result dialog box.
Step 5 Optional: For RTN 905 1E, repeat the preceding steps to create an IF 1+1 protection group
on the other NE.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l An IF 1+1 protection group has been configured.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Background Information
When a 1+0 service is converted into a 1+1 service by configuring the IF 1+1 protection, the
original E1 service is not interrupted. To implement the conversion, set the board where the
1+0 service resides as the working board.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1
Protection from the Function Tree.
NOTE
If you modify the parameters of IF 1+1 protection using the Web LCT, perform the following operations:
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from
the Function Tree. Click the IF 1+1 Protection tab.
Step 2 Click Query. Then, close the dialog box that is displayed. Check the IF 1+1 protection groups
in Protection Group.
Step 3 Select the protection group whose parameters need to be modified. For example, right-click
the Alarm Suppression parameter to suppress the MW_BER_SD, MW_BER_EXC,
MW_RDI, RADIO_RSL_LOW, MAC_EXT_EXC, or MAC_FCS_EXC alarm or cancel the
suppression of the alarm.
NOTE
l Enable Reverse Switching is valid only when Working Mode is set to HSB or SD.
l Generally, it is recommended that you set Enable Reverse Switching to Enabled.
l Each of the parameters Working Mode, Revertive Mode, WTR Time(s),Anti-jitter Time(s), and
Enable Reverse Switching must be set to the same value at both ends of a radio hop.
l It is recommended that you set Alarm Report Mode to Only protection group alarms. In this case,
protection group alarms are reported to indicate radio link faults.
l It is recommended that Anti-jitter Time(s) take its default value.
l The Alarm Suppression parameter specifies whether to suppress the W_BER_SD, MW_BER_EXC,
MW_RDI, RADIO_RSL_LOW, MAC_EXT_EXC, or MAC_FCS_EXC alarms. This parameter is valid
only when Alarm Report Mode is set to Only protection group alarms.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The IF boards and the ODUs to which the IF boards are connected have been added on
the NE Panel.
l The IF board works in SDH, Hybrid (Native E1 + Ethernet) or Hybrid (STM-1 +
Ethernet) mode.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Background Information
l OptiX RTN 905 does not support this operation.
l When an N+0 service is converted into an N+1 service through the configuration of the
N+1 protection group, the original service is not interrupted.
l N+1 protection for OptiX RTN 980 using CSHNA boards is available in two modes:
enhanced N+1 protection and standard N+1 protection. For standard N+1 protection
configured for Integrated IP microwave, the Hybrid/AM attributes of microwave links in
an N+1 protection group must be set consistently. For enhanced N+1 protection, the
Hybrid/AM attributes can be set flexibly for the links.
l For Integrated IP microwave on other NEs, the Hybrid/AM attributes must be set
consistently for the microwave links in an N+1 protection group.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > N+1
Protection from the Function Tree.
NOTE
If you create an N+1 protection group using the Web LCT, perform the following operations:
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from
the Function Tree. Click the N+1 Protection tab.
Step 4 Configure the mapping relationship between the board and the slot.
1. Select Work Unit from Select Mapping Direction.
2. Select a port to which a working channel corresponds from Available Boards, and then
click .
3. Repeat Step 4.2 to select the ports to which other working channels correspond. Click
.
4. Select Protection Unit from Select Mapping Direction.
5. Select a port to which a protection channel corresponds from Available Boards, and
then click .
Step 5 Click OK. Then, click OK to close the dialog box that is displayed, indicating that the
operation is successful.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l The IF 1+1 protection must be configured.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1
Protection from the Function Tree.
NOTE
If you query the IF 1+1 protection status using the Web LCT, perform the following operations:
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from
the Function Tree. Click the IF 1+1 Protection tab.
Step 2 Click Query.Close the displayed operation result dialog box. In Protection Group, check the
IF 1+1 protection groups.
Step 3 Select the IF 1+1 protection group whose protection status needs to be queried. Click Query
Switch Status, and then close the displayed prompt dialog box. In Slot Mapping Relation,
check the protection status of the IF 1+1 protection group.
NOTE
If you query the IF 1+1 protection status using the Web LCT, perform the following operations:
Select the board from Slot Mapping Relation. Right-click on the selected board and choose Query
Switching Status from the shortcut menu to check the protection status of the IF 1+1 protection group.
----End
Prerequisites
l OptiX RTN 905 does not support this operation.
l You must be an NM user with NE administrator authority or higher.
l The IF N+1 protection must be configured.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > N+1
Protection from the Function Tree.
NOTE
If you query the IF N+1 protection status using the Web LCT, perform the following operations:
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from
the Function Tree. Click the N+1 Protection tab.
Step 2 Click Query, and then close the displayed prompt dialog box. In Protection Group, check
the IF N+1 protection groups.
Step 3 Select the protection group whose protection status needs to be queried.
Step 4 Click Query Switch Status, and then close the displayed dialog box. In Slot Mapping
Relation, check the IF N+1 protection status.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The IF 1+1 protection must be configured.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Context
Two RTN 905 1E NEs are cascaded through a cascade cable and form a 1+1 protection group.
Switching operations are conducted only on the main NE.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1
Protection from the Function Tree.
NOTE
If you perform IF 1+1 protection switching using the Web LCT, perform the following operations:
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from
the Function Tree. Click the IF 1+1 Protection tab.
Step 2 In Protection Group, select the protection group for protection switching.
Step 3 In Slot Mapping Settings, select a working unit or the protection unit of the protection group,
and then right-click the selected unit.
Step 4 Choose the required switching mode from the shortcut menu.
The system displays the dialog box that indicates the successful operation.
Step 6 Click Query Switching Status and check whether the switching is successful, and then close
the displayed prompt dialog box.
NOTE
If you perform IF 1+1 protection switching using the Web LCT, perform the following operations:
Select the working unit or the protection unit, right-click Query Switching Status and check whether the
switching is successful.
----End
Prerequisites
l OptiX RTN 905 does not support this operation.
l You must be an NM user with NE operator authority or higher.
l The IF N+1 protection must be configured.
l The N+1 protection protocol is enabled.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > N+1
Protection from the Function Tree.
NOTE
If you perform IF N+1 protection switching using the Web LCT, perform the following operations:
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from
the Function Tree. Click the N+1 Protection tab.
Step 2 In Protection Group, select the protection group for protection switching.
Step 3 In Slot Mapping Relation, select a working unit or the protection unit of the protection
group, and then right-click the selected unit.
Step 4 Choose the desired switching mode from the shortcut menu.
Step 5 In the dialog box that is displayed, click OK.
The system displays the dialog box that indicates the successful operation.
Step 6 Click Close.
Step 7 Click Query Switch Status to check whether the switching operation is successful.
----End
Prerequisites
l OptiX RTN 905 does not support this operation.
l You must be an NM user with NE operator authority or higher.
l The IF N+1 protection must be configured.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Precautions
l Stopping the N+1 protection protocol causes a failure of the N+1 protection.
l When services are switched onto the protection channel, stopping the N+1 protection
protocol causes switchover of the services back to the working tunnel. At this time, if the
working channel is normal, the services are transiently interrupted. If the working
channel is faulty, the services are interrupted until the working channel is restored to
normal or the N+1 protection protocol is started.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > N+1
Protection from the Function Tree.
NOTE
If you start/stop the N+1 protection protocol using the Web LCT, perform the following operations:
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from
the Function Tree. Click the N+1 Protection tab.
Step 2 In Protection Group, select the protection group whose N+1 protection protocol needs to be
started.
Step 3 Click Start Protocol or Stop Protocol. Then, close the displayed prompt dialog box.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The IF boards and the ODUs to which the IF boards are connected have been added on
the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Background Information
l OptiX RTN 910A, OptiX RTN 905, OptiX RTN 950A, OptiX RTN 950 using CSHU/
CSHUA boards, and OptiX RTN 980 using CSHNA boards support EPLA.
l Only OptiX RTN 910A, OptiX RTN 950A, and OptiX RTN 950 using CSHU/CSHUA
boards support EPLA+.
l Only cascaded OptiX RTN 905 1E NEs support PLA.
l For the limitations of PLA/EPLA/EPLA+, see Feature Dependencies and Limitations of
PLA/EPLA/EPLA+ in the Feature Description.
l When you create or delete a PLA group on an ISU2 or ISX2 board, the board is cold
reset.
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree. Choose Configuration >
Physical Link Aggregation from the Function Tree.
Step 2 Click New.
The Create Physical LAG dialog box is displayed. The Create Physical LAG dialog box is
displayed.
l OptiX RTN 910A
Super EPLA
NOTE
– When Scheduling Mode is Mode B, In hitless mode, E-band link bandwidth changes do not affect
the transmission of high-priority services. In this mode, high-priority services are transmitted on
common-band links, and low-priority services are transmitted on E-band links. However, if high-
priority services exceed the common-band link bandwidth upon a burst, the excessive traffic cannot
be transmitted by E-band links and is discarded.
– When Scheduling Mode is Mode A, In common mode, high-priority and low-priority services are
distributed to common-band and E-band links based on their link bandwidths, implementing inter-
frequency AM.
– When Scheduling Mode is Mode B, This threshold can be specified for a Super EPLA group in
hitless mode. Only an SP queue can be configured with a PHB. Services in this SP queue and other
queues with higher-priorities are high-priority services.
l OptiX RTN 980L
NOTE
– If an OptiX RTN 905 2E is configured with cascade EPLA, the cascade port 8-VS2-1 has two
internal channels: channel 1 and channel 2. Channel 1 must connect to port 3-ISV3-1, and channel 2
must connect to port 4-ISV3-1.
– If an OptiX RTN 905 1E is configured with cascade PLA/EPLA, only channel 1 at the cascade port
8-VS2-1 can be configured as the cascade channel.
– When configuring an OptiX RTN 905 1E/2E as the master NE, configure the cascading channel
connecting to IF boards on the slave NE.
– When configuring an OptiX RTN 905 1E/2E as the slave NE, configure the cascading channel
connecting to its IF boards.
– If an OptiX RTN 905 2E that runs V100R007C10 or earlier software and is configured with IF 1+1
protection is the slave NE, the two cascading channels must be added to the EPLA group. If an
OptiX RTN 905 2E that runs V100R008C00 software and is configured with 1+1 protection is the
slave NE, only the cascading channel connected to the main IF board must be added to the EPLA
group.
Step 4 Click OK. Then, close the dialog box that is displayed.
Step 6 Optional: When RTN 980L is used as long-haul microwave, you can enable hitless EPLA
switching by setting the Hitless Switching parameter.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l A PLA/EPLA/EPLA+/Super EPLA group has been configured.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree and then choose
Configuration > Physical Link Aggregation from the Function Tree.
Step 2 Click Query. View the information about the PLA/EPLA/EPLA+/Super EPLA group in
Physical Link Aggregation List.
NOTE
l .Minimum Active Links specifies the minimum number of available links in a PLA group and helps to
trigger ERPS switching even if not all members in the PLA group fail.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface
Management > Microwave Interface from the Function Tree.
Step 3 Configure the Ethernet frame header compression function and the error frame discarding
over air interfaces function.
NOTE
l If Speed Transmission at L2 is set to Enabled, the Layer-2 Ethernet packets transmitted at microwave
ports will be compressed to improve transmission efficiency.
l The settings of Speed Transmission at L2 must be the same at both ends of a radio link.
l If Speed Transmission at L3 is set to Enabled, the IP packets transmitted at microwave ports will be
compressed to improve transmission efficiency.
l The settings of Speed Transmission at L3 must be the same at both ends of a radio link.
Step 4 Click Apply. Then, close the dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l Only ISV3 boards in IS3 mode support this operation.
Context
NOTE
Do not enable enhanced Ethernet frame compression on an NE if the NE interconnects with an NE that does
not support enhanced Ethernet frame compression. Otherwise, services and inband DCN communication
between the two NEs are interrupted.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the desired IF board from the Object Tree in the NE Explorer. Choose Configuration >
Enhanced Compression from the Function Tree.
Step 2 Configure enhanced Ethernet frame compression for an egress queue at the IF port on the IF
board.
NOTE
If enhanced Ethernet frame compression is enabled for a QoS queue at an IF port, Ethernet frame header
compression (L2+L3) is automatically enabled for the IF port.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
l RTN 910A/RTN 980/RTN 950A: AES-based encryption at air interfaces is supported
only by ISV3 boards in IS3 mode.
l RTN 950: AES-based encryption at air interfaces is supported only when CSHU/
CSHUA boards work with ISV3 boards in IS3 mode.
l RTN 980L: AES-based encryption at air interfaces is supported only by ISV3 boards in
IS3 mode or LH ACCP mode.
l RTN 905 does not support AES-based encryption at air interfaces.
l AES-based encryption at air interfaces cannot be enabled when an ISV3 interconnects
with an ISM6 board or an RTN 905.
Procedure
Step 1 In the NE Explorer, select the desired ISV3 board from the Object Tree and choose
Configuration > Radio Interface Encryption from the Function Tree.
Step 4 Set the key update interval. You can specify Key Negotiation Interval to periodically update
keys or click Negotiate Key Manually to forcibly update keys.
Step 5 Click Set Authentication Code. In the displayed Set Authentication Code dialog box, set
authentication code, and click OK.
NOTE
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding board must be added on the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Background Information
When an unprotected service is converted into a linear MSP service by configuring the linear
MSP, the original services are not interrupted.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear MS
from the Function Tree.
Step 4 Click OK, and then close the dialog box that is displayed.
----End
Follow-up Procedure
l In the case of the 1:N linear MSP, you need to configure bidirectional cross-connections
between the services and the working channels later. If extra services need to be
transmitted, it is necessary to configure bidirectional cross-connections between the extra
services and the protection channels.
l In the case of the 1+1 linear MSP, you need to configure bidirectional cross-connections
between the services and the working channels later.
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The linear MSP must be configured.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear MS
from the Function Tree.
Step 2 Click Query > Query Protection Group to query the current linear MSP group. Then close
the dialog box that is displayed.
Step 4 Click Query > Query Switching Status In Slot Mapping Settings, query the status of the
linear MSP.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The linear MSP must be configured.
l The protection protocol is enabled.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear MS
from the Function Tree.
Step 2 In Protection Group, select the MSP group to be switched. In Slot Mapping Settings, select
the working unit or protection unit, and then right-click.
Step 3 Right-click and select the required switching mode.
If the switching of a higher priority occurs in a channel, the switching of a lower priority will not occur
in the channel.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l The linear MSP must be configured.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Precautions
l Stopping the ring MSP protocol causes failure of ring MSP.
l When services are switched onto the protection channel, stopping the ring MSP protocol
causes the services to switch back to the working channel. At this time, if the working
channel is normal, the services are transiently interrupted; if the working channel is
faulty, the services are interrupted until the working channel is restored to normal or the
protocol is started.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear MS
from the Function Tree.
Step 2 In Protection Group, select the MSP group for which the linear MSP protocol is to be
stopped.
Step 3 Click Start Protocol or Stop Protocol, and then close the prompt dialog box that is
displayed.
Step 4 Click Query > Query Protection Group, close the dialog box that is displayed, and check
Protocol Status.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Background Information
l Only OptiX RTN 980 support this operation.
l The number of nodes on an MSP ring should not exceed 16.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
Ring MS from the Function Tree.
Step 5 Click OK. Then, close the dialog box that is displayed.
----End
Prerequisites
l Only OptiX RTN 980 support this operation.
l You must be an NM user with NE administrator authority or higher.
l A ring MSP protection group has been configured.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
Ring MS from the Function Tree.
Step 2 Click Query.
Step 3 Select Query Protection Group from the drop-down list. Then, close the dialog box that is
displayed. In Protection Group, check basic information about the protection group.
Step 4 Select the required protection group and click Query.
Step 5 Select Query Switching Status from the drop-down list. Then, close the dialog box that is
displayed. In Slot Mapping Relation, check the switching status of the protection group.
----End
Prerequisites
l Only OptiX RTN 980 support this operation.
l You must be an NM user with NE administrator authority or higher.
l MSP Ring has been configured for a service.
l The MSP ring protocol has been enabled.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Background Information
NOTICE
All switching operations except exercise switching may interrupt services.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
Ring MS from the Function Tree.
Step 2 Select the required service, right-click the service, and select a switching mode from the drop-
down list.
Then, a confirmation dialog box is displayed.
Step 3 Click Yes. Then, close the dialog box that is displayed.
Step 5 Select Query Switching Status from the drop-down list. Then, close the dialog box that is
displayed.
Step 6 Check whether the service is already switched to the protection channel.
----End
Prerequisites
l Only OptiX RTN 980 support this operation.
l You must be an NM user with NE administrator authority or higher.
l MSP Ring has been configured for a service.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
Ring MS from the Function Tree.
Step 2 Stop the MSP ring protocol.
1. Select the required protection group and click Stop Protocol.
NOTICE
After the MSP ring protocol is stopped, the protection group fails. In addition, services
are unavailable until the working channel is restored or the MSP ring protocol is
restarted, if services have been switched to the protection channel.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding boards have been added in the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Background Information
l When an unprotected service is converted into a linear MSP service by configuring the
packet-based linear MSP, the service is not interrupted.
l Only the 1:1 packet-based linear MSP can be created.
Procedure
Step 1 In the NE Explorer, select an NE from the Object Tree and choose Configuration > Packet-
based linear MS from the Function Tree.
Step 3 Configure the parameters for the new linear MSP group.
----End
Follow-up Procedure
In the case of the 1:1 linear MSP, you need to configure bidirectional cross-connections
between the services and the working channel. If extra services need to be transmitted, you
need to configure bidirectional cross-connections between the extra services and the
protection channel.
Prerequisites
l You must be an NM user with NE operator authority or higher.
l A packet-based linear MSP group has been configured.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select an NE from the Object Tree and choose Configuration > Packet-
based linear MS from the Function Tree.
Step 2 Choose Query > Query Protection Group and close the dialog box displayed.
Step 3 Select the packet-based linear MSP group whose protection status needs to be queried in
Protection Group.
Step 4 Choose Query > Query Switching Status. Query the status of the packet-based linear MSP
group in Slot Mapping Relation.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l A packet-based linear MSP group has been configured.
l The linear MSP protocol has been enabled.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select an NE from the Object Tree and choose Configuration > Packet-
based linear MS from the Function Tree.
Step 2 Select the MSP group on which the switching is to be performed in Protection Group and
right-click the working or protection unit in Slot Mapping Relation.
Step 3 Choose the desired switching mode from the shortcut menu.
Step 4 Click OK. Then, close the operation result dialog box that is displayed.
NOTE
If switching of a higher priority has occurred on the working or protection channel, the configured
switching will not be triggered.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l A packet-based linear MSP group has been configured.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Precautions
l Disabling the linear MSP protocol causes the failure of the linear MSP.
l When services are switched to the protection channel, disabling the linear MSP protocol
switches the services back to the working channel. At this time, if the working channel is
normal, the services are transiently interrupted. If the working channel is faulty, the
services are interrupted until the working channel is restored to normal or the linear MSP
protocol is started.
Procedure
Step 1 In the NE Explorer, select an NE from the Object Tree and choose Configuration > Packet-
based linear MS from the Function Tree.
Step 2 Select the protection group for which the linear MSP protocol needs to be disabled in
Protection Group.
Step 3 Click Start Protocol or Stop Protocol and close the dialog box displayed.
Step 4 Choose Query > Query Protection Group and close the dialog box displayed. View
Protocol Status.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding source and sink boards must be added on NE Panel.
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH/PDH
Service Management from the Function Tree.
Step 2 Click Options to change the VC-12 timeslot numbering policy used by the cross-connection.
NOTE
If you create the cross-connections of point-to-point services using the Web LCT, perform the following
operations:
Click Scheme to change the VC-12 timeslot numbering policy used by the cross-connection.
If you create the cross-connections of point-to-point services using the Web LCT, perform the following
operations:
Click New.
The Create SDH/PDH Service dialog box is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding source and sink boards must be added on NE Panel.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH/PDH
Service Management from the Function Tree.
Step 2 Click Options to change the VC-12 timeslot numbering policy used by the cross-connection.
NOTE
If you create the cross-connections of SNCP services using the Web LCT, perform the following operations:
Click Scheme to change the VC-12 timeslot numbering policy used by the cross-connection.
If you create the cross-connections of SNCP services using the Web LCT, perform the following operations:
Click Create SNCP.
The Create SNCP Service dialog box is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding source and sink boards must be added in the NE Panel.
l The E1 cross-connections must be created. The IF boards in the cross-connections must
support the E1 priority function. The E1 priorities must be set already and need to be
modified.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH/PDH
Service Management from the Function Tree.
Step 2 Click Query, A confirmation dialog box is displayed, Click Yes.
Step 4 Right-click the E1 service and choose Expand to Unidirectional from the shortcut menu.
Step 5 Right-click the E1 service and choose Deactivate from the shortcut menu.
NOTE
Skip this step when the Web LCT is used for configuration.
Step 6 In the displayed dialog box, click Yes. In the second displayed dialog box, click OK and close
the dialog box that is displayed.
NOTE
Skip this step when the Web LCT is used for configuration.
Step 7 If the number of E1 services configured on an IF board is smaller than Full E1 Capacity,
select the required E1 service, right-click the service, and choose Modify from the short-cut
menu. Then, change the E1 priority of each timeslot in the dialog box that is displayed.
NOTE
If you modify the priorities of E1 services using the Web LCT, perform the following operations:
If the number of E1 services configured on an IF board is smaller than Full E1 Capacity, double-click E1
Priority and select the target E1 priority from the drop-down list.
NOTE
For an SNCP service, you need to modify E1 Priority of only the services that are transmitted to the
working source and the protection source of the SNCP service.
Step 8 If the number of E1 services configured on an IF board is the same as Full E1 Capacity, do
as follows to interchange the priority levels of two E1 services:
1. Add one to Full E1 Capacity for both ends of the radio link.
2. Change E1 Priority of the E1 service with a higher priority to Low.
3. Change E1 Priority of the E1 service with a lower priority to High.
4. Change Full E1 Capacity to the original values for both ends of the radio link.
NOTE
If Full E1 Capacity uses its maximum value, do as follows to interchange the priority levels of two services.
1. Delete either E1 service.
2. Change the priority of the other E1 service.
3. Add the E1 service that was deleted, setting its E1 Priority to the required value.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
This operation applies to IF boards that support Integrated IP microwave.
Procedure
Step 1 In the NE Explorer, select the IF board from the Object Tree and choose Alarm > Triggered
Alarm Insertion from the Function Tree.
Step 2 Set Insert E1_AIS to TU_AIS.
NOTE
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The SNCP protection group must be configured.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SNCP
Service Control from the Function Tree.
Step 2 Select the SNCP protection group, and then right-click Switching Condition to which the
working service corresponds.
NOTE
If you configure the automatic switching of SNCP services using the Web LCT, perform the following
operations:
Select the SNCP protection group, and then right-click SD Initiation Condition to which the working service
corresponds.
Step 3 Set the initiation condition for the working service. Click OK.
NOTE
The conditions for automatic switching of higher order services are different from those of lower order
services.
NOTE
If you configure the automatic switching of SNCP services using the Web LCT, perform the following
operations:
Right-click SD Initiation Condition to which the protection service corresponds.
Step 5 Set the initiation condition for the protection service. Click OK.
NOTE
It is recommended that you set Switching Condition of the working service to be the same as
Switching Condition of the protection service.
If you configure the automatic switching of SNCP services using the Web LCT, it is recommended that
you set Switching Condition of the working service to be the same as Switching Condition of the
protection service.
Step 6 Click Apply, and then close the dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The cross-connections of the service must be configured and the service must not be
used.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH/PDH
Service Management from the Function Tree.
NOTE
If you delete cross-connections using the Web LCT, perform the following operations:
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Cross-Connection
Configuration from the Function Tree.
NOTE
Skip this step when the Web LCT is used for configuration.
1. Right-click the service and choose Deactivate from the shortcut menu.
Then, a dialog box is displayed, querying whether you need to deactivate the selected
service.
2. Click Yes.
Then, a dialog box is displayed, indicating that this operation will clear the
corresponding service data on the NE side.
3. Click Yes. Then, close the dialog box that is displayed.
Step 5 Click Query. The queried information should show that the cross-connection is already
deleted.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The unidirectional cross-connection of the normal service must be configured and the
source of the cross-connection must be a line board.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Background Information
When this task is performed to convert a normal service into an SNCP service, the original
services are not interrupted.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH/PDH
Service Configuration from the Function Tree.
NOTE
If you convert a normal service into an SNCP service using the Web LCT, perform the following operations:
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Cross-Connection
Configuration from the Function Tree.
Step 2 Optional: If a bidirectional SDH service is created, select this service in Cross-Connection.
Right-click the selected service and choose Expand to Unidirectional from the shortcut
menu.
NOTE
If you convert a normal service into an SNCP service using the Web LCT, perform the following operations:
If a bidirectional SDH service is created, select this service in Cross-Connection. Right-click the selected
service and choose Expand from the shortcut menu.
Step 3 Select the unidirectional service. Right-click the selected service and choose Convert to
SNCP Service from the shortcut menu.
NOTE
If you convert a normal service into an SNCP service using the Web LCT, perform the following operations:
Select the unidirectional service. Right-click the selected service and choose Convert to SNCP from the
shortcut menu.
Then, a dialog box is displayed, querying whether you need to perform this operation.Then,
the Convert to SNCP Service dialog box is displayed.
Skip this step when the Web LCT is used for configuration.
Then, the Create SNCP Service dialog box is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The SNCP cross-connection in the receive direction must be configured.
l The current service must be transmitted on the working path.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Background Information
When this task is performed to convert an SNCP service into a normal service, the original
services are not interrupted.
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > SDH Service Configuration from the Function Tree.
NOTE
If you convert an SNCP service into a normal service using the Web LCT, perform the following operations:
Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > Cross-
Connection Configuration from the Function Tree.
Step 2 In Auto-Created Cross-Connection, select the configured service. Right-click and choose
Convert to Non-Protection Service from the shortcut menu.
NOTE
If you convert an SNCP service into a normal service using the Web LCT, perform the following operations:
In Auto-Created Cross-Connection, select the configured service and click Service Convert. Choose
SNCP Protection Service Convert to Non-Protection Service or SNCP Working Service Convert to
Non-Protection Service from the displayed menu.
To convert the cross-connection into a cross-connection between the working source and the service sink,
choose SNCP Working Service Convert to Non-Protection Service. To convert the cross-connection into a
cross-connection between the protection source and the service sink, choose SNCP Protection Service
Convert to Non-Protection Service.
Then, a dialog box is displayed, querying whether you need to perform this operation.
----End
Follow-up Procedure
You also need to delete the unidirectional cross-connection between the service source and the
working path or the unidirectional cross-connection between the service source and the
protection path. The SNCP service can be converted into the normal service both in the
receive direction and the transmit direction only after the deletion.
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l TDM services must be configured.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH/PDH
Service Management from the Function Tree.
NOTE
If you query TDM services using the Web LCT, perform the following operations:
Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > Cross-
Connection Configuration from the Function Tree.
Step 4 Close the displayed prompt dialog box. In Cross-Connection, query the TDM services.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The SNCP protection group must be configured.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SNCP
Service Control from the Function Tree.
Step 2 Select the SNCP protection group for SNCP service switching.
Step 3 Click Function. Select the required switching mode from the displayed menu.
Step 5 The system displays a prompt dialog box, indicating that the operation is successful. Then,
close the displayed prompt dialog box.
Step 6 Choose Function > Query Switch Status to check whether the switching operation is
successful.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The SNCP protection group must be configured.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SNCP
Service Control from the Function Tree.
Step 2 Select the SNCP protection group whose service protection status needs to be queried.
Step 3 Click Function > Query Switch Status, and then close the displayed prompt dialog box.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding board must be added on the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > Interface Management > SDH Interface from the Function Tree.
Step 2 Select By Board/Port(Channel), and select Port or VC4 Channel from the list box.
Step 3 Set the parameters of SDH ports.
1. Choose Port from the drop-down list, and then configure the parameters of SDH ports.
Click Apply.
A dialog box is displayed for confirmation.
2. Click OK.
The dialog box is displayed again for confirmation.
3. Click OK, and then close the dialog box that is displayed indicating the operation result.
Step 4 Set the parameters of VC-4 paths.
1. Choose VC4 Channel from the drop-down list, and then configure the parameters of
VC-4 paths.
2. Click Apply.
A dialog box is displayed for confirmation.
3. Click OK, and then close the dialog box that is displayed indicating the operation result.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
NOTE
l For OptiX RTN 905 housing an MN1 board, you can set Service Mode for ports on the logical board
MP1/VS2/CD1 to TDM or Packet.
l For OptiX RTN 950A housing an MN1 board, you can set Service Mode for ports on the logical board
MP1/CD1 to TDM or Packet.
Procedure
Step 1 In the NE Explorer, select the logical board from the Object Tree and then choose
Configuration > Port Mode Configuration from the Function Tree.
Step 2 Select the required port and configure Service Mode according to the planning information.
CD1 configuration based on STM-1 ports (63 E1 channels work in the same mode):
Step 3 Click Apply, and then close the dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding board must be added on the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > PDH Interface from the Function Tree.
NOTE
On RTN 950A housing SLF2CSHO, Port Service Type can be set to T1 for PDH ports on SP3S/SP3D.
Step 7 Click Yes, and then close the dialog box that is displayed indicating the operation result.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding board must be added on the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select an SDH interface board in the NE Explorer Choose Configuration > Overhead
Management > Regenerator Section Overhead from the Function Tree.
3. Click OK.
Step 5 Click Yes, and then close the dialog box that is displayed indicating the operation result.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding board must be added on the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select SDH interface board from the Object Tree in the NE Explorer. Choose Configuration
> Overhead Management > VC4 Path Overhead from the Function Tree.
Step 2 Choose Display in Text Format or Display in Hexadecimal.
4. Click OK.
5. Click Apply.
A dialog box is displayed for confirmation.
6. Click OK, and then close the dialog box that is displayed indicating the operation result.
Step 4 Optional: Configure the C2 byte.
1. Click the Signal Flag C2 tab.
2. Configure the required parameters.
3. Click Apply.
A dialog box is displayed for confirmation.
4. Click OK. Close the dialog box that is displayed indicating the operation result.
Step 5 Optional: Configure the termination mode of the VC-4 overhead.
1. Click the Overhead Termination tab.
2. Configure VC4 Overhead Termination.
3. Click Apply.
A dialog box is displayed for confirmation.
4. Click OK, and then close the dialog box that is displayed indicating the operation result.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding board must be added on the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > Overhead Management > VC12 Path Overhead from the Function Tree.
Step 2 Configure the J2 byte.
1. Click the Trace Byte J2 tab.
2. Choose Display in Text Format or Display in Hexadecimal.
3. Double-click the parameter whose value needs to be changed.
The Please input the overhead byte dialog box is displayed.
4. Configure overhead bytes.
5. Click OK.
6. Click Apply.
A dialog box is displayed for confirmation.
7. Click OK, and then close the dialog box that is displayed.
Step 3 Configure the signal flag.
1. Click the Signal Flag V5 tab.
2. Click Options.
The Options dialog box is displayed.
3. Click Extended Mode.
4. Click OK.
5. Configure the signal flag in the V5 byte.
6. Click Apply.
A dialog box is displayed for confirmation.
7. Click OK, and then close the dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding boards must be added in the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select a channelized STM-1 interface board from the Object Tree and
choose Configuration > Interface Management > Path Configuration from the Function
Tree.
----End
Context
NOTE
RTN 905 does not support ATM services.
Prerequisites
l For an E1 port on the logical board MP1 of an OptiX RTN 905, Service Mode has been
set to CES. For information about how to set Service Mode of an E1 port to CES, see
A.8.2 Setting Working Modes of E1 Ports.
l For an OptiX RTN 950A that houses an MN1 board, set Service Mode of the ports on
the logical board MP1 to CES by following instructions in A.8.2 Setting Working
Modes of E1 Ports.
l You must be an NM user with NE administrator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration >
Interface Management > PDH Interface from the Function Tree.
Step 4 Click Apply. Then, close the dialog box that is displayed.
----End
Prerequisites
l For an E1 port on the logical board MP1 of an OptiX RTN 905, Service Mode has been
set to CES. For information about how to set Service Mode of an E1 port to CES, see
A.8.2 Setting Working Modes of E1 Ports.
l For an OptiX RTN 950A that houses an MN1 board, set Service Mode of the ports on
the logical board MP1 to CES by following instructions in A.8.2 Setting Working
Modes of E1 Ports.
l You must be an NM user with NE administrator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree and choose Configuration >
Interface Management > PDH Interface from the Function Tree.
Step 3 Select the required port and set the parameters for its advanced attributes.
Step 5 Click Yes. Then, close the dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l The ports that travel services are set to Layer 1.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
Interface Management > Serial Interface from the Function Tree.
Step 4 Set the parameters for the serial port according to the planning information.
Step 5 Click OK. Then, close the dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l Serial ports are added.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
Interface Management > Serial Interface from the Function Tree.
Step 3 Select the required port and set the parameters for the serial port according to the planning
information.
Step 4 Click Apply. Then, close the dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The Ethernet board must be added on the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface
Management > Ethernet Interface from the Function Tree.
NOTE
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The Ethernet board must be added on the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface
Management > Ethernet Interface from the Function Tree.
Step 2 Click the Flow Control tab.
NOTE
l Auto-Negotiation Flow Control Mode is valid only when Working Mode is set to Auto-
Negotiation.
l Auto-Negotiation Flow Control Mode of the equipment on the local side must be consistent with
the auto-negotiation flow control mode of the equipment on the opposite side
l OptiX RTN 900 supports only two auto-negotiation flow control modes, namely, Disabled mode
and Enable Symmetric Flow Control mode.
l Non-Autonegotiation Flow Control Mode is valid only when Working Mode is not set to Auto-
Negotiation.
l Non-Autonegotiation Flow Control Mode of the equipment on the local side must be consistent
with the non-autonegotiation flow control mode of the equipment on the opposite side
l OptiX RTN 900 supports only two non-auto-negotiation flow control modes, namely, Disabled
mode and Enable Symmetric Flow Control mode.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The Ethernet board must be added on the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface
Management > Ethernet Interface from the Function Tree.
NOTE
l When Encapsulation Type in the General Attributes tab page is set to QinQ, you need to set
QinQ Type Domain. The default value is 88A8.
l When Encapsulation Type in the General Attributes tab page is set to Null or 802.1Q, you cannot
set QinQ Type Domain. In this case, QinQ Type Domain is displayed as FFFF and cannot be
changed.
l If all the accessed services are frames with the VLAN tag (tagged frames), set TAG to Tag Aware.
l If all the accessed services are frames without the VLAN tag (untagged frames), set TAG to Access.
l If the accessed services contain tagged frames and untagged frames, set TAG to Hybrid.
l Default VLAN ID is valid only when TAG is set to Access or Hybrid.
l VLAN Priority is valid only when TAG is set to Access or Hybrid.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l Port Mode of Ethernet ports are set to Layer 3.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration >
Interface Management > Ethernet Interface from the Function Tree.
Step 3 Set the parameters for Ethernet ports according to the planning information.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The Ethernet board must be added on the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface
Management > Ethernet Interface from the Function Tree.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding IF board must be added to NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface
Management > Microwave Interface from the Function Tree.
NOTE
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding IF board must be added to NE Panel.
l The parameter Port Mode is set to Layer 2.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface
Management > Microwave Interface from the Function Tree.
NOTE
l When Encapsulation Type in the General Attributes tab page is set to QinQ, you need to set
QinQ Type Domain. The default value is 88A8.
l When Encapsulation Type in the General Attributes tab page is set to Null or 802.1Q, you cannot
set QinQ Type Domain. In this case, QinQ Type Domain is displayed as FFFF and cannot be
changed.
l If all the accessed services are frames that contain the VLAN tag (tagged frames), set Tag to "Tag
Aware".
l If all the accessed services are frames that do not contain the VLAN tag (untagged frames), set Tag
to "Access".
l If the accessed services contain tagged frames and untagged frames, set Tag to "Hybrid".
l Default VLAN ID is valid only when TAG is set to Access or Hybrid.
l VLAN Priority is valid only when TAG is set to Access or Hybrid.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l Port Mode of the ports on IF boards are set to Layer 3.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
Interface Management > Microwave Interface from the Function Tree.
Step 3 Set parameters for Layer 3 attributes of the ports on IF boards according to the planning
information.
NOTE
Modifying the IP address may interrupt services.
Step 4 Click Apply. Then, close the dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding IF board must be added to NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface
Management > Microwave Interface from the Function Tree.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding IF board must be added on the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > IF Interface from the Function Tree.
Step 2 Optional: For a dual-channel IF board, select an IF port.
NOTE
l Link ID is set according to the network plan. Each radio link of an NE should have a unique link ID,
and the link IDs at both ends of a radio link should be the same.
l If the XPIC IF board does not perform the XPIC function, XPIC Enabled should be set to
Disabled.
l Enable IEEE-1588 Timeslot needs to be set consistently between two ends of a radio link.
l If the NE needs to transmit IEEE 1588v2 packets, set Enable IEEE-1588 Timeslot to Enabled. If
the NE does not need to transmit IEEE 1588v2 packets, set Enable IEEE-1588 Timeslot to
Disabled.
l RTN 905, RTN 910A, and ISV3/ISM6 boards on RTN 980/RTN 980L/RTN 950/RTN 950A allow
Alarm and Performance Report to be specified. If Alarm and Performance Report is set to
Disabled, alarms of IF ports and the corresponding ODUs/RFUs are not reported.
l An IF port on an ISU2/ISX2 board can interconnect only with an IF port that supports the IS2 mode.
l RTN 905 1E/2E can work in IS2 or IS3 mode. By default, RTN 905 1E/2E works in IS3 mode. Set
Running Mode to the same value for the two IF units on an RTN 905 2E.
l ISV3 boards can work in IS2 or IS3 mode. By default, ISV3 boards work in IS3 mode.
l IF ports on ISM6 boards can work in IS2, IS3, or IS6 mode. By default, IF ports on ISM6 boards
work in IS6 mode. The two IF ports on an ISM6 board must work in the same mode.
l It is recommended that two interconnected IF ports work in the highest-order mode that they both
support.
l Before switching the running mode of an IF port, delete services on the port.
l If IF ports are configured with services or 1+1, N+1, PLA/EPLA/EPLA+, or LAG protection, their
Running Mode cannot be modified.
l You can set Power Switch for an ISM6 board to turn on or off the power switch of an ODU
connected to the ISM6 board.
NOTE
l When AM Enable Status is set to Disabled, the radio link uses only the specified modulation
scheme. In this case, you need to select Manually Specified Modulation Mode.
l When AM Enable Status is set to Enabled, the radio link uses the corresponding modulation
scheme according to the channel conditions.
l Modulation Mode of the Guarantee AM Capacity specifies the lowest-order modulation scheme
that the AM function supports. This parameter is set according to the network plan. Generally, the
value of this parameter is determined by the service transmission bandwidth that the Hybrid radio
must ensure and the availability of the radio link that corresponds to this modulation scheme.
l Modulation Mode of the Full AM Capacity specifies the highest-order modulation scheme that the
AM function supports. This parameter is set according to the network plan. Generally, the value of
this parameter is determined by the bandwidth of the services that need to be transmitted over the
Hybrid radio and the availability of the radio link that corresponds to this modulation scheme.
l Modulation Mode of the Full AM Capacity must be higher than Modulation Mode of the
Guarantee AM Capacity.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding IF board must be added on the NE Panel.
Precautions
l For the IF boards that are configured with 1+1 protection, configure only the ATPC
attributes of the main IF board.
l The following procedure describes the ATPC parameter configurations in the IF port
configuration dialog box for the IF board. You can also configure ATPC parameters in
the Create XPIC Protection Group window.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > IF Interface from the Function Tree.
Step 2 Click the ATPC Attributes tab.
Step 3 Set the parameters of ATPC attributes.
NOTE
l The settings of the ATPC attributes must be consistent at both ends of a radio link.
l In the case of areas where fast fading severely affects the radio transmission, it is recommended that
you set ATPC Enable Status to Disabled.
l If ATPC Automatic Threshold Enable Status is set to Enabled, the equipment automatically uses
the preset ATPC upper and lower thresholds according to the work mode of the radio link.
l If ATPC Automatic Threshold Enable Status is set to Disabled, you need to manually set ATPC
Upper Automatic Threshold(dBm) and ATPC Lower Automatic Threshold(dBm).
l It is recommended that you set ATPC Upper Threshold(dBm) to the sum of the planned central
value between the ATPC upper threshold and the ATPC lower threshold and 10 dB, and ATPC
Lower Threshold(dBm) to the difference between the planned central value between the ATPC
upper threshold and the ATPC lower threshold and 10 dB.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding IF boards must be added in the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the IF board, and then choose Configuration > IF Interface from
the Function Tree.
NOTE
The E1 service capacity in an intermediate modulation scheme can be changed only after the E1 priority
function is enabled.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding IF boards must be added in the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > IF Interface from the Function Tree.
Step 2 Click the IF Attributes tab.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > ATPC Adjustment Records from the Function Tree.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding IF boards have been added in the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
NOTE
After the IF service type is changed, the IF board will be reset. Wait until the IF board resets and set
other IF information.
If IF ports are configured with services or 1+1, common N+1, PLA/EPLA/EPLA+, or LAG protection,
their IF service types cannot be changed.
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > IF Interface from the Function Tree.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding IF boards have been added in the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
l An IF port on an ISU2/ISX2 board can interconnect only with an IF port that supports
the IS2 mode.
l RTN 905 1E/2E can work in IS2 or IS3 mode. By default, RTN 905 1E/2E works in IS3
mode. Set Running Mode to the same value for the two IF units on an RTN 905 2E.
l ISV3 boards can work in IS2 or IS3 mode. By default, ISV3 boards work in IS3 mode.
l IF ports on ISM6 boards can work in IS2, IS3, or IS6 mode. By default, IF ports on
ISM6 boards work in IS6 mode. The two IF ports on an ISM6 board must work in the
same mode.
l It is recommended that two interconnected IF ports work in the highest-order mode that
they both support.
l Before switching the running mode of an IF port, delete services on the port.
l If IF ports are configured with services or 1+1, N+1, PLA/EPLA/EPLA+, or LAG
protection, their Running Mode cannot be modified.
NOTE
When working at a 56 MHz or higher bandwidth, two IF ports on a dual-channel IF board or an RTN 905 2E
cannot switch to the SDH mode. If the two IF ports on a dual-channel IF board or an RTN 905 2E are
required to work in SDH mode at a 56 MHz or higher bandwidth, it is advised to configure a 28 MHz
bandwidth for the two IF ports first, switch their work modes to the SDH mode, and then change the
bandwidth to 56 MHz or higher.
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > IF Interface from the Function Tree.
Step 2 Click the IF Attributes tab.
Step 3 Change the runtime mode based on the network plan.
----End
Prerequisites
l OptiX RTN 905 does not support this operation.
l You must be an NM user with NE operator authority or higher.
l The corresponding ISX2 board has been added on the NE Panel.
l The AM function has been enabled by A.5.1 Configuring a Single-Hop Radio Link.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Background Information
Only ISX2 boards support the AM Booster function.
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > IF Interface from the Function Tree.
Step 2 Click the IF Attributes tab.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding IF boards have been added in the NE Panel.
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > IF Interface from the Function Tree.
Step 4 Optional: When the AM function is disabled, adjust the modulation mode.
1. Set Manually Specified Modulation Mode to its planned value.
2. Click Apply.
Step 7 Optional: When the AM function is enabled, adjust the modulation mode.
If... Then...
You need to lower 1. Perform Step 5 to disable the AM function, and change
Modulation Mode of Manually Specified Modulation Mode to the lowered
the Guarantee AM Modulation Mode of the Guarantee AM Capacity.
Capacity 2. Perform Step 6 to enable the AM function.
In other cases 1. Set Modulation Mode of the Guarantee AM Capacity and
Modulation Mode of the Full AM Capacity to their planned
values.
2. Click Apply.
If... Then...
You need to reduce 1. Perform A.7.6 Deleting Cross-Connections to delete
the number of high- unnecessary E1 services.
priority E1 services 2. Decrease Guarantee E1 Capacity.
3. Click Apply.
You need to increase 1. Increase Guarantee E1 Capacity.
the number of high- 2. If Enable E1 Priority is Enabled, increase Full E1 Capacity
priority E1 services accordingly.
3. Click Apply.
4. Perform A.7.1 Creating the Cross-Connections of Point-to-
Point Services or A.7.2 Creating Cross-Connections of SNCP
Services to add required E1 services.
NOTE
l Full E1 Capacity is the total number of high-priority E1 services and
low-priority E1 services.
l Adding high-priority E1 services does not affect original E1 services.
Step 9 Optional: Change the number of low-priority E1 services (namely, Guarantee E1 Capacity)
in a radio link.
If... Then...
You need to reduce 1. Perform A.7.6 Deleting Cross-Connections to delete
the number of low- unnecessary E1 services.
priority E1 services 2. Decrease Full E1 Capacity.
3. Click Apply.
You need to 1. If Enable E1 Priority is Disabled, change Enable E1 Priority
increase the to Enabled.
number of low- 2. Increase Full E1 Capacity.
priority E1 services
3. Click Apply.
4. Perform A.7.1 Creating the Cross-Connections of Point-to-
Point Services or A.7.2 Creating Cross-Connections of SNCP
Services to add required E1 services.
l Full E1 Capacity is the total number of high-priority E1 services
and low-priority E1 services.
l Adding low-priority E1 services does not affect original E1
services.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The IF boards and the ODU to which the IF boards are connected must be added on the
NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU
Interface from the Function Tree.
Step 2 Click the Radio Frequency Attributes tab.
Step 3 Configure Transmit Frequency(MHz) and T/R Spacing(MHz) of the ODU.
NOTE
l The value of Transmit Frequency(MHz) must not be less than the sum of the minimum transmit
frequency supported by the RFU/RFU-SD/ODU and a half of the channel spacing, and must not be
more than the difference between the maximum transmit frequency supported by the RFU/RFU-
SD/ODU and a half of the channel spacing.
l The difference between the transmit frequencies at both ends of a radio link by ODU should be one
T/R spacing.
l If the ODU is a Tx high station, the transmit frequency is one T/R spacing higher than the receive
frequency. If the ODU is a Tx low station, the transmit frequency is one T/R spacing lower than the
receive frequency.
l A valid T/R spacing value is determined by the ODU itself, and T/R Spacing(MHz) should be set
according to the technical specifications of the ODU.
l The T/R spacing of the ODU should be set to the same value at both ends of a radio link.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The IF boards and theODUs to which the IF boards are connected must be added on the
NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > ODU Interface from the Function Tree.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The IF boards and the ODUs to which the IF boards are connected must be added on the
NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Customize the configuration procedure by equipment.
Option Description
If the Equipment Type Is... Then...
ODU Perform steps 2 to 5.
RFU/RFU-SD Perform steps 6 to 9.
Step 2 Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU
Interface from the Function Tree.
NOTE
l Maximum Transmit Power(dBm) is set according to the network plan. This parameter cannot be
set to a value that exceeds the nominal power rang of the RFU/RFU-SD/ODU in the guaranteed
capacity modulation module.
l The maximum transmit power adjusted by using the ATPC function should not exceed Maximum
Transmit Power(dBm).
l Transmit Power(dBm) is set according to the network plan. This parameter specifies the transmit
power of the RFU/RFU-SD/ODU. This parameter cannot be set to a value that exceeds the nominal
power rang of the RFU/RFU-SD/ODU or a value that exceeds Maximum Transmit Power(dBm).
l Power to Be Received(dBm) is used to set the expected receive power of the RFU/RFU-SD/ODU
and is mainly used in the antenna alignment stage. After this parameter is set, the NE automatically
enables the antenna misalignment indicating function.
l Power to Be Received(dBm) is set according to the network plan. When this parameter takes the
default value, the antenna misalignment indicating function is disabled.
l TX High Threshold(dBm) and TX Low Threshold(dBm) are valid only when the ATPC function
is enabled.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The IF boards and the ODU to which the IF boards are connected must be added on the
NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU
Interface from the Function Tree.
NOTE
l RF Loopback function is used for fault locating for the RF interfaces. The RF Loopback function
is used for diagnosis and may affect the services that are transmitted over the interfaces. Hence,
exercise caution before starting this function.
l In normal cases, RF Loopback is set to Non-Loopback.
l In normal cases, Configure Transmission Status is set to unmute.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l Ethernet boards and IF boards have been added on the NE Panel.
l Port Mode has been set to Layer Mix for Ethernet boards and IF boards.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
VLAN sub-interfaces are similar to Layer 3 ports. By configuring Layer 3 port attributes for
VLAN sub-interfaces, you can create MPLS tunnel-based services. After being received by
access-layer RTN equipment and then mapped into an MPLS tunnel, services are allocated
different VLAN IDs at VLAN sub-interfaces in compliance with configuration requirements
for the third-party network that the services need to traverse. In this manner, services are
differentiated and therefore correctly forwarded on the third-party network.
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree and choose Configuration >
Interface Management > Ethernet Virtual Interface from the Function Tree.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The Ethernet boards, or IF boards must be added to the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protection > ERPS Management.
NOTE
l It is recommended that you plan the counterclockwise direction as the main direction of services
transmission, and plan the port that transmits services in the main direction as an east port, and the port
that receives services as a west port.
l Set East Port or West Port to - for the sub-ring ERPS instance on an interconnection node.
l Set ERP Ring Node Flag and Flag Port to matching values according to the network plan by taking the
following suggestions:
– Only one node on the ring can be set as the RPL owner or RPL neighbor node for each Ethernet
ring.
– If the node is the RPL owner, set this parameter to RPL Port.
– If the node is an RPL neighbor node, set this parameter to Neighbor Port.
– If the node is the next-hop node of the RPL owner or RPL neighbor node, set this parameter to Next
Neighbor Port.
– It is recommended that you set the east port of the RPL owner to RPL Port and the west port of the
RPL neighbor node to Neighbor Port.
– It is recommended that you set the east port on RPL owner node's upstream node and the west port
on the RPL neighbor node's downstream node as Next Neighbor Port.
– If the node on the ring is not any of the preceding nodes, set this parameter to None.
l This parameter generally takes the default value Revertive. You can set this parameter to Non-Revertive
according to the network plan.
l The ID of a Control VLAN must not be the same as any VLAN ID used by Ethernet services. All ring
nodes should use the same Control VLAN ID.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The ERPS protection instance must be created.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protection > ERPS Management from the Function Tree.
NOTE
Set the parameters according to the network plan. Default values are recommended.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l Ethernet boards and IF boards have been added to the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protection > ERPS Management.
Step 2 Set the parameters for the ERPS instance.
NOTE
In this step, you can set Compatible_Version, Virtual Channel Status, Virtual Channel VLANs, and
Major ERPS Ring ID, and query or modify other ERPS instance protocol parameters.
l For multi-ring networks, Compatible_Version for all ring nodes must be ver2.
l For details about values of Virtual Channel Status and Virtual Channel VLANs, refer to Planning
Guidelines for R-APS Virtual Channels in the Feature Description.
l Set this parameter only for the sub-ring ERPS instance on an interconnection node to associate the sub-
ring ERPS instance with the major ring ERPS instance.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l A multi-ring ERPS instance has been created.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Background Information
NOTE
l A virtual channel VLAN forwarding table needs to be created only for sub-rings. The sub-rings need to
be associated with corresponding major rings.
l Virtual Channel Status must have been enabled and Virtual Channel VLANs must have been correctly
set for the major ring by A.9.1.3 Setting Protocol Parameters for an ERPS Instance.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protection > ERPS Management.
Step 2 Select the sub-ring.
Step 5 Configure the parameters for the virtual channel VLAN forwarding table.
NOTE
l The system automatically displays the ID of the sub-ring ERPS instance and the ERPS ID of the major
ring with which the sub-ring ERPS instance is associated.
l Set Virtual Channel VLAN to the control VLAN ID of the sub-ring R-APS virtual channel.
l Set Virtual Channel VLAN on Major Ring to the Virtual Channel VLANs of the associated major
ring node.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The mapping IF boards and RFUs have been added on the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Precautions
l Understand the network topology and properly configure parameters for switching upon
multiple failures to ensure that proper switching can be triggered on an ERPS sub-ring.
Otherwise, normal services may be interrupted. For details about the switching principles
for minimization of segmentation, see Feature Description.
l It is advised to configure a bound MEP for an interconnection node sub-ring port when
the network is normal.
l Modify Interconnected Node and Multi-point Failure only after multiple failures
occur. Restore the two parameters to default values immediately after faults are rectified.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protection > ERPS Management from the Function Tree.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protection > ERPS Management.
Step 3 Click Switching and select an external switch command from the drop-down list.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protection > ERPS Management from the Function Tree.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The board on which the LAG port to be created must be added to the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface
Management > Link Aggregation Group Management from the Function Tree.
Step 2 Click the Link Aggregation Group Management tab.
NOTE
Hold the Ctrl key or the Shift key on the keyboard to select multiple ports.
NOTE
4. Click OK. A dialog box is displayed for confirmation. Click OK. A dialog box is
displayed, indicating that the operation is successful. Close this dialog box.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The board on which the LAG to be created must be added to NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface
Management > Link Aggregation Group Management from the Function Tree.
Step 2 Click the Link Aggregation Parameters tab.
Step 3 Set Port Priority and System Load Sharing Hash Algorithm.
NOTE
l System Load Sharing Hash Algorithm is valid only when Load Sharing of a LAG is set to Sharing.
l After the configuration data is deployed, System Load Sharing Hash Algorithm takes effect for the
entire NE.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The LAG must be created.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface
Management > Link Aggregation Group Management from the Function Tree.
Step 3 Click Query.A dialog box is displayed, indicating that the operation is successful. Close this
dialog box.
The system displays the information about the slave port in the lower part of the Main Interface.
Step 6 Right-click on the selected LAG and choose the LAG-specific information from the shortcut
menu.
Step 9 Click Query. A dialog box is displayed, indicating that the operation is successful. Close this
dialog box.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Service Management > QinQ Link from the Function Tree.
Step 4 Click OK. Then, close the dialog box that is displayed.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
The intra-board Native E-Line services on an EM6T, EM6TA, EM6F, or EM6FA board can be
forwarded in two modes: Center and Local.
l When the centralized forwarding mode is used, intra-board Native E-Line services must
be forwarded through the packet switching unit of a system control board. Therefore,
double backplane bandwidth resources of the system control board are consumed.
l When the distributed forwarding mode is used, intra-board Native E-Line services are
directly forwarded by the switching units of the board. However, this will restrict the
functions of some packet switching units that depend on system control boards. The
restrictions include:
– Intra-board Native E-Line services do not support the LM function of ETH-OAM.
Therefore, the packet loss rate of the Native E-Line services could not be tested
using meter-free tests.
– The source and sink ports of intra-board Native E-Line services do not support the
LAG function. If the source or sink ports are configured with the LAG function, the
forwarding mode is automatically switched to centralized mode.
l The default forwarding mode configured for an EM6T, EM6TA, EM6F, or EM6FA board
is centralized forwarding.
Other types of Ethernet services on an EM6T, EM6TA, EM6F, or EM6FA board and all types
of Ethernet services on other types of Ethernet boards are forwarded in centralized mode.
Procedure
Step 1 Select an NE from the object tree in the NE Explorer. Choose Configuration > Ethernet
Service Forwarding Mode Management from the function tree.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The Ethernet board must be added on the NE Panel.
l The parameter Port Mode is set to Layer 2 for the UNI port that carries the E-Line
service.
Context
NOTE
l For an RTN 980, RTN 980L, or an RTN 950 housing a CSH board, the total number of VLANs
configured for E-Line services, VPLS services, UNIs carrying E-Aggr services, and UNIs carrying
802.1ad bridge-based E-LAN services must not exceed 1024.
l For an RTN 905, RTN 910A, RTN 950A, or RTN 950 housing a CSHU/CSHUA board, the total number
of VLANs configured for E-Line services, E-LAN services, and UNIs carrying E-Aggr services must not
exceed 1024.
l For an RTN 980, RTN 980L, or RTN 950 housing a CSH board, the total number of VLANs configured
for PWs in tag mode and E-Aggr services with UNIs being S ports must not exceed 256.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Service Management > E-Line Service from the Function Tree.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The Ethernet board must be added on the NE Panel.
l The parameter Port Mode is set to Layer 2 for the UNI port that carries the E-Line
service.
Context
NOTE
l For an RTN 980, RTN 980L, or an RTN 950 housing a CSH board, the total number of VLANs
configured for E-Line services, VPLS services, UNIs carrying E-Aggr services, and UNIs carrying
802.1ad bridge-based E-LAN services must not exceed 1024.
l For an RTN 905, RTN 910A, RTN 950A, or RTN 950 housing a CSHU/CSHUA board, the total number
of VLANs configured for E-Line services, E-LAN services, and UNIs carrying E-Aggr services must not
exceed 1024.
l For an RTN 980, RTN 980L, or RTN 950 housing a CSH board, the total number of VLANs configured
for PWs in tag mode and E-Aggr services with UNIs being S ports must not exceed 256.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Service Management > E-Line Service from the Function Tree.
Step 6 Change the Ethernet port attributes of the source and sink ports. Click Apply Port
Attributes.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l Ethernet boards have been added on the NE Panel.
l For ports that carry services, Port Mode has been set to Layer 2 and Encapsulation
Type has been set to QinQ.
Context
NOTE
l For an RTN 980, RTN 980L, or an RTN 950 housing a CSH board, the total number of VLANs
configured for E-Line services, VPLS services, UNIs carrying E-Aggr services, and UNIs carrying
802.1ad bridge-based E-LAN services must not exceed 1024.
l For an RTN 905, RTN 910A, RTN 950A, or RTN 950 housing a CSHU/CSHUA board, the total number
of VLANs configured for E-Line services, E-LAN services, and UNIs carrying E-Aggr services must not
exceed 1024.
l For an RTN 980, RTN 980L, or RTN 950 housing a CSH board, the total number of VLANs configured
for PWs in tag mode and E-Aggr services with UNIs being S ports must not exceed 256.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Service Management > E-Line Service from the Function Tree.
Step 2 Click New.
The New E-Line Service dialog box is displayed.
Step 3 Set Direction to NNI-NNI.
Step 5 Click OK. Then, close the dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l Ethernet boards have been added on the NE Panel.
l For ports that carry services, Encapsulation Type has been set to QinQ.
Context
NOTE
l For an RTN 980, RTN 980L, or an RTN 950 housing a CSH board, the total number of VLANs
configured for E-Line services, VPLS services, UNIs carrying E-Aggr services, and UNIs carrying
802.1ad bridge-based E-LAN services must not exceed 1024.
l For an RTN 905, RTN 910A, RTN 950A, or RTN 950 housing a CSHU/CSHUA board, the total number
of VLANs configured for E-Line services, E-LAN services, and UNIs carrying E-Aggr services must not
exceed 1024.
l For an RTN 980, RTN 980L, or RTN 950 housing a CSH board, the total number of VLANs configured
for PWs in tag mode and E-Aggr services with UNIs being S ports must not exceed 256.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Service Management > E-Line Service from the Function Tree.
Step 2 Click Create.
The Create E-Line Service dialog box is displayed.
Step 3 Set Direction to NNI-NNI.
Step 4 Set relevant attributes of the E-Line service.
Step 5 Optional: Click New to configure the source and sink ends.
NOTE
In this manner, you do not need to configure the QinQ links used at the source and sink ends according to the
network planning information ahead of time. However, you need to set Encapsulation Type of ports
corresponding to the QinQ links to QinQ ahead of time.
1. Click New.
2. Set the attributes of the QinQ link at the source end.
3. Click Configure QinQ Link.
4. Repeat Step 5.2 and Step 5.3 to set the attributes of the QinQ link at the sink end.
5. Select Use existing resource.
Step 6 Optional: Select Use existing resource and select created QinQ links as the QinQ links used
at the source and sink ends.
NOTE
In this manner, you need to configure the QinQ links used at the source and sink ends according to the
network planning information ahead of time.
1. Select Use existing resource.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l Ethernet boards have been added on the NE Panel.
l For UNI and NNI ports that carry services, Port Mode has been set to Layer 2. For NNI
ports, Encapsulation Type has been set to QinQ.
Context
NOTE
l For an RTN 980, RTN 980L, or an RTN 950 housing a CSH board, the total number of VLANs
configured for E-Line services, VPLS services, UNIs carrying E-Aggr services, and UNIs carrying
802.1ad bridge-based E-LAN services must not exceed 1024.
l For an RTN 905, RTN 910A, RTN 950A, or RTN 950 housing a CSHU/CSHUA board, the total number
of VLANs configured for E-Line services, E-LAN services, and UNIs carrying E-Aggr services must not
exceed 1024.
l For an RTN 980, RTN 980L, or RTN 950 housing a CSH board, the total number of VLANs configured
for PWs in tag mode and E-Aggr services with UNIs being S ports must not exceed 256.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Service Management > E-Line Service from the Function Tree.
Step 3 Set Direction to UNI-NNI and set Bearer Type to QinQ Link.
You can configure QinQ links during service creation or before service creation by choosing Configuration >
Ethernet Service Management > QinQ Link.
Step 5 Click OK. Then, close the dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l Ethernet boards have been added on the NE Panel.
l For ports that carry services, Encapsulation Type has been set to QinQ.
Context
NOTE
l For an RTN 980, RTN 980L, or an RTN 950 housing a CSH board, the total number of VLANs
configured for E-Line services, VPLS services, UNIs carrying E-Aggr services, and UNIs carrying
802.1ad bridge-based E-LAN services must not exceed 1024.
l For an RTN 905, RTN 910A, RTN 950A, or RTN 950 housing a CSHU/CSHUA board, the total number
of VLANs configured for E-Line services, E-LAN services, and UNIs carrying E-Aggr services must not
exceed 1024.
l For an RTN 980, RTN 980L, or RTN 950 housing a CSH board, the total number of VLANs configured
for PWs in tag mode and E-Aggr services with UNIs being S ports must not exceed 256.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Service Management > E-Line Service from the Function Tree.
Step 3 Set Direction to UNI-NNI and set Bearer Type to QinQ Link.
Step 9 Optional: Click New and create the QinQ link used at the sink end.
NOTE
In this manner, you do not need to configure the QinQ link used at the sink end according to the network
planning information ahead of time. However, you need to set Encapsulation Type of ports corresponding to
the QinQ links to QinQ ahead of time.
1. Click New.
2. Set the attributes of the QinQ link at the sink end.
Step 10 Optional: Select Use existing and select a created QinQ link as the QinQ link used at the sink
end.
NOTE
In this manner, you need to configure the QinQ link used at the sink end according to the network planning
information ahead of time.
1. Select Use existing resource.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The Ethernet board is added on the NE Panel.
l For the UNI port that carries the service, Port Mode has been set to Layer 2. For the
NNI port that carries the service, Port Mode has been set to Layer 3.
l The tunnel that carries PWs is configured.
Context
NOTE
l For RTN 950 housing CSH boards, RTN 980, and RTN 980L, the total number of VLANs used by UNI-
carried E-Line, VPLS, E-Aggr, and IEEE 802.1ad bridge-based E-LAN services must not exceed 1024.
l For RTN 950 housing CSHU/CSHUA boards, RTN 905, RTN 910, and RTN 950A, the total number of
VLANs used by UNI-carried E-Line, E-Aggr, and E-LAN services must not exceed 1024.
l For RTN 950 housing CSH boards, RTN 980, and RTN 980L, the total number of VLANs used by TAG-
mode PW-carried and S-aware UNI-carried E-Aggr services must not exceed 256.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Service Management > E-Line Service from the Function Tree.
Step 2 Click New.
The New E-Line Service dialog box is displayed.
Step 3 Set Direction to UNI-NNI, Bearer Type to PW, and Protection Type to Unprotection for
E-Line services.
NOTE
When E-Line services are initially configured, it is recommended that you set Protection Type to No
Protection for the services. After successful service creation, add the APS protection when necessary. For
details on how to add APS protection, see A.11.5.1 Creating a PW APS Protection Group.
Step 7 Click the QoS tab and set the QoS parameters for PWs.
Step 8 Click the Advanced Attributes tab and set the advanced parameters for PWs.
Step 10 Click OK. Then, close the dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The Ethernet board is added on the NE Panel.
l Port Mode is set to Layer 2 for the UNI ports that carry services.
Context
NOTE
l For RTN 950 housing CSH boards, RTN 980, and RTN 980L, the total number of VLANs used by UNI-
carried E-Line, VPLS, E-Aggr, and IEEE 802.1ad bridge-based E-LAN services must not exceed 1024.
l For RTN 950 housing CSHU/CSHUA boards, RTN 905, RTN 910, and RTN 950A, the total number of
VLANs used by UNI-carried E-Line, E-Aggr, and E-LAN services must not exceed 1024.
l For RTN 950 housing CSH boards, RTN 980, and RTN 980L, the total number of VLANs used by TAG-
mode PW-carried and S-aware UNI-carried E-Aggr services must not exceed 256.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Service Management > E-Line Service from the Function Tree.
Step 2 Click Create.
The Create dialog box is displayed.
Step 3 Set Direction to UNI-NNI, Bearer Type to PW, and Protection Type to No Protection for
E-Line services.
NOTE
When E-Line services are initially configured, it is recommended that you set Protection Type to No
Protection for the services. After successful service creation, add the APS protection when necessary. For
details on how to add APS protection, see A.11.5.1 Creating a PW APS Protection Group.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l Ethernet boards have been added on the NE Panel.
l For the UNI ports that carry the service, Port Mode has been set to Layer 2 and
Encapsulation Type has been set to 802.1Q or QinQ. For the NNI port that carries the
service, Port Mode has been set to Layer 3.
l The MPLS tunnels that carry PWs have been configured.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
NOTE
l For RTN 950 housing CSH boards, RTN 980, and RTN 980L, the total number of VLANs used by UNI-
carried E-Line, VPLS, E-Aggr, and IEEE 802.1ad bridge-based E-LAN services must not exceed 1024.
l For RTN 950 housing CSHU/CSHUA boards, RTN 905, RTN 910, and RTN 950A, the total number of
VLANs used by UNI-carried E-Line, E-Aggr, and E-LAN services must not exceed 1024.
l For RTN 950 housing CSH boards, RTN 980, and RTN 980L, the total number of VLANs used by TAG-
mode PW-carried and S-aware UNI-carried E-Aggr services must not exceed 256.
Context
l Regardless of whether VLAN ID swapping is required by an E-AGGR service, a VLAN
forwarding table needs to be configured, specifying the source and sink VLAN IDs of
each VLAN service.
l If VLAN ID swapping is required for PW-based E-Line services, change the E-Line
services to an E-AGGR service.
l For an E-AGGR service aggregating services from multiple UNI ports to a PW, the NNI
port must be configured as the sink. For an E-AGGR service aggregating services from
multiple PWs to a UNI port, the UNI port must be configured as the sink.
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree and choose Configuration >
Ethernet Service Management > E-AGGR Service from the Function Tree.
Step 2 Click New.
The New E-AGGR Service dialog box is displayed.
Step 3 Set the basic attributes for the E-AGGR service.
Step 4 Configure the UNI ports required for the E-AGGR service.
1. Click the UNI tab. Click Configuration.
The Configure Port dialog box is displayed.
2. Select the desired port from the Available Port list and click to add the port
to the Selected Port list.
3. In the Selected Port area, set Location and VLANs according to planning information.
NOTE
You can set Location to Source or Sink. You can configure one or more source ports but only one
sink port for an E-AGGR service. Otherwise, configuration of the E-AGGR service will fail.
4. Click OK.
Step 5 Configure the NNI port required for the E-AGGR service.
1. Click the NNI tab. Click the PW tab. Click New.
The New dialog box is displayed.
2. Set parameters in Basic Attributes according to planning information.
4. Click OK.
Step 7 Optional: Click the Configure QoS tab and set QoS parameters.
1. Click the PW tab and set EXP and LSP Mode.
2. Click OK.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l Ethernet boards have been added on the NE Panel.
l A UNI-UNI E-Line service has been created.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Service Management > E-Line Service from the Function Tree.
Step 2 Select the E-Line service for which a VLAN forwarding table needs to be configured.
Step 3 Click the VLAN Forwarding Table Item tab.
Step 4 Click New.
Step 5 Set the attributes for the VLAN forwarding table.
Step 6 Click OK. Then, close the dialog box that is displayed.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree, and then choose
Configuration > TPID Configuration from the Function Tree.
Step 2 Set TPID(Hexadecimal) according to planning information.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l For ports carrying IEEE 802.1d bridge-based E-LAN services, Port Mode has been set
to Layer 2 and Encapsulation Type has been set to Null.
Context
An IEEE 802.1d bridge-based E-LAN service must be configured according to the service
model described in 802.1D Bridge-based E-LAN Service Models.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree. Choose Configuration > Ethernet
Service Management > E-LAN Service from the Function Tree.
Step 2 Click New.
The New E-LAN Service dialog box is displayed.
Step 3 Set the basic attributes of the E-LAN service according to the network plan.
Step 4 Configure the ports mounted to the bridge on the UNI side.
1. Click UNI.
2. Click Configuration.
The Configure Port dialog box is displayed.
3. Configure the ports mounted to the bridge on the UNI side.
3. Click .
4. Click OK.
Step 6 Click OK. Close the displayed dialog box.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Service Management > E-LAN Service from the Function Tree.
Step 2 Click New.
The Create E-LAN Service dialog box is displayed.
Step 3 Click Configure the source and sink. Set the basic attributes of the E-LAN service
according to the network plan.
NOTE
Step 4 Configure the ports mounted to the bridge on the UNI side.
1. Click Get UNI Port.
The Get UNI Port dialog box is displayed.
2. Configure the ports mounted to the bridge on the UNI side.
a. Select the port to be mounted to the bridge.
NOTE
The port members that are added to the same split horizon group cannot communicate with each other.
1. Click Set the service parameters and select Split Horizon Group.
2. Click New.
The Create Split Horizon Group dialog box is displayed.
Hold the Ctrl key on the key board to select multiple ports.
4. Click OK.
Step 6 Click OK.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l For the ports that carry the IEEE 802.1q bridge-based E-LAN services, Port Mode has
been set to Layer 2 and Encapsulation Type has been set to 802.1Q.
Context
l Configure services based on the service model described in 802.1Q Bridge-based E-LAN
Service Models.
l For the OptiX RTN 905, OptiX RTN RTN 910A, the OptiX RTN 950A and the OptiX
RTN 950 that houses CSHU/CSHUA boards, the total number of VLAN IDs configured
for all Ethernet services cannot exceed 1024. The total number of VLAN IDs configured
for all Ethernet services does not include the number of VLAN IDs for E-LAN services
configured in VLAN Filtering Table. Ports in VLAN Filtering Table cannot be used to
transmit other Ethernet services.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree. Choose Configuration > Ethernet
Service Management > E-LAN Service from the Function Tree.
Step 2 Click New.
The New E-LAN Service dialog box is displayed.
Step 3 Set basic attributes of the E-LAN service as planned.
Step 4 Configure the ports mounted to the bridge on the UNI side.
1. Click UNI.
2. Click Configuration.
The Configure Port dialog box is displayed.
3. Configure the ports mounted to the bridge on the UNI side.
a. Select the port to be mounted to the bridge.
3. Click .
4. Click OK.
Step 6 Click OK. Close the displayed dialog box.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
Context
l Configure services based on the service model described in 802.1Q Bridge-based E-LAN
Service Models.
l For the OptiX RTN 905, OptiX RTN RTN 910A, the OptiX RTN 950A and the OptiX
RTN 950 that houses CSHU/CSHUA boards, the total number of VLAN IDs configured
for all Ethernet services cannot exceed 1024. The total number of VLAN IDs configured
for all Ethernet services does not include the number of VLAN IDs for E-LAN services
configured in VLAN Filtering Table. Ports in VLAN Filtering Table cannot be used to
transmit other Ethernet services.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Service Management > E-LAN Service from the Function Tree.
Step 3 Click Configure the source and sink. Set basic attributes of the E-LAN service as planned.
NOTE
Step 4 Configure the ports mounted to the bridge on the UNI side.
1. Click Get UNI Port.
The Get UNI Port dialog box is displayed.
2. Configure the ports mounted to the bridge on the UNI side.
a. Select the port to be mounted to the bridge.
NOTE
The port members that are added to the same split horizon group cannot communicate with each other.
1. Click Set the service parameters and select Split Horizon Group.
2. Click New.
The Create Split Horizon Group dialog box is displayed.
Hold the Ctrl key on the key board to select multiple ports.
4. Click OK.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l For the board that transmits the IEEE 802.1ad bridge-based E-LAN service, Port Mode
has been set to Layer 2.
Context
l Configure services based on the service model described in 802.1ad Bridge-based E-
LAN Services.
l For the OptiX RTN 905, OptiX RTN RTN 910A, the OptiX RTN 950A and the OptiX
RTN 950 that houses CSHU/CSHUA boards, the total number of VLAN IDs configured
for all Ethernet services cannot exceed 1024. The total number of VLAN IDs configured
for all Ethernet services does not include the number of VLAN IDs for E-LAN services
configured in VLAN Filtering Table. Ports in VLAN Filtering Table cannot be used to
transmit other Ethernet services.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree. Choose Configuration > Ethernet
Service Management > E-LAN Service from the Function Tree.
Step 2 Click New.
The New E-LAN Service dialog box is displayed.
Step 3 Set parameters of the E-LAN service as planned.
Step 4 Configure the ports mounted to the bridge on the UNI side.
1. Click UNI.
2. Click Configuration.
The Configure Port dialog box is displayed.
3. Configure the ports mounted to the bridge on the UNI side.
a. Select the port to be mounted to the bridge.
3. Click .
4. Click OK.
Step 7 Click OK. Close the displayed dialog box.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
Context
l Configure services based on the service model described in 802.1ad Bridge-based E-
LAN Services.
l For the OptiX RTN 905, OptiX RTN RTN 910A, the OptiX RTN 950A and the OptiX
RTN 950 that houses CSHU/CSHUA boards, the total number of VLAN IDs configured
for all Ethernet services cannot exceed 1024. The total number of VLAN IDs configured
for all Ethernet services does not include the number of VLAN IDs for E-LAN services
configured in VLAN Filtering Table. Ports in VLAN Filtering Table cannot be used to
transmit other Ethernet services.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Service Management > E-LAN Service from the Function Tree.
Step 2 Click New.
The Create E-LAN Service dialog box is displayed.
Step 3 Click Configure the source and sink. Set parameters of the E-LAN service as planned.
NOTE
Step 4 Configure the ports mounted to the bridge on the UNI side.
The port members that are added to the same split horizon group cannot communicate with each other.
1. Click Set the service parameters and select Split Horizon Group.
2. Click New.
The Create Split Horizon Group dialog box is displayed.
Hold the Ctrl key on the key board to select multiple ports.
4. Click OK.
Step 7 Click OK.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l Port Mode for the port mounted to a VSI on the UNI side has been set to Layer 2 and
Encapsulation Type has been correctly set based on the service model.
Context
l For the OptiX RTN 980 and the OptiX RTN 950 that houses CSH boards, the number of
VLAN IDs configured on a VUNI must not exceed the maximum number allowed. If it
exceeds the maximum number, you can increase the maximum number of VLAN IDs
supported by a VUNI by following instructions in A.9.3.21 Configuring Global
Attributes of VPLS Services. Alternatively, configure the VLAN filtering table on the
VUNI to resolve this issue. However, ports in the VLAN filtering table cannot be used to
transmit other Ethernet services.
l For the OptiX RTN 905/950A/910A and the OptiX RTN 950 that houses CSHU/CSHUA
boards, the total number of VLAN IDs configured for all Ethernet services cannot
exceed 1024. The total number of VLAN IDs configured for all Ethernet services does
not include the number of VLAN IDs for E-LAN services configured in VLAN
Filtering Table. Ports in VLAN Filtering Table cannot be used to transmit other
Ethernet services.
l Only some system control, switching, and timing boards of the RTN 950/980 support
VPLS, as listed in the following table.
Table A-7 VPLS support by system control, switching and timing boards of the RTN
950/980
NE Type System Control, Switching, and
Timing Board That Supports VPLS
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree. Choose Configuration > Ethernet
Service Management > E-LAN Service from the Function Tree.
Step 2 Click New.
The New E-LAN Service dialog box is displayed.
Step 3 Set parameters for the E-LAN services according to the network plan.
Step 4 Configure the port mounted to the VSI on the UNI side.
1. Click the UNI tab.
2. For RTN 905/950A, when Tag Type is set to S-Aware, do not select PB-UNI.
3. Click Configuration.
The Configure Port dialog box is displayed.
4. Configure the port mounted to the VSI on the UNI side.
a. Select the port to be mounted to the VSI and configure VLAN information.
NOTE
For OptiX RTN 950 using CSHU/CSHUA boards and OptiX RTN 905/950A, the total number of
VLANs configured for Ethernet services must not exceed 1024. To avoid this restriction, do as follows:
1. Retain VLANs/CVLAN of some ports to null.
2. Set VLAN Filtering Table to the desired VLANs for the ports.
In this case, the VLANs configured in VLAN Filtering Table will not be counted in the VLANs
configured for Ethernet services. However, theses ports cannot participate in other Ethernet services.
The number of VLANs connected to a V-UNI is restricted when VPLS services are configured on
OptiX RTN 980 and OptiX RTN 950 using CSH boards. Users can use the preceding method to break
through this restriction or decrease the number of V-UNIs supported by an NE to increase the number
of VLANs that can be connected to a V-UNI.
5. Click OK.
Step 5 Configure the PW mounted to the VSI on the NNI side.
1. Click NNI.
2. Click Add.
The Configure PW dialog box is displayed.
3. Configure the PW mounted to the VSI.
4. Click OK.
Step 6 Optional: Configure split horizon groups.
NOTE
The port members that are added to the same split horizon group cannot communicate with each other.
1. Click the Split Horizon Group tab and click New.
The New Split Horizon Group dialog box is displayed.
2. Set port parameters for the split horizon group as planned.
3. Click .
4. Click OK.
Step 7 Click OK. Close the displayed dialog box.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Context
The following table lists the relationships between the number of VUNIs on an OptiX RTN
950/980 and the number of VLANs supported by the VUNIs.
Table A-8 Relationship between the number of VUNI ports and the number of VLANs
Maximum Number of VUNI Ports (X) Maximum Number of VLANs
X ≤ 32 4096
32 < X ≤ 64 2047
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree. Choose Configuration >
VPLS Management from the Function Tree.
NOTE
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The E-LAN services must be created.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree. Choose Configuration > Ethernet
Service Management > E-LAN Service from the Function Tree.
NOTE
l To add or delete ports connected to the VB on the UNI side, click the UNI tab.
l To add or delete ports connected to the VB on the NNI side, click the NNI tab.
1. Click Configuration. In the displayed Configure Port dialog box, select the port to be
added to or deleted from the list of ports connected to the VB.
2. Optional: Click to add ports to the list of ports connected to the VB.
3. Optional: Click to delete ports from the list of ports connected to the VB.
NOTE
Hold the Ctrl key on the key board to select multiple ports.
4. In Selected Port List, set the attributes of the ports connected to the VB.
5. Click OK.
A dialog box is displayed for confirmation.
6. Click Yes.Close the displayed dialog box.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The E-Line service is configured and this service is not used.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Service Management > E-Line Service from the Function Tree.
Step 2 Click Query.Close the displayed dialog box.
Step 3 Select the E-Line service that needs to be deleted and then click Delete.
A dialog box is displayed, querying whether you need to perform this operation.
Step 4 Click Yes. Close the displayed dialog box.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l A configured E-LAN service is not required.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree. Choose Configuration > Ethernet
Service Management > E-LAN Service from the Function Tree.
Step 2 Click Query.Close the displayed dialog box.
----End
Prerequisites
l The E-LAN service must be created.
l You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Service Management > E-LAN Service from the Function Tree.
Step 2 On the main interface, select the E-LAN service whose static MAC address entry needs to be
created.
Step 6 Click OK, and then close the dialog box that is displayed.
----End
Prerequisites
l The E-LAN service must be created.
l You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Service Management > E-LAN Service from the Function Tree.
Step 2 On the main interface, select the E-LAN service whose blacklist entry of MAC addresses
needs to be created.
Step 6 Click OK, and then close the dialog box that is displayed.
----End
Prerequisites
l The E-LAN service must be created.
l You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Service Management > E-LAN Service from the Function Tree.
Step 5 Click Apply, and then close the dialog box that is displayed.
----End
Prerequisites
l The E-LAN service must be created.
l You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Service Management > E-LAN Service from the Function Tree.
Step 2 On the main interface, select the E-LAN service whose dynamic MAC address needs to be
queried or cleared.
Step 3 Click the Self-Learning MAC Address tab.
Step 4 Optional: Select the board whose dynamic MAC address needs to be queried and then check
the dynamic MAC addresses in the MAC address table that is displayed.
Step 5 Optional: Click Clear MAC Address to clear the dynamic MAC addresses.Then, click Yes
in the dialog box that is displayed for confirmation.
----End
Prerequisites
l The E-LAN service must be created.
l You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Service Management > E-LAN Service from the Function Tree.
Step 2 On the main interface, select the E-LAN service, the mode for processing whose unknown
frame needs to be set.
Step 3 Click the Unknown Frame Processing tab.
Step 4 Set the mode for processing an unknown frame of the E-LAN service.
Step 5 Click Apply, and then close the dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The boards where the member ports are located must be added in NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protocol Configuration > MSTP Configuration from the Function Tree.
Step 2 Click the Port Group Parameters tab.
2. Select the board where the member port is located from the drop-down list of Board
under Apply Port.
3. Select the member port from Available Port List. Then, click .
NOTE
To select more than one port at a time, press and hold the Ctrl key or Shift key when selecting the
ports.
4. Click OK.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The port group must be created.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protocol Configuration > MSTP Configuration from the Function Tree.
Step 2 Click the Bridge Parameters tab.
NOTE
The Ethernet board is product-specific.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The port group must be created.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protocol Configuration > MSTP Configuration from the Function Tree.
Step 3 Select the port group from the drop-down list of Port Group.
NOTE
The Ethernet board is product-specific.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The MSTP port group must be created.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protocol Configuration > MSTP Configuration from the Function Tree.
Step 2 Click the CIST Running Information tab.
Step 3 Click Query.
Step 4 Query the CIST running information.
----End
A.9.6.5 Changing the Spanning Tree Protocol Used by the Port Group
When the spanning tree protocol is upgraded (for example, from the STP protocol to the
MSTP protocol) for the equipment that runs the spanning tree together with the local NE, you
need to change the spanning tree protocol used by the port group on the local NE to be the
same.
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protocol Configuration > MSTP Configuration from the Function Tree.
Step 3 Select the target protocol type from the Protocol Type drop-down list of the port group whose
spanning tree protocol needs to be changed.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protocol Configuration > MSTP Configuration from the Function Tree.
Step 2 Click the Port Group Parameters tab.
Step 3 Select Enabled or Disabled from the Enable Protocol drop-down list of the port group for
which the MSTP protocol needs to be enabled or disabled.
Step 5 Select Enabled or Disabled from the Enable Protocol drop-down list in Port Group to
enable or disable the MSTP protocol of a port.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protocol Configuration > MSTP Configuration from the Function Tree.
Step 2 Click the Port Group Parameters tab.
Option Description
If... Then...
A member port needs to 1. Select the board where the member ports are located from
be added the drop-down list of Board.
2. Select the port to be added from Available Port List.
3. Click .
A member port needs to 1. Select the port to be deleted from Selected Port List.
be deleted
2. Click .
NOTE
To select more than one port at a time, press and hold the Ctrl key or Shift key when selecting the ports.
----End
Context
OptiX RTN 950 housing CSHU/CSHUA and OptiX RTN 950A do not support this operation.
Prerequisites
l OptiX RTN 950A does not support this operation.
l OptiX RTN 950 supports this operation only when housing the system control board
CSH.
l You must be an NM user with NE operator authority or higher.
l The E-LAN service must be created.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protocol Configuration > IGMP Snooping Configuration from the Function Tree.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The E-LAN service must be created.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protocol Configuration > IGMP Snooping Configuration from the Function Tree.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The E-LAN service must be created.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protocol Configuration > IGMP Snooping Configuration from the Function Tree.
Step 2 Click the Route Member Port Management tab.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The E-LAN service must be created.
l The NNI port must be configured for the E-LAN service.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protocol Configuration > IGMP Snooping Configuration from the Function Tree.
Step 2 Click the Route Management tab.
1. Select the static router port from the drop-down list of Available Port. Click .
NOTE
To select more than one port at a time, press and hold the Ctrl key or the Shift key when selecting
the ports.
2. Click OK.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The E-LAN service must be created.
l The UNI port must be configured for the E-LAN service.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protocol Configuration > IGMP Snooping Configuration from the Function Tree.
2. Select the member ports from the drop-down list of Available Port. Click .
NOTE
To select more than one port at a time, press and hold the Ctrl key or Shift key when selecting the
ports.
3. Click OK.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The E-LAN service must be created.
l The UNI port must be configured for the E-LAN service.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protocol Configuration > IGMP Snooping Configuration from the Function Tree.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The E-LAN service must be created.
l The UNI port must be configured for the E-LAN service.
l Dynamic or static multicast member ports must be configured.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protocol Configuration > IGMP Snooping Configuration from the Function Tree.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The board of the Ethernet ports must be added on NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Background Information
The OptiX RTN 900 has a default DS domain, whose Mapping Relation ID is 1 and
Mapping Relation Name is default map. If a port is bound to a new DS domain, the NMS
automatically deletes the port from the default DS domain.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Diffserv Domain Management > Diffserv Domain Management from the
Function Tree.
Step 2 Click New.
The Create DS Domain dialog box is displayed.
Step 3 On the main interface, configure the DS domain attributes.
Step 5 Configure the mapping relationships between the priorities of ingress packets and PHB
service classes.
Step 6 Click the Outbound Mapping Relation tab.
Step 7 Configure the mapping relationships between the priorities of egress packets and PHB service
classes.
Step 8 Select Board where the application ports exist from Application Port.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Background Information
The OptiX RTN 900 has a default DS domain, whose Mapping Relation ID is 1 and
Mapping Relation Name is default map.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Diffserv Domain Management > Diffserv Domain Management from the
Function Tree.
Step 2 Select the created DS domain and change its attributes on the main interface.
Step 3 Optional: Change the mapping relationship in the ingress direction.
1. Click the Inbound Mapping Relation tab.
2. Double-click the parameters whose values need to be changed and change the mapping
relationship between the packet priorities and PHB classes in the ingress direction.
----End
A.9.8.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet
Types
This section describes how to add or delete a port that uses the DS domain and set the packet
type over the port.
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Background Information
The OptiX RTN 900 has a default DS domain, whose Mapping Relation ID is 1 and
Mapping Relation Name is default map.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Diffserv Domain Management > Diffserv Domain Management from the
Function Tree.
Step 2 Select the DS domain for which you need to add or delete an application port on the main
interface.
Option Description
If... Then...
You need to add a port that 1. Select the board where the application port is located
uses the DS domain from the drop-down list of Board.
2. Select the port to be added from the drop-down list of
Available Port.
3. Click .
You need to delete a port 1. Select the board where the application port is located
that uses the DS domain from the drop-down list of Board.
2. Select the port to be deleted from the port list of
Selected Port.
3. Click .
You need to change the Select a new packet type from the drop-down list of Packet
packet type identified by the Type.
port
NOTE
Hold the Ctrl key on the key board to select multiple ports.
NOTE
l C-VLAN indicates the client-side VLAN, and the value 7 indicates the highest priority.
l S-VLAN indicates the server-side VLAN, and the value 7 indicates the highest priority.
l The differentiated services code point (DSCP) refers to bits 0-5 of the differentiated services (DS) field in
the packet and indicates the service class and discarding priority of the packet.
l The packets trusted by the OptiX RTN 900 are the C_VLAN, S_VLAN, IP DSCP and MPLS packets that
contain the C_VLAN priority, S_VLAN priority, DSCP value or MPLS EXP value. By default, the
untrusted packets are mapped to the BE service class for best-effort forwarding.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Diffserv Domain Management > Egress DSCP Mapping from the
Function Tree.
Step 2 Choose Enabled or Disabled.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
NOTE
This function is supported by RTN 905, RTN 950 with CSHU/CSHUA boards and RTN 950A .
Procedure
Step 1 In the NE Explorer, select an NE from the object tree, and choose Configuration > QoS
Management > Diffserv Domain Management > Diffserv Domain Management from the
function tree.
Step 2 Click the Application Object tab.
Step 3 Click Modify.
The Configure Port dialog box is displayed.
Step 4 Select the desired port and modify Enable Outbound Mapping.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The board of the Ethernet ports must be added on NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Policy Management > Port Policy from the Function Tree.
Step 2 Click New. The Create Port Policy dialog box is displayed.
NOTE
l The strict priority (SP) scheduling algorithm is designed for the key services. One important characteristic
of the key services is that higher priorities are required to minimize the response delay in the case of
congestion events.
l The weighted round robin (WRR) scheduling algorithm divides each port into multiple output sub-
queues. The polling scheduling is performed among the output sub-queues to ensure that each sub-queue
has a certain period of service time.
l The OptiX RTN 900 supports the setting of the SP+WRR scheduling algorithm of the CoS queue
according to the requirement, and provides one or more queues that comply with the SP algorithm.
Except for the default value, however, the value of the WRR scheduling algorithm and the value of the SP
scheduling algorithm cannot be interleaved. That is, except for the default value, Grooming Police After
Reloading can be changed from SP to WRR according to the queue priorities in a descending order
(CS7-BE).
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The port policy must be created.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Policy Management > Port Policy from the Function Tree.
Step 2 Select the port policy whose parameter values need to be changed.
Step 3 Double-click the parameters whose values need to be changed and change the queue
scheduling, packet dropping policies, and queue shaping of the port queues.
NOTE
l The strict priority (SP) scheduling algorithm is designed for the key services. One important characteristic
of the key services is that higher priorities are required to minimize the response delay in the case of
congestion events.
l The weighted round robin (WRR) scheduling algorithm divides each port into multiple output sub-
queues. The polling scheduling is performed among the output sub-queues to ensure that each sub-queue
has a certain period of service time.
l The OptiX RTN 900 supports the setting of the SP+WRR scheduling algorithm of the CoS queue
according to the requirement, and provides one or more queues that comply with the SP algorithm.
Except for the default value, however, the value of the WRR scheduling algorithm and the value of the SP
scheduling algorithm cannot be interleaved. That is, except for the default value, Grooming Police After
Reloading can be changed from SP to WRR according to the queue priorities in a descending order
(CS7-BE).
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The Ethernet board must be added on the NE Panel.
l The port policy must be created.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Policy Management > Port Policy from the Function Tree.
NOTE
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The board of the Ethernet ports must be added on NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Policy Management > Port WRED Policy from the Function Tree.
Step 3 Configure discard thresholds and discard rates for packets in different colors.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The board of the Ethernet ports must be added on NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
This operation is supported only by OptiX RTN 950A, OptiX RTN 950 (using CSHU or
CSHUA boards), OptiX RTN 910A, and OptiX RTN 905 1E/2E.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Policy Management > Service WRED Policy from the Function Tree.
Step 3 Configure discard thresholds and discard rates for packets in different colors.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The board of the Ethernet ports must be added on NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
In the default WRR scheduling policy for OptiX RTN 900, AF4, AF3, AF2, and AF1 occupy
the same weight of 25% and other queues occupy the weight of 0%.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Policy Management > WRR Scheduling Policy from the Function Tree.
NOTE
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The Ethernet board must be added on the NE Panel.
l The port policy must be created.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Policy Management > Port Policy from the Function Tree.
Step 2 Click the Application Object tab.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The board of the Ethernet ports must be added on NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
This operation is supported only by OptiX RTN 950A, OptiX RTN 950 (using CSHU or
CSHUA boards), OptiX RTN 910A, and OptiX RTN 905 1E/2E.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Policy Management > V-UNI Egress Policy from the Function Tree.
Step 2 Click New. The Create V-UNI Egress Policy dialog box is displayed.
Step 4 Configure scheduling, packet dropping policies, and shaping for V-UNI Egress queues.
NOTE
l The strict priority (SP) scheduling algorithm is designed for the key services. One important characteristic
of the key services is that higher priorities are required to minimize the response delay in the case of
congestion events.
l The weighted round robin (WRR) scheduling algorithm divides each port into multiple output sub-
queues. The polling scheduling is performed among the output sub-queues to ensure that each sub-queue
has a certain period of service time.
l The OptiX RTN 900 supports the setting of the SP+WRR scheduling algorithm of the CoS queue
according to the requirement, and provides one or more queues that comply with the SP algorithm.
Except for the default value, however, the value of the WRR scheduling algorithm and the value of the SP
scheduling algorithm cannot be interleaved. That is, except for the default value, Grooming Police After
Reloading can be changed from SP to WRR according to the queue priorities in a descending order
(CS7-BE).
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The board on which the Ethernet port resides has been added on the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
This operation is supported only by OptiX RTN 950A, OptiX RTN 950 (using CSHU or
CSHUA boards), OptiX RTN 910A, and OptiX RTN 905 1E/2E.
Procedure
Step 1 Select an NE from the object tree in the NE Explorer. Choose Configuration > Ethernet
Service Management > V-UNI Group from the function tree.
Step 2 Click New and the New V-UNI Group dialog box is displayed.
Step 3 Set parameters for the V-UNI group.
NOTE
For the current version, V-UNI Group Type must be set to Egress.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The board of the Ethernet ports must be added on NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
This operation is supported only by OptiX RTN 950A, OptiX RTN 950 (using CSHU or
CSHUA boards), OptiX RTN 910A, and OptiX RTN 905 1E/2E.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Policy Management > PW Policy from the Function Tree.
Step 4 Configure scheduling, packet dropping policies, and shaping for PW queues.
NOTE
l The strict priority (SP) scheduling algorithm is designed for the key services. One important characteristic
of the key services is that higher priorities are required to minimize the response delay in the case of
congestion events.
l The weighted round robin (WRR) scheduling algorithm divides each port into multiple output sub-
queues. The polling scheduling is performed among the output sub-queues to ensure that each sub-queue
has a certain period of service time.
l The OptiX RTN 900 supports the setting of the SP+WRR scheduling algorithm of the CoS queue
according to the requirement, and provides one or more queues that comply with the SP algorithm.
Except for the default value, however, the value of the WRR scheduling algorithm and the value of the SP
scheduling algorithm cannot be interleaved. That is, except for the default value, Grooming Police After
Reloading can be changed from SP to WRR according to the queue priorities in a descending order
(CS7-BE).
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The board of the Ethernet ports must be added on NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
This operation is supported only by OptiX RTN 950A, OptiX RTN 950 (using CSHU or
CSHUA boards), OptiX RTN 910A, and OptiX RTN 905 1E/2E.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Policy Management > QinQ Policy from the Function Tree.
Step 2 Click New. The Create QinQ Policy dialog box is displayed.
Step 4 Configure scheduling, packet dropping policies, and shaping for QinQ queues.
NOTE
l The strict priority (SP) scheduling algorithm is designed for the key services. One important characteristic
of the key services is that higher priorities are required to minimize the response delay in the case of
congestion events.
l The weighted round robin (WRR) scheduling algorithm divides each port into multiple output sub-
queues. The polling scheduling is performed among the output sub-queues to ensure that each sub-queue
has a certain period of service time.
l The OptiX RTN 900 supports the setting of the SP+WRR scheduling algorithm of the CoS queue
according to the requirement, and provides one or more queues that comply with the SP algorithm.
Except for the default value, however, the value of the WRR scheduling algorithm and the value of the SP
scheduling algorithm cannot be interleaved. That is, except for the default value, Grooming Police After
Reloading can be changed from SP to WRR according to the queue priorities in a descending order
(CS7-BE).
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l An Ethernet service has been created.
l An policy has been created.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
This operation is supported only by OptiX RTN 950A, OptiX RTN 950 (using CSHU or
CSHUA boards), OptiX RTN 910A, and OptiX RTN 905 1E/2E.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Service Management > E-Line Service from the Function Tree.
Step 2 Select the Ethernet service and click QoS.
Step 4 Click Apply and close the dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The Ethernet board must be created on the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Port Shaping Management from the Function Tree.
Step 2 Click New.
The New dialog box is displayed.
Step 3 Set the parameters for port shaping.
NOTE
If the traffic shaping function is enabled, OptiX RTN 900 processes the packets in the buffer queue through
the following methods when no packets are available in the queue.
l When the buffer queue is empty, the packets are processed as follows: If the rate of a packet is equal to or
lower than the PIR, it is directly forwarded; if the rate of a packet is higher than the PIR, it enters the
buffer queue and then is forwarded at a rate equal to the PIR.
l When the buffer queue is empty, certain burst packets can be forwarded if the rate of the packets is equal
to or lower than the PIR in a certain period. The maximum traffic of the burst packets is determined by
the PBS.
l When the buffer queue is not empty, the packets whose rate passes the restriction of the PIR directly enter
the buffer queue and then are forwarded at a rate equal to the PIR.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
MPLS Management > Unicast Tunnel Management from the Function Tree.
Step 2 Click the Static Tunnel tab.
Step 3 Select the MPLS tunnel and set CIR (kbit/s).
Step 4 Click Apply and close the dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l An ETH PWE3 service has been created.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Service Management > E-Line Service from the Function Tree.
Step 3 On the PW tab page, set the parameters related to bandwidth limitation.
Step 4 Click Apply and close the dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l An QinQ service has been created.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
This operation is supported only by OptiX RTN 950A, OptiX RTN 950 (using CSHU or
CSHUA boards), OptiX RTN 910A, and OptiX RTN 905 1E/2E.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Service Management > E-Line Service from the Function Tree.
Step 2 Select the QinQ service and click QoS.
Step 3 On the QinQ Link tab page, set the parameters related to bandwidth limitation.
Step 4 Click Apply and close the dialog box that is displayed.
----End
A.9.9.1 Creating an MD
A maintenance domain (MD) defines the Ethernet OAM range and level. MDs of different
ranges and levels can provide users with differentiated OAM services.
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding board must be added on the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Service OAM Management from the Function Tree.
Step 2 Click the Maintenance Association tab.
Step 3 Choose New > New Maintenance Domain.
The system displays the New Maintenance Domain dialog box.
NOTE
----End
A.9.9.2 Creating an MA
An MD can be divided into several independent maintenance associations (MAs). By creating
MAs, you can associate specific Ethernet services with MAs. This facilitates Ethernet OAM
operations.
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The MD must be created.
l The Ethernet service must be created.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Service OAM Management from the Function Tree.
Step 3 Select the maintenance domain in which a maintenance association needs to be created.
Choose New > New Maintenance Association.
The system displays the New Maintenance Association dialog box.
NOTE
Click in Relevant Service. Select the corresponding services in the displayed Select
Service dialog box.
Step 6 Optional: When Y.1731–based Ethernet OAM is used, set Protocol/Standard to Y.1731 and
set the MEG ID corresponding to the MA according to the plan. Then, click Apply.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The MA must be created.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Service OAM Management from the Function Tree.
Step 3 Select the maintenance association in which an MEP needs to be created. Choose New > New
MEP Point.
The system displays the New MEP Point dialog box.
NOTE
l Each MEP needs to be configured with an MP ID, which is unique in the maintenance association.
The MP ID is required in the OAM operation.
l Direction specifies the direction of the MEP.
l Ingress indicates the direction in which the packets are transmitted to the port, and Egress indicates
the direction in which the packets are transmitted from the port.
l In the case of the tests based on the MP IDs, CC Status must be set to Active.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The MA must be created.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Service OAM Management from the Function Tree.
Step 2 Click the Maintenance Association tab.
Step 3 Choose OAM > Manage Remote MEP Point. The Manage Remote MEP Point dialog box
is displayed.
Step 4 Click New.
The Add Maintenance Association Remote Maintenance Point dialog box is displayed.
NOTE
If other MEPs will initiate OAM operations to an MEP in the same MA, set these MEPs as remote
MEPs.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The MA must be created.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Service OAM Management from the Function Tree.
Step 3 Select the maintenance domain in which an MIP needs to be created, and then click New.
The New MIP Maintenance Point dialog box is displayed.
NOTE
l Each MIP needs to be configured with an MP ID, which is unique in the maintenance domain. The
MP ID is required in the OAM operation.
l To create MEPs and MIPs in a service at a port, ensure that only one MIP can be created and the
level of the MIP must be higher than the level of the MEP.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The MEP must be created.
l The remote MEPs must be created.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Background Information
l Only the MEP can enable the CC test and function as the receiving and responding end
in the test.
l During the CC check, the source MEP constructs and transmits continuity check
message (CCM) packets periodically. After receiving the CCM packets from the source
MEP, the sink MEP directly enables the CC function for this source MEP. If the sink
MEP fails to receive the CCM packets from the source MEP within the check period
(that is, 3.5 times of the transmit period), it reports the alarm automatically.
l Performing a CC test does not affect the services.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Service OAM Management from the Function Tree.
Step 3 Select the MEP where you need to perform the CC test and then choose OAM > Activate
CC.
A dialog box is displayed, indicating that the operation is successful.
NOTE
l Before the CC test, you can set CC Test Transmit Period according to the actual requirements.
l To disable a CC test, select the MEP where the CC test is performed and then choose OAM >
Deactivate.
NOTE
l Alternatively, you can enable a CC test by right-clicking an MEP and then choosing Activate CC
from the shortcut menu.
l Alternatively, you can disable a CC test by right-clicking an MEP and then choosing Deactivate CC
from the shortcut menu.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The source and sink MEPs in the same maintenance domain must be created.
l The remote MEPs must be created.
l The CC function must be enabled.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Background Information
l Only MEPs can initiate the LB test and function as the receive end in the test.
l During the LB test, the source MEP constructs and transmits the LBM frames and starts
the timer. If the sink MP receives the LBM frames, it sends the LBR frames back to the
source MEP. This indicates that the loopback is successful. If the source MEP timer
times out, it indicates that the loopback fails.
l Performing an LB test does not affect the services.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Service OAM Management from the Function Tree.
Step 2 Click the Maintenance Association tab.
Step 3 Select the maintenance domain and maintenance association for the LB test.
To enable an LB test, you can also right-click an MEP and then choose Start LB from the shortcut
menu.
Step 5 Select the method for identifying the destination MP and set the parameters involved in the
LB test.
NOTE
l To identify the destination MP according to the MP ID, select MP ID. Only the MEP ID can be set
to the Destination Maintenance Point ID.
l To identify the destination MP according to the MAC address, select Maintenance Point MAC
Address. Only the MAC address of the MEP can be set to the MAC address of the Destination
Maintenance Point MAC Address.
Step 6 Click Start Test. Then, the LB test result is displayed in the Detection Result window.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The source and sink MEPs in the same MD must be created.
l The remote MEPs must be created.
l The CC function must be enabled.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Background Information
l Only MEPs can initiate the LT test and work as the termination point in the test.
l During the LT test, the source MEP constructs and transmits the LTM frames and starts
the timer. All the MPs that receive the LTM frames send the LTR frame response.
According to the LTR frame response, you can verify all the MIPs that pass from the
source MEP to the sink MEP.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Service OAM Management from the Function Tree.
Step 3 Select the maintenance domain and maintenance association for the LT test.
To enable an LT test, you can also right-click an MEP and then choose Start LT from the shortcut menu.
Step 5 Select the method for identifying the destination MP and set the parameters involved in the
LT test.
NOTE
l To identify the destination MP according to the MP ID, select MP ID. Only the MEP ID can be set
to the Destination Maintenance Point ID.
l To identify the destination MP according to the MAC address, select Maintenance Point MAC
Address. Only the MAC address of the MEP can be set to the MAC address of the Destination
Maintenance Point MAC Address.
Step 6 Click Start Test. Then, the LT test result is displayed in the Detection Result window.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The source and sink MEPs in the same MD must be created.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Service OAM Management from the Function Tree.
Step 4 Select the node to be monitored. Double-click or right-click AIS Active Status and then
select Active or Inactive.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l Source and sink maintenance end points (MEPs) in the same maintenance domain (MD)
have been created.
Context
For details about restriction on the features related to the operation, see Feature Dependencies
and Limitations.
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree and choose Configuration >
Ethernet OAM Management > Ethernet Service OAM Management from the Function
Tree.
Step 4 Optional: For OptiX RTN 950 housing CSHU/CSHUA and OptiX RTN 950A, Set the
LM/DM monitoring policy on MEPs at both ends.
1. Select the MEP to test and choose New > New Test ID.
2. Set the performance monitoring policy as required.
3. Click OK.
Step 5 For OptiX RTN 905, OptiX RTN 950 housing CSH, and OptiX RTN 980, right-click an MEP
and choose Browse Performance from the shortcut menu. For OptiX RTN 950 housing
CSHU/CSHUA and OptiX RTN 950A, right-click a Test ID and choose Browse
Performance from the shortcut menu.
If... Then...
You want to query the current packet loss ratio, Click the Statistics Group tab and
delay, or delay variation set required parameters.
You want to query the historical packet loss ratio, Click the History Group tab and set
delay, or delay variation required parameters.
NOTE
Ensure that historical performance monitoring for
associated periods has been enabled before querying the
historical packet loss ratio, delay, or delay variation.
You want to set alarming thresholds for the Click the RMON Setting tab. Then
packet loss ratio, delay, or delay variation click the Event tab and set required
parameters.
You want to set the historical performance Click the RMON Setting tab. Then
monitoring period for the packet loss ratio, delay, click the Object tab and set required
or delay variation parameters.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l E-LAN services have been created.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
l Creation of MEPs is not a prerequisite for service loopback detection.
l During an E-LAN service loopback test, if a node on the network to which the tested
port is connected reports a loopback packet threshold-crossing event, there is an E-LAN
service loop on this node.
l This task can also be completed by choosing Service > Service Path View from the
main menu.
Procedure
Step 1 In the NE Explorer, select the desired NE and choose Configuration > Ethernet Service
Management > E-LAN Service from the Function Tree.
Step 3 Select the services where service loopback detection will be performed and click Start.
The Start Loopback dialog box is displayed.
l Vlans/CVLAN displays the VLAN ID of a loopback service. Loopback detection can be performed for
only one service one time.
l Loopback detection stops if no loopback detection packets are received until Packet Timeout Period(s)
expires.
l Disable Service When Loopback is Detected displays whether a loopback service will be deactivated.
Step 5 Click Start. Then, close the dialog box that is displayed.
Detection Result displays the loopback detection result.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l An E-LAN service port has been shut down due to a service loopback.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree. Choose Configuration > Ethernet
Service Management > E-LAN Service from the Function Tree.
Step 2 Click the Loopback tab.
Step 3 Click Service Status List.
The Service Status List dialog box is displayed.
Step 4 Select the port where an E-LAN service needs to be reactivated and click Enable. Close the
dialog box that is displayed.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
l If a UNI receives a loop detection packet whose destination MAC address is the same as
the source MAC address of the loop detection packet sent by the UNI, a service loop
occurs. If a UNI does not receive a loop detection packet within the specified duration, a
service loop does not occur. The duration ranges from 3s to 10s and the default value is
3s. Upon the detection of a service loop, the looped service is automatically disabled.
l Automatic service loop detection disables the looped service rather than the UNI.
Disabling of the looped service does not affect the other services on the UNI.
l Service loop detection packets are forwarded along the service forwarding path.
Precautions
l If Initiate upon Service Creation is Auto, service loop detection will be automatically
initiated after a logical port is added. If multiple services carrying different VLAN IDs
are added on a logical port, service loop detection will be initiated on any two services
among them. If a loop is detected on either of the two services, all the newly added
services are disabled.
l If Initiate upon Port Status Change is Auto, service loop detection will be
automatically initiated on all logical ports on a physical port after the physical port
changes from Down to Up. If a logical port is configured with multiple services carrying
different VLAN IDs, service loop detection will be automatically initiated on any two
services among them. If a loop is detected on either of the two services, the logical port
is disabled. If the other services are looped, no service loop can be detected.
Procedure
Step 1 In the NE Explorer, select an NE from the object tree, and choose Diagnosis&Maintenance >
E-LAN LD Test Management from the function tree.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l An egress MEP has been created.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Background
l Bandwidth notification can be configured only on an egress MEP.
l Bandwidth notification packets do not affect services.
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree. Choose Configuration >
Ethernet OAM Management > Ethernet Service OAM Management from the Function
Tree.
Step 4 Select the desired MEP. Click OAM and choose Configure Bandwidth Advertisement.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Background Information
The OAM auto-discovery is realized based on the auto-negotiation between the local
equipment and the opposite equipment. If the negotiation fails, the local equipment reports an
alarm. After OAM auto-discovery is successfully completed, the link performance is
monitored according to the error frame threshold. You can set the error frame threshold on the
NMS.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Port OAM Management from the Function Tree.
l The OAM mode includes the active mode and the passive mode. For two interconnected systems,
the OAM mode of either or both systems must be the active mode. Otherwise, the OAM auto-
discovery fails.
l If both ends of a link are in passive OAM mode, a link fault occurs, or either end of a link does not
receive OAM protocol packets within 5 seconds, an alarm is reported, indicating that OAM auto-
discovery fails.
Step 6 Click the Remote OAM Parameter tab. Click Query to obtain the OAM capability of the
opposite end. Close the displayed dialog box.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The OAM auto-discovery operation must successful on the equipment at both ends.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Port OAM Management from the Function Tree.
Step 2 Click the OAM Parameter tab.
Step 3 Select the corresponding port and set Link Event Notification to Enabled.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The IEEE 802.3ah OAM function must be enabled on the remote equipment and the
OAM auto-discovery operation must be successful on the equipment at both ends.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Background Information
After the OAM auto-discovery operation is successful, the remote link event notification
function is enabled and the monitoring time and errored frame threshold are set at the local
end. If the local equipment detects a link event in the receive direction, it informs the opposite
equipment of the link event. If the remote alarm for the link event is also supported at the
opposite end, the opposite equipment can also inform the local equipment of the link event
that is detected at the opposite end. Then, the corresponding alarm is reported at the local end.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Port OAM Management from the Function Tree.
Step 3 Select the port and set the parameters in the OAM Error Frame Monitor tab page.
NOTE
An alarm is reported if the number of errored frame events within Monitor Window or Period Window
exceeds the specified monitoring threshold.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The OAM auto-discovery operation must be successful at both ends of the link.
l On the equipment that initiates the loopback, OAM Working Mode must be set to
Active.
l The equipment that responds to the loopback must support the remote loopback.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Background Information
l If a port is capable of responding to loopbacks, it enters the loopback responding state
and reports the loopback responding alarm after receiving the command of enabling the
remote loopback function sent from the opposite OAM port. In this case, the equipment
that initiates the loopback enters the loopback initiation state and reports the loopback
initiation alarm.
l Generally, after the remote loopback function is enabled, service packets, except the
OAMPDU, are looped back at the remote end.
l After using the remote loopback function to complete the fault locating and the link
performance detection, you need to disable the remote loopback function at the end
where the loopback is initiated and then restore the services. The alarm is automatically
cleared.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Port OAM Management from the Function Tree.
Step 3 Select the port and set Remote Side Loopback Response to Enabled.
Step 5 Choose Enable Remote Loopback from the drop-down menu of OAM. Close the displayed
dialog box.
NOTE
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The required board is already added on the NE Panel.
l All the external physical ports on the Ethernet service processing board must be enabled.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface
Management > Ethernet Interface from the Function Tree.
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l L2 services are configured.
NOTE
L2 services include UNI-UNI E-Line services and UNI-UNI E-LAN services transmitted in a point-to-point
manner.
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT
Management > LPT from the Function Tree.
Step 2 Click the Point-to-Point LPT tab.
Step 3 Click Bind in the lower right corner of the pane based on the type of service network.
Step 4 Choose L2 net from the shortcut menu.
The Bind L2 net dialog box is displayed.
Step 5 Set the parameters of the primary and secondary points of LPT.
Step 6 Click OK, and close the dialog box that is displayed.
Step 7 Optional: Reset Recovery Time(s), Hold-Off Time(ms), and Fault Detection
Period(100ms).
Step 8 Set LPT Enabled to Enabled. Then, click Apply.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l QinQ services exclusively occupying UNI ports have been configured.
l E-Line services carried by PWs exclusively occupying UNI ports have been configured.
NOTE
l For the service models of QinQ services exclusively occupying UNI ports, see Model 1 and Model 2 in
QinQ-Based E-Line Service Models.
l For the service models of E-Line services carried by PWs exclusively occupying UNI ports, see Model 3
in PW-Carried E-Line Services.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT
Management > LPT from the Function Tree.
Step 2 Click the Point-to-Point LPT tab.
Step 4 Click Bind in the lower right corner of the pane. Then, choose PW+QinQ from the shortcut
menu.
Step 5 Optional: Reset Recovery Time(s), Hold-Off Time(ms), and Fault Detection
Period(100ms).
Step 6 Set LPT Enabled to Enabled. Then, click Apply.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l At least one of the following services has been configured.
– L2 services
– QinQ services sharing UNI ports
– E-Line services carried by PWs sharing UNI ports
NOTE
l L2 services include UNI-UNI E-Line services and UNI-UNI E-LAN services transmitted in a point-to-
multipoint manner.
l For the service models of QinQ services sharing UNI ports, see Model 3 in QinQ-Based E-Line Service
Models.
l For the service models of E-Line services carried by PWs sharing UNI ports, see Model 1 and Model 2 in
PW-Carried E-Line Services.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT
Management > LPT from the Function Tree.
Step 3 Click New in the lower right corner of the pane based on the type of service network.
Step 4 Choose PW, QinQ, or L2 net from the shortcut menu based on the type of service network.
The Create LPT dialog box is displayed.
Step 5 Set the parameters of the primary and secondary points of LPT.
Step 6 Click OK, and close the dialog box that is displayed.
Step 7 Optional: Reset Recovery Time(s), Hold-Off Time(ms), and Fault Detection
Period(100ms).
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT
Management > Simple LPT from the Function Tree.
----End
Prerequisites
l Only OptiX RTN 950(CSHU/CSHUA), OptiX RTN 950A, OptiX RTN 905 1E/2E and
OptiX RTN 910A support this operation.
l You are an NMS user with administrator rights or higher rights.
l Native Ethernet services or PW-carried Ethernet services have been created.
Procedure
Step 1 Click a desired NE in the NE Explorer and choose Diagnose&Maintenance > IP Packet
Marking from the main menu.
Step 2 (Optional) Set the coloring bit. The default value is IP FLAG BIT0.
1. Set the following parameters: ID, Name, Role, Action, and Auto Stop After(minutes).
2. Set the packet matching rules and the logical relationship between the matching rules.
l For a QinQ measurement point, set Direction, Service, and QinQ Link.
l For a tunnel measurement point, set Direction, Tunnel ID, Port, PW Label, Service
Tag Role, and PW Type.
Step 6 Click Stop to stop a test or wait for the test to automatically stop.
NOTE
l To stop a test, stop the test for an uplink node and then for a downlink node.
l To delete measurement instances, delete the measurement instance from an uplink node and then from a
downlink node.
----End
Context
NOTE
OptiX RTN 905/910A does not support the Ethernet services on EoS/EoPDH boards.
Prerequisites
l You must be an NM user with NE operator authority or higher.
l An EMS6 board has been added to the NE Panel.
Procedure
Step 1 In the NE Explorer, select the EMS6 board. Choose Configuration > Ethernet Protection >
ERPS Management.
Step 2 Click New.
The Create Ethernet Ring Protection Protocol Instance dialog box is displayed.
Step 3 Set the parameters for the ERPS instance.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l An ERPS instance has been created.
Procedure
Step 1 In the NE Explorer, select the EMS6 board. Choose Configuration > Ethernet Protection >
ERPS Management from the Function Tree.
Step 2 Optional: Double-click Control VLAN, and then modify the control VLAN ID.
NOTE
Set the parameters according to the network plan. Default values are recommended.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
Procedure
Step 1 In the NE Explorer, select the EMS6 board. Choose Configuration > Ethernet Protection >
ERPS Management from the Function Tree.
Step 2 Click Query.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board where the LAG ports are located must be added in the NE Panel.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Interface Management > Ethernet Link Aggregation
Management from the Function Tree.
Step 2 Click the Link Aggregation Group Management tab.
2. Select a slave port from Available Standby Ports and then click .
NOTE
To select more than one port at a time, press and hold the Ctrl or Shift key when selecting the
ports.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board where the LAG ports are located must be added in the NE Panel.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Interface Management > Ethernet Link Aggregation
Management from the Function Tree.
Step 3 Set the parameters associated with the system priority and port priority.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board where the LAG ports are located must be added in the NE Panel.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Interface Management > Ethernet Link Aggregation
Management from the Function Tree.
Step 4 Click Query to check the working status of the main and slave ports in the LAG.
NOTE
The system automatically displays the working status of the slave port at the bottom of the main interface.
Step 5 Right-click the LAG and select an option from the drop-down list. A dialog box is displayed,
indicating the query result.
Step 8 Click Query to check the parameters associated with the port priority and system priority.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
Precautions
For the method of creating QinQ-based Ethernet private line services, see A.10.3.5 Creating
QinQ-Based EVPL Services.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Service > Ethernet Line Service from the Function Tree.
Step 2 Deselect Display QinQ Shared Service.
The result of setting the port attributes during the Ethernet private line service configuration process is the
same as the result of directly setting the Ethernet service port attributes.
.
5. Optional: Repeat Step 6.4 to bind other VC paths.
6. Click OK.
A confirmation dialog box is displayed.
7. Click Yes.
NOTE
The result of configuring the attributes of bound paths during service configuration is consistent with the
result of directly setting the attributes of VCTRUNKs.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
Precautions
For the method of creating the IEEE 802.1ad bridge, see A.10.3.6 Creating IEEE 802.1ad
Bridge-Based EVPLAN Services.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree.
Step 2 Click New.
The Create Ethernet LAN Service dialog box is displayed.
Step 3 Set the attributes of the bridge according to the bridge type.
l Set the attributes of the IEEE 802.1q bridge.
.
3. Optional: Repeat Step 4.2 to mount other ports.
4. Click OK.
Step 5 Optional: Set the bound path.
1. Click Configuration.
The Bound Path Configuration dialog box is displayed. Set the attributes of the bound
path.
The result of configuring the attributes of bound paths during service configuration is consistent with the
result of directly setting the attributes of VCTRUNKs.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l Ethernet LAN services must be created.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree.
Step 2 Select the VB that is already created, and click the Service Mount tab.
Step 4 To change any parameter value of a mounted port, double-click the parameter value and
specify a new value.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The IEEE 802.1q/802.1ad bridge-based Ethernet LAN services must be created.
l In the case of IEEE 802.1ad bridge-based Ethernet LAN services, the learning mode of
the VB must be IVL.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree.
Step 2 Select an IEEE 802.1q or 802.1ad bridge and click the VLAN Filtering tab.
.
4. Optional: Repeat Step 3.3 to select other forwarding ports.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board, and choose Configuration > Ethernet
Service > Ethernet Line Service from the Function Tree.
Step 2 Select Display QinQ Shared Service.
Step 3 Click New.
The Create Ethernet Line Service dialog box is displayed.
Step 4 Set the attributes of the QinQ-based EVPL service.
The result of setting the port attributes during the Ethernet private line service configuration process is the
same as the result of directly setting the Ethernet service port attributes.
.
5. Optional: Repeat Step 6.4 to bind other VC paths.
6. Click OK.
A confirmation dialog box is displayed.
7. Click Yes.
NOTE
The result of configuring the attributes of bound paths during service configuration is consistent with the
result of directly setting the attributes of VCTRUNKs.
Step 7 Click OK. Then, close the dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree.
Step 2 Click New.
The Create Ethernet LAN Service dialog box is displayed.
Step 3 Set the basic attributes of the IEEE 802.1ad bridge.
4. Repeat Step 4.2 and Step 4.3 to add the other mounted ports.
5. Click OK.
6. Optional: You can change the Ethernet port attributes of the mounted ports in the
Service Mount window.
Step 5 Optional: Set the bound path.
1. Click Configuration.
The Bound Path Configuration dialog box is displayed. Set the attributes of the bound
path.
.
5. Optional: Repeat Step 5.4 to bind other VC paths.
6. Click OK.
A confirmation dialog box is displayed.
7. Click Yes.
NOTE
The result of configuring the attributes of bound paths during service configuration is consistent with the
result of directly setting the attributes of VCTRUNKs.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The Ethernet private line service must be configured and the service is not used.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Service > Ethernet Line Service from the Function Tree.
Step 3 Select the Ethernet private line service that needs to be deleted and then click Delete.
A confirmation dialog box is displayed.
Step 5 Click Query. At this time, the Ethernet private line service is already deleted.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The Ethernet LAN services must be configured and the service is not used.
Background Information
Deleting an Ethernet LAN service involves the following tasks:
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree.
Step 4 Select the VLAN filtering entries that need to be deleted. Then, click Delete.
A confirmation dialog box is displayed.
Step 7 Select the Ethernet LAN service to be deleted and click Delete.
A confirmation dialog box is displayed.
Step 9 Click Query. At this time, the Ethernet LAN service is already deleted.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
l The Ethernet LAN services must be created.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree.
Step 2 Select the bridge that is already created, and click the VLAN Unicast tab.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
l The Ethernet LAN services must be created.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree.
Step 2 Select the created bridge and click the Disable MAC Address tab.
Step 5 Click OK. Then, close the dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
l The Ethernet LAN services must be created.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board, and choose Configuration > Layer-2
Switching Management > Aging Time from the Function Tree.
Step 2 Modify the aging time of the MAC address table entry.
1. Double-click MAC Address Aging Time corresponding to the EFP8 board.
The MAC Address Aging Time dialog box is displayed.
2. Set the duration and unit of the aging time.
3. Click OK.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
l The Ethernet LAN services must be created.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree.
Step 2 Select the created bridge and click the Self-learning MAC Address tab.
Step 3 Click First Page, Previous Page, or Next Page to view the dynamic entries of a MAC
address table page by page.
Step 4 Optional: Select a MAC address to be deleted, and then click Clear MAC address. Then,
close the dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
l The Ethernet LAN services must be created.
Precautions
l In the case of EVPLAN services, you can query the capacity of a MAC address table
where MAC addresses are queried based on VLAN IDs and the capacity of a MAC
address table where MAC addresses are queried based on VB logical ports.
l In the case of EPLAN services, you can query the capacity of a MAC address table
where MAC addresses are queried based on VB logical ports.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree.
Step 2 Select a created bridge.
Step 3 Query the actual number of dynamically learnt MAC addresses based on the VLAN IDs.
1. Click the VLAN MAC Address Table Capacity tab.
2. Click Query. Then, close the dialog box that is displayed. Check the actual capacity of
the MAC address table.
Step 4 Query the actual number of dynamically learnt MAC addresses based on the VB ports.
1. Click the VB Port MAC Address Table Capacity tab.
2. Click Query. Then, close the dialog box that is displayed. Check the actual capacity of
the MAC address table.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
Precautions
Ethernet ports FE1 to FE8 on an EFP8 board correspond to PORT1 to PORT8 respectively.
PORT9 on an EFP8 board is used to connect the EoPDH plane to the packet plane. PORT9 is
provided by the Ethernet switching unit of an EFP8 board and is connected to the EoPDH
plane. PORT9 forwards Ethernet services from the packet plane to FE ports or VCTRUNKs
on an EFP8 board.
Ethernet ports GE1 and GE2 on the EMS6 board correspond to PORT1 and PORT2
respectively; Ethernet ports FE1 to FE4 on an EMS6 board correspond to PORT3 to PORT6
respectively. PORT7 on an EMS6 board is used to connect the EoS plane to the packet plane.
PORT9 is provided by the Ethernet switching unit of an EMS6 board and is connected to the
EoS plane. PORT9 forwards Ethernet services from the packet plane to FE/GE ports or
VCTRUNKs on an EMS6 board.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board and then choose Configuration > Ethernet
Interface Management > Ethernet Interface from the Function Tree.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
Precautions
The EFP8 board supports VCTRUNKs 1-16. VCTRUNKs 1-16 determine the services to be
transmitted depending on information about the created Ethernet services.
The EMS6 board supports VCTRUNKs 1-8. VCTRUNKs 1-8 determine the services to be
transmitted depending on information about the created Ethernet services.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board and then choose Configuration > Ethernet
Interface Management > Ethernet Interface from the Function Tree.
Step 4 Set the encapsulation and mapping protocol used by the VCTRUNK.
1. Click the Encapsulation/Mapping tab.
2. Set Mapping Protocol and the protocol parameters.
.
5. Optional: Repeat Step 8.4 to bind other VC paths.
6. Click OK.
A confirmation dialog box is displayed.
7. Click Yes.
NOTE
The result of configuring the attributes of bound paths during service configuration is consistent with the
result of directly setting the attributes of VCTRUNKs.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Advance Attribute > QinQ Type Area Settings from the Function Tree.
Step 2 Modify the type field of QinQ frames.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board and then choose Configuration > Ethernet
Interface Management > Ethernet Interface from the Function Tree.
2. Select the VC paths to be deleted in Selected Bound Paths, and then click .
3. Optional: Repeat Step 6.2 to delete other VC paths.
----End
A.10.6.1 Configuring the Type and Enabled Status of the Spanning Tree Protocol
If a loop is formed in an Ethernet LAN service, you need to enable the STP or RSTP for the
bridge.
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
l The Ethernet LAN services must be created.
Procedure
Step 1 In 1the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Layer-2 Switching Management > Spanning Tree from the Function
Tree.
Step 2 Click the Protocol Enabled tab.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Layer-2 Switching Management > Spanning Tree from the Function
Tree.
3. Click Apply.
3. Click Apply.
Step 4 Optional: If Protocol Type is set to RSTP, specify the point-to-point attribute of the Ethernet
port.
1. Click the Point to Point Attribute tab.
2. Set the point-to-point attribute of the port.
3. Click Apply.
----End
A.10.6.3 Querying the Running Information About the Spanning Tree Protocol
This topic describes how to query the running information about the spanning tree protocol
(STP).
Prerequisites
l You must be an NM user with NE operator authority or higher.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board, and choose Configuration > Layer-2
Switching Management > Spanning Tree from the Function Tree.
Step 2 Query the bridge running information.
1. Click the Bridge Running Information tab.
2. Click Query.
3. Check the bridge running information.
Step 3 Query the port running information.
1. Click the Port Running Information tab.
2. Click Query.
3. Check the port running information.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
l The Ethernet LAN services must be created.
l The VLAN filtering table must be created.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Layer-2 Switching Management > IGMP Snooping Protocol from the
Function Tree.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
l The Ethernet LAN services must be created.
l The VLAN filtering table must be created.
l The IGMP Snooping protocol must be enabled for the bridge.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Layer-2 Switching Management > IGMP Snooping Protocol from the
Function Tree.
Step 2 Click the Static Multicast Table tab.
Click .
NOTE
To select more than one port at a time, press and hold the Ctrl or Shift key when selecting the
ports.
3. Click OK.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
l The Ethernet LAN services must be created.
l The IGMP Snooping protocol must be enabled for the bridge.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Layer-2 Switching Management > IGMP Snooping Protocol from the
Function Tree.
Step 2 Click the Multicast Aging Time tab.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
l The Ethernet LAN services must be created.
l The IGMP Snooping protocol must be enabled for the bridge.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Layer-2 Switching Management > IGMP Snooping Protocol from the
Function Tree.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
l The associated Ethernet services must be created.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > QoS Management > Flow Management from the Function Tree.
Step 2 Click the Flow Configuration tab.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board, and then choose Configuration > QoS
Management > Flow Management from the Function Tree.
Step 2 Click the CAR Configuration.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > QoS Management > Flow Management from the Function Tree.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
l The flow must be created.
l The CAR/CoS must be created.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board, and then choose Configuration > QoS
Management > Flow Management from the Function Tree.
Step 2 Click the Flow Configuration tab.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
Procedure
Step 1 In the NE Explorer, select the required Ethernet switching board from the Object Tree and
choose Configuration > QoS Management > Port Shaping Management from the
Function Tree.
Step 2 In Port List, select a port. In Port Queue Shaping Information, set the traffic shaping
information about the egress queues.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l An EMS6 board has been added to the NE Panel.
Procedure
Step 1 In the NE Explorer, select the EMS6 board from the Object Tree and choose Configuration >
QoS Management > Port Shaping Management from the Function Tree.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l An EMS6 board has been added to the NE Panel.
Procedure
Step 1 In the NE Explorer, select the required Ethernet switching board from the Object Tree and
choose Configuration > QoS Management > Port Shaping Management from the
Function Tree.
Step 2 Click the Port Queue Information tab.
Step 4 Set Scheduling Mode and Weight for the port queue.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree.
NOTE
Step 3 Click New and choose Create MD from the drop-down list.
The Create MD dialog box is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
l The MD must be created.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree.
Step 2 In the right pane, click OAM Configuration.
The OAM Configuration dialog box is displayed.
NOTE
Step 3 Click New and choose Create MA from the drop-down list.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
Precautions
In an OAM test, all MPs that are involved in the operation of the same service flow must be in
the same MD. In an existing MD involved in the same service flow, creating an MP of the
same level or a higher level may damage the existing MD. As a result, the OAM test fails.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree.
Step 4 Optional: Click Advanced. In the displayed dialog box, set the corresponding parameters
and click OK.
NOTE
If an MEP is created, you can choose whether to perform the following configurations:
l Activate the CC and set the sending period of the CC test.
l Set the timeout time for the LB or LT test.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
l The Ethernet services must be created and activated.
l The MD and MA must be created.
l The MEPs must be created.
Background Information
l Only the MEP can enable the continuity test and function as the receive respond end for
the test.
l The source MEP constructs CCM packets and transmits them periodically. After
receiving the CCM packet from the source MEP, the sink MEP directly enables the CC
function for this source MEP. If the sink MEP fails to receive the CCM packet from the
source MEP within the check period (that is, 3.5 times of the transmission interval), it
reports the specific alarm automatically.
l Performing a CC test does not affect the services.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree.
Step 2 Select the node to be monitored, click OAM Operation, and select Activate CC.
NOTE
l Before the CC test, you can set CCM Sending Period(ms) according to the actual requirements.
l To disable a CC test, right-click the MEP where the CC test is performed and then choose Activate
CC from the shortcut menu.
NOTE
l Alternatively, you can enable a CC test by right-clicking an MEP and then choosing Activate CC
from the shortcut menu.
l Alternatively, you can disable a CC test by right-clicking an MEP and then choosing Inactivate CC
from the shortcut menu.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
l The source and sink MEPs in the same MD must be created.
l In the case of a standard MP, you must activate CC before an LB test.
Background Information
l Only an MEP can initiate an LB test.
l During the LB test, the source MEP constructs and transmits the LBM frames and starts
the timer. If the sink MP receives the LBM frames, it sends the LBR frames back to the
source MEP. This indicates that the loopback is successful. If the source MEP timer
times out, it indicates that the loopback fails.
l Performing an LB test does not affect the services.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree.
Step 2 Select the node that requires an LB test, click OAM Operation, and select Start LB.
The LB Test dialog box is displayed.
l In the case of standard MPs, when an MIP functions as the receive end in the LB test, you need to select
Test based on the MAC Address and set LB Sink MP MAC Address.
l Before the LB test, you can set LB Timeout(ms) according to the actual requirements.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
l The source and sink MEPs in the same MD must be created.
l In the case of a standard MP, you must activate CC before an LT test.
Background Information
l Only an MEP can initiate the LT test, and the MEP can work as the receive end in the
test.
l During the LT test, the source MEP constructs and transmits the LTM frames and starts
the timer. All the MPs that receive the LTM frames send the LTR frame response.
According to the LTR frame response, you can verify all the MIPs that pass from the
source MEP to the sink MEP.
l Performing an LT test does not affect the services.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree.
Step 2 Select the node that requires an LT test, click OAM Operation, and select Start LT.
Before the test, you can set LT Timeout(ms) according to the actual requirements.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
l The source and sink MEPs in the same MD must be created.
l Only a standard MP supports this function.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree.
Step 2 Select the node to be monitored. Double-click or right-click AIS Active Status and then
select Active or Inactive.
NOTE
l If several MDs exist on a link, to locate a fault accurately, set AIS Active Status to Active and Client
Layer Level that functions to suppress the AIS information.
l After a fault is detected by an MP, if this MP activates the AIS, it sends the AIS packet to a higher level
MP, informing the higher level MP of the fault information; if this MP does not activate the AIS, it does
not report the fault.
l Normally, if an MP is set to level n, Client Layer Level that functions to suppress the AIS information
should be set to n+1.
l Client Layer Level is valid only if AIS Active Status is Active.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
l The source and sink MEPs in the same MD must be created.
l You must be aware of the IP addresses of the source MP and the sink MP in the ping test.
Background Information
The source end of the ping test obtains the IP addresses of the source MP and sink MP, and
constructs and sends ARP packets and ICMP packets. The MP that receives the ARP packets
or ICMP packets parses the packets, and responds to the source end. After receiving the
response packet, the source end reports the ping test result to the NE software (including the
ratio of packet loss and time delay) based on the response packet.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree.
Step 2 Select the node to be monitored, click OAM Operation, and select Start Ping.
The Ping Test dialog box is displayed.
Step 3 Select Send Mode. Then, set Frame Length, Timeout, and Ping Attempts for the ping
packet.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
l The source and sink MEPs in the same MD must be created.
Background Information
The performance check method provides an in-service test of packet loss ratio and delay
based on the check of the connectivity between the MPs on the Ethernet service processing
unit.
A performance check is implemented as follows: The source MP initiates several LB tests and
counts different packet loss ratio and delay values.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree.
Step 2 Select the node to be monitored, click OAM Operation, and select Performance Detect.
The Performance Detect dialog box is displayed.
Step 3 Select Send Mode. Then, set Frame Length, Timeout, and Detect Attempts for the test
packet.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
Background Information
The OAM auto-discovery is achieved based on auto-negotiation between the local equipment
and the opposite equipment. If the negotiation fails, the local equipment reports an alarm.
After OAM auto-discovery is successful, the link performance is monitored according to the
error frame threshold. You can set the error frame threshold on the NMS.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function Tree.
NOTE
l The OAM mode includes the active mode and the passive mode. For two interconnected systems,
the OAM mode of either or both systems must be the active mode. Otherwise, OAM auto-discovery
fails.
l If the OAM modes of the two systems are passive modes, if a fault occurs on the link, or if one
system fails to receive the OAM protocol message within five consecutive seconds, an alarm is
reported, indicating that OAM auto-discovery fails.
Step 4 Select Enabled from the Enable OAM Protocol drop-down list.
Step 6 Click the Remote OAM Parameter tab. Click Query to check the OAM capability of the
opposite end.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
l The OAM auto-discovery operation must be successful on the equipment at both ends.
Background Information
After the OAM auto-discovery operation is successful at both ends, the link fault detection
and performance detection are automatically started.
l The local end can notify the opposite end of link fault events only if Remote Alarm
Support for Link Event is set to Enabled at the local end.
l The local end can notify the opposite end of link performance events only if Remote
Alarm Support for Link Event is set to Enabled and if the monitoring time and error
frame thresholds are configured at the local end.
l After Remote Alarm Support for Link Event is set to Enabled at the opposite port, if
the opposite end detects link performance degradation, you can query the
ETHOAM_RMT_SD alarm, which is reported on the local end, by using the NMS.
According to the alarm, you can determine the type of the link performance event.
l After Remote Alarm Support for Link Event is set to Enabled at the opposite port, if
the opposite equipment detects a link fault event or encounters a fault that makes the
equipment fail to be restored (such as a power failure), you can query the
ETHOAM_RMT_CRIT_FAULT alarm, which is reported at the local end, by using the
NMS. Based on the alarm, you can determine the fault type.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function Tree.
Step 2 Click the OAM Parameter tab.
Step 3 Select the corresponding port and set Link Event Notification to Enabled.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
l The Ethernet port OAM function must be enabled on the remote equipment and the
OAM auto-discovery operation must be successful on the equipment at both ends.
Background Information
The local end notifies the opposite end after detecting a link event in the receive direction
under the following conditions:
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function Tree.
Step 2 Click the OAM Error Frame Monitor tab.
Step 3 Select the port and set the parameters in the OAM Error Frame Monitor tab page.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
l The OAM auto-discovery operation must be successful on the equipment at both ends.
l On the equipment where the loopback is initiated, OAM Working Mode must be set to
Active.
l The equipment that responds to the loopback must support remote loopbacks.
Background Information
l If a port is capable of responding to loopbacks, it enters the Respond Loopback of
Remote state and reports the loopback responding alarm when receiving the command
of enabling the remote loopback function sent from the opposite OAM port. In this case,
the equipment that initiates the loopback enters the loopback initiating state and reports
the loopback initiating alarm.
l Generally, after the remote loopback function is enabled, service packets, except the
OAMPDU packets, are looped back at the remote end.
l After using the remote loopback function to locate faults and test link performance, you
should disable the remote loopback function at the end where the loopback is initiated
and then restore the services. At this time, the alarm clears automatically.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function Tree.
Step 2 Click the OAM Parameter tab.
Step 3 Choose Enable Remote Loopback from the OAM drop-down menu. Then, close the dialog
box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
l The PORT-based Ethernet private line services must be created and activated.
l The data services must be configured as EPL services that are transmitted from PORTs to
VCTRUNKs and do not carry any VLAN tags.
l An Ethernet port on which the LPT function is enabled must be in auto-negotiation
mode.
Precautions
NOTE
Point-to-point LPT and point-to-multipoint LPT are mutually exclusive. On the same board, you can
select only one configuration mode to implement the LPT function.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Interface Management > LPT Management from the Function
Tree.
Step 3 Select a PORT and a VCTRUNK, and then set the following parameters.
NOTE
If LPT is enabled, you can set PORT-Type Port Hold-Off Time(ms) and VCTRUNK Port Hold-Off
Time(ms) according to actual requirements.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The EFP8/EMS6 board must be added in the NE Panel.
l The VLAN-based EVPL services must be created and activated.
l An Ethernet port on which the LPT function is enabled must be in auto-negotiation
mode.
Precautions
NOTE
Point-to-point LPT and point-to-multipoint LPT are mutually exclusive. On the same board, you can
select only one configuration mode to implement the LPT function.
NOTICE
Before configuring the point-to-multipoint LPT function, make sure that the following two
conditions are met. Otherwise, the services may be interrupted.
l The data services are displayed in the tree topology.
l The data service topology is consistent with the topology of the LPT.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Interface Management > LPT Management from the Function
Tree.
Step 2 Click PtoMP LPT. Then, the LPT Management dialog box appears.
Step 3 Click New.
The Create LPT dialog box is displayed.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and then choose
Configuration > Control Plane Configuration > Address Parse from the Function Tree.
Configure the MAC address in an ARP entry according to the MAC address of its next-hop equipment.
Step 4 Click OK. Then, the static ARP entry is successfully created.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and then choose
Configuration > Control Plane Configuration > Address Parse from the Function Tree.
Step 2 Click Query and query ARP entries in the main interface.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and then choose
Configuration > Control Plane Configuration > Address Parse from the Function Tree.
Step 2 Select the required dynamic ARP entry and click Switch to Static Type.
Step 3 Click Query. Then, ARP List Type changes to Static for the selected dynamic ARP entry.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and then choose
Configuration > Control Plane Configuration > Address Parse from the Function Tree.
Step 2 Select the required static ARP entry and click Delete.
NOTE
When deleting dynamic ARP entries, click Clear. Exercise caution when performing this operation to avoid
service interruption.
A confirmation dialog box is displayed.
Step 3 Click OK.
Step 4 Click Query. The selected static ARP entry is deleted.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > Control
Plane Configuration > Aging Time from the Function Tree.
Step 2 Select the required port, double-click it, and modify the parameter Dynamic ARP Entry
Aging Time(min).
NOTE
It is recommended that Dynamic ARP Entry Aging Time(min) take its default value 720.
----End
Context
NOTE
In this topic, MPLS tunnels are all static LSPs.
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
MPLS Management > Basic Configuration from the Function Tree.
Step 2 Click Basic Configuration tab.
Step 3 Double-click LSR ID and set the LSR ID of the NE according to the planning information.
NOTICE
When PWE3 services are configured on the NE, the PWE3 services may be interrupted if
LSR ID of the NE is changed.
Step 5 Click Yes. Then, close the dialog box that is displayed.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the desired NE from the Object Tree in the NE Explorer. Choose Configuration >
MPLS Management > Basic Configuration from the Function Tree.
Step 2 Click the Global OAM Parameters tab.
Step 4 Click Apply. Then, close the operation result dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l Tunnels/PWs have been created.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 Select the desired NE from the Object Tree in the NE Explorer.
If... Then...
The MPLS tunnel OAM 1. In the NE Explorer, select the required NE from the Object
standard needs to be Tree and choose Configuration > MPLS Management >
changed Unicast Tunnel Management from the Function Tree.
2. Click the Static Tunnel tab.
The MPLS PW OAM 1. In the NE Explorer, select the required NE from the Object
standard needs to be Tree and choose Configuration > MPLS Management >
changed PW Management from the Function Tree.
2. Click the PW Management tab.
Step 2 Right-click the tunnel/PW for which the OAM standard needs to be changed and choose
Switch to Y.1711 or Switch to Y.1731 from the shortcut menu.
NOTE
l MEG IDs adopt the IP-based format after the OAM standard is changed from Y.1711 to Y.1731.
l If MPLS-TP OAM supports the original transmission interval of CC packets, the transmission interval
will not change after the change of OAM standard and no related switching will be triggered. If MPLS-
TP OAM does not support the original transmission interval of CC packets, the transmission interval will
change to a value closest to the original value and there is a possibility that related switching is triggered.
Skip this step when the Web LCT is used for configuration.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The port attributes are set correctly.
l The LSR ID of each NE is set correctly.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
MPLS Management > Unicast Tunnel Management from the Function Tree.
Step 3 Click New and choose Unidirectional Tunnel from the drop-down list.
Step 6 Click OK. Then, close the dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The port attributes have been correctly configured.
l The LSR ID of each NE has been correctly configured.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
MPLS Management > Unicast Tunnel Management from the Function Tree.
Step 2 Click the Static Tunnel tab.
Step 3 Click New and choose Bidirectional Tunnel from the drop-down list.
The New Unicast Bidirectional Tunnel dialog box is displayed.
Step 4 Set parameters for the bidirectional MPLS tunnel.
Step 5 Click OK. Then, close the dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l MPLS tunnels are configured correctly.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
MPLS Management > Unicast Tunnel Management from the Function Tree.
Step 2 Click the Static Tunnel tab.
Step 4 View the information about all MPLS tunnels configured for the NE in the main interface.
Continue:
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The MPLS tunnel has been created.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
MPLS Management > Unicast Tunnel Management from the Function Tree.
Step 2 Click the Static Tunnel tab.
Step 4 Choose the MPLS tunnel whose parameter values need to be changed and click Modify at the
lower right corner.
Step 5 In the dialog box that is displayed, modify the MPLS tunnel information.
Step 7 Click OK. Then, close the dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l An MPLS tunnel is configured correctly and is no longer used to transmit services.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
MPLS Management > Unicast Tunnel Management from the Function Tree.
Step 2 Click the Static Tunnel tab.
Step 6 Click Query and find that the selected MPLS tunnel does not exist.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l MPLS tunnels are created and enabled.
l Node Type is set to Ingress or Egress for tunnels.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
MPLS Management > Unicast Tunnel Management from the Function Tree.
Step 2 Click the OAM Parameter tab.
Step 3 Select the required MPLS tunnel and set MPLS OAM (Y.1711) parameters.
Step 4 Click Apply. Then, close the dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l MPLS tunnels are created and enabled.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
MPLS Management > Unicast Tunnel Management from the Function Tree.
Step 2 Click the FDI tab.
Step 4 Click Apply. Then, close the dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The MPLS OAM (Y.1711) function has been enabled and related parameters have been
configured.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
MPLS Management > Unicast Tunnel Management from the Function Tree.
Step 2 Click the OAM Parameter tab.
1. To enable CV/FFD detection, click Start CV/FFD. Then, close the dialog box that is
displayed.
2. To disable CV/FFD detection, click Stop CV/FFD. Then, close the dialog box that is
displayed.
NOTE
l For unidirectional tunnels, this operation task can be performed only for a tunnel whose Node Type
is Ingress.
l For bidirectional tunnels, this operation task cannot be performed if Node Type is Transit.
l After the MPLS OAM (Y.1711) function is enabled, CV/FFD detection is enabled by default.
NOTE
l You can select more than one tunnel at a time by pressing and holding down the Ctrl key.
l Alternatively, you can select the required tunnel, right-click the tunnel, and then select Start
CV/FFD or Stop CV/FFD from the drop-down list.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The MPLS OAM detection function has been enabled.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
MPLS Management > Unicast Tunnel Management from the Function Tree.
Step 2 Select a navigation path based on the OAM protocol type used by a tunnel.
l If the tunnel uses MPLS OAM (Y.1711), query the LSP running status according to
Click the OAM Parameter tab..
l If the tunnel uses MPLS-TP OAM, click the MPLS-TP OAM tab page.
Step 3 Select the desired tunnel and click OAM Operation at lower right of the main interface.
Step 4 Select Query LSP Status from the drop-down list. Then, close the dialog box that is
displayed.
Step 5 Check the tunnel status according to the LSP Status parameter value in the main interface.
NOTE
For RTN 950A, if MPLS-TP OAM is used, the queried information about LSP status, defect position, and
unavailable duration is invalid.
NOTE
l You can select more than one tunnel at a time by pressing and holding down the Ctrl key.
l Alternatively, you can select a tunnel, right-click the tunnel, and select LSP Status from the drop-
down list.
----End
A.11.2.13 Clearing OAM Configuration Data for MPLS Tunnel OAM (Y.1711)
This topic describes how to restart MPLS OAM detection by clearing MPLS OAM (Y.1711)
configuration data.
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The MPLS OAM (Y.1711) detection function has been enabled.
l The tunnel is not configured in any protection group.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
MPLS Management > Unicast Tunnel Management from the Function Tree.
Step 2 Click the OAM Parameter tab.
Step 3 Select the required tunnel and click OAM Operation at lower right of the main interface.
Step 4 Select Clear OAM from the drop-down list. Then, close the dialog box that is displayed.
NOTE
After this step is performed, OAM parameters for the tunnel are restored to default values. If OAM
operations need to be performed, you need to re-enable and configure the OAM functions.
NOTE
l You can select more than one tunnel at a time by pressing and holding down the Ctrl key.
l Alternatively, you can select a tunnel, right-click the tunnel, and select Clear OAM from the drop-
down list.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
MPLS Management > Unicast Tunnel Management from the Function Tree.
Step 2 Optional: If MPLS tunnel OAM (Y.1711) is used, Click the OAM Parameters tab..
Step 3 Optional: If MPLS-TP tunnel OAM (Y.1731) is used, click the MPLS-TP OAM tab.
Step 4 Select the required tunnel, click OAM Operation in the lower right corner, and choose Ping
Test from the drop-down list.
NOTE
Alternatively, you can select a tunnel, right-click the tunnel, and select Ping Test from the drop-down
list.
The Ping Test dialog box is displayed.
l If LSP ping uses the IPv4 UDP response mode, all the nodes on the tunnel must support DCN
communication over IP protocols.
l To stop a test, click Stop Test.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
MPLS Management > Unicast Tunnel Management from the Function Tree.
Step 2 Optional: If MPLS tunnel OAM (Y.1711) is used, Click the OAM Parameters tab..
Step 3 Optional: If MPLS-TP tunnel OAM (Y.1731) is used, click the MPLS-TP OAM tab.
Step 4 Select the required tunnel, click OAM Operation in the lower right corner, and choose
Traceroute Test from the drop-down list.
NOTE
Alternatively, you can select a tunnel, right-click the tunnel, and select Traceroute Test from the drop-
down list.
The Traceroute Test dialog box is displayed.
Step 5 Set parameters for the traceroute test.
l If LSP traceroute uses the IPv4 UDP response mode, all the nodes on the tunnel must support DCN
communication over IP protocols.
l To stop a test, click Stop Test.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The MPLS tunnel has been configured, with its ingress/egress node as an MEP.
l The MPLS-TP tunnel OAM standard has been changed to Y.1731.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the desired NE from the Object Tree in the NE Explorer. Choose Configuration >
MPLS Management > Unicast Tunnel Management from the Function Tree.
Step 4 Set OAM Status to Enabled and set other OAM parameters.
Step 5 Click Apply. Then, close the operation result dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The MPLS tunnel has been created and the newly created MIP node is a transit node.
l The MPLS-TP tunnel OAM standard has been changed to Y.1731.
l Global OAM parameters have been configured.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the desired NE from the Object Tree in the NE Explorer. Choose Configuration >
MPLS Management > Unicast Tunnel Management from the Function Tree.
Step 6 Click OK. Then, close the operation result dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The MPLS-TP tunnel OAM has been enabled and OAM parameters have been
configured.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the desired NE from the Object Tree in the NE Explorer. Choose Configuration >
MPLS Management > Unicast Tunnel Management from the Function Tree.
Step 4 Select one or more tunnels and choose OAM Operation > Start CC.
NOTE
l Before the CC test, set CC Packet Priority and CC Packet Interval (ms) based on actual
requirements.
l To stop a CC test, select one or more tunnels and choose OAM Operation > Stop CC.
Step 5 Then, close the operation result dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l MPLS-TP tunnel OAM has been enabled for both the source MEP and the sink
MEP/MIP and OAM parameters have been configured.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the desired NE from the Object Tree in the NE Explorer. Choose Configuration >
MPLS Management > Unicast Tunnel Management from the Function Tree.
Step 2 Click the MPLS-TP OAM tab.
Step 4 Select one or more tunnels and choose OAM Operation > Start LB.
Step 6 Click Start Test. View the test result in Test Result.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l MPLS-TP tunnel OAM has been enabled for both the source and sink MPs and OAM
parameters have been configured.
Background Information
An LT test provided by MPLS-TP tunnel OAM can be started only in end-to-end
configuration mode.
Procedure
Step 1 Choose Service > Tunnel > Manage Tunnel from the Main Menu.
The Set Filter Criteria dialog box is displayed.
Step 2 In the Set Filter Criteria dialog box, set filter criteria and click Filter.
The tunnels that meet the criteria are listed in the query result.
Step 3 Right-click the desired tunnel and choose OAM > MPLS-TP OAM Test from the shortcut
menu.
The MPLS-TP OAM Test dialog box is displayed.
Step 4 Select LT from the drop-down menu and click Parameter to configure the LT test.
Step 6 Select the desired path, click Run and check the LT test result in LT Statistics.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l MPLS-TP tunnel OAM has been enabled for both the source and sink MPs and OAM
parameters have been configured.
Background Information
This task is supported only when the configuration is performed in end-to-end mode on the
U2000.
NOTE
l It is recommended that you measure the performance of MPLS tunnels deployed in end-to-end manner by
performing the preceding procedure. For MPLS tunnels deployed on a per-NE basis, it is recommended
that you convert the MPLS tunnels to end-to-end ones by referring to A.15.4 Searching for MPLS
Tunnels and PWE3 Services.
l To perform performance measurement for an MPLS tunnel in the NE Explorer, select the desired MPLS
tunnel, right-click, and choose Performance Statistics Management from the shortcut menu. In the
displayed dialog box, create the corresponding monitoring instance. Note that the PE at both ends must be
configured with the corresponding performance monitoring instance for this MPLS tunnel. Otherwise,
errors occur during performance measurement.
Procedure
Step 1 Choose Service > Tunnel > Manage Tunnel from the Main Menu.
The Set Filter Criteria dialog box is displayed.
Step 2 In the Set Filter Criteria dialog box, set filter criteria and click Filter.
The tunnels that meet the criteria are listed in the query result.
Step 3 Right-click the desired tunnel and choose Performance > Create Monitoring Instance from
the shortcut menu.
Step 4 Query the variation of an MPLS tunnel according to testing instances in the U2000 User
Guide for PMS.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The MPLS-TP tunnel OAM has been enabled and OAM parameters have been
configured.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
OptiX RTN 950 housing CSHU/CSHUA and OptiX RTN 950A do not support this operation.
Procedure
Step 1 Select the desired NE from the Object Tree in the NE Explorer. Choose Configuration >
MPLS Management > Unicast Tunnel Management from the Function Tree.
Step 2 Click the MPLS-TP OAM tab.
Step 4 Select the desired tunnel, and set Lock Status to Unlock or Lock.
Step 5 Click Apply. Then, close the operation result dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l MPLS-TP tunnel OAM has been enabled for both the source MP and the sink MP and
OAM parameters have been configured.
Background Information
l This task is supported only when the configuration is performed in end-to-end mode on
the U2000.
l OptiX RTN 950 housing CSHU/CSHUA and OptiX RTN 950A do not support this
operation.
Procedure
Step 1 Choose Service > Tunnel > Manage Tunnel from the main menu.
Step 2 In the dialog box that is displayed, click Filter to set filter conditions. Query all MPLS
tunnels that meet the filter conditions.
Step 3 Right-click the desired tunnel and choose OAM > MPLS-TP OAM Test from the shortcut
menu.
The MPLS-TP OAM Test dialog box is displayed.
Step 4 Select Test from the drop-down menu. Click Parameter to set the test parameters.
Step 5 Select the NE to initiate the TST test and click Run.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The working and protection MPLS tunnels have been created.
l MPLS OAM as been enabled for both working and protection MPLS tunnel in the
protection group.
l The protection tunnel cannot carry extra services.
l PW APS protection is not configured for the service.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Background Information
MPLS OAM needs to be enabled for working and protection tunnels. The detection packets
used by MPLS OAM are FFD packets. FFD packets are usually sent at an interval of 3.3 ms.
If the packet transmission delay time of an MPLS tunnel exceeds 3.3 ms, the transmission
interval of FFD packets needs to be a value greater than the delay time.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > APS
Protection Management from the Function Tree.
Step 2 Click the Tunnel APS Management tab.
When creating an MPLS APS protection group, set Protocol Status to Disabled. Start the protocol only
when the MPLS APS protection group is successfully created on nodes at both ends.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The MPLS APS protection group has been created.
l The MPLS APS protocol has been enabled.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
APS Protection Management from the Function Tree.
Step 2 Click the Tunnel APS Management tab.
Step 3 Click Query, and then close the dialog box that is displayed. Check basic information about
the protection group.
Step 5 Select Query Switching Status from the drop-down list. Then, close the dialog box that is
displayed. Check the status of the protection group.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The MPLS APS protection group has been created.
l The MPLS APS protocol has been enabled.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
APS Protection Management from the Function Tree.
Step 3 Select the required protection group, click Function, and then select the required switching
mode from the drop-down list.
NOTE
Alternatively, you can select the required protection group, right-click the protection group, and then
select the required switching mode from the drop-down list.
Step 6 Select Query Switching Status from the drop-down list. Then, close the dialog box that is
displayed. Check whether switching is performed successfully.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The MPLS APS protection group has been created.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
APS Protection Management from the Function Tree.
Step 2 Click the Tunnel APS Management tab.
NOTICE
After the MPLS APS protocol is stopped, the protection group fails. In addition, services
are unavailable until the working channel is restored or the MPLS APS protocol is
restarted, if services have been switched to the protection channel.
Alternatively, you can select the required protection group, right-click the protection group, and choose
Start Protocol or Stop Protocol from the shortcut menu.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l PW-carried services have been configured.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
MPLS Management > PW Management from the Function Tree.
Step 2 Click the PW Management tab.
NOTE
If you query information and running statuses of PWs using the Web LCT, perform the following operations:
Click the PW Management tab and click the PW Management tab.
Prerequisites
You must be an NM user with NE operator authority or higher.
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Background Information
The steps for creating MS-PWs vary according to service types. This topic uses an Ethernet
service as an example to describe how to create MS-PWs.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
MPLS Management > PW Management from the Function Tree.
Step 2 Click the MS PW tab.
NOTE
If you create an MS-PW using the Web LCT, perform the following operations:
Click the PW Management tab and click the MS PW tab.
If you create an MS-PW using the Web LCT, perform the following operations:
Click the PW General Attributes tab and set PW parameters.
Step 7 Click the Advanced Attributes tab and set advanced attributes.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l PW-carried services have been configured.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
MPLS Management > PW Management from the Function Tree.
Step 2 Click the PW OAM Parameter tab.
Step 3 Select the required PW and set PW OAM (Y.1711) parameters.
Step 4 Click Apply. Then, close the dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l A PW has been created and enabled.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
MPLS Management > PW Management from the Function Tree.
Step 2 Optional: If PW OAM (Y.1711) is used, Click the PW OAM Parameter tab..
Step 3 Optional: If MPLS-TP PW OAM (Y.1731) is used, click the MPLS-TP OAM tab.
Step 4 Select the required PW and click OAM Operation > Ping Test.
NOTE
Alternatively, you can select a PW, right-click the PW, and select Ping Test from the drop-down list.
l If PW ping/traceroute uses the IPv4 UDP response mode, all the nodes on the PW must support DCN
communication over IP protocols.
l To stop a test, click Stop Test.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l A PW has been created and enabled.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
MPLS Management > PW Management from the Function Tree.
Step 2 Optional: If PW OAM (Y.1711) is used, Click the PW OAM Parameter tab..
Step 3 Optional: If MPLS-TP PW OAM (Y.1731) is used, click the MPLS-TP OAM tab.
Step 4 Select the required PW, click OAM Operation in the lower right corner, and choose
Traceroute Test from the drop-down list.
NOTE
Alternatively, you can select a PW, right-click the PW, and select Traceroute Test from the drop-down
list.
The Traceroute Test dialog box is displayed.
Step 5 Set parameters for the traceroute test.
l If PW ping/traceroute uses the IPv4 UDP response mode, all the nodes on the PW must support DCN
communication over IP protocols.
l To stop a test, click Stop Test.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The PW has been configured, with its T-PE as an MEP.
l The MPLS-TP PW OAM standard has been changed to Y.1731.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the desired NE from the Object Tree in the NE Explorer. Choose Configuration >
MPLS Management > PW Management from the Function Tree.
Step 2 Click the MPLS-TP OAM tab.
Step 5 Click Apply. Then, close the operation result dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The MS-PW has been created and the newly created MIP node is an S-PE node.
l The MPLS-TP PW OAM standard has been changed to Y.1731.
l Global OAM parameters have been configured.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the desired NE from the Object Tree in the NE Explorer. Choose Configuration >
MPLS Management > PW Management from the Function Tree.
Step 2 Click the MPLS-TP OAM tab.
Step 3 Click the MIP tab.
Step 4 Click New.
The Create MS PW MIP dialog box is displayed.
Step 5 Set parameters for the newly configured MIP.
NOTE
Step 6 Click OK. Then, close the operation result dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The MPLS-TP PW OAM has been enabled and OAM parameters have been configured.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the desired NE from the Object Tree in the NE Explorer. Choose Configuration >
MPLS Management > PW Management from the Function Tree.
Step 4 Select one or more PWs and choose OAM Operation > Start CC.
NOTE
l Before the CC test, set CC Packet Priority and CC Packet Interval (ms) based on actual
requirements.
l To stop a CC test, select one or more PWs and choose OAM Operation > Stop CC.
Step 5 Then, close the operation result dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l MPLS-TP PW OAM has been enabled for both the source MEP and the sink MEP/MIP
and OAM parameters have been configured.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the desired NE from the Object Tree in the NE Explorer. Choose Configuration >
MPLS Management > PW Management from the Function Tree.
Step 4 Select one or more PWs and choose OAM Operation > Start LB.
Step 6 Click Start Test. View the test result in Test Result.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l MPLS-TP PW OAM has been enabled for both the source and sink MPs and OAM
parameters have been configured.
Background Information
An LT test provided by MPLS-TP PW OAM can be started only in end-to-end configuration
mode.
Procedure
Step 1 Choose Service > PWE3 Sevice > Manage PWE3 Sevice from the Main Menu.
The Set Filter Criteria dialog box is displayed.
Step 2 In the Set Filter Criteria dialog box, set filter criteria and click Filter.
The PWs that meet the criteria are listed in the query result.
Step 3 Right-click the desired PW and choose PW OAM > TP OAM Test from the shortcut menu.
The MPLS-TP OAM Test dialog box is displayed.
Step 4 Select LT from the drop-down menu and click Parameter to configure the LT test.
Step 6 Select the desired path, click Run and check the LT test result in LT Statistics.
----End
A.11.4.11 Testing the Packet Loss Ratio, Delay, and Delay Variation of a PW
This section describes how to query the packet loss ratio, delay, and delay variation of a PW.
Prerequisites
l You must be an NM user with NE operator authority or higher.
l MPLS-TP PW OAM has been enabled for both the source and sink MPs and OAM
parameters have been configured.
Background Information
This task is supported only when the configuration is performed in end-to-end mode on the
U2000.
NOTE
Procedure
Step 1 Choose Service > PWE3 Sevice > Manage PWE3 Sevice from the Main Menu.
The Set Filter Criteria dialog box is displayed.
Step 2 In the Set Filter Criteria dialog box, set filter criteria and click Filter.
The PWs that meet the criteria are listed in the query result.
Step 3 Right-click the desired PW and choose Performance > Create Monitoring Instance from
the shortcut menu.
Step 4 Query the variation of a PW according to the testing instances in the U2000 User Guide for
PMS.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The MPLS-TP PW OAM has been enabled and OAM parameters have been configured.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
OptiX RTN 950 housing CSHU/CSHUA and OptiX RTN 950A do not support this operation.
Procedure
Step 1 Select the desired NE from the Object Tree in the NE Explorer. Choose Configuration >
MPLS Management > PW Management from the Function Tree.
Step 2 Click the MPLS-TP OAM tab.
Step 3 Click the MEP tab.
Step 4 Select the desired PW, and set Lock Status to Unlock or Lock.
Step 5 Click Apply. Then, close the operation result dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l MPLS-TP PW OAM has been enabled for both the source MP and the sink MP and
OAM parameters have been configured.
Background Information
l This task is supported only when the configuration is performed in end-to-end mode on
the U2000.
l OptiX RTN 950 housing CSHU/CSHUA and OptiX RTN 950A do not support this
operation.
Procedure
Step 1 Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
Step 2 In the dialog box that is displayed, click Filter to set filter conditions. Query all PWs that
meet the filter conditions.
Step 3 Right-click the desired PW and choose PW OAM > TP OAM Test from the shortcut menu.
The MPLS-TP OAM Test dialog box is displayed.
Step 4 Select Test from the drop-down menu. Click Parameter to set the test parameters.
Step 5 Select the NE to initiate the TST test and click Run.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l MPLS APS protection is not configured for the service.
l The tunnel carrying the working and protection PWs has been created.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Background Information
PW OAM needs to be enabled for the working and protection PWs of a PW APS protection
group. The detection packets used by PW OAM are FFD packets. FFD packets are usually
sent at an interval of 3.3 ms. If the packet transmission delay time of a PW exceeds 3.3 ms,
the transmission interval of FFD packets needs to be a value greater than the delay time.
You can create a PW APS protection group during initial service configuration or after service
configuration.
l During initial service configuration, set Protection Type to PW APS, create the working
and protection PWs, use the PWs to configure a PW APS protection group.
l If services are already configured, create the PW APS protection group in the Protection
Group tab page.
l For SS-PWs and MS-PWs, configuration of the PW APS protection group needs to be
done on both source NE and sink NE.
NOTE
l This topic describes how to configure PW APS after services are configured.
l This topic uses a PW-carried E-Line service as an example to describe how to configure PW APS
protection. The methods of configuring PW APS protection for other types of service are similar.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Service Management > E-Line Service from the Function Tree.
Step 2 Select the required services and click the Protection Group tab.
Step 5 Click the Basic Attributes tab and set the basic attributes of the protection PW.
NOTE
If you create a PW APS protection group using the Web LCT, perform the following operations:
Click the PW tab and set the basic attributes of the protection PW.
Step 6 Click the Protection Group tab and set information about the PW APS protection group.
NOTE
When creating a PW APS protection group, set Enabling Status to Disabled. Start the protocol only when
the PW APS protection group is successfully created on nodes at both ends.
l When the PW APS protection group is created, the PW OAM function is automatically enabled to
detect the PW status.
l You can also configure OAM information by choosing Configuration > MPLS Management >
PW Management > PW OAM Parameter.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l MPLS FPS protection is not configured for the services.
l The tunnels carrying the working and protection PWs have been created.
Background
Enable MPLS-TP OAM for both the working and protection PWs in the PW FPS protection
group. The packet transmission interval is often set to 3.3 ms for the enabled MPLS-TP
OAM. If the packet transmitting delay jitter in a PW exceeds 3.3 ms, set the packet
transmission interval to a value greater than the delay.
PW APS protection groups can be created when services are initially configured or after
services are configured.
l During initial service configuration, set Protection Type to PW APS, create the working
and protection PWs, use the PWs to configure a PW FPS protection group.
l If services are already configured, create the PW FPS protection group on the Protect
Group tab page.
l For SS-PWs and MS-PWs, configuration of the PW FPS protection group needs to be
done on the both source NE and sink NE.
NOTE
l This topic only describes how to configure PW FPS after services are configured.
l A PW-carried E-Line service is used as an example to describe how to configure PW FPS protection. The
methods of configuring PW FPS protection for other types of service are similar.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Service Management > E-Line Service from the Function Tree.
Step 2 Select the desired service and click the Protect Group tab.
If you configure the PW using the Web LCT, perform the following operations:
Click the PW tab and set the basic attributes of the protection PW.
Step 6 Click the Protect Group tab and set information about the PW FPS protection group.
NOTE
l When the PW FPS protection group is created, the MPLS-TP OAM function is automatically
enabled to detect the PW status.
l You can also choose Configuration > MPLS Management > PW Management > MPLS-TP
OAM to configure the OAM information.
Step 10 Click Apply and close the dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The mapping between a slave protection pair and a PW APS protection group has been
specified.
l MPLS APS protection is not configured for the service.
l The tunnel carrying the working and protection PWs has been created.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Background Information
The slave protection pairs are bound with a PW APS protection group. You can create a slave
protection pair during initial service configuration or after service configuration.
l During initial service configuration, set Protection Type to Slave Protection Pair,
create the working and protection PWs, use the PWs to configure a slave protection pair.
l If services are already configured, create the slave protection pair in the Protection
Group tab page.
l For SS-PWs and MS-PWs, binding of a slave protection pair to a PW APS protection
group requires that the slave protection pair is added on both the source NE and sink NE.
NOTE
l This topic describes how to configure a slave protection pair after services are configured.
l This topic uses a PW-carried E-Line service as an example to describe how to configure a slave protection
pair. The methods of configuring slave protection pairs for other types of service are similar.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Service Management > E-Line Service from the Function Tree.
Step 2 Select the required services and click the Protection Group tab.
Step 3 Click Slave Protection Pair.
Step 4 Click New.
The Configure PW dialog box is displayed.
Step 5 Click the Basic Attributes tab and set the basic attributes of the protection PW.
Step 6 Click the Protect Group tab and set the ID of the PW APS protection group to which the
slave protection pair is bound.
NOTE
You can manually enter an ID, or double-click the ID parameter and select from the drop-down list.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The PW APS protection group has been created.
l The PW APS protocol has been enabled.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > APS
Protection Management from the Function Tree.
Step 2 Click the PW APS Management tab.
Step 3 Click Query, and then close the dialog box that is displayed. Check basic information about
the protection group.
NOTE
If a slave protection pair is configured, information about the slave protection pair is displayed at the
lower part of the main interface after you select the protection group.
Step 4 Select the required protection group. Click Function > Query Switching Status, and then
close the dialog box that is displayed. Check the status of the protection group.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The PW APS protection group has been created.
l The PW APS protocol has been enabled.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > APS
Protection Management from the Function Tree.
Step 2 Click the PW APS Management tab.
Step 3 Select the required protection group, click Function, and then select the required switching
mode from the drop-down list.
NOTE
Alternatively, you can select the required protection group, right-click the protection group, and then
select the required switching mode from the drop-down list.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The PW APS protection group has been created.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > APS
Protection Management from the Function Tree.
NOTICE
After the PW APS protocol is stopped, the protection group fails. In addition, services
are unavailable until the working channel is restored or the PW APS protocol is
restarted, if services have been switched to the protection channel.
You can enable or disable the PW APS protocol by using either of the following methods:
l Select the required protection group, right-click the protection group, and choose Start Protocol or
Stop Protocol from the short-cut menu.
l Set Enabling Status to Enabled or Disabled.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The attributes of the UNI port that carries the CES service have been configured. That is,
Port Mode has been set to Layer 1, and Frame Format and Frame Mode have also
been configured.
l The MPLS tunnel that carries the PW has been configured.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Background Information
l Generally, UNI-NNI CES services are configured on the equipment. Therefore, this
topic uses a UNI-NNI CES service as an example to describe how to configure CES
services.
l It is recommended that you create protection information before creating a CES service.
In this configuration example, Protection Type is set to No Protection. For details on
how to configure protection information, see A.11.5.1 Creating a PW APS Protection
Group and A.11.5.3 Configuring Slave Protection Pairs of PW APS.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > CES
Service Management from the Function Tree.
Step 3 Set Mode to UNI-NNI. Configure basic information about the CES service carried by a PW.
NOTE
NOTE
If you create CES services using the Web LCT, click the Port Attributes tab to configure port attributes. The
result of setting the port attributes during the service configuration process is the same as the result of directly
setting the Ethernet service port attributes.
Step 4 Click Configure PW, and set the basic attributes of the PW.
NOTE
If you create CES services using the Web LCT, you can select Use existing resource and then use a created
tunnel, or click New to create a tunnel. It is recommended that you plan and create required tunnels during
initial service configuration.
Step 5 Click Advanced Attributes and set parameters for the advanced attributes.
Prerequisites
l You must be an NM user with NE operator authority or higher.
l CES services have been created.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > CES
Service Management from the Function Tree.
Step 2 Select the required CES service and click Query. Then, click the dialog box that is displayed.
Modify basic information about services in the main interface, such as parameters of
transparent transmission of overhead bytes in STM-1 frames.
NOTE
The transparently transmitted bytes cannot function as other channels. For example, transparently transmitted
D bytes cannot function as DCCs.
Step 3 Click PW General Attributes to query information about the PW that carry the service.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > CES
Service Management from the Function Tree.
Step 2 Select the required CES service and click Query. Then, close the dialog box that is displayed.
In the main interface, check basic service information.
Step 3 Click PW General Attributes to query information about the PW that carry the service.
Step 4 Click QoS to check the QoS information of the CES service.
Step 5 Click Advanced Attributes to check advanced attributes of the CES service.
Step 6 Click Protection Group to check whether a protection group is configured and to check
information about the protection group if configured.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The CES service has been created and will no longer be used.
l No ACR clock has been configured for the CES service.
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > CES
Service Management from the Function Tree.
Step 2 Select the required CES service and click Delete.
A confirmation dialog box is displayed.
Step 4 Click Query, and then close the dialog box that is displayed to check whether the CES
service is successfully deleted.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > CES
Service Management from the Function Tree.
Step 2 Click Calculate CES.
The Calculate Max. Number of Remaining CES Services dialog box is displayed.
Step 3 Set the parameters in the main interface based on the type of the CES service to be created.
NOTE
The maximum number of CES services an MPLS tunnel can transmit varies by service type.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l For ATM/IMA E1 services, set Port Mode in PDH Interface to Layer 2.
l For Fractional ATM/IMA services, set Port Mode in PDH Interface to Layer 1 and
configure A.8.7 Setting Serial Port Parameters.
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
NOTE
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration >
Interface Management > ATM IMA Management from the Function Tree.
Step 4 Configure the related parameters according to the network plan. Click to bind the
required E1 ports or SPs to the ATM TRUNK.
NOTE
l If ATM/IMA services need to be mapped into the ATM TRUNK that binds one or more E1 ports,
select E1 in Level.
l If ATM/IMA services need to be mapped into the ATM TRUNK that binds one or more serial ports,
select Fractional E1 in Level.
----End
Follow-up Procedure
If the IMA group is required, you need to bind the member links of the IMA group with the
ATM TRUNK, enable the IMA protocol for the ATM TRUNK, and then configure the
parameters of the IMA group.
Prerequisites
You must be an NM user with NE operator authority or higher.
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
NOTE
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration >
Interface Management > ATM IMA Management from the Function Tree.
Step 2 Click the IMA Group Management tab.
Step 3 Configure the parameters of the IMA group according to the network plan.
NOTE
l Set IMA Protocol Enable Status to Enabled if the links bound in the ATM TRUNK require the
IMA protocol; otherwise, set this parameter to Disabled.
l After IMA Protocol Enable Status is set to Enabled, the E1 links or Fractional E1 timeslots bound
in the ATM TRUNK start running the IMA protocol.
l The values of Minimum Number of Active Transmitting Links and Minimum Number of
Active Receiving Links must be the same because the OptiX RTN 905E supports Symmetrical
Mode and Symmetrical Operation only. The parameters Minimum Number of Active
Transmitting Links and Minimum Number of Active Receiving Links must assume the same
value on the two ends of an IMA link.
l On the two ends of the IMA link, you need to set IMA Protocol Version, IMA Transmit Frame
Length, and Maximum Delay Between Links (ms) to the same values.
l Clock Mode is set to the same value for the interconnected ends of IMA links.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
NOTE
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration >
Interface Management > ATM IMA Management from the Function Tree.
Step 2 Click the ATM Interface Management tab.
Step 3 Configure and adjust the ATM port attributes.
NOTE
l UNI: the port connecting user-side devices. For example, the UNI port applies to the user-side interface
on the common ATM network or to the user-side interface of the PE on the PSN network that transmits
ATM PWE3 services.
l NNI: the port connecting network-side devices. For example, the NNI port applies to the network-side
interface on the common ATM network.
l The ITU-T G.804 stipulates that the payload (48 bytes) of ATM cells must be scrambled before it is
mapped into E1 signals. Therefore, it is recommended that you set ATM Cell Payload Scrambling to
Enabled.
l ATM Cell Payload Scrambling must assume the same value on the two ends of an ATM link.
Otherwise, packet loss will occur.
Step 4 Click Apply, and close the dialog box that is displayed.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
NOTE
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration >
Interface Management > ATM IMA Management from the Function Tree.
Step 2 Click the IMA Group States tab.Close the displayed dialog box.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
NOTE
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration >
Interface Management > ATM IMA Management from the Function Tree.
Step 2 Click the IMA Link States tab.Then, close the dialog box that is displayed.
Step 3 Click Query, and then close the dialog box that is displayed.
Step 4 Query the running status of the member links of an IMA group.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l Generally, UNIs-NNI ATM services are configured on the OptiX RTN 900. Therefore,
this topic uses a UNIs-NNI ATM service as an example to describe how to configure
ATM PWE3 services.
l Before creating ATM PWE3 services, you need to bind member links to the ATM
TRUNK, set the parameters of the IMA group, and create the MPLS tunnels that carries
PWs.
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Background Information
l The OptiX RTN 905 does not support ATM/IMA services.
l To create ATM PWE3 services (UNIs-NNI), it is recommended that you create services
before configuring PW protection. Configuration will be simplified in this manner.
l In this configuration example, Protection Type is set to No Protection. For details on
how to configure PW protection, see A.11.5.1 Creating a PW APS Protection Group
and A.11.5.3 Configuring Slave Protection Pairs of PW APS.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM
Service Management from the Function Tree.
Step 2 Click New.
The New ATM Service dialog box is displayed.
Step 3 Configure the basic information about the ATM PWE3 service according to the network plan.
Step 4 Click the Connection tab and configure the attributes of the ATM connection.
Step 5 Click PW, and click Add to configure the attributes of PWs.
1. Click the General Attributes tab and set the basic attributes of PWs.
NOTE
If you create ATM services using the Web LCT, click Use existing resource or New to select a tunnel.
It is recommended that you create tunnels in advance and click Use existing resource to select a
created tunnel.
2. Click the QoS tab and enable the PW bandwidth restriction.
3. Click the Advanced Attributes tab to configure the advanced attributes of PWs.
Step 6 Click the CoS Mapping tab and click Add to configure the CoS mapping of PWs.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l ATM PWE3 services are already created and their parameters need to be modified
according to the planning information.
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
NOTE
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM
Service Management from the Function Tree.
Step 2 Click Query, and close the dialog box that is displayed.
Step 3 Select the required ATM service and modify the parameters of the ATM service.
Step 4 Click Apply, and close the dialog box that is displayed.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
NOTE
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM
Service Management from the Function Tree.
Step 2 Click Query, and close the dialog box that is displayed.
Step 3 Select the required ATM service and query the parameters of the ATM service.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
NOTE
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM
Service Management from the Function Tree.
Step 2 Click Query, and close the dialog box that is displayed.
Step 5 After the service is deleted, close the dialog box that is displayed.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
NOTE
The OptiX RTN 905 does not support ATM traffic management.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > QoS
Management > Diffserv domain Management > ATM COS Mapping Configuration from
the Function Tree.
Step 2 Click New.
The New ATM CoS Mapping dialog box is displayed.
NOTE
l Eight PHB service classes are available: BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The OptiX RTN
900 provides different QoS policies for the queues of different service classes.
l CS6 to CS7: highest service classes, mainly applicable to signaling transmission.
l EF: fast forwarding, applicable to services of low transmission delays and low packet loss rates.
l AF1 to AF4: assured forwarding, applicable to services that require an assured transmission rate rather
than delay or jitter limits.
The AF1 class includes three subclasses: AF11, AF12, and AF13. Only one of these subclasses can take
effect for one queue. It is the same case with AF2, AF3, and AF4.
l BE: best effort, applicable to services that do not require special processing.
Step 4 Click OK, and close the dialog box that is displayed.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
NOTE
The OptiX RTN 905 does not support ATM traffic management.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > QoS
Management > Diffserv domain Management > ATM COS Mapping Configuration from
the Function Tree.
Step 2 Click Query, and close the dialog box that is displayed.
Step 3 Select the required ATM-Diffserv domain and modify its parameters according to the
planning information.
NOTE
l Eight PHB service classes are available: BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The OptiX RTN
900 provides different QoS policies for the queues of different service classes.
l CS6 to CS7: highest service classes, mainly applicable to signaling transmission.
l EF: fast forwarding, applicable to services of low transmission delays and low packet loss rates.
l AF1 to AF4: assured forwarding, applicable to services that require an assured transmission rate rather
than delay or jitter limits.
The AF1 class includes three subclasses: AF11, AF12, and AF13. Only one of these subclasses can take
effect for one queue. It is the same case with AF2, AF3, and AF4.
l BE: best effort, applicable to services that do not require special processing.
Step 4 Click OK, and close the dialog box that is displayed.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
NOTE
The OptiX RTN 905 does not support ATM traffic management.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > QoS
Management > Policy Management > ATM Policy from the Function Tree.
Step 2 Click New.
The Create ATM Policy dialog box is displayed.
Step 3 Configure the parameters of the ATM policy according to the planning information.
Step 4 Click OK, and close the dialog box that is displayed.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
NOTE
The OptiX RTN 905 does not support ATM traffic management.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > QoS
Management > Policy Management > ATM Policy from the Function Tree.
Step 2 Click Query, and close the dialog box that is displayed.
Step 3 Select the required ATM policy and modify its parameters according to the planning
information.
Step 4 Click Apply, and close the dialog box that is displayed.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
NOTE
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM
OAM Management from the Function Tree.
Step 3 Enable/Disable the AIS/RDI insertion function according to the network plan.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l ATM services have been configured.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
NOTE
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM
OAM Management from the Function Tree.
Step 3 Set the segment and end attributes of AIS/RDI according to the planning information.
Step 4 Click Apply, and close the dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l ATM services have been configured.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
NOTE
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM
OAM Management from the Function Tree.
Step 3 Configure the parameters of the CC test according to the planning information.
Step 4 Click Apply, and close the dialog box that is displayed.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
NOTE
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM
OAM Management from the Function Tree.
Step 4 Click Apply, and close the dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l ATM services have been configured.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
NOTE
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM
OAM Management from the Function Tree.
Step 3 Configure the attributes of the LB test according to the planning information.
Step 5 Click Test, and close the dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l Multiple serial ports or E1 ports have been configured with the PPP protocol activated.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the desired NE from the Object Tree in the NE Explorer. Choose Configuration >
Interface Management > MP Group Management from the Function Tree.
Step 2 Click the Basic Attributes tab.
Step 5 Click OK. Then, close the operation result dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l An MP group has been created.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the desired NE from the Object Tree in the NE Explorer. Choose Configuration >
Interface Management > MP Group Management from the Function Tree.
Step 2 Click the Basic Attributes tab.
Step 3 Click Running Status. Check Link Status. Then, close the dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding boards have been added in the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select a channelized STM-1 interface board from the Object Tree and
choose Configuration > Clock Transparent Transmission > Clock Transparent
Transmission.
Step 2 Set the SDH retiming function.
1. Set Retiming Mode to Line Clock.
2. Select the SDH port for receiving clock signals from the third-party network from the
drop-down list of Line Clock Port according to the network plan. Set all SDH ports on
the channelized STM-1 interface board to use the SDH port for transmitting and
receiving SDH frames.
----End
A.12.1.2 Setting the E1 Clock Source for a Channelized STM-1 Interface Board
Each channelized STM-1 interface board can transparently transmit two E1 clock sources.
You can set the mapping between E1 clock sources and E1 lines.
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The channelized STM-1 interface board has been added in the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select a channelized STM-1 interface board from the Object Tree and
choose Configuration > Clock Transparent Transmission > Clock Transparent
Transmission.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
Physical Clock > Clock Source Priority.
Hold the Ctrl key on the keyboard to select multiple clock sources.
Step 7 Optional: Select a clock source and click or to adjust the priority of
this clock source.
NOTE
The clock priorities levels are arranged in a descending order from the first row to the last row. The internal
clock source is always of the lowest priority.
Step 8 Optional: Set External Clock Source Mode and Synchronous Status Byte for the external
clock sources.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The priority list of the clock source must be configured.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
Physical Clock > Clock Subnet Configuration.
Step 3 Start the clock protection protocol and configure its parameters.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The priority level of a clock source must be set.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
Physical Clock > Physical Clock Subnet Configuration.
NOTE
Step 7 Set the clock quality for which the quality level is zero.
NOTE
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l Clock sources have been configured.
l SSM protocols have been configured.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose ConfigurationClockPhysical
ClockClock Source Group from the Function Tree.
Step 2 Click New in the right pane. The Create Clock Source dialog box is displayed.
You can press and hold the Ctrl key to select multiple ports at a time.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The priority level of a clock source must be set.
l The standard SSM or extended SSM protocol is enabled.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
Physical Clock > Physical Clock Subnet Configuration.
NOTE
l Output S1 Byte Info is valid only when the SSM protocol or the extended SSM protocol is started.
l Output S1 Byte Info indicates whether the SSM is output at the line port.
l When the line port is connected to an NE in the same clock subnet, set Output S1 Byte Info to Enabled.
Otherwise, set this parameter to Disabled.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The priority level of a clock source must be set.
l The extended SSM protocol must be enabled.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
Physical Clock > Physical Clock Subnet Configuration.
NOTE
l Output Clock ID is valid only when the extended SSM protocol is started.
l Output Clock ID indicates whether the clock source ID is output at the line port.
l If the line ports are connected to the NEs in the same clock subnet and if the extended SSM protocol is
started on the opposite NE, Output Clock ID is set to Enabled. Otherwise, this parameter is set to
Disabled.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
Physical Clock > Phase-Locked Source Output by External Clock.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration >
Clock > Physical Clock > Clock Source Priority from the Function Tree.
Step 2 Click the Priority for PLL Clock Sources of 1st External Output tab.
Step 4 Configure the clock sources for external clock output based on network planning information.
NOTE
To select more than one clock source at a time, press and hold the Ctrl key when selecting the clock
sources.
NOTE
l When the PLL clock source of the external clock port extracts the system clock (namely, the local clock
of the NE), Clock Source takes its default value Internal Clock Source. In this case, no manual
configuration is required.
l When the PLL clock source of the external clock port needs to extract the clock from an SDH line board,
clock from a radio link, clock from a PDH tributary board, or synchronous Ethernet clock, set Clock
Source to the corresponding clock source according to the network planning information.
----End
Prerequisites
l OptiX RTN 905 does not support this operation.
l You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
Physical Clock > Clock Source Switching.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
Physical Clock > Clock Source Switching.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
OptiX RTN 905 does not support circuit emulation service (CES) adaptive clock recovery
(ACR) clocks.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
Physical Clock > Clock Synchronization Status.
----End
Prerequisites
l The corresponding board must be added on the NE Panel.
l For an E1 port on the logical board MP1 of an OptiX RTN 905, Service Mode has been
set to CES.
l You must be an NM user with NE administrator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Customize the configuration procedure by board.
Step 2 In the NE Explorer, select the desired NE from the Object Tree and choose Configuration >
Interface Management > PDH Interface from the Function Tree.
Step 4 Select a desired port, and set Retiming Mode to Line Clock Mode.
Step 7 Select the desired NE from the object tree in the NE Explorer, and choose Configuration >
Clock > CES Transmit Clock.
Step 8 Set parameters for the CES transmit clock.
1. Click New.
2. Set parameters for the CES transmit clock in the displayed dialog box.
3. Click Apply.
Step 9 Configure CES services that use the CES transmit clock.
1. Select the configured CES transmit clock and click New in the lower right corner.
2. Select a CES service in the displayed dialog box.
3. Click OK.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l CES services are configured.
Precautions
NOTICE
l An ACR clock domain can bind only the CES services on a local board.
l On the MD1 board, the four ACR clock domains can bind the CES services either from
the former 16 E1 ports or from the latter 16 E1 ports on a local board. That is, the four
ACR clock domains cannot simultaneously bind the CES services from the former 16 E1
ports and from the latter 16 E1 ports on a local board.
l A maximum of four ACR clock domains can bind CES services.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
Clock > ACR Clock from the Function Tree.
Step 2 In CES Service, select a CES service for primary clock extraction.
Step 3 Click Apply. Then, close the dialog box that is displayed.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l CES services are configured.
Precautions
NOTICE
l Ports output clocks from the system clock domain by default. Therefore, it is unnecessary
to set application ports to the system clock domain if system clocks are to be used.
l The ACR clock domain cannot contain ports from different boards.
l For a Smart E1 interface board, the E1 port providing the master clock in the ACR clock
domain must be added in the clock domain. For CD1 and VS2 on OptiX RTN 905, if only
part E1s of a port need to be added in the ACR clock domain, add the E1s corresponding
to the master clock in the ACR clock domain; if all E1s of a port need to be added in the
ACR clock domain, directly add the port to the ACR clock domain, instead of adding all
E1s in this port one after another.
l On the MD1 board, the four ACR clock domains can bind the CES services either from
the former 16 E1 ports or from the latter 16 E1 ports on a local board. That is, the four
ACR clock domains cannot simultaneously bind the CES services from the former 16 E1
ports and from the latter 16 E1 ports on a local board.
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
Clock > Clock Domain from the Function Tree.
Step 2 Click New.
The Create Clock Domain Port dialog box is displayed.
Step 4 In Clock Domain Board, select the board where the ACR clock domain resides.
3. Click .
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l The CES ACR clock has been configured.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
Clock > ACR Clock from the Function Tree.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the desired NE and choose ConfigurationClockPTP Clock PTP
Profile from the Function Tree.
Step 2 Select IEEE-1555v2 or G.8275.1 from PTP Profile.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
Clock > Frequency Selection Mode from the Function Tree.
Step 2 In Select Frequency Source Mode, select different clock synchronization modes.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
Clock > PTP Clock > Clock Synchronization Attribute.
Step 3 In PTP System Time, click , and then set the system time.
NOTE
Set this parameter for the grandmaster only when it uses local real-time clock as a timescale.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
Clock > PTP Clock > Clock Synchronization Attribute.
Step 2 Set parameters for a PTP clock according to the planning information.
NOTE
If a PTP clock or a clock source priority table is configured, the working mode cannot be changed.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
Clock > PTP Clock > Clock Synchronization Attribute from the Function Tree.
Step 2 Click the Port Status tab.
Step 4 Select the required board, select the corresponding port in Available Port, and then click
.
Step 5 Click OK.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l PTP clock ports are added.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
Clock > PTP Clock > Clock Synchronization Attribute from the Function Tree.
Step 3 Set parameters for PTP clock port attributes according to the planning information.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l PTP clock ports are added.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
Clock > PTP Clock > Clock Synchronization Attribute.
Step 3 Set parameters for PTP clock packets according to the planning information.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l PTP clock ports are added.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
Clock > PTP Clock > Clock Synchronization Attribute.
Step 3 Set parameters for configuring the cable transmission offset of PTP clock signals according to
the planning information.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l If IEEE 1588v2 is used, NE Clock Type is OC, BC, or TC+BC.
l If ITU-T G.8275.1 is used, NE Clock Type is T-BC.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
Clock > PTP Clock > Clock Subnet Configuration from the Function Tree.
Step 2 Click the Clock Subnet tab.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l If IEEE 1588v2 is used, NE Clock Type is OC, BC, or TC+BC.
l If ITU-T G.8275.1 is used, NE Clock Type is T-BC.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
Clock > PTP Clock > Clock Subnet Configuration from the Function Tree.
Step 2 Click the BMC tab.
Step 3 Set the parameters for the BMC algorithm according to the planning information.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
Clock > PTP Clock > External Time Interface from the Function Tree.
Step 2 Click the Basic Attribute tab.
Step 3 Set parameters for the basic attributes of external time ports according to the planning
information.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l NE Clock Type is set to BC, OC, or TC+BC for an NE, and Interface Mode in
External Time Interface is set to External Time Interface.
NOTE
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
Clock > PTP Clock > External Time Interface from the Function Tree.
Step 3 Set parameters for the BMC algorithm of external time ports according to the planning
information.
----End
A.12.3.13 Setting the Cable Transmission Offset for External Time Ports
This section describes how to compensate transmission delay of external time ports.
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l NE Clock Type is set to BC, OC, or TC+BC for an NE, and Interface Mode in
External Time Interface is set to External Time Interface.
NOTE
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
Clock > PTP Clock > External Time Interface from the Function Tree.
Step 3 Set parameters for the cable transmission distance according to the planning information.
----End
Context
NOTE
You can query real-time performance data and recent performance data.
Ethernet performance is monitored through RMON. Available performance monitoring periods include 30s,
30 minutes, custom period 1 (15 minutes by default), and custom period 2 (24 hours by default).
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding board must be added in the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 In the NE Explorer, navigate to the performance query interfaces for different objects
according to the following tables.
Basic Ethernet Select the corresponding board from the Object Tree in the NE
performan porta Explorer. Choose Performance > RMON Performance from
ce/ the Function Tree.
Extended
performan
ce
PLA group PLA 1. In the NE Explorer, select the required NE from the Object
performan group Tree and choose Configuration > Physical Link
ce Aggregation.
2. Select the desired PLA group, right-click, and choose
Browse Performance from the shortcut menu.
XPIC XPIC 1. In the NE Explorer, select the required NE from the Object
group group Tree and choose Configuration > Link Configuration.
performan 2. Select the desired XPIC group, right-click, and choose
ce Browse Performance from the shortcut menu.
XPIC XPIC 1. In the NE Explorer, select the required NE from the Object
group group Tree and choose Configuration > IF 1+1 Protection.
performan 2. Select the desired 1+1 protection group, right-click, and
ce choose Browse Performance from the shortcut menu.
MPLS MPLS 1. In the NE Explorer, select the required NE from the Object
tunnel Tunnel Tree and choose Configuration > MPLS Management >
performan Unicast Tunnel Management from the Function Tree.
ce 2. Click the Static Tunnel tab.
3. Select one or more tunnels, right-click the tunnel(s), and
choose Browse Performance from the shortcut menu.
L2 VPN- ETH 1. Select the NE from the Object Tree in the NE Explorer.
PW PWE3 Choose Configuration > Ethernet Service Management >
performan service E-Line Service from the Function Tree.
ce 2. Select one or more ETH PWE3 services, right-click the
service(s), and choose Browse Performance from the
shortcut menu.
L2 VPN UNI-UNI 1. Select the NE from the Object Tree in the NE Explorer.
performan E-Line Choose Configuration > Ethernet Service Management >
ce service E-Line Service from the Function Tree.
2. Select one or more UNI-UNI E-Line services, right-click the
service(s), and choose Browse Performance from the
shortcut menu.
Port traffic Ports that 1. Select the NE from the Object Tree in the NE Explorer.
classificati perform Choose Configuration > QoS Management > Policy
on complex Management > Port Policy from the Function Tree.
performan traffic 2. Click the Application Object tab.
ce classificati
on 3. Select one or multiple ports, right-click and choose Browse
Performance from the shortcut menu.
NOTE
Complete the operation A.9.8.8 Creating Traffic before monitoring the
port traffic classification performance.
Port DS Ports in a 1. Select the NE from the Object Tree in the NE Explorer.
domain DS Choose Configuration > QoS Management > Diffserv
performan domain Domain Management > Diffserv Domain Management
ce from the Function Tree.
2. Select the desired DS domain.
3. Click the Application Object tab.
4. Select one or multiple ports, right-click and choose Browse
Performance from the shortcut menu.
ETH OAM E-Line 1. In the NE Explorer, select the required NE from the Object
E-Line service Tree and choose Configuration > Ethernet OAM
service Management > Ethernet Service OAM Management.
performan 2. Select the desired MEP, right-click, and choose Browse
ce Performance from the shortcut menu.
MPLS-TP TUNNEL 1. In the NE Explorer, select the required NE from the Object
OAM Tree and choose Configuration > MPLS Management >
Unicast Tunnel Management.
2. Click the MPLS-TP OAM tab.
3. Select the desired MEP, right-click, and choose Browse
Performance from the shortcut menu.
NOTE
If you browse current Ethernet performance using the Web LCT: Select the corresponding board from the
Object Tree in the NE Explorer. Choose Performance > RMON Performance from the Function Tree.
If you click Start, the register of the statistics group is not reset to clear the existing data.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding boards must be added in the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 In the NE Explorer, navigate to the performance query interfaces for different objects
according to the following tables.
Basic Ethernet Select the corresponding board from the Object Tree in the NE
performan porta Explorer. Choose Performance > RMON Performance from
ce/ the Function Tree.
Extended
performan
ce
PLA group PLA 1. In the NE Explorer, select the required NE from the Object
performan group Tree and choose Configuration > Physical Link
ce Aggregation.
2. Select the desired PLA group, right-click, and choose
Browse Performance from the shortcut menu.
XPIC XPIC 1. In the NE Explorer, select the required NE from the Object
group group Tree and choose Configuration > Link Configuration.
performan 2. Select the desired XPIC group, right-click, and choose
ce Browse Performance from the shortcut menu.
XPIC XPIC 1. In the NE Explorer, select the required NE from the Object
group group Tree and choose Configuration > IF 1+1 Protection.
performan 2. Select the desired 1+1 protection group, right-click, and
ce choose Browse Performance from the shortcut menu.
MPLS MPLS 1. In the NE Explorer, select the required NE from the Object
tunnel Tunnel Tree and choose Configuration > MPLS Management >
performan Unicast Tunnel Management from the Function Tree.
ce 2. Click the Static Tunnel tab.
3. Select one or more tunnels, right-click the tunnel(s), and
choose Browse Performance from the shortcut menu.
L2 VPN- ETH 1. Select the NE from the Object Tree in the NE Explorer.
PW PWE3 Choose Configuration > Ethernet Service Management >
performan service E-Line Service from the Function Tree.
ce 2. Select one or more ETH PWE3 services, right-click the
service(s), and choose Browse Performance from the
shortcut menu.
L2 VPN UNI-UNI 1. Select the NE from the Object Tree in the NE Explorer.
performan E-Line Choose Configuration > Ethernet Service Management >
ce service E-Line Service from the Function Tree.
2. Select one or more UNI-UNI E-Line services, right-click the
service(s), and choose Browse Performance from the
shortcut menu.
Port traffic Ports that 1. Select the NE from the Object Tree in the NE Explorer.
classificati perform Choose Configuration > QoS Management > Policy
on complex Management > Port Policy from the Function Tree.
performan traffic 2. Click the Application Object tab.
ce classificati
on 3. Select one or multiple ports, right-click and choose Browse
Performance from the shortcut menu.
NOTE
Complete the operation A.9.8.8 Creating Traffic before monitoring the
port traffic classification performance.
Port DS Ports in a 1. Select the NE from the Object Tree in the NE Explorer.
domain DS Choose Configuration > QoS Management > Diffserv
performan domain Domain Management > Diffserv Domain Management
ce from the Function Tree.
2. Select the desired DS domain.
3. Click the Application Object tab.
4. Select one or multiple ports, right-click and choose Browse
Performance from the shortcut menu.
ETH OAM E-Line 1. In the NE Explorer, select the required NE from the Object
E-Line service Tree and choose Configuration > Ethernet OAM
service Management > Ethernet Service OAM Management.
performan 2. Select the desired MEP, right-click, and choose Browse
ce Performance from the shortcut menu.
MPLS-TP TUNNEL 1. In the NE Explorer, select the required NE from the Object
OAM Tree and choose Configuration > MPLS Management >
Unicast Tunnel Management.
2. Click the MPLS-TP OAM tab.
3. Select the desired MEP, right-click, and choose Browse
Performance from the shortcut menu.
NOTE
If you browse current Ethernet performance using the Web LCT: Select the corresponding board from the
Object Tree in the NE Explorer. Choose Performance > RMON Performance from the Function Tree.
Step 2 Click the Event tab and set the corresponding parameters.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding boards must be added in the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
NOTE
To set parameters for monitoring historical Ethernet performance of multiple NEs on the U2000, choose
Performance > RMON History Control Group Management from the main menu.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Performance > RMON
History Control Group.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding boards must be added in the NE Panel.
l The objects and performance events to be monitored must be set.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 In the NE Explorer, navigate to the performance query interfaces for different objects
according to the following tables.
Basic Ethernet Select the corresponding board from the Object Tree in the NE
performan porta Explorer. Choose Performance > RMON Performance from
ce/ the Function Tree.
Extended
performan
ce
PLA group PLA 1. In the NE Explorer, select the required NE from the Object
performan group Tree and choose Configuration > Physical Link
ce Aggregation.
2. Select the desired PLA group, right-click, and choose
Browse Performance from the shortcut menu.
XPIC XPIC 1. In the NE Explorer, select the required NE from the Object
group group Tree and choose Configuration > Link Configuration.
performan 2. Select the desired XPIC group, right-click, and choose
ce Browse Performance from the shortcut menu.
XPIC XPIC 1. In the NE Explorer, select the required NE from the Object
group group Tree and choose Configuration > IF 1+1 Protection.
performan 2. Select the desired 1+1 protection group, right-click, and
ce choose Browse Performance from the shortcut menu.
MPLS MPLS 1. In the NE Explorer, select the required NE from the Object
tunnel Tunnel Tree and choose Configuration > MPLS Management >
performan Unicast Tunnel Management from the Function Tree.
ce 2. Click the Static Tunnel tab.
3. Select one or more tunnels, right-click the tunnel(s), and
choose Browse Performance from the shortcut menu.
L2 VPN- ETH 1. Select the NE from the Object Tree in the NE Explorer.
PW PWE3 Choose Configuration > Ethernet Service Management >
performan service E-Line Service from the Function Tree.
ce 2. Select one or more ETH PWE3 services, right-click the
service(s), and choose Browse Performance from the
shortcut menu.
L2 VPN UNI-UNI 1. Select the NE from the Object Tree in the NE Explorer.
performan E-Line Choose Configuration > Ethernet Service Management >
ce service E-Line Service from the Function Tree.
2. Select one or more UNI-UNI E-Line services, right-click the
service(s), and choose Browse Performance from the
shortcut menu.
Port traffic Ports that 1. Select the NE from the Object Tree in the NE Explorer.
classificati perform Choose Configuration > QoS Management > Policy
on complex Management > Port Policy from the Function Tree.
performan traffic 2. Click the Application Object tab.
ce classificati
on 3. Select one or multiple ports, right-click and choose Browse
Performance from the shortcut menu.
NOTE
Complete the operation A.9.8.8 Creating Traffic before monitoring the
port traffic classification performance.
Port DS Ports in a 1. Select the NE from the Object Tree in the NE Explorer.
domain DS Choose Configuration > QoS Management > Diffserv
performan domain Domain Management > Diffserv Domain Management
ce from the Function Tree.
2. Select the desired DS domain.
3. Click the Application Object tab.
4. Select one or multiple ports, right-click and choose Browse
Performance from the shortcut menu.
ETH OAM E-Line 1. In the NE Explorer, select the required NE from the Object
E-Line service Tree and choose Configuration > Ethernet OAM
service Management > Ethernet Service OAM Management.
performan 2. Select the desired MEP, right-click, and choose Browse
ce Performance from the shortcut menu.
MPLS-TP TUNNEL 1. In the NE Explorer, select the required NE from the Object
OAM Tree and choose Configuration > MPLS Management >
Unicast Tunnel Management.
2. Click the MPLS-TP OAM tab.
3. Select the desired MEP, right-click, and choose Browse
Performance from the shortcut menu.
NOTE
If you browse current Ethernet performance using the Web LCT: Select the corresponding board from the
Object Tree in the NE Explorer. Choose Performance > RMON Performance from the Function Tree.
----End
Prerequisites
l OptiX RTN 905 does not support this operation.
l You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Orderwire
from the Function Tree.
3. Click Apply.
----End
Prerequisites
l OptiX RTN 905 does not support this operation.
l You must be an NM user with NE operator authority or higher.
l The AUX board exists on the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Orderwire
from the Function Tree.
Step 3 Hold on the Ctrl key, select two data channels from Available Data Path, and then click
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The AUX board exists on the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Orderwire
from the Function Tree.
Step 2 Click the Broadcast Data Port tab.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The IF1 board must be added on the NE Panel.
l The DCC channels corresponding to external clocks must be disabled.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > IF Interface from the Function Tree.
Step 3 Configure the enable status of the wayside E1 service and set the slot that houses the board.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The AUX board exists on the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
The external alarms of OptiX RTN 900 are also considered as housekeeping alarms. The
external alarm port of the NE is a relay port. This port can be either in the "on" state or in the
"off" state.
Procedure
Step 1 Select the AUX board from the Object Tree in the NE Explorer. Choose Configuration >
Environment Monitor Configuration > Environment Monitor Interface from the
Function Tree.
3. Click Apply, and then close the dialog box that is displayed.
Step 3 Configure the output alarm.
1. Select Output Relay from the drop-down list.
2. Configure the parameters of the output alarm.
3. Click Apply, and then close the dialog box that is displayed.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree and choose Configuration >
Auxiliary Interface from the Function Tree.
Step 2 Specifies the function of an auxiliary port.
NOTE
l For OptiX RTN 950/950A/980/980L, The ID of the outdoor cabinet monitoring port is 2.
l For OptiX RTN 905/910A, The ID of the outdoor cabinet monitoring port is 1.
l For OptiX RTN 950/950A/980/980L/910A, If the outdoor cabinet of the NE is monitored through an
outdoor cabinet monitoring port, set Interface Mode to MON for the outdoor cabinet monitoring
port.
l For OptiX RTN 905, If the outdoor cabinet of the NE is monitored through an outdoor cabinet
monitoring port, set Interface Mode to External clock (Hz)+outdoor cabinet for the outdoor
cabinet monitoring port.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l Interface Mode has been configured correctly under Auxiliary Interface.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
NOTE
l An OptiX RTN 980 and OptiX RTN 980L can be installed in any of the following outdoor cabinets:
APM30 AC and APM30 DC cabinets.
l An OptiX RTN 905, OptiX RTN 950, OptiX RTN 950A, and OptiX RTN 910A can be installed in any of
the following outdoor cabinets: APM30 AC, APM30 DC, OMB AC, and OMB DC cabinets.
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree and then choose
Configuration > NE Attribute from the Function Tree.
Step 2 Set Outdoor Rack under Advance Attribute.
NOTE
Ensure that the configured cabinet type is the same as the type of the actually used outdoor cabinet.
----End
A.14.6.3 Querying and Setting the Temperature and Fan Information of the
Outdoor Cabinet
By performing these operations, you can query the temperature and fan information of the
outdoor cabinet. In addition, you can set temperature alarm thresholds and set the working
mode of the fan.
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The TCU logical board has been added to the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select TCU from the Object Tree and choose Configuration >
Environment Monitor Configuration > Environment Monitor Interface from the
Function Tree.
Step 2 Select Outdoor cabinet interface from the drop-down list.
Step 3 Optional: Click Query to view the temperature and fan information.
It is recommended that the parameters take their default values, unless otherwise specified.
It is recommended that the parameters take their default values, unless otherwise specified.
----End
A.14.6.4 Querying and Setting the Information About the Power System of the
Outdoor Cabinet
By performing these operations, you can query and set the information about the power
module and the information about the storage batteries managed by the power monitoring unit
(PMU) of the outdoor cabinet.
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The PMU logical board has been added to the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
NOTE
Procedure
Step 1 In the NE Explorer, select PMU from the Object Tree and choose Configuration >
Environment Monitor Configuration > Environment Monitor Interface from the
Function Tree.
Step 2 Configure the information about the power system of the outdoor cabinet.
1. Select Outdoor cabinet interface from the drop-down list.
2. Click Query to view the information about the power system of the outdoor cabinet.
3. Modify the information about the power system of the outdoor cabinet.
4. Click Apply.
NOTE
It is recommended that the parameters take their default values, unless otherwise specified.
Step 3 Configure the information about the PMU of the outdoor cabinet.
1. Select Outdoor cabinet electrical source system attribute from the drop-down list.
2. Click Query to view the information about the PMU of the outdoor cabinet.
3. Modify the information about the power system of the outdoor cabinet.
4. Click Apply.
NOTE
It is recommended that the parameters take their default values, unless otherwise specified.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The PMU logical board has been added to the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
NOTE
Only APM30 AC and OBM AC cabinets support this operation.
Procedure
Step 1 In the NE Explorer, select PMU from the Object Tree and choose Configuration >
Environment Monitor Configuration > Environment Monitor Interface from the
Function Tree.
----End
A.14.6.6 Setting the Temperature and Humidity Alarm Thresholds for the PMU
When the ambient temperature exceeds the preset thresholds, the power monitoring unit
(PMU) reports the ODC_TEMP_ABN alarm; when the relevant humidity exceeds the preset
thresholds, the PMU reports the ODC_HUMI_ABN alarm.
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The PMU logical board has been added to the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Context
NOTE
Only APM30 AC and OBM AC cabinets support this operation.
Procedure
Step 1 In the NE Explorer, select PMU from the Object Tree and choose Configuration >
Environment Monitor Configuration > Environment Monitor Interface from the
Function Tree.
Step 2 Select Outdoor cabinet alarm threshold from the drop-down list.
Step 3 Select Operation Object, and set Upper Alarm Threshold for Ambient Temperature(°C),
Lower Alarm Threshold for Ambient Temperature(°C), Upper Alarm Threshold for
Ambient Humidity(RH%) and Lower Alarm Threshold for Ambient Humidity(RH%).
It is recommended that the parameters take their default values, unless otherwise specified.
----End
Note
This topic describes only common end-to-end configuration operations on the OptiX RTN
905E. For more details, see the U2000 Online Help.
Prerequisites
You must be an NM user with NE operator authority or higher.
Procedure
Step 1 Choose Service > SDH Protection Subnet > Search for SDH Protection Subnet from the
main menu.
Step 2 In the Subnets/Selected dialog box, select a subnet and click Next.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l SDH optical fiber connections have been created between NEs in the main topology.
l Configuration data on the U2000 is the same as that on NEs.
Context
NOTE
This section uses Create 1+1 Linear MSP as an example. You can create other types of linear MSP
protection subnets in a similar way.
Procedure
Step 1 Choose Service > SDH Protection Subnet > Create 1+1 Linear MSP from the main menu.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l SDH optical fiber connections have been created between NEs in the main topology.
l Configuration data on the U2000 is the same as that on NEs.
Context
NOTE
This section uses Create 2f_MS_SPRing as an example. You can create other types of ring MSP protection
subnets in a similar way.
Procedure
Step 1 Choose Service > SDH Protection Subnet > Create 2f_MS_SPRing from the main menu.
Step 2 Set parameters for the protection subnet to be created.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
Procedure
Step 1 Choose Service > SDH Protection Subnet > Manage SDH Protection Subnet from the
main menu.
Step 2 Click Query Networkwide Switching Status to query network-wide switching status.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l TDM services have been configured on a per-NE basis.
l Configuration data on the U2000 is the same as that on NEs.
Procedure
Step 1 Choose Service > SDH Trail > Search for SDH Trail from the main menu.
The Search for Description dialog box is displayed.
Step 2 Specify Search Strategy and click Next.
NOTE
If you select Search by subnet, click Next after selecting a subnet to be searched for.
Step 3 After the trail search is complete, click Next to view searched new trails.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l Port attributes have been correctly configured for boards on related NEs.
l SDH optical fiber connections have been created between NEs in the main topology.
l Configuration data on the U2000 is the same as that on NEs.
Context
l If a server trail to be created passes through intermediate NEs, create the server trail in
end-to-end mode. In this case, higher order VC-4s pass through intermediate NEs.
l If a server trail is created by creating trails between adjacent NEs, creating server trails
does not affect data on the NE side or the NE layer on the U2000 side. It only makes a
mark at the network layer on the U2000 side, which indicates that the VC-4 is used and
cannot be used by other VC-4 trails.
Procedure
Step 1 Choose Service > SDH Trail > Create SDH Trail from the main menu.
Step 3 Double-click the desired NE in the physical topology to configure the source and sink of the
server trail.
Step 4 Optional: Select and right-click the desired node and set it to be an explicit node.
Step 8 Optional: Click Browse Trail. In the Manage SDH Trail window, you can view the created
server trail.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l SDH optical fiber connections have been created between NEs in the main topology.
l Configuration data on the U2000 is the same as that on NEs.
l VC-4 server trails have been created.
Procedure
Step 1 Choose Service > SDH Trail > Create SDH Trail from the main menu.
NOTE
Set Level to VC12 for Native E1 services.
Step 4 Optional: Select and right-click the desired node and set it to be an explicit node.
Prerequisites
l You must be an NM user with NE operator authority or higher.
l Port attributes have been correctly configured for boards on related NEs.
l SDH optical fiber connections have been created between NEs in the main topology.
l Configuration data on the U2000 is the same as that on NEs.
l VC-4 server trails have been created.
Procedure
Step 1 Choose Service > SDH Trail > Create SDH Trail from the main menu.
Step 2 Set Level.
NOTE
Set Level to VC12 for Native E1 services.
Step 4 Optional: Select and right-click the desired node and set it to be an explicit node.
The Add the dual-fed and selective-receiving node dialog box is displayed.
3. Set Dual-Fed Point and Selective-Receiving Point.
4. Click OK.
Step 6 In the Calculate Route area, select Auto-calculation.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
Procedure
Step 1 Choose Service > SDH Trail > Manage SDH Trail from the main menu.
Step 2 In the Set Trail Browse Filter Criteria dialog box, set filter criteria and click Filter All.
The SDH trails that meet the criteria are listed in the query result.
Step 3 Select and right-click a desired trail and choose Copy from the shortcut menu.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
Procedure
Step 1 Choose Service > SDH Trail > Manage SDH Trail from the main menu.
Step 2 In the Set Trail Browse Filter Criteria dialog box, set filter criteria and click Filter All.
The SDH trails that meet the criteria are listed in the query result.
Step 3 Select an SDH trail from the list and check Detailed Physical Route.
Step 4 Optional: Select an SDH trail from the list, click the Transmission Media Layer Route tab,
and check Reachable Route Information.
Step 5 Optional: Select an SDH trail from the list, click the Service Layer Route tab, and check
Server Trail Information.
Step 6 Optional: Select an SDH trail from the list, click the Cross-Connection Information tab,
and check Cross-Connection Information.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l Before managing discrete services, search for SDH trails to ensure that discrete service
data is correct. For details, see A.15.2.1 Searching for SDH Trails.
Procedure
Step 1 Choose Service > SDH Trail > Manage SDH Discrete Service from the main menu.
A prompt dialog box is displayed.
Step 2 Click OK.
Step 3 In the Set Discrete Service Browse Filter Criteria dialog box, set filter conditions, and click
Filter.
The discrete SDH services that meet the criteria are listed in the query result.
Step 4 Select an SDH discrete service and query details about this service.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l Native Ethernet services are configured on a per-NE basis.
l Data is synchronized between the NE and the NMS.
l Fiber connections between ports on the service path are correct.
Context
NOTE
This task searches for Native Ethernet services that have been configured on a per-NE basis but have not
formed a topology on the network layer of the NMS. If Native Ethernet services are configured in end-
to-end mode or have formed a topology on the network layer of the NMS, skip this task and follow
instructions in A.15.3.6 Managing Native Ethernet Services to implement network management.
Procedure
Step 1 Choose Service > Native Ethernet Service > Search for Native Ethernet Service from the
Main Menu.
Step 2 Set the search scope.
If... Then...
The search scope covers all NEs managed by Select All and go to Step 4.
the U2000
The search scope is specified Select Select NE and go to the next step.
Step 6 Optional: Select a service and click Jump Service to start service query and maintenance
operations.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l Port attributes are configured for each board on an NE.
l Fibers or cables for Ethernet links between NEs are on the main topology.
l Data is synchronized between the NE and the NMS.
Procedure
Step 1 Choose Service > Native Ethernet Service > Create E-Line Service from the Main Menu.
4. Click OK.
5. Refer to Step 3 and configure the service sink of the E-Line service.
NOTE
After ETH OAM CC is selected, the U2000 automatically creates source and sink maintenance end points
(MEPs) in the same maintenance association (MA), and activates continuity check (CC).
NOTE
If correct routes have not been configured on the U2000, perform Step 6 and then click Calculate Route.
Step 6 Optional: Configure the explicit nodes for the E-Line service.
1. Click Add.
The Select NE dialog box is displayed.
2. Select the desired NE from the NE list on the left pane and click .
3. Click OK.
4. In Explicit Node, set Interface.
Step 7 Optional: Under Node List, set C-VLANs and S-VLANs for each node based on the node
type and service type.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l Ethernet boards and IF boards have been added in NE Panel.
Procedure
Step 1 Choose Service > ERPS Ring > Create ERPS Ring from the main menu.
.
3. Click OK.
NOTE
l It is recommended that you plan the counterclockwise direction as the main direction of services
transmission, and plan the port that transmits services in the main direction as an east port, and the port
that receives services as a west port.
l Set East Port or West Port to - for the sub-ring ERPS instance on an interconnection node.
l Set ERP Ring Node Flag and Flag Port to matching values according to the network plan by taking the
following suggestions:
– Only one node on the ring can be set as the RPL owner or RPL neighbor node for each Ethernet
ring.
– If the node is the RPL owner, set this parameter to RPL Port.
– If the node is an RPL neighbor node, set this parameter to Neighbor Port.
– If the node is the next-hop node of the RPL owner or RPL neighbor node, set this parameter to Next
Neighbor Port.
– It is recommended that you set the east port of the RPL owner to RPL Port and the west port of the
RPL neighbor node to Neighbor Port.
– It is recommended that you set the east port on RPL owner node's upstream node and the west port
on the RPL neighbor node's downstream node as Next Neighbor Port.
– If the node on the ring is not any of the preceding nodes, set this parameter to None.
– If the ERPS V1 protocol is used, only RPL Port needs to be set.
NOTE
If all NEs on the ERP ring are Huawei NEs, it is recommended that the default values be retained for all
parameters.
Step 7 Optional: Click Select Associated Master Ring to select the major ring associated with the
sub-ring.
----End
Follow-up Procedure
End-to-end ERPS configuration does not involve the ERPS version configuration. To change
the ERPS version, modify the configuration of involved NEs on a per-NE basis.
Prerequisites
l You must be an NM user with NE operator authority or higher.
Procedure
Step 1 Choose ServiceNative Ethernet ServiceCreate E-LAN Service from the Main Menu.
3. Under Available Interface, select the port to be mounted to the bridge and click
.
NOTE
If Port Mode of a port is Layer 3, the port is not displayed under Available Interface. To change
its port mode, right-click the NE, choose NE Explorer from the shortcut menu. Then, follow
instructions in A.8.8.1 Setting the Basic Attributes of Ethernet Ports to change its port mode to
Layer 2.
4. See the following table to set C-VLAN, S-VLAN, and Encapsulation Type.
5. Click OK.
Step 4 Repeat Step 3 to configure the bridge-mounted ports on other NEs in an E-LAN service
network.
1. Click .
2. Click the Interface Information tab.
3. Set the general attributes for the bridge-mounted ports.
The rules for setting these parameters are as follows:
– Enable Port:
n If a port is in use, set this parameter to Enabled.
n If a port is not in use, set this parameter to Disabled.
– Working Mode:
n If a bridge-mounted port is connected to an Ethernet port on the equipment
outside the E-LAN service network, set this parameter to the same value for
the two ports. Generally, the Ethernet port outside the E-LAN service network
works in Auto-Negotiation mode.
n If a bridge-mounted port is connected to an Ethernet port on the same E-LAN
service network, set this parameter to Auto-Negotiation for the two ports.
– Max Frame Length(bytes): If jumbo frames are transmitted, set this parameter
according to the length of jumbo frames. If jumbo frames are not transmitted, it is
recommended that this parameter should take the default value 1536.
1. Click .
2. Click the Interface Information tab.
3. Select the desired bridge-mounted ports.
4. Click .
The NE Explorer window is displayed.
5. Click the Advanced Attributes tab and set the advanced attributes for the ports.
The rules for setting these parameters are as follows:
– Loopback Check: To check whether a port is looped, set this parameter to
Enabled.
– Broadcast Packet Suppression:
n This parameter specifies whether to limit the traffic rate of the broadcast
packets according to the proportion of the broadcast packets in the total
packets. When the equipment at the opposite end may encounter a broadcast
storm, this parameter is set to Enabled.
n This parameter takes effect only for E-LAN services in the ingress direction.
– Broadcast Packet Suppression Threshold(%):When the proportion of the
broadcast packets in the total packets exceeds the value of this parameter, the
received broadcast packets are discarded. The value of this parameter should be
more than the proportion of the broadcast packets in the total packets before the
broadcast storm occurs. In normal cases, this parameter is set to default value.
– Loopback Port Block: To allow a looped port to be automatically blocked, set this
parameter to Enabled. The default value of this parameter is Disabled.
NOTE
a:
– For an OptiX RTN 905E 2E-provided microwave link for which 1+1 protection or link
aggregation group (LAG) is configured, set parameters only for the main IF_ETH port. The
following operations described in this section are also applicable only to the main port.
– For OptiX RTN 905E 1Es that are stacked to implement physical link aggregation/ (PLA),
Enhanced physical link aggregation(EPLA), 1+1 hot standby (HSB), 1+1 frequency diversity
(FD), or 1+1 space diversity (SD), set parameters only for IF_ETH ports on main NEs. The
following operations described in this section are also applicable only to main NEs.
6. Click Apply.
1. Click .
2. Click the ERPS tab. Then, click Add.
The Add ERPS dialog box is displayed.
3. Set the parameters for the ERPS protection instance.
4. Click OK.
5. Set the parameters for the ERPS protocol.
NOTE
– Set the parameters based on the network plan. Default values are recommended.
– The ID of a Control VLAN must not be the same as any VLAN ID used by Ethernet services. All
ring nodes should use the same Control VLAN ID.
1. Click .
2. Click the Split Horizon tab. Then, click Add.
The Add Split Horizon Group dialog box is displayed.
NOTE
After ETH OAM CC is selected, the U2000 automatically creates source and sink maintenance end points
(MEPs) in the same maintenance association (MA), and activates continuity check (CC).
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l Native Ethernet services are configured in end-to-end mode and ETH OAM CC are
enabled.
l The data on the NE and the NMS is synchronized.
Procedure
Step 1 Choose Service > Native Ethernet Service > Manage Native Ethernet Service from the
main menu.
Step 2 In the Set Filter Criteria dialog box, set filter conditions and click Filter.
The Native Ethernet services that meet the criteria are listed in the query result.
Step 3 Right-click the desired Native Ethernet service, and choose Ethernet OAM > Ethernet
OAM Test from the shortcut menu.
Step 5 Optional: If Ethernet OAM has not been configured during end-to-end E-LAN service
configuration, the Prompt dialog box is displayed.
1. Click Add.
2. Set OAM parameters.
3. Click OK.
Step 6 Optional: If Ethernet OAM has not been configured during end-to-end E-Line service
configuration, the Prompt dialog box is displayed. Click OK. Ethernet OAM will be
automatically configured.
Step 7 In the LB Test dialog box, select the desired service trail.
NOTE
l An LB test checks whether a service is bidirectional available. For a bidirectional service, select the
NE at either end to initiate an LB test.
l If Ethernet services are in different VLANs, the U2000 automatically selects the service in a VLAN
for an LB test.
l One NE cannot be involved in multiple LB tests simultaneously.
Step 8 Optional: Choose Config LB Parameter from the shortcut menu. Set Sent Packets, Sent
Packets Length, and Sent Packets Priority. Then, click OK.
Step 10 Click the LB Testing Information and LB Statistics Information tabs, and determine
whether the service is available based on the displayed information.
Normally, Test Results indicates Test Succeeded.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
Procedure
Step 1 Choose Service > Native Ethernet Service > Manage Native Ethernet Service from the
Main Menu.
Step 2 In the Set Filter Criteria dialog box that is displayed, set filter conditions and click Filter.
The Native Ethernet Service that meet the criteria are listed in the query result.
Step 3 Optional: Select the desired Native Ethernet Service from the query result, and view
information in the Topology, NE, Interface and Split Horizon Group tab pages.
Step 4 Optional: Select the desired Native Ethernet Service from the query result, click functional
buttons under the query result or right-click the service and choose options from the shortcut
menu to perform related maintenance operations.
----End
A.15.3.7 Testing the Packet Loss Rate, Delay, or Delay Jitter of a Native Ethernet
Service
This section describes how to test performance (including the packet loss rate, delay, and
delay jitter) of a Native Ethernet service by only one-click.
Prerequisites
l You must be an NM user with NE operator authority or higher.
Background Information
This task is supported only when the configuration is performed in end-to-end mode on the
U2000.
NOTE
For the restrictions on a service performance test, see ETH OAM in Feature Description.
Procedure
Step 1 Choose Service > Native Ethernet Service > Manage Native Ethernet Service from the
Main Menu.
Step 2 In the Set Filter Criteria dialog box, set filter criteria and click Filter.
The Native Ethernet Service that meet the criteria are listed in the query result.
Step 3 Right-click the desired Native Ethernet Service and choose Native Ethernet OAM > ETH
OAM Test from the shortcut menu.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
Procedure
Step 1 Choose Service > Native Ethernet Service > Manage Native Ethernet Discrete Service
from the Main Menu.
Step 2 In the Set Filter Criteria dialog box that is displayed, set filter conditions and click Filter.
The E-Line services that meet the criteria are listed in the query result.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l E-LAN services are configured.
l Data is synchronized between the NE and the NMS.
Procedure
Step 1 Choose Service > Native Ethernet Service > Manage Native Ethernet Service from the
main menu.
Step 2 In the Set Filter Criteria dialog box, set Service Type to E-LAN, and click Filter.
The E-LAN services that meet the criteria are listed in the query result.
5. Under Available Interface, select the port to be mounted to the bridge and click
.
6. See the following table to set C-VLAN, S-VLAN, and Encapsulation Type.
7. Click OK.
8. Click the Interface tab. Set the general attributes for the bridge-mounted ports.
Step 5 Add bridge-mounted ports to the nodes in the E-LAN service network.
1. Click the Interface tab.
2. Click Add.
The Select Port dialog box is displayed.
3. Select the desired nodes for adding bridge-mounted ports.
4. Under Available Interface, select the port to be mounted to the bridge and click
.
5. See the following table to set C-VLAN, S-VLAN, and Encapsulation Type.
6. Click OK.
7. Set the general attributes for the bridge-mounted ports.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l MPLS tunnels and PWE3 services have been correctly configured for NEs.
l The configuration data on the U2000 side is the same as the configuration data on the NE
side.
Procedure
Step 1 Choose Service > Search for Service from the Main Menu.
The Search for Service dialog box is displayed.
Step 2 Set the search domain.
1. Select Select NE and click Add.
The Select NE dialog box is displayed.
2. Select the desired NE and click OK.
The NEs are displayed in the NE list.
Step 3 Configure the service type to search for.
1. In the service list on the left, select one or more service types.
2. Optional: In the Tunnel and PWE3 tab pages, set the search criteria.
Step 5 Click the Add Service, Modify Service, and Discrete Service tabs to view the found
services.
l Add Service refers to a service that is not in the configuration data at the network layer
of the U2000.
l Modify Service refers to a service that is in the configuration data at the network layer
of the U2000 but some service parameters differ between the network layer and the NE
layer of the U2000. For MPLS tunnels, the U2000 does not support the search of
modified services.
l Discrete Service refers to a service that is only in the configuration data at the NE layer
of the U2000.
Step 6 Optional: Select a service and click Jump Service to start related service query and
maintenance operations.
----End
Follow-up Procedure
l Follow the instructions in A.15.5.6 Managing MPLS Tunnels in an End-to-End Mode
to query and maintain the found MPLS tunnels.
l Follow the instructions in A.15.6.11 Managing and Maintaining PWE3 Services to
query and maintain the found PWE3 services.
l Follow the instructions in A.15.5.7 Managing Discrete MPLS Tunnels to query and
maintain the found discrete MPLS tunnels.
l Follow the instructions in A.15.6.12 Managing Discrete PWE3 Services to query and
maintain the found discrete PWE3 services.
Prerequisites
You must be an NM user with NE administrator authority or higher.
Context
l IP addresses cannot be automatically allocated to some MPLS ports, such as ports on
Integrated IP microwave links, on non-point-to-point FE/GE links, or on MPLS links
where the NEs at both ends are unreachable on the NMS. Therefore, do not configure IP
addresses for these ports as the IP address resources for automatic allocation.
l If the IP addresses to be configured are discontinuous, many IP address resources can be
configured.
l The IP address resources should not contain IP addresses in the 192.168.0.0/16 network
segment, 192.169.0.0/16 network segment, or the network segments to which LSR IDs
and NE IP addresses belong.
Procedure
Step 1 Choose Configuration > IP Address Management from the Main Menu.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
Procedure
Step 1 Choose Inventory > Link Management from the Main Menu.
Step 5 Click Apply. Then, close the operation result dialog box that is displayed.
----End
Follow-up Procedure
If alarms are reported on the created L2 link, verify the following items.
l Fibers/cables are correctly connected.
l The port IP addresses at both ends of the L2 link are in the same network segment.
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l The basic attributes of the MPLS nodes have been correctly configured.
l Parameters related to MPLS ports have been correctly configured.
l Links between MPLS nodes are proper.
l Ingress nodes and egress nodes can be managed on the U2000.
Context
l If any ingress node or egress node cannot be managed on the U2000, create MPLS
tunnels when creating PWE3 services.
l It is recommended that you use the automatic route computation function to create
MPLS tunnels. Before you use the automatic route computation function, ensure that L2
links have been created between MPLS nodes.
Precautions
In each step, two snapshots are provided. The first one shows how to create bidirectional
tunnels, whereas the second one shows how to create unidirectional tunnels.
Procedure
Step 1 Choose Service > Tunnel > Create Tunnel from the Main Menu.
l Tunnel Name: Unless otherwise specified, this parameter takes its default value, which
is automatically generated by the U2000 according to the naming rules.
l Protocol Type: MPLS
l Signaling Type: Static CR
l Service Direction: Set this parameter to Bidirectional with priority. On MPLS nodes
that only support unidirectional tunnels, you need to set this parameter to
Unidirectional.
l Create Reverse Tunnel: During the creation of unidirectional tunnels, if routes for
forward tunnels and backward tunnels are the same, you can configure forward and
backward tunnels synchronously.
l Protection Type: Protection-Free
2. In the Select NE dialog box that is displayed, select one or more NEs, and click .
3. Click OK.
4. If the computed route is not the desired one, right-click the explicit or excluded NE in
the Physical Topology tab page, set restrictions from the shortcut menu, and click
Calculate route.
Step 5 Optional: Manually specify a route for a tunnel.
1. Do not select Auto-Calculate route.
2. Optional: Set Restriction Bandwidth(kbit/s).
It is recommended that this parameter takes its default value, No Limit. To use the CES
CAC verification function or to restrict the PW bandwidth, you need to set this
parameter according to the planned tunnel bandwidth.
3. In the Physical Topology tab page on the right, double-click the ingress NE, egress NE,
and the transit NEs between them one by one.
A tunnel route will be generated on the U2000 and displayed in the Physical Topology
tab page.
NOTE
The NEs marked by are ingress NEs, and the NEs marked by are egress NEs.
4. If the generated route is not the desired one, you can modify it in the NE lists on the left.
Step 6 Set information about the tunnels and the MPLS OAM.
1. Click Details.
2. Set information about the working tunnel in the Working Tunnel tab on the right.
The values for the related parameters are provided as follows.
– Tunnel ID: Set the parameter according to the network planning information. If the
parameter value is not specified in the planning information and the entire network
is managed by the U2000, the U2000 automatically allocates tunnel IDs.
– LSP Type and EXP: Unless otherwise specified, the two parameters take their
default values.
– In Interface, Out Interface, Next Hop, and Reverse Next Hop: When the
automatic route computation function is used, these parameters are automatically
configured by the U2000. When the route is computed manually, set these
parameters according to the route planning information.
– Incoming Label, Reverse Incoming Label, Outgoing Label, and Reverse
Outgoing Label: Set these parameters according to the network planning
information. If the parameter values are not specified in the planning information
and the entire network is managed by the U2000, the U2000 automatically allocates
these labels.
4. Optional: Click Configure OAM to configure MPLS OAM complying with ITU-T Y.
1711. In the dialog box that is displayed, set OAM parameters and click OK.
The values for the related parameters are provided as follows.
– Detection Packet Type: Set this parameter to FFD.
– Detection Packet Period(ms): Set this parameter to 3.3 (in most cases). If the
packet transmitting delay jitter in an MPLS tunnel exceeds 3.3 ms, set the packet
transmission interval to a value greater than the delay.
– Other parameters: Unless otherwise specified, it is recommended that the
parameters take their default value.
5. Repeat steps Step 6.2 and Step 6.4, to set information about tunnels and OAM on the
Reverse Working Tunnel tabs.
Step 9 In the Operation Result dialog box that is displayed, select View Tunnel.
The created tunnels are listed in the tunnel list.
----End
Follow-up Procedure
Follow the instructions in A.15.5.6 Managing MPLS Tunnels in an End-to-End Mode to
query and maintain the created MPLS tunnels.
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l The basic attributes of the MPLS nodes have been correctly configured.
l Parameters related to MPLS ports have been correctly configured.
Context
l If any ingress node or egress node cannot be managed on the U2000, create MPLS
tunnels when creating PWE3 services.
l It is recommended that you use the automatic route computation function to create
MPLS tunnels. Before you use the automatic route computation function, ensure that L2
links have been created between MPLS nodes.
Precautions
In each step, two snapshots are provided. The first one shows how to create bidirectional
tunnels, whereas the second one shows how to create unidirectional tunnels.
Procedure
Step 1 Choose Service > Tunnel > Create Tunnel from the Main Menu.
l Tunnel Name: Unless otherwise specified, this parameter takes its default value, which
is automatically generated by the U2000 according to the naming rules.
l Protocol Type: MPLS
l Signaling Type: Static CR
l Service Direction: Set this parameter to Bidirectional with priority. On MPLS nodes
that only support unidirectional tunnels, you need to set this parameter to
Unidirectional.
l Create Reverse Tunnel: During the creation of unidirectional tunnels, if routes for
forward tunnels and backward tunnels are the same, you can configure forward and
backward tunnels synchronously.
l Protection Type: 1:1
l Switching Mode: Unless otherwise specified, it is recommended that you set this
parameter to Double-Ended.
2. In the Select NE dialog box that is displayed, select one or more NEs, and click .
3. Click OK.
4. Double-click NE Role to set an NE node type.
Step 4 Optional: Configure a route for the tunnel using the automatic route computation function.
1. Select Auto-Calculate route.
2. Optional: Set Restriction Bandwidth(kbit/s) to No Limit.
To use the CES CAC verification function or to restrict the PW bandwidth, you need to
set this parameter according to the planned tunnel bandwidth.
3. Double-click the ingress NE, and then the egress NE in the Physical Topology tab page
on the right.
The U2000 will automatically computes a working tunnel and a protection tunnel
between the ingress NE and the egress NE, and display the tunnels in the Physical
Topology tab page.
4. If the computed working or protection route is not the desired one, you can right-click
the explicit or excluded NE in the Physical Topology tab page, set restrictions in the
dialog box displayed, and click Calculate route.
It is recommended that this parameter takes its default value, No Limit. To use the CES
CAC verification function or to restrict the PW bandwidth, you need to set this
parameter according to the planned tunnel bandwidth.
3. In the Physical Topology tab page on the right, double-click the ingress NE, egress NE,
and the transit NEs between them one by one.
A tunnel route will be generated on the U2000 and displayed in the Physical Topology
tab page.
NOTE
The NEs marked by are ingress NEs, and the NEs marked by are egress NEs.
4. If the generated route is not the desired one, you can modify it in the NE lists on the left.
Step 6 Set information about the tunnels and the MPLS OAM used for MPLS APS protection.
1. Click Details.
2. Set information about the working tunnel in the Working Tunnel or the Forward
Working Tunnel tab on the right.
The values for the related parameters are provided as follows.
– Tunnel ID: Set the parameter according to the network planning information. If the
parameter values are not specified in the planning information and the entire
network is managed by the U2000, the U2000 automatically allocates tunnel IDs.
– LSP Type and EXP: Unless otherwise specified, the two parameters take their
default values.
– In Interface, Out Interface, Next Hop, and Reverse Next Hop: When the
automatic route computation function is used, these parameters are automatically
configured by the U2000. When the route is computed manually, set these
parameters according to the planned route information.
– Incoming Label, Reverse Incoming Label, Outgoing Label, and Reverse
Outgoing Label: Set these parameters according to the network planning
information. If the parameter values are not specified in the planning information
and the entire network is managed by the U2000, the U2000 automatically allocates
these labels.
3. Optional: Click Configure MPLS-TP OAM to configure MPLS-TP OAM complying
with ITU-T Y.1731. Click Add in the dialog box that is displayed, set the required
parameters, and click OK.
The values for the related parameters are provided as follows:
– OAM Status: Set this parameter to Enable.
– It is recommended that you set CC Packet Sending Priority to 7 to ensure that CC
packets are preferentially forwarded. CC Packet Sending Priority can be set only
for egress nodes on bidirectional tunnels and ingress nodes.
– Detection Mode can be set only for a T-PE. Unless otherwise specified, it is
recommended that this parameter takes its default value Adaptive.
4. Optional: Click Configure OAM to configure MPLS OAM complying with ITU-T Y.
1711. In the dialog box that is displayed, set OAM parameters and click OK.
The values for the related parameters are provided as follows.
– Detection Packet Type: Set this parameter to FFD.
– Detection Packet Period(ms): Set this parameter to 3.3 (in most cases). If the
packet transmitting delay jitter in an MPLS tunnel exceeds 3.3 ms, set the packet
transmission interval to a value greater than the delay.
– Other parameters: Unless otherwise specified, it is recommended that the
parameters take their default value.
5. Repeat steps Step 6.2 and Step 6.4, to set information about tunnels and OAM on the
Protection Tunnel tab, or the Reverse Working Tunnel, Forward Protection Tunnel,
and Reverse Protection Tunnel tabs.
Step 7 Click Configure Protection Group. In the dialog box displayed, set attributes about MPLS
APS protection groups and click OK.
The values for the related parameters are provided as follows.
l Revertive Mode: Unless otherwise specified, it is recommended that you set this
parameter to Revertive.
l Other parameters: Unless otherwise specified, it is recommended that the parameters
take their default value.
Follow-up Procedure
l Follow the instructions in A.15.5.6 Managing MPLS Tunnels in an End-to-End Mode
to query and maintain the created MPLS tunnels.
l Follow the instructions in A.15.5.9 Managing MPLS APS Protection Groups in an
End-to-End Mode to query and maintain the created MPLS APS protection groups.
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l MPLS tunnels have already been deployed.
Procedure
Step 1 Choose Service > Tunnel > Manage Tunnel from the Main Menu.
Step 2 In the Set Filter Criteria dialog box that is displayed, set filter conditions and click Filter.
The MPLS tunnels that meet the criteria are listed in the query result.
Step 3 Right-click the tunnel to verify. Choose Test and Check from the shortcut menu.
NOTE
You can select and verify several MPLS tunnels concurrently.
Step 5 Optional: Click the on the right and set parameters about the LSP ping/LSP
traceroute test in the dialog box that is displayed.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
Procedure
Step 1 Choose Service > Tunnel > Manage Tunnel from the Main Menu.
Step 2 In the Set Filter Criteria dialog box that is displayed, set filter conditions and click Filter.
The MPLS tunnels that meet the criteria are listed in the query result.
Step 3 Optional: Select a desired tunnel, and browse the tunnel information in the Topology, Hop
Information, QoS Information, and Relevant Service tab pages at the bottom.
Step 4 Optional: Select the desired tunnels from the query result, click functional buttons under the
query result or right-click the service and choose options from the shortcut menu to perform
related maintenance operations.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
Procedure
Step 1 Choose Service > Tunnel > Manage Discrete Tunnel from the Main Menu.
Step 2 In the Set Filter Criteria dialog box that is displayed, set filter conditions and click Filter.
The discrete tunnels that meet the criteria are listed in the query result.
Step 3 Optional: Select a discrete tunnel, and browse the tunnel information on the Hop
Information and QoS Information tabs at the bottom.
Step 4 Optional: Select the desired discrete tunnel from the query result, click the Delete button or
right-click the tunnel and choose Delete to delete the tunnel.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l MPLS APS protection groups have been correctly configured.
l The configuration data on the U2000 side is the same as the configuration data on the NE
side.
Procedure
Step 1 Choose Service > Tunnel > Search for Protection Group from the Main Menu.
The Searching for Protection Groups dialog box is displayed.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
Procedure
Step 1 Choose Service > Tunnel > Manage Protection Group from the Main Menu.
Step 2 In the Set Filter Criteria dialog box that is displayed, set filter conditions and click Filter.
The MPLS APS protection groups that meet the criteria are listed in the query result.
Step 3 Optional: Select the desired MPLS APS protection group from the query result, right-click
the MPLS APS protection group and choose options from the shortcut menu or directly click
functional buttons under the query result to perform related maintenance operations.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l MPLS-TP tunnel OAM has been enabled for both the source and sink MPs and OAM
parameters have been configured.
Background Information
This task is supported only when the configuration is performed in end-to-end mode on the
U2000.
NOTE
l It is recommended that you measure the performance of MPLS tunnels deployed in end-to-end manner by
performing the preceding procedure. For MPLS tunnels deployed on a per-NE basis, it is recommended
that you convert the MPLS tunnels to end-to-end ones by referring to A.15.4 Searching for MPLS
Tunnels and PWE3 Services.
l To perform performance measurement for an MPLS tunnel in the NE Explorer, select the desired MPLS
tunnel, right-click, and choose Performance Statistics Management from the shortcut menu. In the
displayed dialog box, create the corresponding monitoring instance. Note that the PE at both ends must be
configured with the corresponding performance monitoring instance for this MPLS tunnel. Otherwise,
errors occur during performance measurement.
Procedure
Step 1 Choose Service > Tunnel > Manage Tunnel from the Main Menu.
The Set Filter Criteria dialog box is displayed.
Step 2 In the Set Filter Criteria dialog box, set filter criteria and click Filter.
The tunnels that meet the criteria are listed in the query result.
Step 3 Right-click the desired tunnel and choose Performance > Create Monitoring Instance from
the shortcut menu.
Step 4 Query the variation of an MPLS tunnel according to testing instances in the U2000 User
Guide for PMS.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l MPLS-TP tunnel OAM has been enabled for both the source MP and the sink MP and
OAM parameters have been configured.
Background Information
l This task is supported only when the configuration is performed in end-to-end mode on
the U2000.
l OptiX RTN 950 housing CSHU/CSHUA and OptiX RTN 950A do not support this
operation.
Procedure
Step 1 Choose Service > Tunnel > Manage Tunnel from the main menu.
Step 2 In the dialog box that is displayed, click Filter to set filter conditions. Query all MPLS
tunnels that meet the filter conditions.
Step 3 Right-click the desired tunnel and choose OAM > MPLS-TP OAM Test from the shortcut
menu.
The MPLS-TP OAM Test dialog box is displayed.
Step 4 Select Test from the drop-down menu. Click Parameter to set the test parameters.
Step 5 Select the NE to initiate the TST test and click Run.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
Context
l When a PWE3 service template is used for configuring a PWE3 service, the U2000
displays the default service parameter values. If the OptiX RTN 905E does not support
default parameter values in the service template, the U2000 displays parameter values
defaulted to the OptiX RTN 905E.
l To configure a PWE3 service, you can use a default service template that is exported
from the U2000 or customize a service template by making related modifications to the
exported service template. This section describes how to customize a service template by
making related modifications to a default service template.
Procedure
Step 1 Choose Service > Service Template from the Main Menu.
Step 2 In the Set Filter Criteria dialog box that is displayed, set filter conditions and click Filter.
The templates that meet the criteria are listed in the query result.
Step 4 In the Clone dialog box that is displayed, modify the template name and parameter values,
and select/deselect Set as Default Template.
NOTE
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l Parameters related to UNI ports have been configured correctly.
Procedure
Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the Main Menu.
Step 3 Configure the NEs and service ports on the NEs that are involved in the PWE3 services.
1. Double-click the source NE in the Physical Topology tab page.
2. Select the service port on the source NE, configure its SAI information, and click OK.
– If mapping between source ports and sink ports is specified and the PWs connected
by the mapping source and sink ports are transmitted over the same tunnel, you can
select some or all the source ports and configure parameters for the source service
ports at the same time.
– For SAToP CES services, deselect Channeled.
– For CESoPSN CES services, select Channeled and set 64K TimeSlot.
NOTE
For PCM30 services, the 64K TimeSlot parameter values must contain 16.
3. Repeat Step 3.1 and Step 3.2 to configure the service ports on the sink NE.
4. Optional: In the Physical Topology tab page, right-click the S-PE and choose Set As
Switching Node > Working from the shortcut menu.
NOTE
To create an unterminated PWE3 service, of which the PE at one end is unreachable on the U2000, right-click
the service in the physical topology and choose corresponding options from the shortcut menu to create the
service source or sink (a virtual node).
l Forward Tunnel and Reverse Tunnel: If there are end-to-end working MPLS tunnels
between PEs, the U2000 automatically generates the parameter values. If the tunnels
generated by the U2000 are different from the planned tunnels, select correct tunnels if
the tunnels have already been created or create the desired tunnels.
l PW ID, Forward Label, and Reverse Label: Set these parameters according to the
service planning information. If the parameter values are not specified in the service
planning information and the entire network is managed by the U2000, the U2000
automatically allocates values for these parameters.
NOTE
If these parameters need to be set according to planning information when multiple pairs of source and
sink ports have configured, you need to set the parameters separately for each pair of source and sink
ports.
l Protection Type: Protection-Free
l Service ID and Service Name: Unless otherwise specified, these two parameters take
their default values. The U2000 automatically generates the parameter values according
to the service naming rules.
Unless otherwise specified, it is recommended that all parameters in the tab take their
default values.
Step 8 In the Operation Result dialog box that is displayed, select Browse Trail.
The new CES service is displayed in the PWE3 service list.
NOTE
If multiple pairs of source and sink service ports have been configured, you need to create a CES service for
each pair of the source and sink ports.
----End
Follow-up Procedure
Follow the instructions in A.15.6.11 Managing and Maintaining PWE3 Servicesto query
and maintain the created PWE3 services.
Prerequisites
You must be an NM user with NE operator authority or higher.
Procedure
Step 1 Choose Configuration > PTN QoS Profile > ATM Profile from the Main Menu.
Step 2 Right-click in ATM Profile and choose Add Global Profile from the shortcut menu.
Step 5 Optional: Check and manage the global ATM policy profile in the Details, NE Reference,
and NE Unreference tabs.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
Procedure
Step 1 Choose Configuration > PTN QoS Profile > ATM CoS Mapping Profile from the Main
Menu.
If... Then...
You need to change the default global ATM CoS mapping Perform Step 3 and Step 5.
profile
You need to create a global ATM CoS mapping profile Perform Step 6 and Step 8.
Step 4 Modify the global ATM CoS mapping profile according to network planning information.
NOTE
l Eight PHB service classes are available: BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The OptiX RTN
900 provides different QoS policies for the queues of different service classes.
l CS6 to CS7: highest service classes, mainly applicable to signaling transmission.
l EF: fast forwarding, applicable to services of low transmission delays and low packet loss rates.
l AF1 to AF4: assured forwarding, applicable to services that require an assured transmission rate rather
than delay or jitter limits.
The AF1 class includes three subclasses: AF11, AF12, and AF13. Only one of these subclasses can take
effect for one queue. It is the same case with AF2, AF3, and AF4.
l BE: best effort, applicable to services that do not require special processing.
Step 6 Right-click in ATM CoS Mapping Profile and choose Add Global Profile from the shortcut
menu.
Step 7 Create a global ATM CoS mapping profile according to network planning information.
NOTE
l Eight PHB service classes are available: BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The OptiX RTN
900 provides different QoS policies for the queues of different service classes.
l CS6 to CS7: highest service classes, mainly applicable to signaling transmission.
l EF: fast forwarding, applicable to services of low transmission delays and low packet loss rates.
l AF1 to AF4: assured forwarding, applicable to services that require an assured transmission rate rather
than delay or jitter limits.
The AF1 class includes three subclasses: AF11, AF12, and AF13. Only one of these subclasses can take
effect for one queue. It is the same case with AF2, AF3, and AF4.
l BE: best effort, applicable to services that do not require special processing.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
Procedure
Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the Main Menu.
Step 2 Set the basic attributes for ATM services.
Set the parameters as follows:
l Service template: If no service template has been specified, it is recommended that you
set this parameter to DEFAULT_PWE3_ATM_PTN/ATN.
l Service Type: ATM
l Service ID and Service Name: Unless otherwise specified, these two parameters take
their default values. The U2000 automatically generates the parameter values according
to the service naming rules. An appropriate Service Name improves service
maintainability in the case of centralized management.
l Protection Type: Protection-Free
Step 3 Configure the NEs and service ports on the NEs that are involved in the ATM service.
1. Double-click the source NE in the Physical Topology tab page.
2. Select the service port on the NE.
3. Click OK.
4. Repeat Step 3.1 and Step 3.3 to configure the service port on the sink NE.
5. Optional: In the Physical Topology tab page, right-click the S-PE and choose Set As
Switching Node > Working from the shortcut menu.
NOTE
To create an unterminated PWE3 service, of which the PE at one end is unreachable on the U2000, right-click
the service in the physical topology and choose related options from the shortcut menu to create the service
source or sink (a virtual node).
Set Forward Tunnel, Reverse Tunnel, PW ID, Forward Label, and Reverse Label.
Unless otherwise specified, it is recommended that all parameters in the tab take their
default values.
Unless otherwise specified, it is recommended that all parameters in the tab take their
default values.
Step 10 In the Operation Result dialog box that is displayed, select Browse Trail.
The new ATM service is displayed in the PWE3 service list.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l Parameters related to UNI ports have been configured correctly.
Procedure
Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the Main Menu.
Step 3 Configure the NEs and service ports on the NEs that are involved in the PW-carried E-Line
service.
1. Double-click the source NE in the Physical Topology tab page.
2. Select the service port on the source NE, configure its VLAN ID, and click OK.
– Set VLAN ID to the VLAN ID planned for the Ethernet services over the UNI port.
– If you do not configure VLAN ID, Ethernet services exclusively occupy the UNI
port.
3. Repeat Step 3.1 and Step 3.2 to configure the service port on the sink NE.
The information about the source and sink NEs is displayed in Node List.
4. Optional: In the Physical Topology tab page, right-click the S-PE and choose Set As
Switching Node > Working from the shortcut menu.
NOTE
To create an unterminated PWE3 service, of which the PE at one end is unreachable on the U2000, right-click
the service in the physical topology and choose corresponding options from the shortcut menu to create the
service source or sink (a virtual node).
Unless otherwise specified, it is recommended that all parameters in the tab take their
default values.
If you select Deploy, the service configuration data is saved on the U2000 side and deployed
to the NE side. If you do not select Deploy, the service configuration data is saved on the
U2000 side but is not deployed to the NE side.
Step 8 In the Operation Result dialog box that is displayed, select Browse Trail.
The new Ethernet PWE3 service is displayed in the PWE3 service list.
----End
Follow-up Procedure
Query and verify the created Ethernet PWE3 service by referring to A.15.6.10 Verifying PW-
Based Ethernet Service Configurations (in an End-to-End Mode).
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l The UNI interfaces have been configured correctly.
Context
After planning and configuring MPLS tunnels, aggregate Ethernet services from BTSs to the
RNC by means of PWs. The service requirements are as follows:
l Ethernet services (VLAN ID: 100) at BTS11 need to be transmitted to the RNC. A
bidirectional working tunnel (ID: 1501), which has a protection tunnel, is available
between NE11 and NE31.
l Ethernet services (VLAN ID: 100) at BTS21 need to be transmitted to the RNC. A
bidirectional working tunnel (ID: 1701), which has a protection tunnel, is available
between NE21 and NE31.
l Ethernet services at all preceding BTSs have already been configured with
corresponding VLAN priorities based on service types (real-time voice services, HSDPA
real-time services, R99 non-real-time services, and HSDPA data services), and the
transmission network is required to provide end-to-end QoS control based on the VLAN
priorities specified at the BTSs.
l GE ports on NE31, which are connected to the RNC, need to be protected in link
aggregation group (LAG) mode.
Figure A-9 Networking diagram (hybrid configuration of E-Line and E-LAN services carried
by PWs)
Working tunnel
(ID=1501)
NNI UNI
BTS11
NE32
VLAN 100
GE
NE31
NE11 RTN 950
RTN 980 NE21
R4 E-Line RTN 980 VPLS RNC
E-Line
Working tunnel
(ID=1701)
R4
BTS21
VLAN 100
Procedure
Step 1 Configure hybrid E-Line services and E-LAN services carried by PWs in end-to-end mode.
Figure A-10 Configuring hybrid E-Line services and E-LAN services carried by PWs in end-
to-end mode
NOTE
For OptiX RTN 950A, OptiX RTN 910A, OptiX RTN 905 or OptiX RTN 950 that uses a CSHU/CSHUA
board, MAC Address Learning Mode can be set to IVL.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
Procedure
Step 1 Choose Service > PWE3 Service > Manage PWE3 Service from the Main Menu.
The Set Filter Criteria dialog box is displayed.
After you click Filter, all configured PWE3 services will be displayed.
Step 3 Right-click the PWE3 service to verify and choose Diagnose > Test And Check from the
shortcut menu.
The Diagnosis Option tab page is displayed.
If... Then...
You perform a PW ping test Perform Step 5 and Step 9.
You perform a PW traceroute Perform Step 10 and Step 14.
test
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
Procedure
Step 1 Choose Service > PWE3 Service > Manage PWE3 Service from the Main Menu.
The Set Filter Criteria dialog box is displayed.
Step 2 Click Filter.
NOTE
After you click Filter, all configured PWE3 services will be displayed.
Step 3 Right-click the ATM PWE3 service to verify and choose Connectivity Test from the shortcut
menu.
The Connectivity Test dialog box is displayed.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l PW-based Ethernet services have been configured.
Procedure
Step 1 Choose Service > PWE3 Service > Manage PWE3 Service from the Main Menu.
Step 2 In the Set Filter Criteria window, select Source NE and Sink Node. Click Filter.
Step 3 Right-click the PWE3 service to verify, and choose Ethernet OAM > LB Test... from the
shortcut menu.
Step 4 In the Eth Oam LB Test dialog box that is displayed, select the source NE for initiating an
LB test.
NOTE
Step 5 Optional: Right-click the service that is selected for an LB test, and choose Configure...
from the shortcut menu. In the Config Eth Oam LB Test Parameter dialog box that is
displayed, set Sent Packets, Sent Packets Length, and Sent Packets Priority. Then, click
OK.
Step 6 Right-click the service that is selected for an LB test, and choose Run from the shortcut
menu.
Step 7 Click the LB Statistic Information tab and determines whether the service is available based
on the displayed information.
If Test Result displays Test Succeeded, the service is available.
If Packet Loss Ratio(%) displays 100 and Test Result displays Test Failed, the service is
unavailable. If the service is unavailable, check whether the service configurations are
incorrect.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
Procedure
Step 1 Choose Service > PWE3 Service > Manage PWE3 Service from the Main Menu.
Step 2 In the Set Filter Criteria dialog box that is displayed, set filter conditions and click Filter.
The PWE3 services that meet the criteria are listed in the query result.
Step 3 Optional: Select a desired PWE3 service and browse the service information in the
Topology, SAI, Service Parameter, and PW tab pages at the bottom.
Step 4 Optional: Select the desired PWE3 service from the query result, click functional buttons
under the query result or right-click the service and choose options from the shortcut menu to
perform related maintenance operations.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
Procedure
Step 1 Choose Service > PWE3 Service > Manage PWE3 Discrete Service from the Main Menu.
Step 2 In the Set Filter Criteria dialog box that is displayed, set filter conditions and click Filter.
The discrete PWE3 services that meet the criteria are listed in the query result.
Step 3 Optional: Select a desired discrete PWE3 service and browse the service information in the
SAI, Service Parameter, and PW tab pages at the bottom.
Step 4 Optional: Select the desired discrete PWE3 service from the query result, click Delete
Discrete Service, or right-click the service and choose Delete Discrete Service from the
shortcut menu.
Step 5 Optional: Select the desired discrete PWE3 service from the query result, click Convert to
Unterminated, or right-click the service and choose Convert to Unterminated from the
shortcut menu.
----End
A.15.6.13 Testing the Packet Loss Ratio, Delay, and Delay Variation of a PW
This section describes how to query the packet loss ratio, delay, and delay variation of a PW.
Prerequisites
l You must be an NM user with NE operator authority or higher.
l MPLS-TP PW OAM has been enabled for both the source and sink MPs and OAM
parameters have been configured.
Background Information
This task is supported only when the configuration is performed in end-to-end mode on the
U2000.
NOTE
Procedure
Step 1 Choose Service > PWE3 Sevice > Manage PWE3 Sevice from the Main Menu.
The Set Filter Criteria dialog box is displayed.
Step 2 In the Set Filter Criteria dialog box, set filter criteria and click Filter.
The PWs that meet the criteria are listed in the query result.
Step 3 Right-click the desired PW and choose Performance > Create Monitoring Instance from
the shortcut menu.
Step 4 Query the variation of a PW according to the testing instances in the U2000 User Guide for
PMS.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l MPLS-TP PW OAM has been enabled for both the source MP and the sink MP and
OAM parameters have been configured.
Background Information
l This task is supported only when the configuration is performed in end-to-end mode on
the U2000.
l OptiX RTN 950 housing CSHU/CSHUA and OptiX RTN 950A do not support this
operation.
Procedure
Step 1 Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
Step 2 In the dialog box that is displayed, click Filter to set filter conditions. Query all PWs that
meet the filter conditions.
Step 3 Right-click the desired PW and choose PW OAM > TP OAM Test from the shortcut menu.
The MPLS-TP OAM Test dialog box is displayed.
Step 4 Select Test from the drop-down menu. Click Parameter to set the test parameters.
Step 5 Select the NE to initiate the TST test and click Run.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
End-to-end Ethernet services have been deployed.
Procedure
Step 1 Optional: Search for an E-Line service path.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
End-to-end Ethernet services have been deployed.
Procedure
Step 1 Search for an E-LAN service path.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
End-to-end Ethernet services have been created and the related fibers/cables have been
created.
Procedure
Step 1 Search for an E-LAN service path.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
Procedure
Step 1 Search for services.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
End-to-end Ethernet services have been created and the related fibers/cables have been
created.
Procedure
Step 1 Search for an E-LAN service path.
NOTE
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
End-to-end Ethernet services have been created and the related fibers/cables have been
created.
Procedure
Step 1 Search for service paths.
Step 2 Query the real-time and historical performance data of each measured object on each service
path.
The following figure shows how to query the real-time performance data of priority queues on
a port. Querying the real-time and historical performance data of other measured objects is
similar.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
NOTE
Procedure
Step 1 Select Clock View from the Current View drop-down list in Main Topology.
NOTE
Alternatively, right-click in the physical topology view and choose Switch to Clock View from the shortcut
menu.
Step 2 Right-click a desired NE and choose Display Current Tracing Path from the shortcut menu.
l The clock view displays the clock tracing relationship between NEs.
NOTE
– The arrow direction in the clock view indicates the clock tracing direction. For example, if
NE(208-1) points to NE(208-2), NE(208-2) traces the clock information transmitted from
NE(208-1).
– The number displayed on the continuous line indicates the priority of the traceable clock. The
smaller the number, the higher the priority. The clock view displays the line clock source IDs only.
Internal clock sources are numbered, but their IDs are not displayed in the clock view.
l Details about the clock link are displayed in the lower part of the window.
2. Choose View > Display Setting > Legend from the main menu to browse meanings of
the icons and colors in the clock view.
----End
B Parameters Description
Navigation Path
Choose File > Discovery > NE from the Main Menu.
Navigation Path
Click NE Search in NE List and select a desired search type.
Domain Type GNE IP Domain GNE IP Domain l To search for all the
GNE IP Address NEs that
communicate with the
GNE, select GNE IP
Domain.
l To search for the
GNE only, select
GNE IP Address.
Navigation Path
1. Choose File > New > NE from the Main Menu.
2. Choose RTN Series from the Object Tree and select a desired product.
Name - - l This
parameter
specifies the
name of the
NE.
l After you
have
specified the
name of the
NE, the
name is
displayed
under the
icon of the
NE.
Protocol IP IP l This
parameter
needs to be
set when
Gateway
Type is set to
Gateway.
l In other
cases, this
parameter is
set to IP.
Navigation Path
In NE List, click Add NE. Then, select Europe.
Gateway Type IP Gateway IP Gateway This parameter specifies the type of the
Serial Port gateway that is used for the
communication between the Web LCT and
SSL Gateway the NEs.
USB
Port l 1400 (when l 1400 (when This parameter specifies the port
Gateway Type Gateway Type corresponding to the gateway NE to which
is set to IP is set to IP the NE to be created belongs.
Gateway) Gateway)
l COM1-COM32 l COM1 (when
(when Gateway Gateway Type
Type is set to is set to Serial
Serial Port) Port)
Navigation Path
In the NE List, select the target NE and click NE Login.
Parameters
Parameter Value Range Default Value Description
Use same user Selected Deselected When this parameter is selected, enter
name and Deselected User Name and Password to log in to all
password to login the selected NEs.
Use the user name Selected Deselected When this parameter is selected, enter
and password that Deselected User Name and Password that were used
was used last time for the latest login to log in to the NE.
Navigation Path
1. In the Main Topology, right-click the NE whose ID needs to be changed.
2. Choose Properties.
3. Click Modify NE ID.
Navigation Path
1. Choose Configuration > NE Batch Configuration > NE Time Synchronization from
the Main Menu.
2. Click the NE Time Synchronization tab.
Navigation Path
1. In the NE Explorer, select the NE from the Object Tree and then choose Configuration
> NE Time Synchronization from the Function Tree.
2. Set the synchronous mode.
Encryption Type MD5 MD5 This parameter specifies the MD5 key
algorithm.
Navigation Path
1. Choose Configuration > NE Batch Configuration > NE Time Localization
Management from the Main Menu.
2. Select the NE for time localization management from the Object Tree, and then click
Navigation Path
1. Choose Configuration > NE Batch Configuration > NE Time Synchronization from
the Main Menu.
2. Click the Standard NTP Key Management tab.
Navigation Path
1. In the NE Explorer, select the NE and then choose Configuration > License
Management from the Function Tree.
2. Click the License Management tab.
Navigation Path
1. On the Main Topology, choose Configuration > NE Batch Configuration > Automatic
Disabling of NE Function.
2. Select the NE whose functions need to be automatically disabled from the Object Tree,
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Communication >
Communication Parameters from the Function Tree.
Connection Mode Common + Security Common + Security l Specifies the connection mode that the
SSL SSL gateway NE allows the NMS to use for
Common connecting to the gateway NE.
Security SSL l If the gateway NE has no special
security requirement for connection to
the NMS, Connection Mode can be
set to Common.
l If the gateway NE requests secure
connection to the NMS for preventing
information interception and cracking,
Connection Mode needs to be set to
Security SSL.
l If NE communication security level
needs to be the same as NMS
communication security level,
Connection Mode needs to be set to
Common + Security SSL.
l The default parameter value is
recommended unless the gateway NE
requires that the NMS use the SSL
connection mode.
l The parameter value takes effect only
when it is set for a gateway NE and the
gateway NE is connected to the NMS
by means of the IP protocol.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Communication >
DCC Management from the Function Tree.
2. Click the DCC Rate Configuration tab.
Channel D1-D3 D1-D1 (for the It is recommended that you use the default
D4-D12 PDH radio whose value, except for the following cases:
transmission l If the IP DCN solution is adopted,
D1-D12 capacity is less than Channel for the SDH line ports is set
D1-D1 16xE1) to a value that is the same as the value
D1-D3 (for other for third-party network.
cases) l If the DCC transparent transmission
solution is adopted, the value of
Channel for the SDH line ports should
not conflict with the value that is set for
the third-party network.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Communication >
DCC Management from the Function Tree.
2. Click the DCC Transparent Transmission Management tab.
3. Click Create.
NOTE
a. A bidirectional cross-connection is set up between the source port and the sink port. Hence, a port functions
the same regardless of the source port or sink port.
Navigation Path
Click an NE in the NE Explorer. Choose Communication > ECC Management from the
Function Tree.
ECC Extended Auto mode Autosensing mode It is recommended that you use the default
Mode Specified mode value.
NOTE
Autosensing mode
By default, the adaptive mode is enabled for the
extended ECC on an NE. That is, when the
NMS port on an NE finds that the automatic
extended ECC is enabled on another NE in the
same network segment, the automatic extended
ECC is enabled on this NE. Otherwise, the
extended ECC is not enabled on this NE.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Communication > NE ECC
Link Management from the Function Tree.
Navigation Path
1. In the NE Explorer, select the desired NE from the Object Tree and then choose
Communication > NE ECC Link Management from the Function Tree.
2. Click Reachability Test and choose Ping or Trace Route from the drop-down menu.
Ping Parameters
Parameter Value Range Default Value Description
Traceroute Parameters
Parameter Value Range Default Value Description
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP
Protocol Stack Management from the Function Tree.
2. Click the IP Route Management tab.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP
Protocol Stack Management from the Function Tree.
2. Click the IP Route Management tab.
3. Click New.
Navigation Path
1. In the NE Explorer, select the desired NE from the Object Tree and then choose
Communication > IP Protocol Stack Management from the Function Tree.
2. Click Reachability Test and choose Ping Test or Trace Route from the drop-down
menu.
Traceroute Parameters
Parameter Value Range Default Value Description
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP
Protocol Stack Management from the Function Tree.
2. Click the OSPF Parameter Settings tab.
OSPF Parameters
Parameter Value Range Default Value Description
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP
Protocol Stack Management from the Function Tree.
2. Click the Proxy ARP tab.
Proxy ARP Disabled Disabled l The proxy ARP enables the NEs in the
Enabled same network segment but different
domains to communicate with each
other.
l To realize communication between
such NEs, the source NE sends the
ARP broadcast packet to address the
route to the destination NE. The NE
with the proxy ARP function enabled
checks the routing table after sensing
the ARP broadcast packet. If the
routing table contains the destination
address that the ARP broadcast packet
looks for, the NE returns an ARP
spoofing packet, which enables the NE
that sends the ARP broadcast packet to
consider that the MAC address of the
NE that returns the ARP spoofing
packet is the MAC address of the
destination NE. In this manner, the
packet that is to be sent to the
destination NE is first sent to the NE
with the proxy ARP function enabled
and then forwarded to the destination
NE.
Navigation Path
1. In the NE Explorer, select the desired NE and choose Communication > IP Protocol
Stack Management from the Function Tree.
2. Click the Multi-area OSPF Management tab.
Network Parameters
Parameter Value Range Default Value Description
Navigation Path
1. In the NE Explorer, select the desired NE and choose Communication > IP Protocol
Stack Management from the Function Tree.
2. Click the Multi-area OSPF Management tab.
3. Click New.
Stub Type NON-STUB NON-STUB Set the STUB type of an area according to
STUB planning information.
NSSA l For the backbone area, this parameter
must be set to NON-STUB.
l For other areas, it is recommended that
you set this parameter to NON-STUB.
If required, this parameter can also be
set to STUB or NSSA.
Navigation Path
1. In the NE Explorer, select the desired NE and choose Communication > IP Protocol
Stack Management from the Function Tree.
2. Click the Multi-OSPF Management tab.
3. In Manual Route Aggregation, click Add.
Navigation Path
1. In the NE Explorer, select the required NE and choose Communication > IP Protocol
Stack Management from the Function Tree.
2. Click the Port OSPF Parameter Settings tab.
Navigation Path
1. In the NE Explorer, select the desired NE from the Object Tree. Choose
Communication > Static Route Entries in the Kernel Route Table from the Function
Tree.
2. Click Create.
Parameters
Parameter Value Range Default Value Description
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Communication >
DCN Management from the Function Tree.
2. Click the Bandwidth Management tab.
NMS Port VLAN 2 to 4094 - NMS Port VLAN ID indicates the VLAN
ID ID of Huawei NMS and is used to
distinguish Huawei DCN packets from
third-party DCN packets on NMS ports.
The OptiX RTN 950 using CSH/CST
boards, OptiX RTN 980, and OptiX RTN
980L do not support this parameter.
The OptiX RTN 950 using CSH/CST
boards and OptiX RTN 980 using CSHN
boards do not support this parameter.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Communication >
DCN Management from the Function Tree.
2. Click the Port Settings tab.
Navigation Path
l In the NE Explorer, select the desired NE from the Object Tree and then choose
Communication > DCN Management from the Function Tree.
l Click the Access Control tab.
Parameters
Parameter Value Default Description
Range Value
Navigation Path
l In the NE Explorer, select the desired NE from the Object Tree and then choose
Communication > DCN Management from the Function Tree.
l Click the Packet Control tab.
Packet Priority CS6 CS6 (Packet Type Specifies the VLAN priorities of inband
EF is VLAN) DCN packets or the PHBs corresponding
BE (Packet Type is to the DSCP values of the inband DCN
AF4 packets.
DSCP)
AF3
AF2
AF1
BE
Navigation Path
l In the NE Explorer, select the desired NE from the Object Tree and then choose
Communication > L2DCN Management from the Function Tree.
l Click Query.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Communication > Access
Control from the Function Tree.
Enable Serial Port Selected Selected After Enable Serial Port Access is
Access Deselected selected, the NE can access the NMS or
command lines through the serial port.
Enable OAM Selected Selected After Enable OAM Access is selected, the
Access Deselected NE can access the NMS or command lines
through the mini USB port.
Navigation Path
1. In the NE Explorer, select the desired NE from the Object Tree. Choose
Communication > SNMP Communication Parameters from the Function Tree.
Parameters
Parameter Value Range Default Value Description
Report Trap SNMPV1 SNMPV3 Set the Report Traps Version parameter
Version SNMPV2C based on the SNMP protocol version
running on the SNMP server.
SNMPV3
Navigation Path
Select the desired NE from the object tree in the NE Explorer and choose Configuration >
LLDP Configuration from the function tree.
Multicast Mode Nearest bridge Nearest bridge This parameter can only be set to Nearest
bridge.
Navigation Path
1. In the NE Explorer, select the desired NE from the Object Tree and choose Security >
NE RADIUS Configuration from the Function Tree.
2. Click New.
Parameters
Parameter Value Range Default Value Description
Navigation Path
1. In the NE Explorer, select the desired NE from the Object Tree and choose Security >
NE RADIUS Configuration from the Function Tree.
2. Click the RADIUS Server Configuration tab.
The RADIUS Server Information dialog box is displayed.
3. Click New.
Parameters
Parameter Value Range Default Value Description
Server Type RADIUS Server RADIUS Server Specifies the server type used for NE
Proxy Server RADIUS authentication.
l When an NE uses RADIUS
authentication in the NAS mode or
functions as a proxy server, set Server
Type to RADIUS Server.
l When an NE uses RADIUS
authentication in the proxy NAS mode,
set Server Type to Proxy Server.
Navigation Path
In the NE Explorer, select the desired NE from the Object Tree and choose Security > NE
RADIUS Configuration from the Function Tree.
Parameters
Parameter Value Range Default Value Description
Background Information
NOTE
OptiX RTN 905 does not support the creation of an IF N+1 protection group.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > N+1
Protection from the Function Tree.
2. Click Create.
WTR time(s) 300 to 720 600 l This parameter specifies the wait-to-
restore (WTR) time.
l When the time after the former
working channel is restored to normal
reaches the set WTR time, a revertive
switching occurs.
Protect Group Enhanced N+1 Standard N+1 l Only OptiX RTN 980L supports this
Type Standard N+1 parameter. Enhanced N+1 protection
can be configured for only shorthaul
microwave links or longhaul
microwave links on ISV3 boards
running in IS3 mode.
l Only OptiX RTN 980L and OptiX 980
using CSHNA boards support
enhanced N+1 protection.
l Standard N+1 protection is
implemented based on a load sharing
link aggregation group (LAG). The
number of TDM services carried by
each member link in a standard N+1
protection group must be the same.
l N+1 protection in enhanced mode is
implemented based on enhanced
physical link aggregation (EPLA). The
number of TDM services carried by
each member link in an enhanced N+1
protection group can be flexibly
configured.
Background Information
NOTE
OptiX RTN 905 does not support the configuration of IF N+1 protection.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > N+1
Protection from the Function Tree.
Protect Group Enhanced N+1 Standard N+1 l Only OptiX RTN 980L supports this
Type Standard N+1 parameter. Enhanced N+1 protection
can be configured for only shorthaul
microwave links or longhaul
microwave links on ISV3 boards
running in IS3 mode.
l Only OptiX RTN 980L and OptiX 980
using CSHNA boards support
enhanced N+1 protection.
l Standard N+1 protection is
implemented based on a load sharing
link aggregation group (LAG). The
number of TDM services carried by
each member link in a standard N+1
protection group must be the same.
l N+1 protection in enhanced mode is
implemented based on enhanced
physical link aggregation (EPLA). The
number of TDM services carried by
each member link in an enhanced N+1
protection group can be flexibly
configured.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1
Protection from the Function Tree.
2. Click Create.
Parameters
Parameter Value Range Default Value Description
Revertive Mode Revertive Mode Revertive Mode l This parameter specifies the
Non-Revertive revertive mode of the IF 1+1
protection.
l When Revertive Mode is set to
Revertive Mode, the NE that is in
the switching state releases the
switching and enables the former
working channel to return to the
normal state some time after the
former working channel is restored
to normal. It is recommended that
you set this parameter to Revertive
Mode.
l When Revertive Mode is set to
Non-Revertive, the NE that is in the
switching state keeps the current
state unchanged unless another
switching occurs even though the
former working channel is restored
to normal.
WTR Time(s) 300 to 720 600 l This parameter specifies the wait-to-
restore (WTR) time.
l When the time after the former
working channel is restored to
normal reaches the set WTR
Time(s), a revertive switching
occurs.
l You can set WTR Time(s) only
when Revertive Mode is set to
Revertive Mode. It is
recommended that you use the
default value.
Alarm Report Only board alarms Only board alarms l When Alarm Report Mode is set to
Mode Only protection group Only board alarms, only IF board
alarms alarms are reported.
Protection group and l When Alarm Report Mode is set to
board alarms Only protection group alarms,
protection group alarms are reported
if a protection group fails or
degrades. Service alarms on IF
boards and radio links are
suppressed.
l When Alarm Report Mode is set to
Protection group and board
alarms, IF board alarms and
protection group alarms are
reported.
l It is recommended that you set
Alarm Report Mode to Only
protection group alarms. In this
case, protection group alarms are
reported to indicate radio link faults.
NOTE
The faulty board reports related fault alarms
regardless of parameter settings.
NOTE
Each of the parameters Working Mode, Revertive Mode, WTR Time(s),Anti-jitter Time(s), and
Enable Reverse Switching must be set to the same value at both ends of a radio hop.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1
Protection from the Function Tree.
Alarm Report Only board alarms - l When Alarm Report Mode is set to
Mode Only Protection Only board alarms, only IF board
group alarms alarms are reported.
Protection group l When Alarm Report Mode is set to
and board alarms Only protection group alarms,
protection group alarms are reported if
a protection group fails or degrades.
Service alarms on IF boards and radio
links are suppressed.
l When Alarm Report Mode is set to
Protection group and board alarms,
IF board alarms and protection group
alarms are reported.
l It is recommended that you set Alarm
Report Mode to Only protection
group alarms. In this case, protection
group alarms are reported to indicate
radio link faults.
NOTE
The faulty board reports related fault alarms
regardless of parameter settings.
NOTE
Each of the parameters Working Mode, Revertive Mode, WTR Time(s), Anti-jitter Time (s), and
Enable Reverse Switching must be set to the same value at both ends of a radio hop.
Background Information
NOTE
l Only OptiX RTN 950 using CSHU/CSHUA boards, OptiX RTN 910A, and OptiX RTN 950 support
EPLA+.
l OptiX RTN 910A, OptiX RTN 905, OptiX RTN 950A, OptiX RTN 950 using CSHU/CSHUA boards,
and OptiX RTN 980 using CSHNA boards support EPLA.
Navigation Path
1. In the NE Explorer, select the desired NE from the Object Tree. Choose Configuration
> Physical Link Aggregation from the Function Tree.
2. Click New.
Parameters for Creating a PLA/EPLA Group (for OptiX RTN 905 1E/2E)
Parameter Value Range Default Value Description
Parameters for Creating a PLA/EPLA Group (for OptiX RTN 980L/OptiX RTN
980)
Parameter Value Range Default Value Description
Cascading Status Not Cascaded Not Cascaded This parameter specifies the cascading
status.
Scheduling Mode Mode A Mode A This parameter can be specified only when
Mode B PLA Type is S-EPLA.
l When Scheduling Mode is Mode B, In
hitless mode, E-band link bandwidth
changes do not affect the transmission
of high-priority services. In this mode,
high-priority services are transmitted on
common-band links, and low-priority
services are transmitted on E-band
links. However, if high-priority services
exceed the common-band link
bandwidth upon a burst, the excessive
traffic cannot be transmitted by E-band
links and is discarded.
l When Scheduling Mode is Mode A, In
common mode, high-priority and low-
priority services are distributed to
common-band and E-band links based
on their link bandwidths, implementing
inter-frequency AM.
Main Port Priority Auto Auto l This parameter specifies the priority for
Low a super EPLA group's member link.
This parameter generally takes the
High default value.
l This parameter can be specified only
when Scheduling Mode is Mode B.
Background Information
NOTE
l Only OptiX RTN 910A, OptiX RTN 950A using CSHU/CSHUA boards and OptiX RTN 950 support
EPLA+.
l OptiX RTN 910A, OptiX RTN 905, OptiX RTN 950A, OptiX RTN 950 using CSHU/CSHUA boards,
and OptiX RTN 980 using CSHNA boards support EPLA.
Navigation Path
1. In the NE Explorer, select the desired NE from the Object Tree and then choose
Configuration > Physical Link Aggregation from the Function Tree.
PLA/EPLA Parameters (for OptiX RTN 905 1E/2E,RTN 980 and RTN 980L)
Parameter Value Range Default Value Description
Hitless Switching Enabled Disabled Hitless EPLA switching can be enabled for
Disabled RTN 980L working as long-haul
microwave.
Main Port Priority Auto Auto l This parameter specifies the priority for
Low a super EPLA group's member link.
This parameter generally takes the
High default value.
l This parameter can be specified only
when Scheduling Mode is Mode B.
Navigation Path
1. In the NE Explorer, select the desired NE from the Object Tree. Choose Configuration
> Radio Link Configuration from the Function Tree.
Basic Parameters
Parameter Value Range Default Value Description
IF Parameters
Parameter Value Range Default Value Description
RF Parameters
Parameter Value Range Default Value Description
ATPC Upper - -45.0 l Set the central value between the ATPC
Threshold(dBm) upper threshold and the ATPC lower
threshold to the expected receive
ATPC Lower - -70.0 power.
Threshold(dBm)
l It is recommended that you set ATPC
Upper Threshold(dBm) to the sum of
the planned central value between the
ATPC upper threshold and the ATPC
lower threshold and 10 dB, and ATPC
Lower Threshold(dBm) to the
difference between the planned central
value between the ATPC upper
threshold and the ATPC lower
threshold and 10 dB.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear
MS from the Function Tree.
2. Click Create.
Protection Type 1+1 Protection 1+1 Protection l This parameter specifies the
1:N Protection protection type of the linear MSP
group.
l In the case of 1+1 linear MSP, one
working channel and one protection
channel are required. When the
working channel fails, the service is
switched from the working channel to
the protection channel.
l In the case of 1:N linear MSP, N
working channels and one protection
channel are required. Normal services
are transmitted on the working
channels and extra services are
transmitted on the protection channel.
When one working channel fails, the
services are switched from this
working channel to the protection
channel, and the extra services are
interrupted.
l If extra services need to be transmitted
or several working channels are
required, select 1:N Protection.
Revertive Mode Non-Revertive Non-Revertive (1+1 l This parameter specifies the revertive
Revertive Protection) mode of the linear MSP.
Revertive (1:N l When this parameter is set to
Protection) Revertive, the NE that is in the
switching state releases the switching
and enables the former working
channel to return to the normal state
some time after the former working
channel is restored to normal.
l When this parameter is set to Non-
Revertive, the NE that is in the
switching state keeps the current state
unchanged unless another switching
occurs even though the former
working channel is restored to normal.
l It is recommended that you set this
parameter to Revertive.
l If the linear MSP type is set to 1:N
Protection, Revertive Mode can be
set to Revertive only.
WTR Time(s) 300 to 720 600 l This parameter specifies the WTR
time.
l When the time after the former
working channel is restored to normal
reaches the preset WTR time, a
revertive switching occurs.
l You can set WTR Time(s) only when
Revertive Mode is set to Revertive.
l It is recommended that you use the
default value.
Protocol Type New Protocol New Protocol l The new protocol is more mature, and
Restructure the restructure protocol complies with
Protocol the standard. It is recommended that
you use the new protocol.
l You must ensure that the
interconnected NEs run the protocols
of the same type.
Select Mapping Direction West Working Unit West Working Unit This parameter
West Protection Unit specifies the
mapping direction of
the linear MSP.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear MS
from the Function Tree.
Navigation Path
1. In the NE Explorer, select an NE from the Object Tree and choose Configuration >
Packet-based linear MS from the Function Tree.
2. Click Create.
Protection Type 1:N Protection 1:N Protection Specifies the protection type of a packet-
based linear MSP group. Packet-based
linear MSP groups support only 1:1
protection.
Protocol Type New Protocol New Protocol l The new protocol is more mature, and
Restructure the restructured protocol complies with
Protocol the standard. It is recommended that
you use the new protocol.
l Ensure that the interconnected NEs run
the protocols of the same type.
SD/SF PRI Low priority Low priority l Specifies whether an SD/SF alarm is a
Switching Tag High priority high-priority or low-priority switching
condition. You can set the parameter
value manually.
l When this parameter is set to High
priority, bits 1 to 4 of the K1 byte uses
1101 to indicate a high-priority SF
switching request and 1011 to indicates
a high-priority SD switching request.
l When this parameter is set to Low
priority, bits 1 to 4 of the K1 byte uses
1100 to indicate a low-priority SF
switching request and 1010 to indicates
a low-priority SD switching request.
l It is recommended that you set this
parameter to the default value.
Select Mapping West Working Unit West Working Unit Specifies the mapping direction of the
Direction West Protection linear MSP. You can set the parameter
Unit value manually.
Navigation Path
In the NE Explorer, select an NE from the Object Tree and choose Configuration > Packet-
based linear MS from the Function Tree.
WTR Time(s) 300-720 - l Specifies the WTR time. You can set
the parameter value manually.
l When the time after the original
working channel is restored to normal
reaches the preset WTR time, a
revertive switching occurs.
l You can set WTR Time(s) only when
Revertive Mode is set to Revertive.
l It is recommended that you set this
parameter to the default value.
SD/SF PRI High priority Low priority l Specifies whether an SD/SF alarm is a
Switching Tag Low priority high-priority or low-priority switching
condition. You can set the parameter
value manually.
l When SD/SF PRI Switching Tag is set
to High priority, bits 1 to 4 of the K1
byte uses 1101 to indicate a high-
priority SF switching request and 1011
to indicates a high-priority SD
switching request.
l When SD/SF PRI Switching Tag is set
to Low priority, bits 1 to 4 of the K1
byte uses 1100 to indicate a low-
priority SF switching request and 1010
to indicates a low-priority SD
switching request.
l It is recommended that this parameter
take its default value.
Context
NOTE
Only OptiX RTN 980 and OptiX RTN 980L support the configuration of a ring MSP group.
Navigation Path
1. In the NE Explorer, select the required NE from the Object Tree and choose
Configuration > Ring MS from the Function Tree.
2. Click Create.
A dialog box is displayed, prompting for confirmation.
3. Click Yes.
WTR Time(s) 300-720 600 l Specifies the WTR time for the
local NE. After the working
channel recovers, services are
switched back from the protection
channel to the working channel
when the WTR time expires.
l Prevents frequent service
switches. The default value is
recommended.
Protocol Type New Protocol New Protocol l The new MSP protocol is
Restructure supported from an early stage,
Protocol and is still widely used.
l Compared with the new MSP
protocol, the restructure MSP
protocol is optimized and more
stable, incorporating better
protection measures.
l The new MSP protocol has higher
technology maturity than the
restructure MSP protocol, and
therefore is generally
recommended. The restructure
MSP protocol, however, features
higher standard compliance than
the new MSP protocol. Therefore,
the restructure MSP protocol is
used when the new MSP protocol
fails to support interconnection
between Huawei RTN equipment
and third-party equipment.
l Two interconnected NEs must use
the same MSP protocol type.
Select Mapping West Line 1 West Line 1 Specifies the mapping direction of a
Direction East Line 1 member in a ring MSP protection group.
Context
NOTE
Only OptiX RTN 980 and OptiX RTN 980L support the configuration of a ring MSP group.
Navigation Path
In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
Ring MS from the Function Tree.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
SDH/PDH Service Management from the Function Tree.
2. Click Options to change the VC-12 timeslot numbering policy used by the cross-
connection.
3. Click Create.
Parameters
Parameter Value Range Default Value Description
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
SDH/PDH Service Management from the Function Tree.
2. Click Options to change the VC-12 timeslot numbering policy used by the cross-
connection.
3. Click Create SNCP Service.
Service Type SNCP SNCP This parameter indicates that the type of
the service to be created is SNCP.
WTR Time(s) 300 to 720 600 l This parameter specifies the WTR time.
l When the time after the original
working channel is restored to normal
reaches the preset WTR time, a
revertive switching occurs.
l You can set WTR Time(s) only when
Revertive Mode is set to Revertive.
l It is recommended that you use the
default value.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
SDH/PDH Service Configuration from the Function Tree.
2. Optional: If a bidirectional SDH service is created, select this service in Cross-
Connection. Right-click the selected service and choose Expand to Unidirectional
from the shortcut menu.
3. Select the unidirectional service. Right-click the selected service and choose Convert to
SNCP Service from the shortcut menu.
Service Type SNCP SNCP This parameter indicates that the type of
the service to be created is SNCP.
WTR Time(s) 300 to 720 600 l This parameter specifies the WTR time.
l When the time after the original
working channel is restored to normal
reaches the preset WTR time, a
revertive switching occurs.
l You can set WTR Time(s) only when
Revertive Mode is set to Revertive.
l It is recommended that you use the
default value.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH/PDH
Service Management from the Function Tree.
Cross-Connection Parameters
Parameter Value Range Def Description
ault
Val
ue
Source Slot - - This parameter indicates the slot of the service source.
Source Timeslot/ - - This parameter indicates the timeslot or timeslot range of the
Path service source.
Sink Slot - - This parameter indicates the slot of the source sink.
Sink Timeslot/ - - This parameter indicates the timeslot or timeslot range of the
Path service sink.
Bound Group - - OptiX RTN 900 does not support this parameter.
Number
Lockout Status - - OptiX RTN 900 does not support this parameter.
Trail Name - - OptiX RTN 900 does not support this parameter.
Schedule No. - - OptiX RTN 900 does not support this parameter.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SNCP
Service Control from the Function Tree.
Background Information
NOTE
when Integrated IP microwave links construct an E1 SNCP ring together with SDH microwave links provided
by ISV3 boards, or SDH optical lines, an E1_AIS needs to be converted to a TU_AIS on the IF boards that
construct the Integrated IP microwave links.
Navigation Path
In the NE Explorer, select the IF board from the Object Tree and choose Alarm > Triggered
Alarm Insertion from the Function Tree.
Background Information
NOTE
l For OptiX RTN 905 housing an MN1 board, you can set Service Mode for ports on the logical board
MP1/VS2/CD1 to TDM or Packet.
l For OptiX RTN 950A housing an MN1 board, you can set Service Mode for ports on the logical board
MP1/CD1 to TDM or Packet.
Navigation Path
In the NE Explorer, select the MP1 logical board from the Object Tree and then choose
Configuration > Port Mode Configuration from the Function Tree.
Navigation Path
1. In the NE Explorer, select the NE from the Object Tree and choose Configuration >
Interface Management > PDH Interface from the Function Tree.
Before changing Port Mode for a port enabled with inband DCN, disable inband DCN.
Navigation Path
1. In the NE Explorer, select the desired NE from the Object Tree and choose
Configuration > Interface Management > PDH Interface from the Function Tree.
2. Click the Advanced Attributes tab.
Before changing Frame Format and Frame Mode for a port enabled with inband DCN, disable inband
DCN.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Interface Management > Ethernet Interface from the Function Tree.
2. Click the Basic Attributes tab.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Interface Management > Ethernet Interface from the Function Tree.
2. Click the Flow Control tab.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Interface Management > Ethernet Interface from the Function Tree.
2. Click the Layer 2 Attributes tab.
Navigation Path
1. In the NE Explorer, select the NE from the Object Tree and choose Configuration >
Interface Management > Ethernet Interface from the Function Tree.
2. Click the Layer 3 Attributes tab.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Interface Management > Ethernet Interface from the Function Tree.
2. Click the Advanced Attributes tab.
this
parameter to
Enabled;
otherwise, set
this
parameter to
Disabled.
l Only the PoE
port on OptiX
RTN 905 2E
supports
auto-
negotiation.
l OptiX RTN
905 1E does
not support
this
parameter.
Navigation Path
1. In the NE Explorer, select the required NE from the Object Tree and choose
Configuration > Interface Management > Serial Interface from the Function Tree.
2. Click the Basic Attributes tab.
Navigation Path
1. In the NE Explorer, select the required NE from the Object Tree and choose
Configuration > Interface Management > Serial Interface from the Function Tree.
2. Click the New tab.
Navigation Path
1. In the NE Explorer, select a channelized STM-1 interface board from the Object Tree
and choose Configuration > Clock Transparent Transmission > Clock Transparent
Transmission.
Navigation Path
1. In the NE Explorer, select a channelized STM-1 interface board from the Object Tree
and choose Configuration > Interface Management > Path Configuration from the
Function Tree.
Parameters in the Window for Configuring Paths over Channelized STM-1 Ports
NOTE
Before changing VC12 Frame Format and Frame Mode for a port enabled with inband DCN, disable
inband DCN.
Background Information
NOTE
The maximum frame length (MFL) is invalid for L3VPN services.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Interface Management > Microwave Interface from the Function Tree.
2. Click the Basic Attributes tab.
Parameters
Parameter Value Range Default Value Description
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Interface Management > Microwave Interface from the Function Tree.
2. Click the Layer 2 Attributes tab.
Tag Tag Aware Tag Aware l If all the accessed services are frames
Access that contain the VLAN tag (tagged
frames), set Tag to "Tag Aware".
Hybrid
l If all the accessed services are frames
that do not contain the VLAN tag
(untagged frames), set Tag to "Access".
l If the accessed services contain tagged
frames and untagged frames, set Tag to
"Hybrid".
NOTE
Tag specifies the TAG flag of a port. For details
about the TAG flags and associated frame-
processing methods, see Table B-2.
Ingress Port Tagged frame The port receives The port discards The port receives
the frame. the frame. the frame.
Untagged frame The port discards The port receives The port receives
the frame. the frame after the the frame after the
VLAN tag that VLAN tag that
corresponds to corresponds to
"Default VLAN "Default VLAN
ID" and "VLAN ID" and "VLAN
Priority" is added to Priority" is added to
the frame. the frame.
Egress Port Tagged frame The port transmits The port strips the l If the VLAN ID
the frame. VLAN tag from the in the frame is
frame and then "Default VLAN
transmits the frame. ID", the port
strips the VLAN
tag from the
frame and then
transmits the
frame.
l If the VLAN ID
in the frame is
not "Default
VLAN ID", the
port directly
transmits the
frame.
Navigation Path
1. In the NE Explorer, select the required NE from the Object Tree and choose
Configuration > Interface Management > Microwave Interface from the Function
Tree.
2. Click the Layer 3 Attributes tab.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Interface Management > Microwave Interface from the Function Tree.
Navigation Path
l Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > IF Interface from the Function Tree.
l Click the IF Attributes tab.
Parameters
Parameter Value Range Default Value Description
Alarm and Enabled Enabled RTN 905, RTN 910A, and ISV3/ISM6
Performance Disabled boards on RTN 980/RTN 980L/RTN
Report 950/RTN 950A allow Alarm and
Performance Report to be specified. If
Alarm and Performance Report is set to
Disabled, alarms of IF ports and the
corresponding ODUs/RFUs are not
reported.
NOTE
For RTN 950/980, the IF1 boards support setting of Radio Working Mode but does not support setting of IF
Service Type, XPIC Enabled, Enable IEEE-1588 Timeslot, and Running Mode.
For RTN 950/980, the IF1 board does not support Hybrid/AM configuration.
Navigation Path
l Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > IF Interface from the Function Tree.
l Click the ATPC Attributes tab.
Parameters
Parameter Value Range Default Value Description
ATPC Upper - -45.0 l Set the central value between the ATPC
Threshold(dBm) upper threshold and the ATPC lower
threshold to a value for the expected
receive power.
Navigation Path
l In the NE Explorer, select the IF board, and then choose Configuration > IF Interface
from the Function Tree.
l Click the AM Advanced Attributes tab.
Parameters
Parameter Value Range Default Value Description
Navigation Path
Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > ATPC Adjustment Records from the Function Tree.
Parameters
Parameter Value Range Default Value Description
Parameters
Parameter Value Range Default Value Description
Parameters
Parameter Value Range Default Value Description
Parameters
Parameter Value Range Default Value Description
Parameters
Parameter Value Range Default Value Description
Navigation Path
1. Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > Interface Management > SDH Interface from the Function Tree.
2. Select By Board/Port(Channel), and select Port or VC4 Channel from the list box.
Parameters
Parameter Value Range Default Value Description
NOTE
l a: Indicates the parameters that are supported when Port is selected from the list box.
l b: Indicates the parameters that are supported when VC4 Channel is selected from the list box.
Navigation Path
Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > Automatic Laser Shutdown from the Function Tree.
Parameters
Parameter Value Range Default Value Description
Off Period(ms) 2000 to 300000 60000 This parameter indicates or specifies the
period when the laser does not work (with
the ALS function being enabled).
Continuously On- 2000 to 300000 90000 This parameter indicates or specifies the
test Period(ms) period when a shutdown laser is manually
started up and tests whether the optical
fiber is normal.
Navigation Path
1. Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > PDH Interface from the Function Tree.
2. Select By Board/Port(Channel).
3. Select Port from the list box.
Parameters
Parameter Value Range Default Value Description
E1 Frame Format Unframe Unframe Specifies the E1 frame format for E1 ports.
Double Frame l To detect E1 BER performance on an
CRC-4 Multiframe OptiX RTN 900, set E1 Frame Format
of the local E1 port to the same value as
that of the opposite E1 port. It is
recommended that E1 Frame Format
of both the local and opposite E1 ports
be CRC-4 Multiframe.
l In other scenarios wherein an OptiX
RTN 900 is used, it is recommended
that E1 Frame Format take its default
value Unframe. If E1 Frame Format
is Unframe, the OptiX RTN 900
transparently transmits E1 frames and
the local E1 port allows for
interconnection with another E1 port
whose E1 Frame Format is Double
Frame or CRC-4 Multiframe.
NOTE
E1 Frame Format needs to be set to the same
value at both ends of an E1 link.
Navigation Path
1. Select an SDH interface board in the NE Explorer Choose Configuration > Overhead
Management > Regenerator Section Overhead from the Function Tree.
2. Choose Display in Text Format or Display in Hexadecimal.
Display in Text Selected Selected This parameter specifies the display in the
Format Deselected text format.
Navigation Path
1. Select SDH interface board from the Object Tree in the NE Explorer. Choose
Configuration > Overhead Management > VC4 Path Overhead from the Function
Tree.
2. Choose Display in Text Format or Display in Hexadecimal.
Display in Text Selected Selected This parameter specifies the display in the
Format Deselected text format.
Navigation Path
1. Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > Overhead Management > VC12 Path Overhead from the Function
Tree.
2. Choose Display in Text Format or Display in Hexadecimal.
Display in Text Selected Selected This parameter specifies the display in the
Format Deselected text format.
Navigation Path
1. In the NE Explorer, select the desired NE from the Object Tree and choose
Configuration > Interface Management > Ethernet Virtual Interface from the
Function Tree.
Layer 3 Attributes
Parameter Value Range Default Value Description
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Ethernet Service Management > E-Line Service from the Function Tree.
2. Click New.
Bearer Type 1 QinQ Link QinQ Link Uses the QinQ link to
carry the E-Line service.
Bearer Type 2 QinQ Link QinQ Link Uses the QinQ link to
carry the E-Line service.
Parameters of PWs
NOTE
l Parameters of PWs need to be configured only when Direction is UNI-NNI and Bearer Type is PW.
l If the parameter Protection Type of PWs is set to PW APS or Slave Protection Pair, all the parameters
of working and protection PWs need to be configured. This section considers the parameters of the
working PW as an example.
QoS parameters need to be configured only when Direction is UNI-NNI and Bearer Type is PW.
The parameters of the PW APS protection group need to be configured if the Protection Type of PWs is set
to PW APS.
OAM Parameters
NOTE
l The OAM parameters of the PW APS protection group need to be configured if the Protection Type of
PWs is set to PW APS.
l To configure PW OAM parameters, choose Configuration > MPLS Management > PW Management
> PW OAM Parameter from the Function Tree.
The parameters of the PW APS protection group need to be configured if the Protection Type of PWs is set
to Slave Protection Pair.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Ethernet Service Management > E-Line Service from the Function Tree.
2. Click Create.
Parameters on the Main Interface (Configuring the Source and Sink Ports)
Bearer Type QinQ Link QinQ Link Uses the QinQ link to
carry the E-Line service.
Parameters of PWs
NOTE
l Parameters of PWs need to be configured only when Direction is UNI-NNI and Bearer Type is PW.
l If the parameter Protection Type of PWs is set to PW APS or Slave Protection Pair, all the parameters
of working and protection PWs need to be configured. This section considers the parameters of the
working PW as an example.
The parameters of the PW APS protection group need to be configured if the Protection Type of PWs is set
to PW APS.
OAM Parameters
NOTE
l The OAM parameters of the PW APS protection group need to be configured if the Protection Type of
PWs is set to PW APS.
l To configure PW OAM parameters, choose Configuration > MPLS Management > PW Management
> PW OAM Parameter from the Function Tree.
The parameters of the PW APS protection group need to be configured if the Protection Type of PWs is set
to Slave Protection Pair.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Service Management > E-Line Service from the Function Tree.
QoS Parameters
Parameter Value Range Default Value Description
The following parameters are available only after the PW APS protection group is configured.
The following parameters are available only after the slave protection pair is configured.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Ethernet Service Management > E-Line Service from the Function Tree.
2. Click the VLAN Forwarding Table Item tab.
3. Click New.
NOTE
l The VLAN ID of the UNI-UNI E-Line service can be converted after a VLAN forwarding table item is
created. In this case, a service from Source Interface to Sink Interface carries the VLAN ID specified in
Sink VLAN ID when the service is transmitted from Sink Interface.
l The VLAN ID in a VLAN forwarding table item is converted unidirectionally and can be converted from
Source VLAN ID to Sink VLAN ID only. The VLAN ID can be converted bidirectionally only when the
other VLAN forwarding table item is configured reversely.
l In normal cases, Ethernet services are bidirectional. Hence, you need to set bidirectional conversion of
VLAN IDs.
Navigation Path
1. In the NE Explorer, select the NE from the Object Tree. Choose Configuration >
Ethernet Service Management > E-LAN Service from the Function Tree.
2. Click New.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Ethernet Service Management > E-LAN Service from the Function Tree.
2. Click New.
Parameters on the Main Interface (Configuring the Source and Sink Ports)
Parameter Value Range Default Value Description
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Service Management > E-LAN Service from the Function Tree.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Service Management > E-LAN Service from the Function Tree.
Port Parameters
Parameter Value Range Default Value Description
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Ethernet Service Management > QinQ Link from the Function Tree.
2. Click New.
Navigation Path
1. In the NE Explorer, select the desired NE from the Object Tree and choose
Configuration > Ethernet Service Management > E-AGGR Service from the
Function Tree.
2. Click New.
UNI Parameters
Parameter Value Range Default Value Description
Control Channel Type Alert Label Alert Label This parameter specifies
None the control channel type,
which determines the PW
CW continuity check (CC)
mode.
l None: indicates that
virtual circuit
connectivity
verification (VCCV)
packets are not used.
l Alert Label: indicates
that VCCV packets in
Alert Label
encapsulation mode
are used.
l CW: indicates that
VCCV packets
encapsulated based on
the control word are
used.
NOTE
l Regardless of whether VLAN ID swapping is required by an E-AGGR service, a VLAN forwarding table
needs to be configured, specifying the source and sink VLAN IDs of each VLAN-based service.
l A VLAN forwarding table enables VLAN ID swapping for an E-AGGR service. After a VLAN
forwarding table is created, a service from Source Interface will carry the VLAN ID specified in Sink
VLAN ID when leaving Sink Interface.
l For an E-AGGR service, the VLAN forwarding table specifies bidirectional VLAN ID swapping
relationships. This means that swapping from Sink VLAN ID to Source VLAN ID and swapping from
Source VLAN ID to Sink VLAN ID will be implemented once a VLAN forwarding entry for changing
Source VLAN ID to Sink VLAN ID is configured.
l For service aggregation from UNI ports to an NNI port, Source VLAN ID must take any of the VLAN
IDs that have been configured for UNI ports.
l For service aggregation from NNI ports to a UNI port, Sink VLAN ID must take any of the VLAN IDs
that have been configured for UNI ports.
QoS (PW)
Parameter Value Range Default Value Description
Navigation Path
1. In the NE Explorer, select the desired NE from the Object Tree and choose
Configuration > Ethernet Service Management > E-AGGR Service from the
Function Tree.
UNI Parameters
Parameter Value Range Default Value Description
NOTE
l Regardless of whether VLAN ID swapping is required by an E-AGGR service, a VLAN forwarding table
needs to be configured, specifying the source and sink VLAN IDs of each VLAN-based service.
l A VLAN forwarding table enables VLAN ID swapping for an E-AGGR service. After a VLAN
forwarding table is created, a service from Source Interface will carry the VLAN ID specified in Sink
VLAN ID when leaving Sink Interface.
l For an E-AGGR service, the VLAN forwarding table specifies bidirectional VLAN ID swapping
relationships. This means that swapping from Sink VLAN ID to Source VLAN ID and swapping from
Source VLAN ID to Sink VLAN ID will be implemented once a VLAN forwarding entry for changing
Source VLAN ID to Sink VLAN ID is configured.
l For service aggregation from UNI ports to an NNI port, Source VLAN ID must take any of the VLAN
IDs that have been configured for UNI ports.
l For service aggregation from NNI ports to a UNI port, Sink VLAN ID must take any of the VLAN IDs
that have been configured for UNI ports.
QoS (PW)
Parameter Value Range Default Value Description
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Ethernet Protection > ERPS Management.
2. Click New.
Parameters
Parameter Value Range Default Value Description
ERP Ring Node Flag None None l If the node is the RPL owner,
RPL Port set this parameter to RPL
Port.
Neighbor Port
l If the node is an RPL
Next Neighbor Port neighbor node, set this
parameter to Neighbor Port.
l If the node is the next-hop
node of the RPL owner or
RPL neighbor node, set this
parameter to Next Neighbor
Port.
l Only one node on the ring
can be set as the RPL owner
or RPL neighbor node for
each Ethernet ring.
l If the node on the ring is not
any of the preceding nodes,
set this parameter to None.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protection > ERPS Management from the Function Tree.
Parameters
Parameter Value Range Default Value Description
the same as or
different from the
fault that triggers
the initial startup
of the hold-off
timer.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Ethernet Protocol Configuration > MSTP Configuration from the Function Tree.
2. Click the Port Group Parameters tab.
3. Click Create.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Ethernet Protocol Configuration > MSTP Configuration from the Function Tree.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Ethernet Protocol Configuration > MSTP Configuration from the Function Tree.
2. Click the Bridge Parameters tab.
Bridge Parameters
Parameter Value Range Default Value Description
Port Parameters
Parameter Value Range Default Value Description
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Ethernet Protocol Configuration > MSTP Configuration from the Function Tree.
2. Click the CIST&MSTI Parameters tab.
Port Parameters
Parameter Value Range Default Value Description
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Ethernet Protocol Configuration > MSTP Configuration from the Function Tree.
2. Click the CIST Running Information tab.
Port Parameters
Parameter Value Range Default Value Description
Background Information
OptiX RTN 950 housing CSHU/CSHUA and OptiX RTN 950A do not support this operation.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Ethernet Protocol Configuration > IGMP Snooping Configuration from the Function
Tree.
2. Click the Protocol Configuration tab.
Background Information
OptiX RTN 950 housing CSHU/CSHUA and OptiX RTN 950A do not support this operation.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Ethernet Protocol Configuration > IGMP Snooping Configuration from the Function
Tree.
2. Click the Protocol Config tab.
3. Click Add.
Background Information
OptiX RTN 950 housing CSHU/CSHUA and OptiX RTN 950A do not support this operation.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Ethernet Protocol Configuration > IGMP Snooping Configuration from the Function
Tree.
2. Click the Router Port Management tab.
Background Information
OptiX RTN 950 housing CSHU/CSHUA and OptiX RTN 950A do not support this operation.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Ethernet Protocol Configuration > IGMP Snooping Configuration from the Function
Tree.
2. Click the Route Management tab.
3. Click New.
Background Information
OptiX RTN 950 housing CSHU/CSHUA and OptiX RTN 950A do not support this operation.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Ethernet Protocol Configuration > IGMP Snooping Configuration from the Function
Tree.
2. Click the Route Member Port Management tab.
Background Information
OptiX RTN 950 housing CSHU/CSHUA and OptiX RTN 950A do not support this operation.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Ethernet Protocol Configuration > IGMP Snooping Configuration from the Function
Tree.
2. Click the Route Member Port Management tab.
3. Click New.
Background Information
OptiX RTN 950 housing CSHU/CSHUA and OptiX RTN 950A do not support this operation.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Ethernet Protocol Configuration > IGMP Snooping Configuration from the Function
Tree.
2. Click the Data Count tab.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Interface Management > Link Aggregation Group Management from the Function
Tree.
2. Click the Link Aggregation Group Management tab.
3. Click New.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Interface Management > Link Aggregation Group Management from the Function
Tree.
2. Click the Link Aggregation Parameters tab.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT
Management > Simple LPT from the Function Tree.
2. Click New.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT
Management > LPT from the Function Tree.
2. Click the Point-to-Point LPT tab.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT
Management > LPT from the Function Tree.
2. Click the Point-to-Point LPT tab.
3. Click Bind in the lower right corner of the pane based on the type of service network.
4. Choose PW+QinQ or L2 net from the shortcut menu based on the type of service
network.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT
Management > LPT from the Function Tree.
2. Click the Point-to-Multipoint LPT tab.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT
Management > LPT from the Function Tree.
2. Click the Point-to-Multipoint LPT tab.
3. Click New in the lower right corner of the pane based on the type of service network.
4. Choose PW, QinQ, or L2 net from the shortcut menu based on the type of service
network.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Ethernet OAM Management > Ethernet Service OAM Management from the
Function Tree.
2. Click the Maintenance Association tab.
3. Choose New > New Maintenance Domain.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Ethernet OAM Management > Ethernet Service OAM Management from the
Function Tree.
2. Click the Maintenance Association tab.
3. Select the maintenance domain in which a maintenance association needs to be created.
Choose New > New Maintenance Association.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Ethernet OAM Management > Ethernet Service OAM Management from the
Function Tree.
2. Click the Maintenance Association tab.
3. Select the maintenance association in which an MEP needs to be created. Choose New >
New MEP Point.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Ethernet OAM Management > Ethernet Service OAM Management from the
Function Tree.
2. Click the Maintenance Association tab.
3. Choose OAM > Manage Remote MEP Point. The Manage Remote MEP Point dialog
box is displayed.
4. Click New.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Ethernet OAM Management > Ethernet Service OAM Management from the
Function Tree.
2. Click the MIP Point tab.
3. Select the maintenance domain in which an MIP needs to be created, and then click
New.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Ethernet OAM Management > Ethernet Service OAM Management from the
Function Tree.
2. Click the Maintenance Association tab.
3. Select the maintenance domain and maintenance association for the LB test.
4. Choose OAM > Start LB.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Ethernet OAM Management > Ethernet Service OAM Management from the
Function Tree.
2. Click the Maintenance Association tab.
3. Select the maintenance domain and maintenance association for the LT test.
4. Choose OAM > Start LT.
Navigation Path
1. In the NE Explorer, select the desired NE and choose Configuration > Ethernet
Service Management > E-LAN Service from the Function Tree.
2. Click Manual Loopback Detection tab.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Ethernet OAM Management > Ethernet Port OAM Management from the Function
Tree.
2. Click the OAM Parameter tab.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Ethernet OAM Management > Ethernet Port OAM Management from the Function
Tree.
2. Click the OAM Error Frame Monitor tab.
Error Frame 1000 to 60000, in 1000 This parameter specifies the duration of
Monitor step of 100 monitoring error frames.
Window(ms)
Error Frame 1488 to 892800000, 892800000 This parameter specifies the window of
Period in step of 1 monitoring the error frame period.
Window(frame)
Error Frame 10 to 900, in step of 60 This parameter specifies the time window
Second Window(s) 1 of monitoring the error frame second.
Navigation Path
1. In the NE Explorer, select the desired NE from the Object Tree. Choose Configuration
> Ethernet OAM Management > Ethernet Service OAM Management from the
Function Tree.
2. Specify Maintenance Domain Name, Maintenance Association Name, and MEP
Point according to the data plan.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Diffserv Domain Management > Diffserv Domain Management from the
Function Tree.
NOTE
If one default DS domain exists on the OptiX RTN 900 equipment, Mapping Relation ID is set to 1, and
Mapping Relation Name is set to Default Map. If these parameters are not set, all the ports belong to this
domain.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Diffserv Domain Management > Diffserv Domain Management
from the Function Tree.
2. Click New.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Diffserv Domain Management > Diffserv Domain Management
from the Function Tree.
2. Select the DS domain to be changed in the main interface.
3. Click the Apply Port tab.
4. Click Modify.
NOTE
If one default DS domain exists on the OptiX RTN 900, Mapping Relation ID is set to 1, and Mapping
Relation Name is set to Default Map. If these parameters are not set, all the ports belong to this domain.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Policy Management > Port Policy from the Function Tree.
2. Click the CoS Configuration tab.
Parameters
Parameter Value Range Default Value Description
Grooming Police After SP CS7, CS6, EF, BE: SP l The strict priority
Reloading WRR AF4, AF3, AF2, AF1: (SP) scheduling
WRR algorithm is designed
for the key services.
One important
characteristic of the
key services is that
higher priorities are
required to minimize
the response delay in
the case of congestion
events.
l The weighted round
robin (WRR)
scheduling algorithm
divides each port into
multiple output sub-
queues. The polling
scheduling is
performed among the
output sub-queues to
ensure that each sub-
queue has a certain
period of service time.
l The OptiX RTN 900
supports the setting of
the SP+WRR
scheduling algorithm
of the CoS queue
according to the
requirement, and
provides one or more
queues that comply
with the SP algorithm.
Except for the default
value, however, the
value of the WRR
scheduling algorithm
and the value of the
SP scheduling
algorithm cannot be
interleaved. That is,
except for the default
value, Grooming
Police After
Reloading can be
changed from SP to
WRR according to
the queue priorities in
a descending order
(CS7-BE).
l This parameter is set
according to the
planning information.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Policy Management > Port Policy from the Function Tree.
2. Click New. The Create Port Policy dialog box is displayed.
3. Click the CoS Configuration tab.
Parameters
Parameter Value Range Default Value Description
respectively, the
actual bandwidth
allocation weight of
each queue will be
recalculated based
on the proportion
between the set
WRR weight
(1:1:1:1). That is,
each queue is
allocated with 25%
total bandwidth.
Grooming Police After SP CS7, CS6, EF, BE: SP l The strict priority
Reloading WRR AF4, AF3, AF2, AF1: (SP) scheduling
WRR algorithm is
designed for the
key services. One
important
characteristic of the
key services is that
higher priorities are
required to
minimize the
response delay in
the case of
congestion events.
l The weighted round
robin (WRR)
scheduling
algorithm divides
each port into
multiple output sub-
queues. The polling
scheduling is
performed among
the output sub-
queues to ensure
that each sub-queue
has a certain period
of service time.
l The OptiX RTN
900 supports the
setting of the SP
+WRR scheduling
algorithm of the
CoS queue
according to the
requirement, and
provides one or
more queues that
comply with the SP
algorithm. Except
for the default
value, however, the
value of the WRR
scheduling
algorithm and the
value of the SP
scheduling
algorithm cannot be
interleaved. That is,
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Policy Management > Port Policy from the Function Tree.
2. Click the Traffic Classification Configuration tab.
3. Click New.
Ingress Parameters
Parameter Value Range Default Value Description
Egress Parameters
Parameter Value Range Default Value Description
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Port Shaping Management from the Function Tree.
2. Click New.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Policy Management > Port WRED Policy from the Function Tree.
2. Click New.
Parameters
Parameter Value Range Default Value Description
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Policy Management > Service WRED Policy from the Function Tree.
2. Click New.
Parameters
Parameter Value Range Default Value Description
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Policy Management > WRR Scheduling Policy from the Function
Tree.
2. Click New.
Parameters
Parameter Value Range Def Description
ault
Val
ue
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Policy Management > V-UNI Egress Policy from the Function Tree.
2. Click New. The Create V-UNI Egress Policy dialog box is displayed.
Parameters
Parameter Value Range Default Value Description
respectively, the
actual bandwidth
allocation weight of
each queue will be
recalculated based
on the proportion
between the set
WRR weight
(1:1:1:1). That is,
each queue is
allocated with 25%
total bandwidth.
Grooming Police After SP CS7, CS6, EF, BE: SP l The strict priority
Reloading WRR AF4, AF3, AF2, AF1: (SP) scheduling
WRR algorithm is
designed for the
key services. One
important
characteristic of the
key services is that
higher priorities are
required to
minimize the
response delay in
the case of
congestion events.
l The weighted round
robin (WRR)
scheduling
algorithm divides
each port into
multiple output sub-
queues. The polling
scheduling is
performed among
the output sub-
queues to ensure
that each sub-queue
has a certain period
of service time.
l The OptiX RTN
900 supports the
setting of the SP
+WRR scheduling
algorithm of the
CoS queue
according to the
requirement, and
provides one or
more queues that
comply with the SP
algorithm. Except
for the default
value, however, the
value of the WRR
scheduling
algorithm and the
value of the SP
scheduling
algorithm cannot be
interleaved. That is,
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Policy Management > PW Policy from the Function Tree.
2. Click New. The Create PW Policy dialog box is displayed.
Parameters
Parameter Value Range Default Value Description
respectively, the
actual bandwidth
allocation weight of
each queue will be
recalculated based
on the proportion
between the set
WRR weight
(1:1:1:1). That is,
each queue is
allocated with 25%
total bandwidth.
Grooming Police After SP CS7, CS6, EF, BE: SP l The strict priority
Reloading WRR AF4, AF3, AF2, AF1: (SP) scheduling
WRR algorithm is
designed for the
key services. One
important
characteristic of the
key services is that
higher priorities are
required to
minimize the
response delay in
the case of
congestion events.
l The weighted round
robin (WRR)
scheduling
algorithm divides
each port into
multiple output sub-
queues. The polling
scheduling is
performed among
the output sub-
queues to ensure
that each sub-queue
has a certain period
of service time.
l The OptiX RTN
900 supports the
setting of the SP
+WRR scheduling
algorithm of the
CoS queue
according to the
requirement, and
provides one or
more queues that
comply with the SP
algorithm. Except
for the default
value, however, the
value of the WRR
scheduling
algorithm and the
value of the SP
scheduling
algorithm cannot be
interleaved. That is,
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Policy Management > QinQ Policy from the Function Tree.
2. Click New. The Create QinQ Policy dialog box is displayed.
Parameters
Parameter Value Range Default Value Description
respectively, the
actual bandwidth
allocation weight of
each queue will be
recalculated based
on the proportion
between the set
WRR weight
(1:1:1:1). That is,
each queue is
allocated with 25%
total bandwidth.
Grooming Police After SP CS7, CS6, EF, BE: SP l The strict priority
Reloading WRR AF4, AF3, AF2, AF1: (SP) scheduling
WRR algorithm is
designed for the
key services. One
important
characteristic of the
key services is that
higher priorities are
required to
minimize the
response delay in
the case of
congestion events.
l The weighted round
robin (WRR)
scheduling
algorithm divides
each port into
multiple output sub-
queues. The polling
scheduling is
performed among
the output sub-
queues to ensure
that each sub-queue
has a certain period
of service time.
l The OptiX RTN
900 supports the
setting of the SP
+WRR scheduling
algorithm of the
CoS queue
according to the
requirement, and
provides one or
more queues that
comply with the SP
algorithm. Except
for the default
value, however, the
value of the WRR
scheduling
algorithm and the
value of the SP
scheduling
algorithm cannot be
interleaved. That is,
Navigation Path
Click a desired NE in the NE Explorer and choose Diagnose&Maintenance > IP Packet
Marking from the main menu.
Set IP mark bits l IP FLAG BIT0 IP FLAG BIT0 Set the flag bit of the
l IP TOS BIT3 marked packets, which is
used to count the packets.
l IP TOS BIT4
l IP TOS BIT5
l IP TOS BIT6
l IP TOS BIT7
NOTE
OptiX RTN 905/910A does not support the Ethernet services on EoS/EoPDH boards.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Service > Ethernet Line Service from the Function Tree.
2. Deselect Display QinQ Shared Service.
3. Click New.
Service Type EPL EPL Specify the Ethernet service type to EPL.
Port Enabled Enabled - l When the source port or the sink port is
Disabled set to a PORT, set Port Enabled to
Enabled.
l This parameter need not be set when
the source port or sink port is a
VCTRUNK.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board, and choose Configuration >
Ethernet Service > Ethernet Line Service from the Function Tree.
2. Select Display QinQ Shared Service.
3. Click New.
Bidirectional
.
VL
AN
and
tran
spa
rent
ly
tran
smi
t C-
VL
AN
l Stri
p
S-
VL
AN
a non-null
value, only
the services
of the source
port whose
VLAN IDs
are included
in the value
range of this
parameter
work as the
service
source.
value, only
the services
of the sink
port whose
VLAN IDs
are included
in the value
range of this
parameter
work as the
service sink.
Navigation Path
In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Service > Ethernet Line Service from the Function Tree.
Table B-24 Parameters on the main interface (Display QinQ Shared Service is not selected)
Parameter Value Range Default Value Description
Table B-25 Parameters on the main interface (Display QinQ Shared Service is selected)
Parameter Value Range Default Value Description
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree.
2. Click New.
Bridge Switch l IVL/Ingress l IVL/Ingress l When the bridge uses the SVL mode,
Mode Filter Enable Filter Enable all the VLANs share one MAC address
(supported by (IEEE 802.1q table. When the bridge uses the IVL
the IEEE 802.1q bridge and the mode, each VLAN has an MAC
bridge and IEEE IEEE 802.1ad address table.
802.1ad bridge, bridge) l When the filtering function is enabled
unsupported by l SVL/Ingress at the ingress port, the ingress port
the IEEE 802.1d Filter Disable checks the VLAN tags of all incoming
bridge) (IEEE 802.1d packets. If the VLAN ID contained in
l SVL/Ingress bridge) the VLAN tag of a packet is not
Filter Disable included in the VLAN filtering table,
(supported by the packet is discarded. When the
the IEEE 802.1d filtering function is disabled at the
bridge and IEEE ingress port, the ingress port does not
802.1ad bridge, check any VLAN tag of the incoming
unsupported by packets.
the IEEE 802.1q
bridge)
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board, and then choose Configuration >
Ethernet Service > Ethernet LAN Service from the Function Tree.
2. Click New.
Bridge Switch l IVL/Ingress l IVL/Ingress l When the bridge uses the SVL mode,
Mode Filter Enable Filter Enable all the VLANs share one MAC address
(supported by (the 802.1q table. When the bridge uses the IVL
the 802.1q bridge and the mode, all the VLANs correspond to
bridge and 802.1ad bridge) their respective MAC address tables.
802.1ad bridge, l SVL/Ingress l If the ingress filter is enabled, the
unsupported by Filter Disable VLAN tag is checked at the ingress
the 802.1d (the 802.1d port. If the VLAN ID does not equal
bridge) bridge) the VLAN ID of the port defined in the
l SVL/Ingress VLAN filtering table, the packet is
Filter Disable discarded. If the ingress filter is
(supported by disabled, the preceding described check
the 802.1d is not conducted.
bridge and
802.1ad bridge,
unsupported by
the 802.1q
bridge)
Operation Type Add S-VLAN base Add S-VLAN base For the meaning of each operation type,
for port for port see Application of QinQ in 802.1ad Bridge
Add S-VLAN base Services.
for Port and C-
VLAN
Mount Port
Mount Port and
base for Port and S-
VLAN
Navigation Path
In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree.
2. Select an IEEE 802.1q or 802.1ad bridge and click the VLAN Filtering tab.
NOTE
In the case of IEEE 802.1ad bridge-based Ethernet LAN services, the learning mode of the VB
must be IVL.
3. Click New.
Navigation Path
In the NE Explorer, select the EFP8/EMS6 board, and choose Configuration > Layer-2
Switching Management > Aging Time from the Function Tree.
MAC Address l 1 to 120 Min 5 Min l If one entry is not updated in a certain
Aging Time l 1 to 120 Hour period, that is, if no new packet from
this MAC address is received to enable
l 1 to 12 Day the re-learning of this MAC address,
this entry is deleted automatically. This
mechanism is called aging, and this
period is called the aging time.
l If you set this parameter to a very large
value, the bridge stores excessive MAC
address table entries that are outdated,
which exhausts the resources of the
MAC address forwarding table.
l If you set this parameter to a very small
value, the bridge may delete the MAC
address table entry that is required,
which reduces the forwarding
efficiency.
l It is recommended that this parameter
takes the default value.
NOTE
The maximum MAC Address Aging Time
supported by EFP8 and EMS6 boards is 12
days.
Navigation Path
1. In the NE Explorer, select the EMS6 board. Choose Configuration > Ethernet
Protection > ERPS Management.
2. Click New.
Parameters
Parameter Value Range Default Value Description
Navigation Path
In the NE Explorer, select the EMS6 board. Choose Configuration > Ethernet Protection >
ERPS Management from the Function Tree.
Parameters
Parameter Value Range Default Value Description
the same as or
different from the
fault that triggers
the initial startup
of the hold-off
timer.
Navigation Path
1. In 1the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Layer-2 Switching Management > Spanning Tree from the Function
Tree.
2. Click the Protocol Enabled tab.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Layer-2 Switching Management > Spanning Tree from the Function
Tree.
2. Click the Bridge Parameters tab.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board, and choose Configuration > Layer-2
Switching Management > Spanning Tree from the Function Tree.
2. Click the Port Parameters tab.
Admin Edge Enabled Disabled l Is valid only when the RSTP is used.
Attribute Disabled l Specifies whether to set the port to an
edge port. The edge port refers to the
bridge port that is connected only to the
LAN. The edge port receives the
BPDU and does not transmit the
BPDU.
l Set this parameter to Enabled only
when the Ethernet port on the Ethernet
board is directly connected to the data
communication terminal equipment,
such as a computer. In other cases, it is
recommended that this parameter takes
the default value.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board, and choose Configuration > Layer-2
Switching Management > Spanning Tree from the Function Tree.
2. Click the Bridge Running Information tab.
Root Path Cost - - Displays the root path cost. The root path
cost is the path cost of the root port and is
used for calculating the network topology.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board, and choose Configuration > Layer-2
Switching Management > Spanning Tree from the Function Tree.
2. Click the Port Running Information tab.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board, and choose Configuration > Layer-2
Switching Management > Spanning Tree from the Function Tree.
2. Click the Point to Point Attribute tab.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Layer-2 Switching Management > IGMP Snooping Protocol from
the Function Tree.
2. Click the Enable IGMP Snooping Protocol tab.
The Discarded Tag Disabled Disabled l This parameter specifies the method of
of the Packet the port to process unknown multicast
Excluded in the packets. When the IEEE 802.1q or
Multicast Group 802.1ad bridge receives the multicast
packets whose multicast addresses are
not included in the multicast table,
these packets are considered as
unknown packets.
l This parameter is valid only when
Protocol Enable is Enabled.
l If this parameter is set to Disabled,
unknown multicast packets are
broadcast in the VLAN.
l Set this parameter as required by the
IGMP multicast server.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Layer-2 Switching Management > IGMP Snooping Protocol from
the Function Tree.
2. Click the Static Multicast Table tab.
3. Click New.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Layer-2 Switching Management > IGMP Snooping Protocol from
the Function Tree.
2. Click the Multicast Aging Time tab.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Interface Management > Ethernet Link Aggregation
Management from the Function Tree.
2. Click the Link Aggregation Group Management tab.
3. Click New.
Attribute Parameters
Parameter Value Range Default Value Description
Sharing Mode IP Sharing Mode IP Sharing Mode You can set this parameter only when
MAC Sharing Load Sharing is Sharing.
Mode
Revertive Mode Revertive Revertive l You can set this parameter only when
Non-Revertive Load Sharing is Non-Sharing.
l If this parameter is set to Revertive,
services are automatically switched
back to the working path after the
working path recovers.
l If this parameter is set to Non-
Revertive, services are still transmitted
in the protection path after the working
path recovers and the LAG remains the
same.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Interface Management > Ethernet Link Aggregation
Management from the Function Tree.
2. Click the Link Aggregation Parameters tab.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Interface Management > LPT Management from the
Function Tree.
2. Click Query.
Bearer Mode GFP(HUAWEI) GFP(HUAWEI) l Specifies the bearer mode of the LPT
Ethernet packets.
GFP-CSF l The default value is recommended.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Interface Management > LPT Management from the
Function Tree.
2. Click PtoMP LPT. Then, the LPT Management dialog box appears.
3. Click New.
Bearer Mode GFP(HUAWEI) GFP(HUAWEI) l This parameter can be set only when
Ethernet the selected port is a VCTRUNK.
GFP-CSF l The default value is recommended.
Bearer Mode GFP(HUAWEI) GFP(HUAWEI) l This parameter can be set only when
Ethernet the selected port is a VCTRUNK.
GFP-CSF l The default value is recommended.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Interface Management > Port Mirroring from the
Function Tree.
2. Click New.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function
Tree.
2. In the right pane, click OAM Configuration.
3. Click New and choose Create MD from the drop-down list.
Maintenance Domain Consumer High(7) Operator Low(0) Specifies the level of the
Level Consumer Middle(6) MD. The greater the
value, the higher the
Consumer Low(5) level.
Provider High(4)
Provider Low(3)
Operator High(2)
Operator Middle(1)
Operator Low(0)
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function
Tree.
2. In the right pane, click OAM Configuration.
3. Click New and choose Create MA from the drop-down list.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function
Tree.
2. Click New.
Level Consumer High(7) Provider High(4) Specifies the level of a common MP. The
Consumer greater the value, the higher the level.
Middle(6) NOTE
This parameter is valid only for a common MP
Consumer Low(5) (NULL).
Provider High(4)
Provider Low(3)
Operator High(2)
Operator Middle(1)
Operator Low(0)
CCM Sending Standard MP: Standard MP Specifies the interval for sending the CCM
Period(ms) 1000 1000 packet at the MP where the CC test is
performed.
10000 Common MP:
l If this parameter takes a very small
6000 5000 value, service bandwidth decreases
600000 significantly.
Common MP: l If this parameter takes a very large
1000 to 60000, in value, the CC test will become less
step of 100 capable in detecting service
interruptions. The default value is
recommended.
l This parameter can be set only for an
MEP.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function
Tree.
2. Select the node that requires an LB test, click OAM Operation, and select Start LB.
Test based on the MAC Selected Not selected Select this parameter for
Address Not selected an LB test based on MAC
addresses.
NOTE
This parameter is valid
only for a standard MP.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function
Tree.
2. Select the node that requires an LT test, click OAM Operation, and select Start LT.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function
Tree.
2. Click the OAM Parameter tab.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function
Tree.
2. Click the OAM Error Frame Monitor tab.
Error Frame 1000 to 60000, in 1000 In the specified Error Frame Monitor
Monitor step of 100 Window (ms), if the number of error
Window(ms) frames exceeds the specified Error Frame
Monitor Threshold (frames) due to the
link degradation, the link event alarm is
reported.
Error Frame 1488 to 89280000, GE port: 1488000 Within the specified value of Error
Period in step of 1 FE port: 148800 Frame Period Window (frames), if the
Window(frames) number of error frames on the link exceeds
the preset value of Error Frame Period
Threshold (frames), an alarm is reported.
Error Frame 10 to 900, in step of 60 If any error frame occurs in one second,
Second Window(s) 1 this second is called an error frame second.
Within the specified value of Error
Frame Second Window(s), if the number
of error frames on the link exceeds the
preset value of Error Frame Second
Threshold (s), an alarm is reported.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board and choose Configuration > Ethernet
Maintenance > Ethernet Port OAM from the Function Tree.
2. Click the Remote OAM parameter tab.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > QoS Management > Flow Management from the Function Tree.
2. Click the Flow Configuration tab.
3. Click New.
Flow Type Port Flow Port Flow l Port flow: The packets from a certain
Port+VLAN Flow port are classified as a type of flow.
The Ethernet service associated with
Port+SVLAN Flow this flow type is the line service or
Port+CVLAN Layer 2 switching service that uses this
+SVLAN Flow port as the service source.
Port+VLAN l Port+VLAN flow: The packets that are
+Priority Flow from a certain port and have a specified
VLAN ID are classified as a type of
flow. The associated Ethernet service of
this flow type is the EVPL service
(based on VLAN) or EVPLAN service
(based on the 802.1q bridge) that uses
this PORT+VLAN as the service
source.
l Port+SVLAN flow: The packets that
are from a certain port and have a
specified SVLAN ID are classified as a
type of flow. The associated Ethernet
service of this flow type is the EVPL
service (based on QinQ) or EVPLAN
service (based on the 802.1ad bridge)
that uses this PORT+SVLAN as the
service source.
l Port+CVLAN+SVLAN flow: The
packets that are received from or
transmitted to a certain port and have a
specified CVLAN+SVLAN are
classified as a type of flow. The
associated Ethernet service of this flow
type is the EVPL service (based on
QinQ) or EVPLAN service (based on
the 802.1ad bridge) that uses this PORT
+CVLAN+SVLAN as the service
source.
l Port+VLAN+Priority flow: The
packets that are from a certain port and
have a specified VLAN ID and a
specified VLAN priority are classified
as a type of flow. The associated
Ethernet service of this flow type is the
line service that uses this Port+VLAN
+Priority as the service source.
Port EFP8: PORT1 to PORT1 l When the associated service is the line
PORT9, service, set this parameter to the source
VCTRUNK1 to port or sink port of the associated
VCTRUNK16 Ethernet service.
EMS6: PORT1 to l When the associated service is the
PORT7, Layer 2 switching service, set this
VCTRUNK1 to parameter to a mounted port of the
VCTRUNK8 bridge.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board, and then choose Configuration >
QoS Management > Flow Management from the Function Tree.
2. Click the CAR Configuration.
3. Click New.
Committed Burst EFP8: 0 to 1024 0 Indicates the CBS. When the rate of a
Size (kbyte) EMS6: 0 to 16384 packet that passes the restriction of the
CAR is not more than the CIR in a certain
period, some packets can burst. These
packets can be forwarded first even in the
case of network congestion. The
maximum traffic of the burst packets is
determined by the CBS. Note that the CBS
has an inherent size, and this parameter
indicates the increment value only. The
inherent size of the CBS is determined by
the CIR. The greater the CIR, the greater
the CBS.
Peak information EFP8: 0 to 100032, 0 l Indicates the PIR. When the rate of a
Rate (kbit/s) in steps of 64 packet is more than the PIR, the packet
EMS6 (FE ports): 0 that exceeds the rate restriction is
to 102400, in steps directly discarded. When the rate of
of 64 packets is more than the CIR but is
lower than or equal to the PIR, these
EMS6 (GE ports): packets whose rate exceeds the CIR
0 to 1024000, in can pass the restriction of the CAR and
steps of 64 are marked yellow.
l The value of this parameter should not
be more than the port bandwidth.
Maximum Burst EFP8: 0 to 1024 0 Indicates the MBS. When the rate of the
Size (kbyte) EMS6: 0 to 16384 packet that passes the restriction of the
CAR is more than the CIR but is not more
than the PIR, some packets can burst and
are marked yellow. The maximum traffic
of the burst packets is determined by the
MBS. Note that the MBS has an inherent
size, and this parameter indicates the
increment value only. The inherent size of
the MBS is determined by the PIR. The
greater the PIR, the greater the MBS.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > QoS Management > Flow Management from the Function Tree.
2. Click the CoS Configuration tab.
3. Click New.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board, and then choose Configuration >
QoS Management > Flow Management from the Function Tree.
2. Click the Flow Configuration tab.
Navigation Path
In the NE Explorer, select the required Ethernet switching board from the Object Tree and
choose Configuration > QoS Management > Port Shaping Management from the
Function Tree.
CIR (kbit/s) EFP8: 0 to 100032, 0 l When the rate of a packet is not more
in steps of 64 than the CIR, this packet directly enters
EMS6 (FE ports): 0 the egress queue.
to 102400, in steps l The value of this parameter should not
of 64 be more than the PIR.
EMS6 (GE ports): 0
to 1024000, in steps
of 64
PIR (kbit/s) EFP8: 0 to 100032, 0 l When the rate of a packet is more than
in steps of 64 the PIR, the packet that exceeds the
EMS6 (FE ports): 0 rate restriction is directly discarded.
to 102400, in steps When the rate of packets is more than
of 64 the CIR but not more than the PIR, the
packets that exceed the restriction of
EMS6 (GE ports): 0 the CIR enter the buffer of the CIR.
to 1024000, in steps When the buffer overflows, the packets
of 64 are marked yellow and enter the egress
queue, which enables the packets to be
discarded first in the case of queue
congestion.
l The value of this parameter should not
be more than the port bandwidth.
Scheduling Mode SP Queue 1: WRR By default, queue 8 (with the CoS priority
WRR Queue 2: WRR of 7) of the EMS6 board is the SP queue,
and queues 1-7 (with the respective CoS
Queue 3: WRR priority of 0-6) are the WRR queues and
Queue 4: WRR their weights are in the proportion of
Queue 5: WRR 1:2:8:16:32:64.
Queue 6: WRR The scheduling principles of the SP+WRR
are as follows:
Queue 7: WRR
l A port immediately transmits the
Queue 8: SP
packets in the SP queue and can
transmit the packets in the WRR queue
only when no packets exist in the SP
queue.
l If multiple SP queues exist on a port,
the port compares the SP queues
according to their priorities (queue 8
has the highest priority and queue 1 has
the lowest priority).
l According to the fixed weight value,
you can allocate the time slice to each
WRR queue. Then, the port transmits
the packets in the corresponding WRR
queue in each time slice. If a WRR
queue in a time slice does not contain
any packets, the WRR queue removes
this time slice and then transmits the
packets in the corresponding WRR
queue in the next time slice.
Weight An integer ranging Queue 1: 1 By default, queue 8 (with the CoS priority
from 1 to 64 Queue 2: 2 of 7) of the EMS6 board is the SP queue,
and queues 1-7 (with the respective CoS
Queue 3: 4 priority of 0-6) are the WRR queues and
Queue 4: 8 their weights are 1:2:4:8:16:32:64.
Queue 5: 16
Queue 6: 32
Queue 7: 64
Queue 8: -
Navigation Path
In the NE Explorer, select the EMS6 board from the Object Tree and choose Configuration >
QoS Management > Port Shaping Management from the Function Tree.
PIR (kbit/s) EMS6 (FE ports): 0 0 In the case of an EMS6 board, the PIR of a
to 102400, in steps port meets the following constraints:
of 64 l The PIR of the port is equal to or more
EMS6 (GE ports): 0 than the PIR of any queue at this port.
to 1024000, in steps l The PIR of the port is equal to or more
of 64 than the sum of the CIRs of all the
queues at this port.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board and then choose Configuration >
Ethernet Interface Management > Ethernet Interface from the Function Tree.
2. Select External Port.
l 1000M Full-
Duplex
Maximum Frame EFP8: 1518 to 2000 1522 l Set this parameter to a value greater
Length (bytes) EMS6: 1518 to than the maximum length of all the data
9600 frames to be transmitted.
l The default value is recommended if
the jumbo frame is not considered and
the data frames contain only one layer
of VLAN tags or even no tags. The
value of 1526 or greater is
recommended if the data frames
contain two layers of tags, such as
QinQ.
TAG Tag Aware Tag Aware l With different tag attributes, the port
Access processes frames in different modes.
For details, see Table B-73.
Hybrid
l Set this parameter to Tag Aware if the
port processes the frames with VLAN
tags (or tagged frames).
l Set this parameter to Access if the port
processes the frames without VLAN
tags (or untagged frames).
l Set this parameter to Hybrid if the port
processes the tagged frames and
untagged frames.
Port Attributes UNI UNI l If this parameter is set to UNI, the port
C-Aware processes data frames according to the
tag attribute.
S-Aware
l If this parameter is set to C-Awareor S-
Aware, the port processes the data
frames by using the processing method
of QinQ services.
l Set this parameter to C-Aware or S-
Aware when the port processes QinQ
services. Otherwise, this parameter
takes the default value.
Ingress port Tagged frame Receives the frame. Discards the frame. Receives the frame.
Untagged frame Discards the frame. The port receives The port receives
the frame after the frame after
adding to the frame adding to the frame
the VLAN tag that the VLAN tag that
contains Default contains Default
VLAN ID and VLAN ID and
VLAN Priority. VLAN Priority.
Egress port Tagged frame Transmits the The port strips the l If the VLAN ID
frame. VLAN tag from the in the frame is
frame and then Default VLAN
transmits the frame. ID, the port
strips the VLAN
tag from the
frame and then
transmits the
frame.
l If the VLAN ID
in the frame is
not Default
VLAN ID, the
port directly
transmits the
frame.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board and then choose Configuration >
Ethernet Interface Management > Ethernet Interface from the Function Tree.
2. Select Internal Port.
Name - -
Check Field FCS32 FCS32 l When the Ethernet board uses the GFP
Length No mapping protocol, set this parameter to
FCS32 or No.
l When you set this parameter to FCS32,
a 32-bit FCS is used.
l The default value is recommended.
FCS Calculated Big endian Big endian l When you set this parameter to Big
Bit Sequence Little endian endian, the least significant byte of the
FCS is placed first and the most
significant byte is placed last.
l When you set this parameter to Little
endian, the most significant byte of the
FCS is placed first and the least
significant byte is placed last.
l The default value is recommended.
Port Attributes UNI UNI l If this parameter is set to UNI, the port
C-Aware processes data frames according to the
tag attribute.
S-Aware
l If this parameter is set to C-Aware or
S-Aware, the port processes the data
frames by using the processing method
of QinQ services.
l Set this parameter to C-Aware or S-
Aware when the port processes QinQ
services. Otherwise, this parameter
takes the default value.
LCAS Mode Huawei Mode Huawei Mode l Indicates the sequence in which the
Standard Mode LCAS sink sends the MST control
packet and Rs-Ack control packet.
l When you set this parameter to
Huawei Mode, the LCAS sink first
sends the Rs-Ack and then sends the
MST.
l When you set this parameter to
Standard Mode, the LCAS sink first
sends the MST and then sends the Rs-
Ack.
l If the equipment at the opposite end is
the third-party equipment and does not
support the Huawei mode, set this
parameter to Standard Mode.
Otherwise, set this parameter to
Huawei Mode.
Hold Off Time(ms) An integer ranging 2000 l When a member link is faulty, the
from 0, 2000 to LCAS performs switching after a delay
10000, in the of time to prevent the situation where
increments of 100 an NE simultaneously performs a
protection switching such as SNCP and
performs an LCAS switching. This
parameter specifies the duration of the
delay.
l The default value is recommended.
WTR Time(s) 0-720 300 l When the time after a member link is
restored to normal reaches the specified
value of this parameter, the VCG uses
the restored member link.
l The default value is recommended.
Ingress port Tagged frame Receives the frame. Discards the frame. Receives the frame.
Untagged frame Discards the frame. The port receives The port receives
the frame after the frame after
adding to the frame adding to the frame
the VLAN tag that the VLAN tag that
contains Default contains Default
VLAN ID and VLAN ID and
VLAN Priority. VLAN Priority.
Egress port Tagged frame Transmits the The port strips the l If the VLAN ID
frame. VLAN tag from the in the frame is
frame and then Default VLAN
transmits the frame. ID, the port
strips the VLAN
tag from the
frame and then
transmits the
frame.
l If the VLAN ID
in the frame is
not Default
VLAN ID, the
port directly
transmits the
frame.
Navigation Path
In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Advance Attribute > QinQ Type Area Settings from the Function Tree.
NOTE
For parameters for PW-carried E-Line services, see B.6 Parameters for Ethernet Services and
Ethernet Features on the Packet Plane.
Navigation Path
In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
MPLS Management > Basic Configuration from the Function Tree.
Navigation Path
1. Select the desired NE from the Object Tree in the NE Explorer. Choose Configuration >
MPLS Management > Basic Configuration from the Function Tree.
2. Click the Global OAM Parameters tab.
Navigation Path
1. In the NE Explorer, select the required NE from the Object Tree and choose
Configuration > MPLS Management > Unicast Tunnel Management from the
Function Tree.
2. Click the Static Tunnel tab.
3. Click Query.
Navigation Path
1. In the NE Explorer, select the required NE from the Object Tree and choose
Configuration > MPLS Management > Unicast Tunnel Management from the
Function Tree.
In Port - - NOTE
l If the MPLS port is an FE/GE
port, ensure that:
l The Port Mode parameter of
the MPLS port is set to Layer
3 according to A.8.8.1
Setting the Basic Attributes
of Ethernet Ports.
l The Enable Tunnel, Specify
IP Address, andIP Address
parameters of the MPLS port
are set to the values specified
in the network plan according
to A.8.8.4 Setting Layer 3
Attributes of Ethernet
Ports.
l If the MPLS port is an IF_ETH
port, ensure that:
l The Port Mode parameter of
the MPLS port is set to Layer
3 according to A.8.9.1
Setting the Basic Attributes
of IF_ETH Ports.
l The Enable Tunnel, Specify
IP Address, and IP Address
parameters of the MPLS port
are set to the values specified
in the network plan according
to A.8.9.3 Setting Layer 3
Attributes of IF_ETH
Ports.
Navigation Path
1. In the NE Explorer, select the required NE from the Object Tree and choose
Configuration > MPLS Management > Unicast Tunnel Management from the
Function Tree.
2. Click the Static Tunnel tab.
3. Click New and choose Bidirectional Tunnel from the drop-down list.
In Port - - NOTE
l If the MPLS port is an FE/GE port,
ensure that:
l The Port Mode parameter of the
MPLS port is set to Layer 3
according to A.8.8.1 Setting the
Basic Attributes of Ethernet
Ports.
l The Enable Tunnel, Specify IP
Address, and IP Address
parameters of the MPLS port are
set to the values specified in the
network plan according to A.8.8.4
Setting Layer 3 Attributes of
Ethernet Ports.
l If the MPLS port is an IF_ETH port,
ensure that:
l The Port Mode parameter of the
MPLS port is set to Layer 3
according to A.8.9.1 Setting the
Basic Attributes of IF_ETH
Ports.
l The Enable Tunnel, Specify IP
Address, and IP Address
parameters of the MPLS port are
set to the values specified in the
network plan according to A.8.9.3
Setting Layer 3 Attributes of
IF_ETH Ports.
Forward Out Label 16 to 1048575 - Specifies the MPLS label at the egress
direction of a forward tunnel on an
ingress or transit node.
Navigation Path
1. In the NE Explorer, select the required NE from the Object Tree and choose
Configuration > MPLS Management > Unicast Tunnel Management from the
Function Tree.
2. Click the OAM Parameter tab.
Navigation Path
1. In the NE Explorer, select the required NE from the Object Tree and choose
Configuration > MPLS Management > Unicast Tunnel Management from the
Function Tree.
2. Click the FDI tab.
Navigation Path
1. In the NE Explorer, select the required NE from the Object Tree and choose
Configuration > MPLS Management > Unicast Tunnel Management from the
Function Tree.
2. Click the OAM Parameters tab.
3. Select the required tunnel, click OAM Operation in the lower right corner, and choose
Ping Test from the drop-down list.
Response Mode IPv4 UDP Response IPv4 UDP Response l Specifies the response
No Response mode of test request
packets.
Application Control
Channel Response l The value No
Response indicates
that the test
performance event is
reported without
sending response
packets.
l The value
Application Control
Channel Response
indicates that response
is performed through
the reverse channel.
l The value IPv4 UDP
Response indicates
that the IPv4 UDP
packets encapsulating
MPLS echo reply
messages are sent as
response packets.
l The value IPv4 UDP
Response is reserved
for scenarios where all
nodes on an LSP
communicate with
each other over a
DCN running IP
protocols.
l Set this parameter
based on the situation
of the egress node. If
the egress node
supports reverse
channel response, set
this parameter to
Application Control
Channel Response. If
the egress node does
not support reverse
channel response but
supports DCN
channel response by
means of IP protocols,
set this parameter to
IPv4 UDP Response.
Navigation Path
1. In the NE Explorer, select the required NE from the Object Tree and choose
Configuration > MPLS Management > Unicast Tunnel Management from the
Function Tree.
2. Click the OAM Parameters tab.
3. Select the required tunnel, click OAM Operation in the lower right corner, and choose
Traceroute Test from the drop-down list.
Response Mode IPv4 UDP Response IPv4 UDP Response l Specifies the response
No Response mode of test request
packets.
Application Control
Channel Response l The value No
Response indicates
that the test
performance event is
reported without
sending response
packets.
l The value
Application Control
Channel Response
indicates that response
is performed through
the reverse channel.
l The value IPv4 UDP
Response indicates
that the IPv4 UDP
packets encapsulating
MPLS echo reply
messages are sent as
response packets.
l The value IPv4 UDP
Response is reserved
for scenarios where all
nodes on an LSP
communicate with
each other over a
DCN running IP
protocols.
l Set this parameter
based on the situation
of the egress node. If
the egress node
supports reverse
channel response, set
this parameter to
Application Control
Channel Response. If
the egress node does
not support reverse
channel response but
supports DCN
channel response by
means of IP protocols,
set this parameter to
IPv4 UDP Response.
Navigation Path
1. Select the desired NE from the Object Tree in the NE Explorer. Choose Configuration >
MPLS Management > Unicast Tunnel Management from the Function Tree.
2. Click the MPLS-TP OAM tab.
3. Click the MEP tab.
Navigation Path
1. Select the desired NE from the Object Tree in the NE Explorer. Choose Configuration >
MPLS Management > Unicast Tunnel Management from the Function Tree.
2. Click the MPLS-TP OAM tab.
3. Click the MIP tab.
4. Click New.
Navigation Path
1. Select the desired NE from the Object Tree in the NE Explorer. Choose Configuration >
MPLS Management > Unicast Tunnel Management from the Function Tree.
2. Click the MPLS-TP OAM tab.
3. Click the MEP tab.
4. Select one or more tunnels and choose OAM Operation > Start LB.
Navigation Path
1. In the NE Explorer, select the required NE from the Object Tree and choose
Configuration > MPLS Management > PW Management from the Function Tree.
2. Click the PW Management tab.