Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
V100R003C03
Issue 04
Date 2013-11-30
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 equipment. This document
describes the basic information and configuration process, and uses configuration examples to
show how to set specific parameters.
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.
Section Description
Section Description
Section Description
Contents
A Task Collection.........................................................................................................................864
A.1 Web LCT Quick Start................................................................................................................................................866
A.1.1 Connecting the Web LCT to the IDU.....................................................................................................................866
A.1.2 Using Online Help..................................................................................................................................................868
A.1.3 Navigating to the NE Explorer...............................................................................................................................869
A.2 Network Management...............................................................................................................................................870
A.2.1 Managing NEs........................................................................................................................................................870
A.2.1.1 Creating NEs by Using the Search Method.........................................................................................................870
A.2.1.2 Creating NEs by Using the Manual Method........................................................................................................873
A.2.1.3 Logging In to an NE............................................................................................................................................874
A.2.1.4 Configuring the Logical Board............................................................................................................................875
A.2.1.5 Configuring an SFP Port......................................................................................................................................876
A.8.4.3 Setting the Aging Time of a MAC Address Table Entry .................................................................................1063
A.8.4.4 Querying or Deleting a Dynamic MAC Address..............................................................................................1064
A.8.4.5 Querying the Actual Capacity of a MAC Address Table..................................................................................1064
A.8.5 Configuring Ethernet Ports...................................................................................................................................1065
A.8.5.1 Configuring External Ethernet Ports.................................................................................................................1065
A.8.5.2 Configuring VCTRUNKs on an Ethernet Board...............................................................................................1067
A.8.5.3 Modifying the Type Field of QinQ Frames.......................................................................................................1069
A.8.5.4 Dynamically Increasing/Decreasing the VCTRUNK Bandwidth.....................................................................1070
A.8.6 Managing the Spanning Tree Protocol.................................................................................................................1071
A.8.6.1 Configuring the Type and Enabled Status of the Spanning Tree Protocol........................................................1071
A.8.6.2 Setting the Parameters of Spanning Tree Protocol............................................................................................1072
A.8.6.3 Querying the Running Information About the Spanning Tree Protocol............................................................1073
A.8.7 Managing the IGMP Snooping Protocol..............................................................................................................1074
A.8.7.1 Configuring the IGMP Snooping Protocol........................................................................................................1074
A.8.7.2 Configuring Static Multicast Entries.................................................................................................................1075
A.8.7.3 Modifying the Aging Time of a Multicast Table Entry.....................................................................................1076
A.8.7.4 Querying the Running Information of the IGMP Snooping Protocol...............................................................1077
A.8.8 Managing the QoS................................................................................................................................................1077
A.8.8.1 Creating a Flow..................................................................................................................................................1078
A.8.8.2 Creating the CAR..............................................................................................................................................1078
A.8.8.3 Creating the CoS................................................................................................................................................1079
A.8.8.4 Binding the CAR/CoS.......................................................................................................................................1081
A.8.8.5 Configuring Traffic Shaping for Egress Queues...............................................................................................1082
A.8.8.6 Configuring Port Shaping..................................................................................................................................1083
A.8.8.7 Setting Egress Queue Scheduling Policies........................................................................................................1083
A.8.9 Using the Ethernet service OAM..........................................................................................................................1084
A.8.9.1 Creating MDs.....................................................................................................................................................1084
A.8.9.2 Creating MAs.....................................................................................................................................................1085
A.8.9.3 Creating MPs.....................................................................................................................................................1086
A.8.9.4 Performing a CC Test........................................................................................................................................1088
A.8.9.5 Performing an LB Test......................................................................................................................................1089
A.8.9.6 Performing an LT Test.......................................................................................................................................1090
A.8.9.7 Activating the AIS.............................................................................................................................................1091
A.8.9.8 Performing a Ping Test .....................................................................................................................................1092
A.8.9.9 Performing Performance Check........................................................................................................................1093
A.8.10 Using the Ethernet port OAM.............................................................................................................................1093
A.8.10.1 Enabling the OAM Auto-Discovery Function.................................................................................................1093
A.8.10.2 Enabling the Link Event Notification..............................................................................................................1095
A.8.10.3 Modifying the OAM Error Frame Monitoring Threshold...............................................................................1096
A.8.10.4 Performing the Remote Loopback...................................................................................................................1097
A.8.11 Configuring LPT.................................................................................................................................................1097
B Parameters Description..........................................................................................................1208
B.1 Parameters for Network Management.....................................................................................................................1209
B.1.1 Parameters for NE Management...........................................................................................................................1209
B.1.1.1 Parameter Description: NE Searching...............................................................................................................1209
B.1.1.2 Parameter Description: NE Creation.................................................................................................................1210
B.1.1.3 Parameter Description: Login to an NE.............................................................................................................1212
B.1.1.4 Parameter Description: NE Attribute_Changing NE IDs..................................................................................1212
B.1.1.5 Parameter Description: NE Time Synchronization............................................................................................1213
C Glossary....................................................................................................................................1849
1 Configuration Preparations
Before configuring the NE data, you must make the required preparations.
Documents
l Network planning documents, such as the XXX Network Planning
l OptiX RTN 950 Radio Transmission System Configuration Guide
Tools
A computer where the Web LCT software is installed
NOTE
For information about the software and hardware required for the Web LCT and the installation method, see the
documents that accompany the Web LCT.
Context
Ensure that the following requirements are met:
The Web LCT quick start guide helps to learn about basic operations on the Web LCT.
You can select the proper configuration procedure according to the actual configuration
scenarios.
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 3-1 shows the
configuration procedure.
Start
Configuring EoS/EoPDH-Based
Ethernet services
End
Required
Optional
Operation Description
8 Configuring Native Ethernet Services Required when Native Ethernet services based
on the Packet Plane on the packet plane need to be transmitted.
Operation Description
11 Configuring
PWE3 Services
NOTE
The configuration sequence provided in Table 3-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 3-2.
Operation Description
14.1 Common Task Collection (NEs) This common task collection lists configuration
operations associated with NE attributes,
including changing the ID and IP address of an
NE.
14.2 Common Task Collection (Radio This common task collection lists configuration
Links) 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.
14.3 Common Task Collection (TDM This common task collection lists configuration
Services) operations associated with TDM services,
including deleting TDM services and upgrading
a normal service to an SNCP service.
Operation Description
14.4 Common Task Collection (Packet- This common task collection lists configuration
Plane Ethernet Services) operations associated with Native Ethernet
services based on the packet plane, including
setting or modifying Ethernet port parameters
and deleting Ethernet services.
14.5 Task Collection (EoS/EoPDH- This common task collection lists configuration
Plane Ethernet Services) operations associated with Ethernet services
based on the EoS/EoPDH plane, including
setting or modifying Ethernet port parameters
and deleting Ethernet services.
Initial configuration examples of each section are provided in the same TDM radio network
scenario or IP radio network scenario.
Overall Topology
Figure 4-1 shows the overall topology of the TDM radio network. On this network, base station
backhaul services are converged at a TDM radio chain network and a TDM radio ring network
and then are transmitted over a third-party SDH network to the BSC.
STM-1
TDM radio chain Third party SDH network
network
BSC
E1
E1
BTS12 DCN
STM-1
E1 Third party
NE14
SDH network
BTS13
E1 STM-1
NE13 NE12 NE11
E1 BTS11
E1
NE16 NE15
BTS15 BTS14
Figure 4-3 shows the board configuration of each NE on the radio network.
Figure 4-3 Board configuration of NEs on the TDM radio chain network
CST CST
IF1
NE6
IF1 NE6
IF1 IF1
SP3S SP3S
NE16 NE15 E1
E1
BTS14
BTS15
NMS
DCN
Third party E1
SDH network NE21
BTS21
BTS22
NE23
BTS23
Figure 4-5 shows the board configuration of each NE on the radio network.
Figure 4-5 Board configuration of NEs on the TDM radio ring network
NE21
CST
IF1
NE6
IF1 IF1
Third party
SDH netw ork E1 SP3S
E1 NE22
CST NE24
BTS21
NE6 CST
IF1 IF1 IF1
SP3S NE6
IF1 IF1 E1
SP3S
E1
BTS22
BTS24
NE23
CST
NE6
IF1 IF1
SP3S
E1
BTS23
Overall Topology
Figure 4-6 shows the overall topology of the IP radio network. The base station backhaul
services converged from a Hybrid radio chain network, a Hybrid radio ring network, and a packet
radio chain network are transmitted to the BSC/RNC over a GE packet ring.
GE packet ring
NMS
Hybrid radio chain
network
BSC
Hybrid radio ring
network
RNC
Packet Network
Figure 4-7 shows the topology of the packet network. The packet network receives various base
station services and the base station backhaul services converged from a Hybrid radio chain
network and a Hybrid radio ring network. The base station services transmitted on the network
are:
l 2G base station services (CES services transmitted to the BSC from E1 ports)
l R99 base station services (ATM PWE3 services transmitted to the RNC from E1 ports)
l R4 base station services (ETH PWE3 services transmitted to the RNC from GE ports)
FE
BTS31
R4
BTS32
E1 E1 R4
FE
R99
BTS34 GE GE
NE32
Hybrid radio chain
NE11 NE31 NMS
network
E1
GE
NE21 GE
E1
E1
E1
+G
BSC
E
BTS36 BTS35 Hybrid radio ring
network R99 R99
BTS37 BTS38
RNC
NOTE
l NE31 is an OptiX PTN NE in an actual network as it does not connect to any radio links. In this example,
NE31 is an IDU.
l NE11 receives base station services from BTS35 and BTS36 by using the Fractional E1 function.
l NE21 receives base station services from BTS37 and BTS38 by using the Fractional E1 function.
Figure 4-8 provides the board configuration of each NE on the packet network.
NE34 NE33
CSH CSH
BTS33 ISX2
NE6
ISU2 NE6
ISU2 ISX2
EM6T ML1 ML1
FE
R4
E1 E1
BTS31
BTS34 R99 BTS32
FE
NE32
CSH R4
Hybrid radio chain ISX2
NE6
ISX2
network
NE11 EM6F NE31
CSH
GE GE CSH
ISU2
NE6 GE
ISU2 ML1 FE NE6
EM6T
SP3S EM6F GE
NE21 EM6F ML1
E1 CSH GE
GE E1 GE
ISU2 ML1 GE
BTS36 BTS35 NE6 ISU2
ISU2 E1
EM6F SP3S
E1
R99 R99 BSC RNC
BTS38 BTS37
Hybrid radio ring
network
NOTE
l The Native E1 services received by the Hybrid radio network are converted to CES services by cross-
connecting some E1 ports on the SP3S and ML1 boards of NE11 and NE21.
l The Native E-LAN services received by the Hybrid radio network are converted to E-Line services, which
can be carried by PWs, by cross-connecting some FE ports on the EM6F board of NE21. NE11 receives
Native E-Line services and does not require port cross-connections.
l The GE port connected to the RNC is configured into a LAG.
R4 FE
BTS12
E1+GE+
NE cascade
E1 NE14
R99 Packet network
BTS13 FE
NE13 NE12 NE11
R4
E1 BTS11
FE NE15
NE16
R99
R4
BTS14
BTS15
NOTE
The cascading ports of NE12 and NE13 are connected by using network cables for DCN communication.
Figure 4-10 shows the board configuration of each NE on the radio network.
Figure 4-10 Board configuration of NEs on the Hybrid radio chain network
NE16 NE15
CSH CSH
ISU2
NE6 NE6
ISU2 ISU2 ISU2
E1
EM6T SP3S R99
BTS14
FE
R4
BTS15
Packet network
NE21
R4 FE
BTS21 FE
R4
E1 NE22 NE24 BTS24
BTS22
FE
NE23
R4
BTS23
Figure 4-12 shows the board configuration of each NE on the radio network.
Figure 4-12 Board configuration of NEs on the Hybrid radio ring network
Packet network
NE21
FE
NE22
R4 CSH NE24
BTS21 NE6 CSH
ISU2 ISU2 ISU2
EM6T SP3S NE6
ISU2 ISU2
EM6T
E1
FE R4
BTS22
BTS24
NE23
CSH
NE6
ISU2 ISU2
EM6T
FE
R4
BTS23
You can manage a transport network by using the Web LCT only after configuring the network
topology on the network.
5.1.1 DCN
To manage and maintain an NE, the Web LCT needs to communicate with the NE through the
data communication network (DCN).
On a DCN, the Web LCT and all the NEs are considered as nodes on the DCN. The DCN between
the Web LCT 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 950 supports several DCN solutions,
including HWECC and IP DCN. HWECC is the commonest DCN solution.
HWECC is a DCN solution provided by Huawei. In this solution, the NMS manages NEs using
network management messages that are encapsulated in the HWECC protocol stack.
Figure 5-1 shows how network management messages are transmitted in the HWECC solution.
Network management messages encapsulated in compliance with the HWECC protocol stack
can be transmitted through the following DCN channels:
l DCCs carried by SDH or microwave links
l Integrated IP radio links or Ethernet paths over FE/GE ports
l Ethernet network management ports or NE cascading ports
Message
HWECC
DCC
NMS
Message Message
HWECC HWECC
DCC DCC
OptiX radio
OptiX optical transmission equipment
transmission equipment
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.
ECC communication between the GNEs may create an oversized DCN. To prevent this, disable
extended ECC for the 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 Web LCT 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
Table 5-1 provides the mappings between the physical boards and logical boards.
Table 5-1 Mappings between the physical boards and logical boards
Figure 5-2 provides the procedure for configuring the network topology.
Start
Creating NEs
Configuring NE attributes
Configuring DCCs
Synchronizing NE time
End
Required
Optional
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 ID and bandwidth of the inband DCN are set during the NE
commissioning, the configuration data is automatically synchronized onto the Web LCT in the NE data
uploading process. Hence, you do not need to perform the corresponding operations in the initial
configuration process.
l The DCN configuration procedure provided in Figure 5-2 is only a typical HWECC solution configuration.
For the configuration procedure for an HWECC solution containing special requirements or another DCN
solution, see related descriptions in the Feature Description.
1 A.2.1.3 Required.
Logging In
to an NE
3 A.2.1.7 Optional.
Changing
the NE
Name
4 A.2.1.4 Required.
Configuring
the Logical
Board
4 A.2.4.4 Perform this operation if the OptiX RTN equipment uses the
Configuring inband DCN solution and if the VLAN ID and bandwidth
the VLAN planned for this inband DCN do not assume their default
ID and values (the default VLAN ID is 4094 and the default
Bandwidth bandwidth is 512 kbit/s).
Used by an
Inband
DCN
Figure 5-3 shows a TDM radio chain network configured according to the following
requirements.
l The TDM radio chain network is comprised of the OptiX RTN equipment managed by the
standalone Web LCT.
l The Web LCT is connected to NE11 with a network cable. Therefore, NE11 serves as a
GNE and the other NEs are non-GNEs with an access to the Web LCT through NE11.
l NE12 and NE13 are interconnected by using fibers.
l The TDM radio chain network is interconnected with a third-party SDH network by using
fibers. Therefore, the base station backhaul services converged from the TDM radio chain
network are transmitted over the third-party SDH network.
E1
BTS12 DCN
STM-1
E1 Third party
NE14
SDH network
BTS13
E1 STM-1
NE13 NE12 NE11
E1 BTS11
E1
NE16 NE15
BTS15 BTS14
The connections of DCN links shown in Figure 5-3 are described as follows.
Link between NE11 and the 1-SL1D-1 (working unit) l Configure the ports as a 1
third-party SDH network +1 linear MSP group.
1-SL1D-2 (protection unit)
l The base station backhaul
services converged from
the TDM radio chain
network are transmitted
over the third-party SDH
network to the BSC.
l In this example, the network is comprised of OptiX RTN equipment only, and therefore
HWECC is preferred as the DCN solution. In the HWECC solution, NE12 and NE13
communicate with each other through DCC channels in the SDH optical fibers and the
other NEs communicate with each other through the DCC channels over microwave. If no
fiber connections are set up between NE12 and NE13, NE12 and NE13 communicate with
each other through the extended ECC that is enabled by default.
l NE11 is the GNE. Hence, the extended ECC function of NE11 needs to be disabled.
l The TDM radio chain network is connected to the third-party network through STM-1
optical fibers. The TDM radio chain and the third-party network are managed by the Web
LCT. Therefore, the DCC channel needs to be disabled over the port on the N11 for
connecting to the third-party network.
l Figure 5-4 shows the ID and IP address that are allocated to each NE according to the
uniform DCN planning information.
Figure 5-4 Allocated IDs and IP addresses (TDM radio chain network)
NMS
9-14 10.0.0.100/16
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 Third party
0.0.0.0 0.0.0.0 0.0.0.0 SDH network
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
NOTE
Precautions
If the NE ID and the values of NE communication parameters are changed and the logical boards
are configured in the NE commissioning process, skip the operations.
Procedure
Step 1 See A.2.1.1 Creating NEs by Using the Search Method and create the NEs.
The values for the related parameters are provided as follows.
Parameter Value
Domain 129.9.255.255
NOTE
In this configuration example, it is assumed that the IP address of the GNE is not changed manually and is not
known. Hence, you need to search for and create the NEs by using the 129.9.255.255 network segment as the
search domain. If the IP address of the GNE is known, it is recommended that you use the IP address of the
GNE as the search domain.
Normally, NE11 to NE16 should be added in the NE list.
Step 2 See A.2.1.3 Logging In to an NE and log in to the NEs.
The values for the relevant parameters are provided as follows.
Parameter Value
Password password
Paramete Value
r
NE11 NE12 NE13 NE14 NE15 NE16
New ID 11 12 13 14 15 16
Step 4 See A.2.1.4 Configuring the Logical Board and configure the logical boards.
Configure the logical boards according to the mapping relations between the physical boards
and logical boards.
Step 5 See A.2.4.1 Setting NE Communication Parameters and set the NE communication
parameters.
The values for the related parameters are provided as follows.
Parameter Value
NE11
IP 10.0.0.11
Extended ID 9
NOTE
The IP addresses of all the NEs, except NE11, are in the interlocking relations with the NE IDs. Hence, you
need not change the values of the NE communication parameters manually.
The values for the relevant parameters of NE11 are provided as follows.
Parameter Value
1-SL1D-1 1-SL1D-2
Step 7 See A.2.4.8 Configuring Extended ECC Communication and disable the automatic extended
ECC function for the gateway NE (NE11).
Step 8 See A.2.1.8 Synchronizing the NE Time and synchronize the NE time.
Parameter Value
Synchronous Mode NM
Period(days) 1
----End
Figure 5-5 shows a TDM radio ring topology configured according to the following
requirements.
l The TDM radio ring network is comprised of the OptiX RTN equipment managed by the
standalone Web LCT.
l The Web LCT is connected to NE21 with a network cable. Therefore, NE21 serves as a
GNE and the other NEs are non-GNEs with an access to the Web LCT through NE21.
l The TDM radio ring network is interconnected with a third-party SDH network by using
E1 cables. Therefore, the base station backhaul services converged from the TDM radio
ring network are transmitted over the third-party SDH network.
NMS
DCN
Third party E1
SDH network NE21
BTS21
BTS22
NE23
BTS23
The connections of DCN links shown in Figure 5-5 are described as follows.
Link between NE21 and the 2-SP3S The base station backhaul
third-party SDH network services converged from the
TDM radio ring network are
transmitted over the third-
party SDH network to the
BSC.
l In this example, the network is comprised of OptiX RTN equipment only, and therefore
HWECC is preferred as the DCN solution. In the HWECC solution, the NEs communicate
with each other through the DCC channels over microwave.
l NE21 is the GNE. Hence, the extended ECC function of NE21 should be disabled.
l The TDM radio ring network is connected to the third-party network through E1 cables
and cannot communicate with the third-party network. Therefore, the DCC channels need
to be disabled on NE21.
l Figure 5-6 shows the ID and IP address that are allocated to each NE according to the
uniform DCN planning information.
Figure 5-6 Allocated IDs and IP addresses (TDM radio ring network)
Third part
SDH network E1 10.0.0.101/16
9-21
10.0.0.21
0.0.0.0
NE21 9-24
9-22
129.9.0.22 129.9.0.24
0.0.0.0 0.0.0.0
NE22 9-23
NE24
129.9.0.23
0.0.0.0
Extended ID-Basic ID
NE23 IP address
Gateway
NOTE
Precautions
If the NE ID and the values of NE communication parameters are changed and the logical boards
are configured in the NE commissioning process, skip the operations.
Procedure
Step 1 See A.2.1.1 Creating NEs by Using the Search Method and create the NEs.
Parameter Value
Domain 129.9.255.255
NOTE
In this configuration example, it is assumed that the IP address of the GNE is not changed manually and the IP
addresses of the non-GNEs are not known. Hence, you need to search for and create the NEs by using the
129.9.255.255 network segment as the search domain. If the IP address of the GNE is known, it is recommended
that you use the IP address of the GNE as the search domain.
Normally, NE21 to NE24 should be added in the NE list.
Parameter Value
Password password
Parameter Value
New ID 21 22 23 24
New Extended 9 (default value) 9 (default value) 9 (default value) 9 (default value)
ID
Step 4 See A.2.1.4 Configuring the Logical Board and configure logical boards.
Configure the logical boards according to the mapping relations between the physical boards
and logical boards.
Step 5 See A.2.4.1 Setting NE Communication Parameters and set the NE communication
parameters.
Parameter Value
NE21
IP 10.0.0.21
Extended ID 9
NOTE
The IP addresses of all the NEs, except NE21, are in the interlocking relations with the NE IDs. Hence, you
need not change the values of the NE communication parameters manually.
Step 6 See A.2.4.8 Configuring Extended ECC Communication and disable the automatic extended
ECC function for the gateway NE (NE21).
Step 7 See A.2.1.8 Synchronizing the NE Time and synchronize the NE time.
Parameter Value
Synchronous Mode NM
Period(days) 1
----End
Figure 5-7 shows a Hybrid radio chain network configured according to the following
requirements.
l The Hybrid radio chain network is comprised of the OptiX RTN equipment managed by
the Web LCT connected to the packet network.
l All NEs on the Hybrid radio chain network are non-GNEs with an access to the Web
LCT through the packet network.
l The Hybrid radio chain network receives various base station services and transmits them
to the packet network through NE11.
l NE12 and NE13 are interconnected through cascading ports.
NOTE
For details on configuration of NE11, see 5.7 Configuration Example (Packet Network).
R4 FE
BTS12
E1+GE+
NE cascade
E1 NE14
R99 Packet network
BTS13 FE
NE13 NE12 NE11
R4
E1 BTS11
FE NE15
NE16
R99
R4
BTS14
BTS15
Figure 5-8 Allocated IDs and IP addresses (Hybrid radio chain network)
9-14
129.9.0.14
0.0.0.0
NE14 9-13 9-12
129.9.0.13 129.9.0.12
0.0.0.0 0.0.0.0 Packet
network
NE13 NE12
9-15 NE11
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
NOTE
Precautions
If the NE ID and the values of NE communication parameters are changed and the logical boards
are configured in the NE commissioning process, skip the operations.
Procedure
Step 1 See A.2.1.1 Creating NEs by Using the Search Method and create the NEs.
The values for the related parameters are provided as follows.
Parameter Value
Domain 129.9.255.255
NOTE
In this configuration example, it is assumed that the IP address of the GNE has not been changed manually and
that the IP addresses of the non-GNEs are not known. Hence, you need to search for and create the NEs by using
the 129.9.255.255 network segment as the search domain. If the IP address of the GNE is known, it is
recommended that you use the IP address of the GNE as the search domain.
Normally, NE12 to NE16 should be added in the NE list.
Step 2 See A.2.1.3 Logging In to an NE and log in to the NE.
The values for the related parameters are provided as follows.
Parameter Value
Password password
Parameter Value
New ID 12 13 14 15 16
Step 4 See A.2.1.4 Configuring the Logical Board and configure logical boards.
Configure the logical boards according to the mapping relationships between the physical boards
and logical boards.
Step 5 See A.2.4.6 Setting Parameters of Inband DCN and enable/disable the inband DCN at the
ports.
The values for the related parameters of NE12 to NE16 are provided as follows.
Parameter Value
All Ports
Step 6 See A.2.1.8 Synchronizing the NE Time and synchronize the NE time.
The values for the related parameters are provided as follows.
Parameter Value
Synchronous Mode NM
Period(days) 1
----End
l The Hybrid radio ring network is comprised of the OptiX RTN equipment managed by the
Web LCT connected to the packet network.
l All NEs on the Hybrid radio ring network are non-GNEs with an access to the Web LCT
through the packet network.
l The Hybrid radio ring network receives various base station services and transmits them
to the packet network through NE21.
NOTE
For details on configuration of NE21, see 5.7 Configuration Example (Packet Network).
Packet network
NE21
R4 FE
BTS21 FE
R4
E1 NE22 NE24 BTS24
BTS22
FE
NE23
R4
BTS23
l All NEs except NE21 adopt HWECC for DCN communication. In HWECC mode, NEs
use DCC channels in radio signals for DCN communication.
l NEs numbered 22 to 24 are not connected to the packet network. Therefore, to improve
bandwidth utilization, the inband DCN function is disabled at all ports of these NEs.
l Figure 5-10 shows the ID and IP address that are allocated to each NE according to the
uniform DCN planning information.
Figure 5-10 Allocated IDs and IP addresses (Hybrid radio ring network)
Packet network
NE21 9-24
9-22
129.9.0.22 129.9.0.24
0.0.0.0 0.0.0.0
NOTE
Precautions
If the NE ID and the values of NE communication parameters are changed and the logical boards
are configured in the NE commissioning process, skip the operations.
Procedure
Step 1 See A.2.1.1 Creating NEs by Using the Search Method and create the NEs.
Parameter Value
Domain 129.9.255.255
NOTE
In this configuration example, it is assumed that the IP address of the GNE has not been changed manually and
that the IP addresses of the non-GNEs are not known. Hence, you need to search for and create the NEs by using
the 129.9.255.255 network segment as the search domain. If the IP address of the GNE is known, it is
recommended that you use the IP address of the GNE as the search domain.
Normally, NE22 to NE24 should be added in the NE list.
Parameter Value
Password password
Parameter Value
New ID 22 23 24
Step 4 See A.2.1.4 Configuring the Logical Board and configure logical boards.
Configure the logical boards according to the mapping relationships between the physical boards
and logical boards.
The values for the related parameters of NE22 to NE24 are provided as follows.
Parameter Value
All Ports
Step 6 See A.2.1.8 Synchronizing the NE Time and synchronize the NE time.
Parameter Value
Synchronous Mode NM
Parameter Value
Period(days) 1
----End
Figure 5-11 shows a packet network configured according to the following requirements.
l The packet network receives various base station services and the base station backhaul
services converged from a Hybrid radio chain network and a Hybrid radio ring network.
l The packet network is comprised of the OptiX RTN equipment managed by the Web
LCT.
NOTE
NE31 is an OptiX PTN NE in an actual network because it does not support any radio links. In this
example, NE31 is an IDU.
l The Web LCT is connected to NE31 by using a network cable. Therefore, NE31 serves as
a GNE and the other NEs are non-GNEs with an access to the Web LCT through NE31.
l The NEs on the packet ring are interconnected through GE fiber links. The NEs on the
packet chain are interconnected through Packet radio links.
FE
BTS31
R4
BTS32
E1 E1 R4
FE
R99
BTS34 GE GE
NE32
Hybrid radio chain
NE11 NE31 NMS
network
E1
GE
NE21 GE
E1
E1
E1
+G
BSC
E
BTS36 BTS35 Hybrid radio ring
network R99 R99
BTS37 BTS38
RNC
The connections of DCN links shown in Figure 5-11 are described as follows.
Between NE32 and NE33 3-ISU2-1 (main IF board of a Transmits services on the
1+1 HSB protection group) packet chain.
Between NE33 and NE32 4-ISU2-1 (main IF board of a Transmits services on the
1+1 HSB protection group) packet chain.
l Service channels are used for communication because NEs on the packet ring are
interconnected through GE fiber links. For the convenience of maintenance, inband DCN
is adopted on the packet ring and the packet chain.
l Plan the channel for inband DCN.
– On the packet ring, the inband DCN function needs to be enabled at Ethernet ports of
all NEs and be disabled at other ports.
– On the packet chain, the inband DCN function needs to be enabled at microwave ports
of all NEs and be disabled at other ports.
l Plan the management VLAN ID and bandwidth of inband DCN for each NE.
– The management VLAN ID takes the default value 4094.
– If the number of NEs is not greater than 50, set the bandwidth of the inband DCN to
512 kbit/s (default value).
l To facilitate interconnection with equipment that does not support HWECC, plane inband
DCN channels to use the default IP protocol.
l The extended ECC function needs to be disabled on the GNE, namely, NE31.
l Figure 5-12 shows the ID and IP address that are allocated to each NE according to the
uniform DCN planning information.
NE11 NE31
9-21
GE
10.0.0.103/16
GE 129.9.0.21
0.0.0.0
NE21
Hybrid Radio
Network
Extended ID-Basic ID
IP address
Gateway
NOTE
Precautions
If the NE ID and the values of NE communication parameters are changed and the logical boards
are configured in the NE commissioning process, skip the operations.
Procedure
Step 1 See A.2.1.1 Creating NEs by Using the Search Method and create the NEs.
Parameter Value
Domain 129.9.255.255
NOTE
In this configuration example, it is assumed that the IP address of the GNE has not been changed manually and
that the IP addresses of the non-GNEs are not known. Hence, you need to search for and create the NEs by using
the 129.9.255.255 network segment as the search domain. If the IP address of the GNE is known, it is
recommended that you use the IP address of the GNE as the search domain.
Normally, NE31 to NE34, NE11, and NE21 should be added in the NE list.
Parameter Value
Password password
Paramete Value
r
NE31 NE32 NE33 NE34 NE11 NE21
New ID 31 32 33 34 11 21
Step 4 See A.2.1.4 Configuring the Logical Board and configure logical boards.
Configure the logical boards according to the mapping relationships between the physical boards
and logical boards.
Step 5 See A.2.4.1 Setting NE Communication Parameters and set the NE communication
parameters.
Parameter Value
NE31
IP 10.0.0.31
Extended ID 9
NOTE
The IP addresses of all the NEs, except NE31, are in the interlocking relationships with the NE IDs. Hence, you
need not change the values of the NE communication parameters manually.
Step 6 See A.2.4.8 Configuring Extended ECC Communication and disable the automatic extended
ECC function for the gateway NE (NE31).
Step 7 See A.2.4.6 Setting Parameters of Inband DCN and configure the extended ECC.
The values for the related parameters of NE31 are provided as follows.
Parameter Value
The values for the related parameters of NE32 are provided as follows.
Parameter Value
The values for the related parameters of NE33 are provided as follows.
Parameter Value
The values for the related parameters of NE34 are provided as follows.
Parameter Value
The values for the related parameters of NE11 are provided as follows.
Parameter Value
The values for the related parameters of NE21 are provided as follows.
Parameter Value
Step 8 See A.2.1.8 Synchronizing the NE Time and synchronize the NE time.
Parameter Value
Synchronous Mode NM
Period(days) 1
----End
Before configuring services on a radio link, you need to configure the radio link.
6.3 Configuration Example (Radio Links on the TDM Radio Chain Network)
This section considers radio links on a TDM radio chain network as examples to describe how
to configure radio links according to the planning information.
6.4 Configuration Example (Radio Links on the TDM Radio Ring Network)
This section considers TDM radio links on a TDM radio ring network as examples to describe
how to configure radio links according to the network planning information.
6.5 Configuration Example (Radio Links on the Hybrid Radio Chain Network)
This section considers radio links on a Hybrid radio chain network as examples to describe how
to configure radio links according to the network planning information.
6.6 Configuration Example (Radio Links on the Hybrid Radio Ring Network)
This section considers radio links on a Hybrid radio ring network as examples to describe how
to configure radio links according to the network planning information.
When the AM technology is adopted, in the case of the same channel spacing, the microwave
service bandwidth varies according to the modulation scheme; the higher the modulation
efficiency, the higher the bandwidth of the transmitted services.
l When the channel quality is good (such as on days when weather conditions are favorable),
the equipment adopts a high-efficiency modulation scheme to transmit more user services.
This improves transmission efficiency and spectrum utilization of the system.
l When the channel quality deteriorates (such as on days with adverse weather), the
equipment adopts a low-efficiency modulation scheme to transmit only higher-priority
services within the available bandwidth while discarding lower-priority services. This
method improves anti-interference capabilities of the radio link, which helps ensure the
link availability for higher-priority services.
In Integrated IP radio mode, the equipment supports the AM technology. With configurable
priorities for E1 services and packet services, the transmission is controlled based on the service
bandwidth and QoS policies corresponding to the current modulation scheme. The highest-
priority services are transmitted with precedence.
NOTE
In Integrated IP radio mode, when the equipment transmits STM-1 services and packet services at the same
time, STM-1 services have highest priority and their transmission is ensured.
l Priorities of E1 services
The priorities of E1 services are assigned based on the number of E1 services that each
modulation scheme can transmit. When modulation scheme switching occurs, only the E1
services whose number is specified in the new modulation scheme can be transmitted and
the excess E1 services are discarded.
l Priorities of packet services
With the QoS technology, packet services are scheduled to queues with different priorities.
The services in different queues are transmitted to the microwave port after running the
queue scheduling algorithm. When modulation scheme switching occurs, certain queues
may be congested due to insufficient capacity at the air interface. As a result, certain services
or all the services in these queues are discarded.
Figure 6-1 shows the change in services brought by the AM technology. The orange part
indicates E1 services. The blue part indicates packet services. The closer the service is to the
outside of the cylinder in the figure, the lower the service priority. Under all channel conditions,
the service capacity varies according to the modulation scheme. When the channel conditions
are unfavorable (during adverse weather conditions), lower-priority services are discarded.
256QAM
128QAM
64QAM
32QAM
16QAM
QPSK
16QAM
Channel
Capability 32QAM
64QAM
128QAM
E1 Services
256QAM
Ethernet
Services
The AM technology used by the OptiX RTN 950 has the following characteristics:
l The AM technology uses the QPSK, 16QAM, 32QAM, 64QAM, 128QAM, and 256QAM
modulation schemes.
l The lowest-efficiency modulation scheme (also called reference scheme or modulation
scheme of guaranteed capacity) and the highest-efficiency modulation scheme (also called
nominal scheme or modulation scheme of full capacity) used by the AM can be configured.
l In AM, when modulation schemes are switched, the transmit frequency, receive frequency,
and channel spacing remain unchanged.
l In AM, modulation schemes are switched step-by-step.
l In AM, modulation scheme switching is hitless. When the modulation scheme is
downshifted, high-priority services will not be affected when low-priority services are
discarded. The switching is successful even when 100 dB/s channel fast fading occurs.
The capacity in CCDP transmission mode is twice the capacity in single-polarized transmission
mode.
The ideal situation of CCDP transmission is that no interference exists between the two
orthogonal signals that operate at the same frequency, and then the receiver can easily recover
the two signals. In actual engineering conditions, however, regardless of the orthogonality of
the two signals, certain interference between the signals exists, due to cross-polarization
discrimination (XPD) of the antenna and channel deterioration. To cancel the interference, the
XPIC technology is used to receive and process the signals in the horizontal and vertical
directions so that the original signals are recovered.
XPIC Configuration
The XPIC adopts both the horizontally polarized wave and the vertically polarized wave over
one channel to transmit two channels of signals. The radio link capacity in XPIC configuration
is double the radio link capacity in 1+0 configuration.
The OptiX RTN 950 only supports the XPIC configuration for Integrated IP radio.
6.1.4 PLA
Physical link aggregation (PLA) aggregates all Ethernet bandwidths in several Integrated IP
radio links between two NEs into a logical Ethernet path for higher Ethernet bandwidth. Using
PLA can effectively improve the bandwidth and reliability for transmitting Ethernet services
over Integrated IP radio links.
As shown in Figure 6-4, PLA allows all Ethernet transmission paths in several Integrated IP
radio links connected to the same equipment to be aggregated as a PLA group. For MAC users,
a PLA group works as a single link.
NOTE
Native TDM services on the Integrated IP radio links are irrelevant to the PLA.
Different from air-interface LAG, PLA dynamically allocates Ethernet traffic based on the real–
time Ethernet bandwidth over each member radio link to achieve almost the same Ethernet
bandwidth utilization on member radio links. Except being free from impacts of the Ethernet
frame type and packet length, the load sharing mechanism used by PLA even does not require
the same Ethernet bandwidth on radio links involved. Moreover, this load sharing mechanism
is also able to ensure almost the same Ethernet bandwidth utilization on member links when the
Ethernet bandwidth changes differently on each member link.
Radio link 2
PLA helps to improve Ethernet service bandwidth utilization and reliability in integrated IP radio
mode when air-interface LAG does not apply (for example, when member radio links provide
different Ethernet bandwidths or the load sharing algorithm used by air-interface LAG cannot
implement load balancing between member radio links).
NOTE
l The member links in a PLA group must be carried by the same type of IF board (ISU2 or ISX2).
l In the current version, PLA aggregates only two links, which means that a PLA group can contain only one
main port and one slave port. The IF boards where the main and slave ports are located must be installed in
two paired slots.
Configure IF
Configure IF 1+1
1+1 Configure AM attributes
Configure IF/ODU Configure IF/ODU
protection
protection for XPIC function
information for radio links information for radio links
End
Configure N+1 protection Configure AM advanced
Configure ODU power
attributes
attributes
Compulsory End
Optional
Procedure for Configuring TDM Radio Links (with the XPIC Function Enabled)
Table 6-1 Procedure for configuring TDM radio links (with the XPIC function enabled)
Operation Description
A.3.4 Configuring the IF/ For the ISX2, set IF Service Type for the IF boards in both
ODU Information of a the vertically and horizontally polarized directions of an XPIC
Radio Link workgroup according to the plan.
NOTE
The default value of IF Service Type is Hybrid(Native E1+ETH).
Operation Description
A.3.1 Creating an IF 1+1 Required when two XPIC workgroups need to form two IF 1
Protection Group +1 protection groups.
Set the parameters according to the network plan.
NOTE
One XPIC workgroup cannot form an IF 1+1 protection group. The
radio link in the horizontal/vertical polarization direction of the XPIC
workgroup can form an IF 1+1 protection group with the radio link in
the horizontal/vertical polarization direction of the other XPIC
workgroup.
NOTE
l During the site commissioning, you can configure the two XPIC links as two separate non-XPIC links.
l The preceding parameters need to be set to the same values, separately for the radio links in the vertical and
horizontal polarization directions.
l For radio links configured with 1+1 HSB/SD, you need to configure the IF and ODU information on the
main radio link only. For radio links configured with 1+1 FD, you need to configure the IF and ODU
information on the main radio link and the ODU information on the standby radio link.
Procedure for Configuring TDM Radio Links (with the XPIC Function Disabled)
Table 6-2 Procedure for configuring TDM radio links (with the XPIC function disabled)
Operation Description
A.3.4 Configuring the IF/ For the ISU2 and ISX2, set IF Service Type to SDH.
ODU Information of a NOTE
Radio Link The default value of IF Service Type is Hybrid(Native E1+ETH).
Operation Description
A.3.1 Creating an IF 1+1 Required when the radio links are configured with 1+1
Protection Groupa protection.
Set the parameters according to the network plan.
A.6.8.2 Configuring ATPC Required when the ATPC function needs to be used.
Attributesa l If the ATPC function needs to be used, set ATPC Enable
Status to Enabled.
l During site commissioning, set ATPC Enable Status to
Disabled.
l It is recommended that you set ATPC Upper Threshold
(dBm) to the central value plus 10 dB.
l It is recommended that you set ATPC Lower Threshold
(dBm) to the central value minus 10 dB.
l It is recommended that you set ATPC Automatic
Threshold Enable Status to Disabled.
Operation Description
A.3.6 Creating an N+1 Required when the radio links are configured with N+1
Protection Group protection.
Set the attributes of the N+1 protection group to the same
values for the equipment at both ends.
Set the parameters according to the network plan.
NOTE
l a: Generally, during the site commissioning, the previous steps are completed. After the site commissioning,
however, you need to reset ATPC Enable Status.
l For radio links configured with 1+1 HSB/SD, you need to configure the IF and ODU information on the
main radio link only. For radio links configured with 1+1 FD, you need to configure the IF and ODU
information on the main radio link and the ODU information on the standby radio link.
l For TDM radio links configured with N+1 protection, you need to configure the IF and ODU information
on each link. Working Mode must be configured as 7, STM-1, 28MHz, 128QAM.
Procedure for Configuring Integrated IP radio Links (with the XPIC Function
Enabled)
Table 6-3 Procedure for configuring Integrated IP radio links (with the XPIC function enabled)
Operation Description
A.3.4 Configuring the IF/ODU For the ISX2, set IF Service Type for the IF boards in
Information of a Radio Link both the vertically and horizontally polarized
directions of an XPIC workgroup according to the plan.
NOTE
The default value of IF Service Type is Hybrid(Native E1
+ETH).
A.3.1 Creating an IF 1+1 Required when two XPIC workgroups need to form
Protection Group two IF 1+1 protection groups.
Set the parameters according to the network plan.
NOTE
One XPIC workgroup cannot form an IF 1+1 protection
group. The radio link in the horizontal/vertical polarization
direction of the XPIC workgroup can form an IF 1+1
protection group with the radio link in the horizontal/vertical
polarization direction of the other XPIC workgroup.
Operation Description
Operation Description
NOTE
l During the site commissioning, you can configure the two XPIC links as two separate non-XPIC links
according to Table 6-4.
l The preceding parameters need to be set to the same values, separately for the radio links in the vertical and
horizontal polarization directions.
l For radio links configured with 1+1 HSB/SD, you need to configure the IF and ODU information on the
main radio link only. For radio links configured with 1+1 FD, you need to configure the IF and ODU
information on the main radio link and the ODU information on the standby radio link.
l The MW_CFG_MISMATCH alarm is reported if the E1 count, AM enabled status, 1588 timeslot enabled
status, modulation scheme, or STM-1 count is set inconsistently for both ends of an Integrated IP radio link.
Clear this alarm immediately. Otherwise, service configurations may be applied unsuccessfully or services
may be interrupted.
Procedure for Configuring Integrated IP radio links (with the XPIC Function
Disabled)
Table 6-4 Procedure for configuring Integrated IP radio links (with the XPIC function disabled)
Operation Description
A.3.4 Configuring the IF/ODU For the ISU2 and ISX2, set IF Service Type
Information of a Radio Link according to the plan.
NOTE
The default value of IF Service Type is Hybrid(Native
E1+ETH).
A.3.1 Creating an IF 1+1 Protection Required when the radio links are configured with
Groupa IF 1+1 protection.
Set the parameters according to the network plan.
Operation Description
Operation Description
A.6.8.2 Configuring ATPC Attributesa Required when the ATPC function needs to be
used.
l If the ATPC function needs to be used, set
ATPC Enable Status to Enabled.
l During site commissioning, set ATPC Enable
Status to Disabled.
l It is recommended that you set ATPC Upper
Threshold(dBm) to the central value plus 10
dB.
l It is recommended that you set ATPC Lower
Threshold(dBm) to the central value minus
10 dB.
l It is recommended that you set ATPC
Automatic Threshold Enable Status to
Disabled.
Operation Description
Configuring A.3.12 Creating a Required when the ISU2/ISX2 needs to use the
PLA PLA Group PLA feature.
Set PLA-associated parameters according to the
network plan.
NOTE
l In V100R003C03, PLA aggregates only two links,
which means that a PLA group can contain only one
main port and one slave port. The IF boards where
the main and slave ports are located must be
installed in two paired slots.
l IF boards are reset (cold) during creation or deletion
of a PLA group.
l PLA can work together with adaptive modulation
(AM). Member links in a PLA group can use
different Hybrid/AM attributes and modulation
modes.
l Native TDM services in Integrated IP radio links
are irrelevant to the PLA group consisting of the
Integrated IP radio links, and need to be configured
separately on the Integrated IP radio links.
A.3.6 Creating an N+1 Protection Required when the radio links are configured with
Group N+1 protection.
Set the attributes of the N+1 protection group to
the same values for the equipment at both ends.
Set the parameters according to the network plan.
NOTE
l a: Generally, during the site commissioning, the previous steps are completed. After the site commissioning,
however, you need to reset AM Status and ATPC Enable Status.
l For radio links configured with 1+1 HSB/SD, you need to configure the IF and ODU information on the
main radio link only. For radio links configured with 1+1 FD, you need to configure the IF and ODU
information on the main radio link and the ODU information on the standby radio link.
l To configure Integrated IP radio links with N+1 protection, you need to configure the IF and ODU
information on each link.
l The MW_CFG_MISMATCH alarm is reported if the E1 count, AM enabled status, 1588 timeslot enabled
status, modulation mode, or STM-1 count is set inconsistently for both ends of an Integrated IP radio link.
Clear this alarm immediately. Otherwise, service configurations may be applied unsuccessfully or services
may be interrupted.
Number of 16 8 8 14 8
E1 services
l To improve transmission reliability of important services, the radio links between NE11
and NE12, between NE13 and NE14, and between NE13 and NE15 are configured with 1
+1 HSB protection.
l The ATPC function is enabled to reduce inter-site interference.
The connections of radio links shown in Figure 6-6 are described as follows.
Between NE11 and NE12 3-IF1 (main IF board) Configure the ports as a 1+1
HSB protection group.
5-IF1 (standby IF board)
Between NE12 and NE11 3-IF1 (main IF board) Configure the ports as a 1+1
HSB protection group.
5-IF1 (standby IF board)
Between NE13 and NE14 3-IF1 (main IF board) Configure the ports as a 1+1
HSB protection group.
5-IF1 (standby IF board)
Between NE13 and NE15 4-IF1 (main IF board) Configure the ports as a 1+1
HSB protection group.
6-IF1 (standby IF board)
Between NE14 and NE13 3-IF1 (main IF board) Configure the ports as a 1+1
HSB protection group.
5-IF1 (standby IF board)
Between NE15 and NE13 4-IF1 (main IF board) Configure the ports as a 1+1
HSB protection group.
6-IF1 (standby IF board)
NOTE
l To prevent interference on a microwave site, it is recommended that you plan the microwave site as
only a TX high site or a TX low site at a time.
l To prevent interference between two radio links on a microwave site that use transmit frequencies with
a small spacing between, it is recommended that you set the two radio links to operate in different
polarization directions.
l The planning information that is not related to the configuration of the IDU (except for the polarization
direction) is not provided in this example.
Receive power -42 (NE11) -44 (NE13) -43 (NE13) -48 (NE15)
(dBm) -42 (NE12) -44 (NE14) -43 (NE15) -48 (NE16)
Upper threshold -32 (NE11) -34 (NE13) -33 (NE13) -38 (NE15)
of ATPC -32 (NE12) -34 (NE14) -33 (NE15) -38 (NE16)
adjustment
(dBm)
Lower threshold -52 (NE11) -54 (NE13) -53 (NE13) -58 (NE15)
of ATPC -52 (NE12) -54 (NE14) -53 (NE15) -58 (NE16)
adjustment
(dBm)
Maximum - - - -
transmit power
(dBm)
NOTE
l In this example, the ATPC is enabled to reduce the inter-site interference. The ATPC may be disabled if
there is no such a requirement.
l The ATPC controls the receive power within a range, namely, (2 dB more or less than the central value
between the upper threshold and lower threshold of ATPC adjustment). Hence, this example sets the upper
threshold to 10 dB higher than the receive power, and the lower threshold is 10 dB lower than the receive
power.
l The maximum transmit power is the actual maximum transmit power of the ODU after the ATPC is enabled.
When this parameter is not specified, the value of the parameter is the rated maximum transmit power of
the ODU. If the ODU works at the rated maximum transmit power, the electromagnetic wave agrees with
the spectrum configuration profile. Hence, this parameter is not set generally.
Information of IF Boards
According to the radio type, slot priorities of IF boards, and configuration rules of the 1+1
protection, you can obtain the information of IF boards as provided in Table 6-14.
Main IF board 3-IF1 (NE11) 3-IF1 (NE13) 4-IF1 (NE13) 3-IF1 (NE15)
3-IF1 (NE12) 3-IF1 (NE14) 4-IF1 (NE15) 3-IF1 (NE16)
NOTE
l It is recommended that you configure the two IF boards that construct the 1+1 HSB protection group in slot
3 and slot 5, slot 4 and slot 6, or slot 1 and slot 2. In addition, it is recommended that you configure the main
IF board in the slot with the smaller slot number.
l It is recommended that you configure the two IF boards that construct the 1+1 FD/SD protection group in
slot 3 and slot 5, slot 4 and slot 6, or slot 1 and slot 2. In addition, it is recommended that you configure the
main IF board in the slot with the smaller slot number.
l In 1+1 HSB configuration, it is recommended that you disable the reverse switching function. In 1+1 SD
configuration, it is recommended that you enable the reverse switching function.
l Unless otherwise specified, it is recommended that alarms be reported by protection group.
l Unless otherwise specified the other parameters of the 1+1 HSB/FD/SD all take default values.
Procedure
Step 1 See A.3.1 Creating an IF 1+1 Protection Group and create the IF 1+1 protection groups for
NE11 to NE15.
l The values for the relevant parameters of NE11 are provided as follows.
Parameter Value
NE11
l The values for the relevant parameters of NE12 are provided as follows.
Parameter Value
NE12
Parameter Value
NE12
l The values for the relevant parameters of NE13 are provided as follows.
Parameter Value
NE13
l The values for the relevant parameters of NE14 are provided as follows.
Parameter Value
NE14
Parameter Value
NE14
l The values for the relevant parameters of NE15 are provided as follows.
Parameter Value
NE15
Step 2 See A.3.4 Configuring the IF/ODU Information of a Radio Link and configure the IF/ODU
information of the radio link.
l The values for the relevant parameters of NE11 are provided as follows.
Parameter Value
Link ID 101
TX Frequency(MHz) 14930
TX Power(dBm) 5
TX Status unmute
l The values for the relevant parameters of NE12 are provided as follows.
Parameter Value
Link ID 101
TX Frequency(MHz) 14510
TX Power(dBm) 5
TX Status unmute
l The values for the relevant parameters of NE13 are provided as follows.
Parameter Value
TX Power(dBm) 10 10
l The values for the relevant parameters of NE14 are provided as follows.
Parameter Value
Link ID 102
TX Frequency(MHz) 14952
TX Power(dBm) 10
Parameter Value
TX Status unmute
l The values for the relevant parameters of NE15 are provided as follows.
Parameter Value
TX Power(dBm) 15 10
l The values for the relevant parameters of NE16 are provided as follows.
Parameter Value
Link ID 104
TX Frequency(MHz) 14510
TX Power(dBm) 15
TX Status unmute
Step 3 See A.6.8.2 Configuring ATPC Attributes and configure the ATPC function.
l The values for the relevant parameters of NE11 are provided as follows.
Parameter Value
Parameter Value
l The values for the relevant parameters of NE12 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE13 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE14 are provided as follows.
Parameter Value
Parameter Value
l The values for the relevant parameters of NE15 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE16 are provided as follows.
Parameter Value
----End
Based on 5.4 Configuration Example (TDM Radio Ring Network Topology), configure the
TDM radio links according to the network planning information (as shown in Figure 6-7):
Number of E1 4 4 4 4
services
l To improve transmission reliability of important services, the radio links between NE21
and NE24 are configured with 1+1 SD protection.
l The ATPC function is enabled to reduce inter-site interference.
Third party
SDH network
201 204
14930M 14958M
14510M 14538M
16E1,14M,16QAM NE21 16E1,14M,16QAM
1+0 1+1
V-polarzation V-polarization
Tx high Tx high
Tx low Tx low
BTS21
Tx low Tx low
NE22 NE24 BTS24
Tx high Tx high
BTS22 202 203
14958M 14930M
14538M 14510M
16E1,14M,16QAM 4E1 16E1,14M,16QAM
1+0 1+0
H-polarization NE23 H-polarzation
BTS23
Link ID
Tx high station Tx Freq.
Tx low station Tx Freq.
Radio work mode
RF configuarion
Polarization
The connections of radio links shown in Figure 6-7 are described as follows.
Between NE21 and NE24 3-IF1 (main IF board) Configure the ports as a 1+1
SD protection group.
5-IF1 (standby IF board)
Between NE24 and NE21 4-IF1 (main IF board) Configure the ports as a 1+1
HSB protection group.
6-IF1 (standby IF board)
Radio working 16E1, 14MHz, 16E1, 14MHz, 16E1, 14MHz, 16E1, 14MHz,
mode 16QAM 16QAM 16QAM 16QAM
NOTE
The planning information that is not related to the configuration of the IDU (except for the polarization
direction) is not provided in this example.
Receive power -46 (NE21) -44 (NE23) -43 (NE23) -47 (NE21)
(dBm) -46 (NE22) -44 (NE22) -43 (NE24) -47 (NE24)
Upper threshold -36 (NE21) -34 (NE23) -33 (NE23) -37 (NE21)
of ATPC -36 (NE22) -34 (NE22) -33 (NE24) -37 (NE24)
adjustment
(dBm)
Lower threshold -56 (NE21) -54 (NE23) -53 (NE23) -57 (NE21)
of ATPC -56 (NE22) -54 (NE22) -53 (NE24) -57 (NE24)
adjustment
(dBm)
Maximum - - - -
transmit power
(dBm)
NOTE
l In this example, the ATPC is enabled to reduce the inter-site interference. The ATPC may be disabled if
there is no such a requirement.
l The ATPC controls the receive power within a range, namely, (2 dB more or less than the central value of
the upper threshold and lower threshold of ATPC adjustment). Hence, this example sets the upper threshold
to 10 dB higher than the receive power, and the lower threshold is 10 dB lower than the receive power.
l The maximum transmit power is the actual maximum transmit power of the ODU after the ATPC is enabled.
When this parameter is not specified, the value of the parameter is the rated maximum transmit power of
the ODU. If the ODU works at the rated maximum transmit power, the electromagnetic wave agrees with
the spectrum configuration profile. Hence, this parameter is not set generally.
Main IF board 4-IF1 (NE21) 4-IF1 (NE22) 4-IF1 (NE23) 4-IF1 (NE24)
3-IF1 (NE22) 3-IF1 (NE23) 3-IF1 (NE24) 3-IF1 (NE21)
Reverse - - - Enabled
switching
enabling
NOTE
l It is recommended that you configure the two IF boards that construct the 1+1 HSB protection group in slot
3 and slot 5, slot 4 and slot 6, or slot 1 and slot 2. In addition, it is recommended that you configure the main
IF board in the slot with the smaller slot number.
l It is recommended that you configure the two IF boards that construct the 1+1 FD/SD protection group in
slot 3 and slot 5, slot 4 and slot 6, or slot 1 and slot 2. In addition, it is recommended that you configure the
main IF board in the slot with the smaller slot number.
l In 1+1 HSB configuration, it is recommended that you disable the reverse switching function. In 1+1 SD
configuration, it is recommended that you enable the reverse switching function.
l Unless otherwise specified, it is recommended that alarms be reported by protection group.
l Unless otherwise specified, the other parameters of the 1+1 HSB/FD/SD all take default values.
Procedure
Step 1 See A.3.1 Creating an IF 1+1 Protection Group and configure the 1+1 protection groups for
NE21 and NE24.
l The values for the relevant parameters of NE21 are provided as follows.
Parameter Value
NE21
Working Mode SD
l The values for the relevant parameters of NE24 are provided as follows.
Parameter Value
NE24
Working Mode SD
Step 2 See A.3.4 Configuring the IF/ODU Information of a Radio Link and configure the IF/ODU
information of the radio link.
l The values for the relevant parameters of NE21 are provided as follows.
Parameter Value
Parameter Value
TX Power(dBm) 8 9
l The values for the relevant parameters of NE22 are provided as follows.
Parameter Value
TX Power(dBm) 9 10
l The values for the relevant parameters of NE23 are provided as follows.
Parameter Value
TX Power(dBm) 10 10
l The values for the relevant parameters of NE24 are provided as follows.
Parameter Value
TX Power(dBm) 10 8
Step 3 See A.6.8.2 Configuring ATPC Attributes and configure the ATPC function.
l The values for the relevant parameters of NE21 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE22 are provided as follows.
Parameter Value
Parameter Value
l The values for the relevant parameters of NE23 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE24 are provided as follows.
Parameter Value
----End
Based on 5.5 Configuration Example (Hybrid Radio Chain Network), configure the Hybrid
radio links according to the following network planning information (as shown in Figure 6-8):
l Each Hybrid radio link transmits E1 services and Ethernet services. The AM function is
enabled on each link.
l To improve transmission reliability of important services, the radio links between NE11
and NE12, between NE13 and NE14, and between NE13 and NE15 are configured with 1
+1 HSB protection.
l The service capacity accessed by each BTS is provided in Table 6-23.
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 guaranteed with sufficient transmission resources and are not discarded even in
the case of an AM switch. Low-priority services are not guaranteed with sufficient transmission resources
and may be discarded in the case of an AM switch. The common service priorities are provided in Table
6-24.
ATM E1s (IMA E1s are not used) that High-priority services
transmit 3G base station services
The connections of radio links shown in Figure 6-8 are described as follows.
Between NE11 and NE12 3-ISU2 (main IF board) Configure the ports as a 1+1
HSB protection group.
5-ISU2 (standby IF board)
Between NE12 and NE11 3-ISU2 (main IF board) Configure the ports as a 1+1
HSB protection group.
5-ISU2 (standby IF board)
Between NE13 and NE14 3-ISU2 (main IF board) Configure the ports as a 1+1
HSB protection group.
5-ISU2 (standby IF board)
Between NE13 and NE15 4-ISU2 (main IF board) Configure the ports as a 1+1
HSB protection group.
6-ISU2 (standby IF board)
Between NE14 and NE13 3-ISU2 (main IF board) Configure the ports as a 1+1
HSB protection group.
5-ISU2 (standby IF board)
Between NE15 and NE13 4-ISU2 (main IF board) Configure the ports as a 1+1
HSB protection group.
6-ISU2 (standby IF board)
Channel 28 14 14 7
spacing (MHz)
NOTE
The planning information that is not related to the configuration of the IDU (except for the polarization
direction) is not provided in this example.
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)
NOTE
The Hybrid radio capacity and the AM function require the proper license file.
Receive power -46 (NE11) -44 (NE13) -43 (NE13) -48 (NE15)
(dBm) -46 (NE12) -44 (NE14) -43 (NE15) -48 (NE16)
ATPC - - - -
automatic
threshold
enabling
Upper threshold - - - -
of ATPC
adjustment
(dBm)
Lower threshold - - - -
of ATPC
adjustment
(dBm)
Maximum - - - -
transmit power
(dBm)
NOTE
Main IF board 3-ISU2 (NE11) 3-ISU2 (NE13) 4-ISU2 (NE13) 3-ISU2 (NE15)
3-ISU2 (NE12) 3-ISU2 (NE14) 4-ISU2 (NE15) 3-ISU2 (NE16)
NOTE
l It is recommended that you configure the two IF boards that construct the 1+1 HSB protection group in slot
3 and slot 5, slot 4 and slot 6, or slot 1 and slot 2. In addition, it is recommended that you configure the main
IF board in the slot with the smaller slot number.
l It is recommended that you configure the two IF boards that construct the 1+1 FD/SD protection group in
slot 3 and slot 5, slot 4 and slot 6, or slot 1 and slot 2. In addition, it is recommended that you configure the
main IF board in the slot with the smaller slot number.
l In 1+1 HSB configuration, it is recommended that you disable the reverse switching function. In 1+1 SD
configuration, it is recommended that you enable the reverse switching function.
l Unless otherwise specified, it is recommended that alarms be reported by protection group.
l Unless otherwise specified the other parameters of the 1+1 HSB/FD/SD all take default values.
Procedure
Step 1 See A.3.1 Creating an IF 1+1 Protection Group and create the IF 1+1 protection groups for
NE11 to NE15.
l The values for the relevant parameters of NE11 are provided as follows.
Parameter Value
NE11
l The values for the relevant parameters of NE12 are provided as follows.
Parameter Value
NE12
l The values for the relevant parameters of NE13 are provided as follows.
Parameter Value
NE13
Parameter Value
NE13
l The values for the relevant parameters of NE14 are provided as follows.
Parameter Value
NE14
l The values for the relevant parameters of NE15 are provided as follows.
Parameter Value
NE15
Step 2 See A.3.4 Configuring the IF/ODU Information of a Radio Link and configure the IF/ODU
information of the radio link.
l The values for the relevant parameters of NE11 are provided as follows.
Parameter Value
Link ID 101
AM Status Enabled
Guarantee E1 Capacity 3
Full E1 Capacity 5
TX Frequency(MHz) 14930
TX Power(dBm) 16.5
TX Status unmute
l The values for the relevant parameters of NE12 are provided as follows.
Parameter Value
Link ID 101
AM Status Enabled
Parameter Value
Guarantee E1 Capacity 3
Full E1 Capacity 5
TX Frequency(MHz) 14510
TX Power(dBm) 16.5
TX Status unmute
l The values for the relevant parameters of NE13 are provided as follows.
Parameter Value
Guarantee E1 Capacity 1 2
Full E1 Capacity 1 4
TX Power(dBm) 16.5 16
Parameter Value
l The values for the relevant parameters of NE14 are provided as follows.
Parameter Value
Link ID 102
AM Status Enabled
Guarantee E1 Capacity 1
Full E1 Capacity -
TX Frequency(MHz) 14952
TX Power(dBm) 16.5
TX Status unmute
l The values for the relevant parameters of NE15 are provided as follows.
Parameter Value
Parameter Value
Guarantee E1 Capacity 0 2
Full E1 Capacity - 4
TX Power(dBm) 20 16
l The values for the relevant parameters of NE16 are provided as follows.
Parameter Value
Link ID 104
IF Channel Bandwidth 7M
AM Status Enabled
Guarantee E1 Capacity 0
Full E1 Capacity -
TX Frequency(MHz) 14510
TX Power(dBm) 20
Parameter Value
TX Status unmute
Parameter Value
l The values for the relevant parameters of NE12 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE13 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE14 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE15 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE16 are provided as follows.
Parameter Value
Step 4 See A.6.8.2 Configuring ATPC Attributes and configure the ATPC function.
l The values for the relevant parameters of NE11 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE12 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE13 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE14 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE15 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE16 are provided as follows.
Parameter Value
----End
Based on 5.6 Configuration Example (Hybrid Radio Ring Network), configure the Hybrid
radio links according to the network planning information (as shown in Figure 6-9):
l Each Hybrid radio link transmits E1 services and Ethernet services. The AM function is
enabled on each link.
l To improve transmission reliability of important services, the radio links between NE21
and NE24 are configured with 1+1 SD protection.
l The service capacity accessed by each BTS is provided in Table 6-35.
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 guaranteed with sufficient transmission resources and are not discarded even in
the case of an AM switch. Low-priority services are not guaranteed with sufficient transmission resources
and may be discarded in the case of an AM switch. The common service priorities are provided in Table
6-36.
ATM E1s (IMA E1s are not used) that High-priority services
transmit 3G base station services
Packet
network
201 204
14930M 14958M
14510M 14538M
14M NE21 14M
1+0 1+1
V-polarzation V-polarization
Tx high Tx high
Tx low Tx low
BTS21
Tx low Tx low
NE22 NE24 BTS24
Tx high Tx high
BTS22 202 203
14958M 14930M
14538M 14510M
14M 4E1 14M
1+0 1+0
H-polarization NE23 H-polarzation
BTS23
Link ID
Tx high station Tx Freq.
Tx low station Tx Freq.
Channel spacing
RF configuarion
Polarization
The connections of radio links shown in Figure 6-9 are described as follows.
Between NE21 and NE24 3-ISU2 (main IF board) Configure the ports as a 1+1
SD protection group.
5-ISU2 (standby IF board)
Between NE24 and NE21 4-ISU2 (main IF board) Configure the ports as a 1+1
SD protection group.
6-ISU2 (standby IF board)
Channel 14 14 14 14
spacing (MHz)
NOTE
The planning information that is not related to the configuration of the IDU (except for the polarization
direction) is not provided in this example.
Number of E1s 2 2 2 2
in 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 low- 40 40 40 40
priority
Ethernet
services (Mbit/
s)
NOTE
l In this example, E1 services are high-priority services and therefore the E1 service priority function
does not need to be enabled.
l According to the Hybrid ring protection scheme, each Hybrid radio link must carry all the services on
the ring.
l The Hybrid radio capacity and the AM function require the appropriate license file.
Receive power -42 (NE21) -44 (NE23) -43 (NE23) -45 (NE21)
(dBm) -42 (NE22) -44 (NE22) -43 (NE24) -45 (NE24)
ATPC - - - -
automatic
threshold
enabling
Upper threshold - - - -
of ATPC
adjustment
(dBm)
Lower threshold - - - -
of ATPC
adjustment
(dBm)
Maximum - - - -
transmit power
(dBm)
NOTE
Main IF board 4-ISU2 (NE21) 4-ISU2 (NE22) 4-ISU2 (NE23) 4-ISU2 (NE24)
3-ISU2 (NE22) 3-ISU2 (NE23) 3-ISU2 (NE24) 3-ISU2 (NE21)
Reverse - - - Enabled
switching
enabling
NOTE
l It is recommended that you configure the two IF boards that construct the 1+1 HSB protection group in slot
3 and slot 5, slot 4 and slot 6, or slot 1 and slot 2. In addition, it is recommended that you configure the main
IF board in the slot with the smaller slot number.
l It is recommended that you configure the two IF boards that construct the 1+1 FD/SD protection group in
slot 3 and slot 5, slot 4 and slot 6, or slot 1 and slot 2. In addition, it is recommended that you configure the
main IF board in the slot with the smaller slot number.
l In 1+1 HSB configuration, it is recommended that you disable the reverse switching function. In 1+1 SD
configuration, it is recommended that you enable the reverse switching function.
l Unless otherwise specified, it is recommended that alarms be reported by protection group.
l Unless otherwise specified, the other parameters of the 1+1 HSB/FD/SD all take default values.
Procedure
Step 1 See A.3.1 Creating an IF 1+1 Protection Group and create the IF 1+1 protection groups for
NE21and NE24.
l The values for the relevant parameters of NE21 are provided as follows.
Parameter Value
NE21
Working Mode SD
Parameter Value
NE21
l The values for the relevant parameters of NE24 are provided as follows.
Parameter Value
NE24
Working Mode SD
Step 2 See A.3.4 Configuring the IF/ODU Information of a Radio Link and configure the IF/ODU
information of the radio link.
l The values for the relevant parameters of NE21 are provided as follows.
Parameter Value
Guarantee E1 Capacity 2 2
Parameter Value
TX Power(dBm) 15 16.5
l The values for the relevant parameters of NE22 are provided as follows.
Parameter Value
Guarantee E1 Capacity 2 2
l The values for the relevant parameters of NE23 are provided as follows.
Parameter Value
Parameter Value
Guarantee E1 Capacity 2 2
TX Power(dBm) 16.5 16
l The values for the relevant parameters of NE24 are provided as follows.
Parameter Value
Guarantee E1 Capacity 2 2
Parameter Value
TX Power(dBm) 15 16
Parameter Value
l The values for the relevant parameters of NE22 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE23 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE24 are provided as follows.
Parameter Value
Step 4 See A.6.8.2 Configuring ATPC Attributes and configure the ATPC function.
l The values for the relevant parameters of NE21 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE22 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE23 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE24 are provided as follows.
Parameter Value
----End
Based on 5.7 Configuration Example (Packet Network), configure radio links according to
the network plan (as shown in Figure 6-10).
Capacity of high- 5 1 4
priority services
(Mbit/s)
Capacity of low- 24 15 4
priority services
(Mbit/s)
NOTE
High-priority services are services that require transmission guarantees. High-priority services cannot 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. Table 6-46 lists common
high-priority services.
ATM E1s (IMA E1s are not used) that High-priority services
transmit 3G base station services
303 301,302
14930M 14967M
14510M 14547M
7M 14M
1+0 XPIC
H- polarzation Dual - polarization
BTS33
PLA
NE34
NE33 NE32
BTS34
BTS32 Link ID
Tx high station Tx Freq.
Tx low station Tx Freq.
Channel spacing
RF configuarion
Polarization
The connections of radio links shown in Figure 6-10 are described as follows.
Between NE32 and NE33 3-ISX2 (main port in the PLA Uses XPIC and provides
group) PLA protection.
NOTE
5-ISX2 (slave port in the The boards where the main and
PLA group) slave ports in the PLA group are
located must be installed in two
paired slots.
Between NE33 and NE2 4-ISX2 (main port in the PLA Uses XPIC and provides
group) PLA protection.
NOTE
6-ISX2 (slave port in the The boards where the main and
PLA group) slave ports in the PLA group are
located must be installed in two
paired slots.
Channel spacing 56 56 7
(MHz)
NOTE
The link plan (except the polarization direction) that is irrelevant to IDU configuration is not provided in
this example.
Capacity of high- 5 5 6
priority services
(Mbit/s)
NOTE
The Hybrid radio capacity and the AM function are available only if the corresponding license files are
configured.
Automatic ATPC - - -
threshold setting
Upper threshold of - - -
ATPC adjustment
(dBm)
Lower threshold of - - -
ATPC adjustment
(dBm)
Maximum transmit - - -
power (dBm)
NOTE
LAG ID 1 1
Procedure
Step 1 Follow instructions in A.3.4 Configuring the IF/ODU Information of a Radio Link and
configure IF/ODU information for radio links.
The values for the IF/ODU parameters of NE32 are provided as follows.
Parameter Value
3-ISX2-1 5-ISX2-1
The values for the IF/ODU parameters of NE33 are provided as follows.
Parameter Value
4-ISX2-1 6-ISX2-1
The values for the IF/ODU parameters of NE33 and NE34 are provided as follows.
IF Channel Bandwidth 7M 7M
Guarantee E1 Capacity 0 0
Full E1 Capacity - -
TX Power(dBm) 20 20
Step 2 Follow instructions in A.3.2 Creating an XPIC Workgroup and create XPIC workgroups for
NE32 and NE33.
Step 3 Follow instructions in A.3.12 Creating a PLA Group and create a PLA group.
The values for the related parameters of NE32 are provided as follows.
Parameter Value
PLA ID 1
Parameter Value
Board 5-ISX2
The values for the related parameters of NE33 are provided as follows.
Parameter Value
PLA ID 1
Board 6-ISX2
Step 4 Follow instructions in A.3.13 Querying the Status of a PLA Group and query the status of the
PLA group.
The values for the related parameters of NE32 and NE23 are provided as follows.
Parameter Value
Parameter Value
3-ISX2 5-ISX2
l The values for the related parameters of NE33 are provided as follows.
Parameter Value
4-ISX2 6-ISX2
l The values for the related parameters of NE34 are provided as follows.
Parameter Value
3-ISU2
Step 6 Follow instructions in A.6.8.2 Configuring ATPC Attributes and set the ATPC function.
l The values for the related parameters of NE32 are provided as follows.
Parameter Value
3-ISX2 5-ISX2
l The values for the related parameters of NE33 are provided as follows.
Parameter Value
4-ISX2 6-ISX2
l The values for the related parameters of NE34 are provided as follows.
Parameter Value
3-ISU2
----End
The key to configuring TDM services is configuring the corresponding service cross-
connections.
Linear MSP
Linear MSP applies to point-to-point physical networks. Linear MSP provides protection for the
services between two multiplex section termination (MST) modules. That is, when a linear MSP
switching occurs, the services are switched from the working section to the protection section.
In the case of the OptiX RTN 950, linear MSP provides protection for TDM services that are
transmitted over SDH fibers.
Linear MSP is classified into 1+1 linear MSP and 1:N linear MSP.
Protection
channel
Protection switching
Working
NE A NE B
channel
Protection
channel
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
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
SNCP
In the case of subnetwork connection protection (SNCP), the protection subnetwork connection
takes over when the working subnetwork connection fails or deteriorates. In the case of the
OptiX RTN 950, SNCP provides protection for TDM services that are transmitted on STM-1
fiber ring networks, TDM radio ring networks, Hybrid radio ring networks, or hybrid ring
networks that comprise optical network equipment and Hybrid radio equipment.
The SNCP protection scheme, which requires one working subnetwork and one protection
subnetwork, selects one service from the dually transmitted services. In the case of SNCP, the
services are switched to the protection subnetwork for transmission when the working
subnetwork connection fails or deteriorates. Figure 7-3 shows the application of SNCP.
Working SNC
NE A NE B
Protection SNC
Protection switching
Working SNC
NE A NE B
Protection SNC
The OptiX RTN 950 supports the coexistence of SNCP and the 1+1 protection or N+1 protection.
In the case of coexistence of the SNCP and the 1+1 protection or N+1 protection, you can set
the hold-off time for SNCP so that the protection switching for the radio link can be performed
first, thus preventing circular switchings.
TDM Radio
When the IF board works in PDH radio mode and when the radio capacity is nxE1, the first to
nth VC-12 timeslots on the IF board are available and correspond to first to nth E1s that are
transmitted over microwave. For example, if the radio capacity is 4xE1, only the first to fourth
VC-12 timeslots in VC4-1 on the IF board are available. If a cross-connection is configured
between the E1 port of a service board and the second VC-12 in VC4-1 on the IF board, the E1
services that are accessed from the E1 port are sent to the second E1 timeslot that is transmitted
over radio.
When the IF board works in STM-1 radio mode, all the timeslots in VC4-1 on the IF board are
available and correspond to the timeslots in the VC-4 that is transmitted on microwave.
Hybrid Radio
When the IF board works in Hybrid radio mode and when the Guarantee E1 Capacity is set to
n in Hybrid/AM Configuration, 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 the E1 port of a service board and the second VC-12 in VC4-2 on the IF
board, the E1 services that are accessed from the E1 port are sent to the sixty-fifth E1 timeslot
that is transmitted over microwave.
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-6, the timeslot allocation diagram contains three areas, namely, site area,
timeslot area, and timeslot allocation area.
The site area contains the NE icons and interface boards that carry radio links.
l The start and end NEs each have only one interface board, which is located under the NE
icon. The intermediate NEs each have two interface boards, which are located at the two
sides of the vertical line under the NE icon. The interface boards may be IF boards or line
boards.
l The interface board on the left side of the vertical line under an 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 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 radio link, before planning the site area, you need to divide the ring
radio link into a chain radio 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 radio links,
timeslots occupied by an STM-1 service are all in the first VC-4.
In the timeslot allocation 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 uniform route, you only need to draw a
continuous 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 continuous line to represent the working service and a dotted
line to represent the protection service.
1. Select the chain that contains the maximum of hops as the main chain. Then, divide the
chain network into several sub-chains by considering the main chain as the reference.
Consider the E1 channels or fiber connections that are used for transferring services
between NEs as links.
2. Allocate the timeslots for the add/drop or pass-through services on the NEs of the main
chain one after another, in the descending order of the NE distance.
3. Repeat the previous step to configure the timeslots for the services on all the sub-chains.
This timeslot allocation method ensures that only the numbers of the timeslots that the 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 allocation diagram are as follows:
For details, see 7.3 Configuration Example (TDM Services on a TDM Radio Chain
Network) and 7.5 Configuration Example (TDM Services on a Hybrid Radio Chain
Network).
1. Allocate the timeslots to add/drop services on the NEs in anti-clockwise order. Allocate
the minimum 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 the timeslots for the services on all the sub-chains.
This timeslot allocation method ensures that only the timeslots that the services on the nodes of
the aggregation sub-chain occupy change.
The principles for obtaining the timeslot cross-connection configurations from the SNCP service
timeslot allocation diagram are as follows:
For details, see 7.4 Configuration Example (TDM Services on a TDM Radio Ring
Network) and 7.6 Configuration Example (TDM Services on a Hybrid Radio Ring
Network).
Required
Start
Optional
Configuring MSP
Setting parameters
of SDH port
End
3 A.5.5 Configuring the Optional when the TDM service is an SNCP service.
Automatic Switching
of SNCP Services
8 A.13.1 Testing E1 The test results should show that each E1 service
Services 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 the TDM service on the
working channel only. In the case of N+1 protection configuration or 1:N linear MSP configuration, you need
to configure TDM services on the working channels and the extra service (if any) on the protection channel.
Based on 6.3 Configuration Example (Radio Links on the TDM Radio Chain Network),
configure the TDM services according to the following network planning information (as shown
in Figure 7-8):
l To ensure reliable transmission of the services between NE11 and the third-party network,
linear MSP is configured for the optical transmission line.
l Services are transferred between NE12 and NE13 through STM-1 optical ports.
Figure 7-8 Networking diagram (TDM services on a TDM radio chain network)
8xE1
BTS12
STM-1 STM-1
8xE1 NE14 Third party
BTS13
16xE1 network
NE13 NE12 NE11
14xE1 BTS11
8xE1
NE16 NE15
BTS15 BTS14
The connections of TDM links shown in Figure 7-8 are described as follows.
Between NE11 and the third- 1-SL1D-1 (working port) Configure the ports as a 1+1
party network linear MSP group.
1-SL1D-2 (protection port)
Between NE11 and NE12 3-IF1 (main IF board) Configure the ports as a 1+1
HSB protection group.
5-IF1 (standby IF board)
Between NE12 and BTS11 2-SP3S (1-16) Configure the ports to access
services from BTS11.
Between NE12 and NE11 3-IF1 (main IF board) Configure the ports as a 1+1
HSB protection group.
5-IF1 (standby IF board)
Between NE13 and NE14 3-IF1 (main IF board) Configure the ports as a 1+1
HSB protection group.
5-IF1 (standby IF board)
Between NE13 and NE15 4-IF1 (main IF board) Configure the ports as a 1+1
HSB protection group.
6-IF1 (standby IF board)
Between NE14 and BTS12 2-SP3S (1-16) Configure the ports to access
services from BTS12 and
Between NE14 and BTS13 BTS13.
Between NE14 and NE13 3-IF1 (main IF board) Configure the ports as a 1+1
HSB protection group.
5-IF1 (standby IF board)
Between NE15 and BTS14 2-SP3S (1-14) Configure the ports to access
services from BTS14.
Between NE15 and NE13 4-IF1 (main IF board) Configure the ports as a 1+1
HSB protection group.
6-IF1 (standby IF board)
Between NE16 and BTS15 2-SP3S (1-8) Configure the ports to access
services from BTS15.
Figure 7-9 Timeslot allocation diagram (TDM services on the TDM radio chain network)
Links-1: NE11 - NE12 - NE13 -NE15 -NE16
Station BSC
NE11 NE12 NE13 NE15 NE16
Timeslot 1-SL1D-1 3-IF1 3-IF1 1-SL1D-1 1-SL1D-1 4-IF1 4-IF1 3-IF1 3-IF1
VC12: 1-8
VC12: 9-22 2-SP3S:1-8
Links-2: NE13-NE14
Station NE13 NE14
Timeslot 1-SL1D-1 3-IF1 3-IF1
VC12: 23-38 VC12: 1-16
VC4-1
2-SP3S:1-16
Pass through
Add/Drop
Foward
As shown in Figure 7-9, the information about the timeslots that the TDM services occupy on
each NE is as follows:
l E1 services on NE16:
– The E1 services are added to or dropped from the first to eighth ports on the SP3S board
in slot 2 of NE16.
– The E1 services occupy the first to eighth VC-12 timeslots on the link between the first
optical port on the SL1D board in slot 1 of NE11 and the IF1 board in slot 3 of NE16.
l E1 services on NE15:
– The E1 services are added to or dropped from the first to fourteenth ports on the SP3S
board in slot 2 of NE15.
– The E1 services occupy the ninth to twenty-second VC-12 timeslots on the link between
the first optical port on the SL1D board in slot 1 of NE11 and the IF1 board in slot 3 of
NE15.
l E1 services on NE14:
– The E1 services are added to or dropped from the first to sixteenth ports on the SP3S
board in slot 2 of NE14.
– The E1 services occupy the twenty-third to thirty-eighth VC-12 timeslots on the link
between the first optical port on the SL1D board in slot 1 of NE11 and the SL1D board
in slot 1 of NE13.
– The E1 services occupy the first to sixteenth VC-12 timeslots on the link between the
IF1 board in slot 3 of NE13 and the IF1 board in slot 3 of NE14.
l E1 services on NE12:
– The E1 services are added to or dropped from the first to sixteenth ports on the SP3S
board in slot 2 of NE12.
– The E1 services occupy the thirty-ninth to fifty-fourth VC-12 timeslots on the link
between the first optical port on the SL1D board in slot 1 of NE11 and the IF1 board in
slot 3 of NE12.
Linear MSP
In this configuration example, no extra services need to be transmitted. Hence, the single-ended
non-revertive 1+1 linear MSP is configured to protect the optical transmission line between
NE11 and the third-party network. Table 7-8 provides the related planning information.
Parameter NE11
Parameter NE11
NOTE
Unless otherwise specified, SD Switching, Protocol Type take the default values.
Procedure
Step 1 See A.4.1 Configuring Linear MSP and configure 1+1 linear MSP.
Parameter Value
NE11
SD Switching Enabled
Step 2 See A.5.1 Creating the Cross-Connections of Point-to-Point Services and create the point-
to-point service cross-connections.
l The values for the related parameters of NE11 are provided as follows.
Parameter Value
NE11
Level VC-12
Direction Bidirectional
Source 1-SL1D
Source Port 1
Parameter Value
NE11
Sink 3-IF1
Sink Port 1
l The values for the related parameters of NE12 are provided as follows.
Parameter Value
NE12
Source Port 1 1
Sink Port 1 -
l The values for the related parameters of NE13 are provided as follows.
Parameter Value
NE13
Source Port 1 1
Parameter Value
NE13
Sink Port 1 1
l The values for the related parameters of NE14 are provided as follows.
Parameter Value
NE14
Level VC-12
Direction Bidirectional
Source 3-IF1
Source Port 1
Sink 2-SP3S
Sink Port -
Sink VC4 -
l The values for the related parameters of NE15 are provided as follows.
Parameter Value
NE15
Source Port 1 1
Parameter Value
NE15
Sink Port 1 -
l The values for the related parameters of NE16 are provided as follows.
Parameter Value
NE16
Level VC-12
Direction Bidirectional
Source 3-IF1
Source Port 1
Sink 2-SP3S
Sink Port -
Sink VC4 -
Step 3 See A.13.1 Testing E1 Services Using PRBS and test the E1 services.
Test two E1 services on each BTS. The test results should show that the E1 services contain no
bit errors.
----End
Based on 6.4 Configuration Example (Radio Links on the TDM Radio Ring Network),
configure the TDM services according to the service requirements. To ensure reliable
transmission of the services between the BTSs and the third-party network, SNCP is configured
to provide protection for TDM services on the ring network. See Figure 7-10.
Figure 7-10 Networking diagram (TDM services on a TDM radio ring network)
Third party
SDH network 16E1
NE21
4E1
BTS21 4E1
BTS22
4E1
NE23
BTS23
The connections of TDM links shown in Figure 7-10 are described as follows.
Between NE21 and the third- 2-SP3S (1-16) Configure the ports to
party network transmit TDM services.
Between NE21 and NE24 3-IF1 (main IF board of a 1+1 Configure the ports as west
SD protection group) ports.
Between NE22 and BTS21 2-SP3S (1-8) Configure the ports to access
services from BTS21 and
Between NE22 and BTS22 BTS22.
Between NE23 and BTS23 2-SP3S (1-4) Configure the ports to access
services from BTS23.
Between NE24 and BTS24 2-SP3S (1-4) Configure the ports to access
services from BTS24.
Between NE24 and NE21 4-IF1 (main IF board of a 1+1 Configure the ports as east
SD protection group) ports.
Figure 7-11 Timeslot allocation diagram (TDM service on the TDM radio ring network)
Station NE22
NE21 NE23 NE24 NE21
Timeslot 4-IF1 3-IF1 4-IF1 3-IF1 4-IF1 3-IF1 4-IF1 3-IF1
VC12: 1-8 VC12: 1-8
2-SP3S:1-8 2-SP3S:1-8 2-SP3S:1-8 2-SP3S:1-8
VC12: 9-12 VC12: 9-12
VC4-1 2-SP3S:9-12 2-SP3S:1-4 2-SP3S:1-4 2-SP3S:9-12
VC12: 13-16 VC12: 13-16
2-SP3S:13-16 2-SP3S:1-4 2-SP3S:1-4 2-SP3S:13-16
As shown in Figure 7-11, the information about the timeslots that the TDM services occupy on
each NE is as follows:
l E1 services on NE22:
– The E1 services are added to or dropped from the first to eighth ports on the SP3S board
in slot 2 of NE22.
– The E1 services are added to or dropped from the first to eighth ports on the SP3S board
in slot 2 of NE21.
– The E1 services occupy the first to eighth VC-12 timeslots on the ring.
l E1 services on NE23:
– The E1 services are added to or dropped from the first to fourth ports on the SP3S board
in slot 2 of NE23.
– The E1 services are added to or dropped from the ninth to twelfth ports on the SP3S
board in slot 2 of NE21.
– The E1 services occupy the ninth to twelfth VC-12 timeslots on the ring.
l E1 services on NE24:
– The E1 services are added to or dropped from the first to fourth ports on the SP3S board
in slot 2 of NE24.
– The E1 services are added to or dropped from the thirteenth to sixteenth ports on the
SP3S board in slot 2 of NE21.
– The E1 services occupy the thirteenth to sixteenth VC-12 timeslots on the ring.
SNCP
Table 7-13 provides the information about SNCP.
Parameter Value
NOTE
Unless otherwise specified, WTR Time, Hold-Off Time, and Switching Condition take the default values.
Procedure
Step 1 See A.5.2 Creating Cross-Connections of SNCP Services and configure the SNCP service
cross-connections.
l The values for the related parameters of NE21 are provided as follows.
Parameter Value
NE21
Hold-off Time(100ms) 0 0
Source Port 1 1
Parameter Value
NE21
Sink Port - -
Sink VC4 - -
l The values for the related parameters of NE22 are provided as follows.
Parameter Value
NE22
Direction Bidirectional
Level VC-12
Hold-off Time(100ms) 0
Source Port 1
Sink 2-SP3S
Sink Port -
Sink VC4 -
l The values for the related parameters of NE23 are provided as follows.
Parameter Value
NE23
Direction Bidirectional
Level VC-12
Hold-off Time(100ms) 0
Source Port 1
Sink 2-SP3S
Sink Port -
Sink VC4 -
l The values for the related parameters of NE24 are provided as follows.
Parameter Value
NE24
Direction Bidirectional
Level VC-12
Hold-off Time(100ms) 0
Source Port 1
Parameter Value
NE24
Sink 2-SP3S
Sink Port -
Sink VC4 -
Step 2 See A.5.1 Creating the Cross-Connections of Point-to-Point Services and configure the
service cross-connections on NE22, NE23, and NE24.
l The values for the related parameters of NE22 are provided as follows.
Parameter Value
NE22
Level VC-12
Direction Bidirectional
Source 3-IF1
Source Port 1
Sink 4-IF1
Sink Port 1
l The values for the related parameters of NE23 are provided as follows.
Parameter Value
NE23
Level VC-12
Direction Bidirectional
Source 3-IF1
Source Port 1
Parameter Value
NE23
Sink 4-IF1
Sink Port 1
l The values for the related parameters of NE24 are provided as follows.
Parameter Value
NE24
Level VC-12
Direction Bidirectional
Source 3-IF1
Source Port 1
Sink 4-IF1
Sink Port 1
Step 3 See A.13.1 Testing E1 Services Using PRBS and test the E1 services.
Test two E1 services on each BTS. The test results should show that the E1 services contain no
bit errors.
----End
Based on 6.5 Configuration Example (Radio Links on the Hybrid Radio Chain Network),
configure the TDM services according to the following network planning information (as shown
in Figure 7-12):
Number of high-priority E1 1 2
services
Number of low-priority E1 0 2
services
Figure 7-12 Networking diagram (TDM services on a Hybrid radio chain network)
Packet
E1 network
1xE1 NE14
BTS13
NE13 NE12 NE11
4xE1
NE16 NE15
BTS14
The connections of TDM links shown in Figure 7-12 are described as follows.
Between NE11 and the PSN 1-SP3S-1 (1-5) Configure the ports to
transmit TDM services.
Between NE11 and NE12 3-ISU2 (main IF board) Configure the ports as a 1+1
HSB protection group.
5-ISU2 (standby IF board)
Between NE12 and NE11 3-ISU2 (main IF board) Configure the ports as a 1+1
HSB protection group.
5-ISU2 (standby IF board)
Between NE13 and NE14 3-ISU2 (main IF board) Configure the ports as a 1+1
HSB protection group.
5-ISU2 (standby IF board)
Between NE13 and NE15 4-ISU2 (main IF board) Configure the ports as a 1+1
HSB protection group.
6-ISU2 (standby IF board)
Between NE14 and BTS13 2-SP3S (1) Configure the ports to access
services from BTS13.
Between NE14 and NE13 3-ISU2 (main IF board) Configure the ports as a 1+1
HSB protection group.
5-ISU2 (standby IF board)
Between NE15 and BTS14 2-SP3S (1-4) Configure the ports to access
services from BTS14.
Between NE15 and NE13 4-ISU2 (main IF board) Configure the ports as a 1+1
HSB protection group.
6-ISU2 (standby IF board)
Figure 7-13 Timeslot allocation diagram (TDM services on the Hybrid chain radio network)
Links-1: NE11 - NE12 - NE13 -NE5
Station
RNC NE11 NE12 NE13 NE15
Timeslot 1-SP3S 3-ISU2 3-ISU2 2-SP3S 2-SP3S 4-ISU2 4-ISU2
VC12: 1-2
2-SP3S:1-2
VC12: 3-4
2-SP3S:3-4
VC12: 5
VC4-1
Links-2: NE13-NE14
Station NE13 NE14
Timeslot 2-SP3S 3-ISU2 3-ISU2
VC12: 5 VC12: 1
VC4-1
2-SP3S:1
/ Pass through(low/high)
/ Add/Drop(low/high)
/ Foward(low/high)
As shown in Figure 7-13, the information about the timeslots that the TDM services occupy on
each NE is as follows:
l E1 services on NE15
– The E1 services are added to or dropped from ports 1-4 of the SP3S board in slot 2 on
NE15.Ports 1 and 2 add and drop high-priority services and ports 3 and 4 add and drop
low-priority services.
– The E1 services occupy the first to fourth VC-12 timeslots on the link between the
SP3S board in slot 1 of NE11 and the ISU2 board in slot 4 of NE15. Ports 1 and 2
transmit high-priority services and ports 3 and 4 transmit low-priority services.
l E1 services on NE14
– The E1 services are added to or dropped from the first port on the SP3S board in slot
2 of NE14. The E1 services received by NE14 are high-priority services by default,
because the E1 service priority function is disabled on the radio link to which NE14
belongs.
– The E1 services occupy the fifth VC-12 timeslot on the link between the SP3S board
in slot 1 of NE11 and the SP3S board in slot 2 of NE13.
– The E1 services occupy the first VC-12 timeslot on the link between the ISU2 board in
slot 3 of NE13 and the ISU2 board in slot 3 of NE14.
Procedure
Step 1 See A.5.1 Creating the Cross-Connections of Point-to-Point Services and create point-to-
point service cross-connections.
l The values for the relevant parameters of NE11 are provided as follows.
Parameter Value
NE11
Source Port - -
Source VC4 - -
Sink Port 1 1
l The values for the relevant parameters of NE12 are provided as follows.
Parameter Value
NE12
Parameter Value
NE12
Source Port 1 1
Sink Port - -
Sink VC4 - -
l The values for the relevant parameters of NE13 are provided as follows.
Parameter Value
NE13
Source Port - - -
Source VC4 - - -
Sink Port 1 1 1
l The values for the relevant parameters of NE14 are provided as follows.
Parameter Value
NE14
Level VC12
Direction Bidirectional
Source 3-ISU2
Source Port 1
Sink 2-SP3S
Sink Port -
Sink VC4 -
E1 Priority -
l The values for the relevant parameters of NE15 are provided as follows.
Parameter Value
NE15
Source Port 1 1
Sink Port - -
Sink VC4 - -
Step 2 See A.13.1 Testing E1 Services Using PRBS and test the E1 services.
Test one E1 service on BTS13 and BTS14. The test results should show that the E1 services
contain no bit errors.
----End
Based on 6.6 Configuration Example (Radio Links on the Hybrid Radio Ring Network),
configure the TDM services according to the service requirements. To ensure reliable
transmission of the services between the BTSs and the PSN, SNCP is configured to provide
protection for TDM services on the ring network. See Figure 7-14.The service capacity accessed
by each BTS is provided in Table 7-20.
BTS BTS22
Number of E1s 2
Figure 7-14 Networking diagram (TDM services on a Hybrid radio ring network)
Packet
network 2E1
NE21
BSC
BTS21
BTS22
NE23
BTS23
The connections of TDM links shown in Figure 7-14 are described as follows.
Between NE21 and the PSN 2-SP3S (1-2) Configure the ports to
transmit TDM services.
Between NE21 and NE24 3-ISU2 (main IF board of a 1 Configure the ports as west
+1 SD protection group) ports.
Between NE22 and BTS22 2-SP3S (1-2) Configure the ports to access
services from BTS22.
Between NE24 and NE21 4-ISU2 (main IF board of a 1 Configure the ports as east
+1 SD protection group) ports.
Figure 7-15 Timeslot allocation diagram (TDM services on the Hybrid radio ring network)
Station NE22
NE21 NE23 NE24 NE21
Timeslot 4-ISU2 3-ISU2 4-ISU2 3-ISU2 4-ISU2 3-ISU2 4-ISU2 3-ISU2
VC12: 1-2 VC12: 1-2
2-SP3S:1-2 2-SP3S:1-2 2-SP3S:1-2 2-SP3S:1-2
As shown in Figure 7-15, the information about the timeslots that the TDM services occupy on
each NE is as follows:
l The E1 services are added to or dropped from the first to second ports on the SP3S board
in slot 2 of NE22.
l The E1 services are added to or dropped from the first to second ports on the SP3S board
in slot 2 of NE21.
l The E1 services occupy the first to second VC-12 timeslots on the ring.
SNCP
Table 7-25 provides the information about SNCP.
Parameter Value
Parameter Value
NOTE
Unless otherwise specified, WTR Time, Hold-Off Time, and Switching Condition take the default values.
Procedure
Step 1 See A.5.2 Creating Cross-Connections of SNCP Services and configure the SNCP service
cross-connections.
l The values for the relevant parameters of NE21 are provided as follows.
Parameter Value
NE21
Direction Bidirectional
Level VC-12
Hold-off Time(100ms) 0
Source Port 1
Sink 2-SP3S
Sink Port -
Sink VC4 -
Parameter Value
NE21
E1 Priority -
l The values for the relevant parameters of NE22 are provided as follows.
Parameter Value
NE22
Direction Bidirectional
Level VC-12
Hold-off Time(100ms) 0
Source Port 1
Sink 2-SP3S
Sink Port -
Sink VC4 -
E1 Priority -
Step 2 See A.5.1 Creating the Cross-Connections of Point-to-Point Services and configure the
service cross-connections on NE23 and NE24.
l The values for the relevant parameters of NE23 are provided as follows.
Parameter Value
NE23
Level VC-12
Direction Bidirectional
Parameter Value
NE23
Source 3-ISU2
Source Port 1
Sink 4-ISU2
Sink Port 1
Priority -
l The values for the relevant parameters of NE24 are provided as follows.
Parameter Value
NE24
Level VC-12
Direction Bidirectional
Source 3-ISU2
Source Port 1
Sink 4-ISU2
Sink Port 1
Priority -
Step 3 See A.13.1 Testing E1 Services Using PRBS and test the E1 services.
Test one E1 service on BTS22. The test results should show that the E1 services contain no bit
error.
----End
Native Ethernet services on the packet plane include Native E-Line services and Native E-LAN
services.
This section describes how to configure a radio network that transmits E-Line services and E-
LAN services at the same time according to the network planning information.
As shown in Figure 8-1, the ports connecting to the packet plane are classified into the following
types:
Since an IF port corresponds to an IF_ETH port, the IF ports or the microwave ports corresponding to IF
ports can be regarded as being directly connected to the packet plane.
l Bridging port (PORT 10) connecting to the packet plane on the EFP8 board
The EFP8 board has two bridging ports: PORT 9 and PORT 10.
– PORT 9 and PORT 10 are two back-to-back internal GE ports, having no PHY-layer
function.
– PORT 10 is connected to the packet plane. The Ethernet services on the packet plane
are transmitted to the EoPDH plane through PORT 10.
– PORT 9 is connected to the EoPDH plane. The Ethernet services on the packet plane
are transmitted to the FE port or VCTRUNK port on the EFP8 board through PORT 9.
l Bridging port (PORT 8) connecting to the packet plane on the EMS6 board
The EMS6 board has two bridging ports: PORT 7 and PORT 8.
– PORT 7 and PORT 8 are two back-to-back internal GE ports, having no PHY-layer
function.
– PORT 8 is connected to the packet plane. The Ethernet services on the packet plane are
transmitted to the EoS plane through PORT 8.
– PORT 7 is connected to the EoS plane. The Ethernet services on the packet plane are
transmitted to the FE port, GE port, or VCTRUNK port on the EMS6 board through
PORT 7.
switching IF unit
FE/GE PORTn unit GE GE
…
…
switching IF unit
FE/GE PORTn unit GE GE
EFP8
PORT10 PORT9
Ethernet EoPDH plane
GE switching unit
GE
EMS6
PORT8 PORT7
Ethernet
GE switching unit EoS plane
GE
8.1.3 Auto-Negotiation
The auto-negotiation function allows the network equipment to send information about its
supported working mode to the opposite end of the network and to receive corresponding
information that the opposite end may transfer.
Table 8-1 Auto-negotiation rules for FE electrical ports (when the local FE electrical port works
in auto-negotiation mode)
NOTE
As provided in Table 8-1, when the opposite FE electrical port works in 10M full-duplex or 100M full-duplex
mode, auto-negotiation does not necessarily achieve full matching between the working modes of the FE
electrical ports at both ends. As a result, some packets are lost. Therefore, when the opposite FE electrical port
works in 10M full-duplex or 100M full-duplex mode, set the working mode of the local FE electrical port to
10M full-duplex or 100M full-duplex.
When the FE electrical ports at both ends work in auto-negotiation mode, the equipment at both
ends can negotiate flow control.
Table 8-2 Auto-negotiation rules for GE electrical ports (when the local GE electrical port works
in auto-negotiation mode)
NOTE
As provided in Table 8-2, when the opposite GE electrical port works in 10M full-duplex or 100M full-duplex
mode, auto-negotiation does not necessarily achieve full matching between the working modes of the GE
electrical ports at both ends. As a result, some packets are lost. Therefore, when the opposite GE electrical port
works in 10M full-duplex or 100M full-duplex mode, set the working mode of the local GE electrical port to
10M full-duplex or 100M full-duplex.
When the GE electrical ports at both ends work in auto-negotiation mode, the equipment at both
ends can negotiate flow control.
Half-duplex Ethernet uses a back-pressure mechanism to control flow. Full-duplex Ethernet uses
PAUSE frames to control flow. Currently, half-duplex Ethernet is not widely applied; therefore,
flow control implemented on the equipment is used for full-duplex Ethernet.
The flow control function on the equipment is classified into two types: auto-negotiation flow
control and non-auto-negotiation flow control.
l Symmetric PAUSE
The port can transmit PAUSE frames and process received PAUSE frames.
l Both asymmetric and symmetric PAUSE
The port has the following capabilities:
– Transmits and processes PAUSE frames.
– Transmits PAUSE frames but cannot process received PAUSE frames.
– Processes received PAUSE frames but cannot transmit PAUSE frames.
l Disabled
The port does not transmit or process PAUSE frames.
NOTE
On the NMS, the OptiX RTN 950 supports only two auto-negotiation flow control modes: Disabled mode and
Enable Symmetric Flow Control (symmetric PAUSE) mode.
On the NMS, the OptiX RTN 950 supports only two non-auto-negotiation flow control modes: Disabled mode
and Enable Symmetric Flow Control (symmetric) mode.
Service Model
Table 8-3 describes the point-to-point transparently transmitted E-Line service model.
Typical Application
Figure 8-2 shows the typical application of service model 1.
In service model 1, Ethernet service 1 and Ethernet service 2, which carry no VLAN IDs or carry
unknown VLAN IDs, are accessed to NE1 through port 1 and port 2 respectively. Port 1 and
port 2 transparently transmit Ethernet service 1 and Ethernet service 2 to port 3 and port 4,
respectively. Port 3 and port 4 then transmit Ethernet service 1 and Ethernet service 2 to NE2.
Service processing on NE2 is the same as on NE1.
In service model 2, Ethernet service 1 and Ethernet service 2, which carry no VLAN IDs or carry
unknown VLAN IDs, are accessed to NE1 through port 1 and port 2 respectively. Port 1 and
Port 2 process the incoming packets based on their own TAG attributes. Then, Port 1 and Port
2 send Ethernet service 1 and Ethernet service 2 to Port 3 and Port 4 respectively. Port 3 and
Port 4 process the incoming packets based on their own TAG attributes. Then, Port 3 and Port
4 send Ethernet service 1 and Ethernet service 2 to NE2. Service processing on NE2 is the same
as on NE1.
Service Model
Table 8-4 shows the VLAN-based E-Line service model.
Typical Application
Figure 8-3 shows the typical application of the VLAN-based E-Line service model. Service 1
and service 2 carry different VLAN IDs. After the two Ethernet services are received at NE1
through port 1 and port 2 respectively, they share the same transmission channel at port 3.
On NE1, port 1 and port 2 process the incoming packets based on their own TAG attributes;
then, port 1 and port 2 send service 1 and service 2 to port 3. Port 3 processes all the outgoing
packets based on its TAG attribute, and then sends service 1 and service 2 to NE2. Due to the
different VLAN IDs, service 1 and service 2 can be transmitted through port 3 at the same time.
NOTE
11.1.1.3 PW-Carried E-Line Services describes QinQ-based E-Line services carried by PWs.
Service Model
Table 8-5 shows the QinQ-based E-Line service models.
Model 1 PORT (source) UNI-NNI Null (source) The source port adds
QinQ link (sink) QinQ (sink) the S-VLAN tag that
corresponds to the
QinQ link to all the
received Ethernet
frames, and then
transmits the
Ethernet frames to
the sink port to
which the QinQ link
is connected.
Model 2 PORT (source) UNI-NNI 802.1Q (source)a The source port only
QinQ link (sink) receives the
QinQ (sink)
Ethernet frames that
carry C-VLAN tags.
After receiving the
Ethernet frames, it
adds the S-VLAN
tag that corresponds
to the QinQ link to
the Ethernet frames
and then transmits
the Ethernet frames
to the sink port to
which the QinQ link
is connected.
Model 4 QinQ link (source) NNI-NNI QinQ (source) The source port
QinQ link (sink) QinQ (sink) transmits the
Ethernet frames that
carry a specific S-
VLAN tag
(corresponding to
the source QinQ
link) to the sink port
to which the sink
QinQ link is
connected. If the
source and sink
QinQ links have
different S-VLAN
tags, S-VLAN tag
swapping occurs.
NOTE
Typical Application
Figure 8-4 shows the typical application of service model 1.
Service 1 and service 2 contain tagged frames and untagged frames. Service 1 is transmitted to
NE1 through port 1, and service 2 is transmitted to NE1 through port 2. Port 1 adds an S-VLAN
tag to service 1, and port 2 adds another S-VLAN tag to service 2. Service 1 and service 2 are
then transmitted to Port 3. Port 3 transmits service 1 and service 2 to NE2.
Strip S-VLAN Label Add S-VLAN Label Add S-VLAN Label Strip S-VLAN Label
Service 1 and service 2 carry different unknown C-VLAN tags. Service 1 is transmitted to NE1
through port 1, and service 2 is transmitted to NE1 through port 2. Port 1 adds an S-VLAN tag
to service 1, and port 2 adds another S-VLAN tag to service 2. Service 1 and service 2 are then
transmitted to port 3. Port 3 transmits service 1 and service 2 to NE2.
NE 1 NE 2
Port 1 Port 1
E-Line
Service 1
Port 3 Transmission Port 3 E-Line Service 1
Unknown CVLAN Network Unknown CVLAN
Service 2 e E-Lin Service 2
Unknown CVLAN E-Lin e Unknown CVLAN
Port 2 Port 2
Service 1 and service 2 carry different C-VLAN tags. Service 1 is transmitted to NE1 through
port 1, and service 2 is transmitted to NE1 through port 2. Port 1 adds an S-VLAN tag to service
1, and port 2 adds another S-VLAN tag to service 2. Service 1 and service 2 are then transmitted
to port 3. Port 3 transmits service 1 and service 2 to NE2.
NE 1 NE 2
Port 1 Port 1
Service 1 E-Line Service 1
Port 3 Transmission Port 3 E-Line
VLAN ID: 100 Network VLAN ID: 100
Service 2 e E-Lin Service 2
VLAN ID: 200 E-Lin e
Port 2 Port 2 VLAN ID: 200
Service 1 and service 2 carry the same S-VLAN tag. Service 1 is transmitted to NE1 through
port 1, and service 2 is transmitted to NE1 through port 2. Port 1 changes the S-VLAN tag carried
in service 1 and port 2 changes the S-VLAN tag carried in service 2 so that the service 1 and
service 2 carry different S-VLAN tags. Service 1 and service 2 are then transmitted to port 3.
Port 3 transmits service 1 and service 2 to NE2.
NE 1 NE 2
Port 1 Port 1
E-Line
Service 1
Port 3 Transmission Port 3 E-Line Service 1
S-VLAN ID: 100 Network S-VLAN ID: 100
Service 2 e E-Lin Service 2
S-VLAN ID: 100 E-Lin e
Port 2 Port 2 S-VLAN ID: 100
Service Model
Table 8-6 shows the 802.1D bridge-based E-LAN service model.
Typical Application
Figure 8-8 shows the typical application of the 802.1D bridge-based E-LAN service model.
Services A are received at NE2 and NE3, and then transmitted over the transmission network.
These services are finally converged and switched at NE1. The services do not need to be
separated. Therefore, an 802.1D bridge is used at NE1 to groom services.
Port 2 Port 1
User A2
NE 1 Transmission
Network
Port 1 Port 2
User A1
Port 3
802.1d bridge NE 3
Transmission
Network
Port 1
User A3
Port 2
Service Model
Table 8-7 shows the 802.1Q bridge-based E-LAN service model.
Typical Application
Figure 8-9 shows the typical application of the 802.1Q bridge-based E-LAN service model.
Services G and H are received at NE2 and NE3, and then are transmitted over the transmission
network. These services finally are converged and switched at NE1. As services G and H use
different VLAN planning, 802.1Q bridges are configured on NEs and sub-switching domains
are divided based on VLANs, differentiating and separating the two services.
VLAN 100
Port 1
User G2
Port 3
NE 1
VLAN 200
Transmission Port 2
VLAN 100
Port 1 Network User H2
User G1
Port 3
802.1q bridge
VLAN 200
Port 2 Port 4
User H1 NE 3
Transmission
VLAN 100
Network
802.1q bridge Port 1
User G3
VLAN 200
Port 3 Port 2
User H3
802.1q bridge
NOTE
You can configure 8.1.5.2 VLAN-based E-Line Services on NE2 and NE3 for receiving services.
Service Model
Table 8-8 shows the 802.1ad bridge-based E-LAN service model.
PORT+S-
VLAN (NNI
port)
NOTE
a: When the encapsulation mode of port is 802.1Q, set Tag to Tag Aware.
Typical Application
Figure 8-10 shows the typical application of the 802.1ad bridge-based E-LAN service model.
Services G and H are received at NE2 and NE3, and then are transmitted over the transmission
network. These services finally are converged and switched at NE1. As services G and H use
the same C-VLAN planning, extra S-VLAN tags are configured on NEs, differentiating and
separating the two services.
Figure 8-10 Typical application of the 802.1ad bridge-based E-LAN service model
NE 2
NE 2
SVLAN 300
Port 1
User G2
CVLAN 100
Port 3
SVLAN 400
NE 1 Port 2
Transmission User H2
SVLAN 300 Network CVLAN 100
Port 1 Port 3
User G1 802.1ad bridge
CVLAN 100
SVLAN 400
NE 3
Port 2
User H1
CVLAN 100 Port 4 SVLAN 300
Transmission
Port 1
Network
802.1ad bridge User G3
CVLAN 100
SVLAN 400
Port 3 Port 2
NE 1 User H3
CVLAN 100
Strip S-VLAN Label Add S-VLAN Label
NOTE
You can configure 8.1.5.3 QinQ-Based E-Line Services on NE2 and NE3 for service access.
through the regional backhaul network to the BSC. Therefore, in this example, services on the
Hybrid radio network of the mobile carrier 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
As shown in Figure 8-12, the mobile carrier network need not sense whether the received BTS
services carry any VLAN IDs. Services from each BTS are aggregated at NE1 and then
transmitted through the regional backhaul network to the BSC. Therefore, in this example, the
services on the Hybrid radio network (NE1 to NE6) of the mobile carrier network are configured
as IEEE 802.1d bridge-based E-LAN services. The Hybrid radio network checks the destination
ports in the MAC address table according to the destination MAC addresses carried by the BTS
services and then forwards BTS services to the ports.
NOTE
IEEE 802.1d bridge-based E-LAN 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 need not 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
On the mobile carrier network shown in Figure 8-13, the VLAN IDs that received BTS services
carry are planned in a unified manner and are unique within each domain. BTS services in
different domains are isolated from each other by means of VLAN IDs and BTSs in the same
domain can communicate with each other. The BTS services are aggregated at NE1 and then
transmitted through the regional backhaul network to the BSC. Therefore, in this example, the
services on the Hybrid radio network of the mobile carrier network are configured as IEEE
802.1q bridge-based E-LAN services. The Hybrid radio network checks the destination ports in
the MAC address table according to the destination MAC addresses and VLAN IDs carried by
the BTS services and then forwards BTS services to the ports.
NOTE
IEEE 802.1q bridge-based E-LAN service packets can be broadcast within each domain. Therefore, isolate the
ports that need not 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
NOTE
a: To block communication between certain ports connected to a bridge, you need to add the ports into a split
horizon group.
l Dynamic entry
A dynamic entry is obtained by a bridge in SVL or IVL mode. A dynamic entry will be
aged out and will be lost after the Ethernet processing unit is reset.
l Static entry
A static entry is manually added to the MAC address table by a network administrator on
the NMS. A static entry will not be aged out. Generally, a static entry is configured if a
piece of equipment with a known MAC address is mounted to a port and the equipment
has constant heavy traffic. A static entry is not lost after the Ethernet processing unit is
reset.
l Blacklist entry
A blacklist entry is also called a MAC disabled entry or blackhole entry. If the source MAC
address or destination MAC address of a data frame is defined in a blacklist entry, this data
frame is discarded. A blacklist entry is configured by a network administrator. A blacklist
entry will not be aged out, and will not be lost after the Ethernet processing board is reset.
NOTE
An forwarding entry is automatically deleted if it is not updated within a specified period, that is, no new
packet from the MAC address defined in the entry is received to enable the re-learning of this MAC address
within a specified period. This mechanism is called aging, and the specified period is called aging time.
For VLAN-based E-Line services, the VLAN IDs on the source and sink nodes are usually set
to the same value. If packets carry different VLAN IDs on the source and sink nodes, these
VLAN IDs need to be set for the source and sink nodes of the E-Line services. In addition, you
need to configure a VLAN forwarding table to achieve the switch of VLAN IDs at the source
and sink nodes.
Figure 8-14 shows an application of the VLAN forwarding table. In this figure, service 1 carries
a VLAN ID of 100, and it is transmitted to NE1 through port 1. On a transmission network, the
VLAN ID of service 1 may be in conflict with the VLAN IDs of other services. To avoid this
situation, the VLAN ID of service 1 must be changed to another value before it is transmitted
on the transmission network and then be changed to the original value after it is transmitted out
of the transmission network. Therefore, a VLAN forwarding table is configured at NE1 and
NE2, so that the VLAN IDs of services between port 1 and port 3 can be changed as required.
For service 1, when it traverses NE1, the VLAN ID is changed from 100 to 200 and then changes
back to 100 again at NE2.
Figure 8-15 shows a typical application of the split horizon group. NEs on the network are
configured with E-LAN services, and the east and west IF_ETH ports and service access ports
are configured as mounted ports of a bridge. In this case, if a split horizon group is not configured
at NE1, broadcast storm occurs due to a network loop as the east and west IF_ETH ports can
forward packets to each other. If a split horizon group is created at NE1 and the east and west
IF_ETH ports are configured as members of the split horizon group, the east and west IF_ETH
ports do not forward packets to each other. Therefore, a service loop is prevented.
NE1
BTS
BTS
NE3
BTS
NOTE
l ERPS can prevent a service loop on a ring network. If ERPS is already enabled for a ring network, a split
horizon group is not needed as it may affect ERPS operation.
l On the OptiX RTN 950, only the split horizon group configuration based on physical ports is supported.
Therefore, the logical ports mapped from a physical port are added to the split horizon group automatically.
ERPS
ERPS is applicable to ring physical networks and can provide protection for the E-LAN services
between all the nodes on the ring network. Generally, when a ring network is configured with
ERPS, the RPL node blocks the RPL port on one side so that all the services are transmitted
through the ports on the other side. In this manner, service loops are prevented. If a section of
link fails or an NE becomes faulty, the RPL node unblocks its RPL port so that the services are
switched from the faulty point to the RPL port for transmission. In this manner, protection for
the ring network is achieved.
The Ethernet ring network shown in Figure 8-16 is configured with ERPS. Generally, the RPL
node (NE D) blocks its RPL port that is connected to NE A, and all the services are transmitted
over the link NE A <-> NE B <-> NE C <-> NE D. When the link between NE A <-> NE B
becomes faulty, NE D unblocks the blocked port so that the services can be transmitted over the
link NE A <-> NE D <-> NE C <-> NE B.
NE A
NE B NE D
NE C
Protection switching
Failure NE A
NE B NE D
NE C
Link
Blocked port
LAG
Link aggregation allows multiple links that are attached to the same equipment to be aggregated
to form a link aggregation group (LAG) so that the bandwidths and availability of the links
increase. The aggregated links can be considered as a single logical link.
The LAG provides users with a cost-effective method for increasing link bandwidth. The
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 balancing algorithm, achieving
the load balancing at the link level.
l Improved the link availability
The links in a LAG provide backup for each other dynamically. When a link fails, another
link in the LAG quickly takes over. This process in which link aggregation starts the backup
link only applies to the links in the same LAG and it cannot be performed on links that are
not in the LAG.
Link 1
Link 2
Ethernet Link 3 Ethernet
packet packet
Link aggregation
group
MSTP
The OptiX RTN 950 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 applicable in case of a network loop. This protocol adopts certain
algorithms to reconstruct a loop network into a loop-free tree network and therefore prevents
Ethernet frames from increasing and cycling in an endless manner on the loop network.
On the OptiX RTN 950, the MSTP is used to prevent a network loop on the access side.
See Figure 8-18. When the user equipment is connected to the OptiX RTN 950 through two
different trails, you can configure the ports on the OptiX RTN 950 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 a service access link becomes faulty, the MSTP enables a re-configuration to
generate the spanning tree topology, providing protection for the user network that is configured
with multiple access points.
Root Root
Port group
CIST
Blocked Port
Figure 8-19 Configuration flow chart (point-to-point transparently transmitted E-Line services)
Required Start
Optional
Configuring LAGs
Configuring QoS
End
Operation Description
A.7.2.1 Required if LAG protection is configured for FE/GE ports or for the
Creating a Integrated IP radio that works in N+0/XPIC mode. Set the parameters as
LAG follows:
NOTE
For ISU2/ISX2 boards, if they have been added to a PLA group during radio link
configuration, the LAG does not need to be configured.
l Set LAG Type to the same value as that at the opposite end. Generally,
set LAG Type to Static at both ends.
l For FE/GE ports, set Load Sharing to the same value as that at the
opposite end. It is recommended that you set Load Sharing to Non-
Sharing at both ends, if the LAG is configured only to provide
protection. It is recommended that you set Load Sharing to Sharing
at both ends, if the LAG is configured to increase the bandwidth.
l Set Load Sharing to Sharing at both ends, if Integrated IP radio works
in N+0/XPIC mode and uses LAG protection.
l Set Revertive Mode to the same value as that at the opposite end.
Generally, set Revertive Mode to Revertive at both ends. This
parameter is valid only to LAGs whose Load Sharing is set to Non-
Sharing.
l It is recommended that the main and slave ports take the same settings
at both ends. In this case, you can set System Priority as required. It
is recommended that this parameter take its default value. This
parameter is valid only to static LAGs.
l For an air interface LAG, to enable microwave signal degrade to trigger
LAG switching, set Switch LAG upon Air Interface SD to
Enabled.
l Set Main Board, Main Port, and Selected Standby Ports according
to the network plan. It is recommended that the main and slave ports
take the same settings at both ends.
NOTE
Set the AM attributes to the same value for the microwave ports in a LAG.
Table 8-11 Procedure for configuring point-to-point transparently transmitted E-Line services
Operation Description
A.7.3.7 Required when the VLAN tags of the Ethernet service need to be swapped
Creating a at the source and sink.
VLAN Set the parameters according to the network planning information.
Forwarding
NOTE
Table for an E- The corresponding VLAN forwarding table entries need to be configured for the
Line Service source port and sink port.
Operation Description
Operation Description
A.6.6.5 Optional.
Setting the
Advanced
Attributes
of Ethernet
Ports
A.6.7.4 Optional.
Setting the NOTE
Advanced l For the ISU2/ISX2, it is recommended that you set Speed
Attributes Transmission at L2 and Speed Transmission at L3 to
of IF_ETH Enabled, if the corresponding permission to enable the two
Ports functions is already obtained.
l When Speed Transmission at L3 is set to Enabled,
Encapsulation Type of the ISU2 and ISX2 boards cannot be set
to Null.
l Set Speed Transmission at L2 and Speed Transmission at L3
consistently for both ends of a radio link.
Operation Description
A.7.7.2 Required if the default mappings for the DS domain are inapplicable.
Modifying the Set the related parameters according to the network plan.
Mapping
Relationships You can learn the default mappings for the DS domain by referring to A.
for the DS 7.7.10 Querying the DS Domain of a Port.
Domain
A.7.7.3 Required if the trusted packet type of the port is different from the default
Changing the trusted packet type (C-VLAN priority) applied to the DS domain.
Ports Applied Set the related parameters according to the network plan.
to a DS Domain
and Their
Trusted Packet
Types
A.7.7.4 Required if you need to apply QoS policies other than DS and port shaping
Creating a Port for a specific port.
Policy Set the related parameters according to the network plan.
A.7.7.6 Required if you need to perform the ACL, CoS, CAR or shaping operation
Creating for a specific flow over the port.
Traffic Set the related parameters according to the network plan.
A.7.7.8 Required if you need to limit the egress bandwidth that an Ethernet service
Configuring occupies.
Port Shaping Set the related parameters according to the network plan.
Operation Description
A.7.8.1 Required for the NEs where the two Ethernet ports involved in the service
Creating an test are located. Set the parameters as follows:
MD l Set Maintenance Domain Name and Maintenance Domain Level to
the same values for the NEs.
l For an Ethernet service between two edge nodes on the transport
network, it is recommended that Maintenance Domain Level takes its
default value of 4. For an Ethernet service between two internal NEs
on the transport network, set Maintenance Domain Level to a value
smaller than 4. 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 of an Ethernet service between two
internal NEs on the transport network.
A.7.8.2 Required for the NEs where the two Ethernet ports involved in the service
Creating an test are located. Set the parameters as follows:
MA 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 NEs.
l Set Relevant Service to the same service for the NEs.
l It is recommended that you set CC Test Transmit Period to 1s.
A.7.8.3 Required for the NEs where the two Ethernet ports involved in the service
Creating test are located. Set the parameters as follows:
MEPs l Set Maintenance Association Name to the value of Maintenance
Association Name that is set in the preceding step.
l Set Board and Port to the Ethernet ports that are involved in the service
test.
l Set MP ID to different values for MEPs in the same MD.
l If the OAM information initiated by the MEP travels through the packet
switching unit on the local NE, set Direction of the MEP to Ingress.
Otherwise, set Direction to Egress.
l Set CC Status to Active, as the MEP ID is used to identify the MEP
during the LB test.
Operation Description
A.7.8.4 Required for the NE where the Ethernet ports involved in the OAM
Creating operation are located. Set the parameters as follows:
Remote MEPs l Set Maintenance Domain Name to the value of Maintenance
in an MA Domain Name that is set in the preceding step.
l Set Maintenance Association Name to the value of Maintenance
Association Name that is set in the preceding step.
l To ensure that an MEP can respond to the OAM operations initiated
by the other MEPs in the same MA, you need to set the other MEPs as
the remote MEPs.
Perform an LB Required.
test to test the The LB test result should show that no packet loss occurs.
Ethernet
service
configurations
Configuration Flowchart
Figure 8-20 provides the procedure for configuring VLAN-based E-Line services.
Optional
Configuring LAGs
Configuring E-Line
services
Configuring QoS
End
Operation Description
A.7.2.1 Required if LAG protection is configured for FE/GE ports or for the
Creating a Integrated IP radio that works in N+0/XPIC mode. Set the parameters as
LAG follows:
NOTE
For ISU2/ISX2 boards, if they have been added to a PLA group during radio link
configuration, the LAG does not need to be configured.
l Set LAG Type to the same value as that at the opposite end. Generally,
set LAG Type to Static at both ends.
l For FE/GE ports, set Load Sharing to the same value as that at the
opposite end. It is recommended that you set Load Sharing to Non-
Sharing at both ends, if the LAG is configured only to provide
protection. It is recommended that you set Load Sharing to Sharing
at both ends, if the LAG is configured to increase the bandwidth.
l Set Load Sharing to Sharing at both ends, if Integrated IP radio works
in N+0/XPIC mode and uses LAG protection.
l Set Revertive Mode to the same value as that at the opposite end.
Generally, set Revertive Mode to Revertive at both ends. This
parameter is valid only to LAGs whose Load Sharing is set to Non-
Sharing.
l It is recommended that the main and slave ports take the same settings
at both ends. In this case, you can set System Priority as required. It
is recommended that this parameter take its default value. This
parameter is valid only to static LAGs.
l For an air interface LAG, to enable microwave signal degrade to trigger
LAG switching, set Switch LAG upon Air Interface SD to
Enabled.
l Set Main Board, Main Port, and Selected Standby Ports according
to the network plan. It is recommended that the main and slave ports
take the same settings at both ends.
NOTE
Set the AM attributes to the same value for the microwave ports in a LAG.
Operation Description
A.7.3.7 Required when the VLAN tags of the Ethernet service need to be switched
Creating a at the source and sink.
VLAN The parameters need to be set according to the network planning
Forwarding information.
Table for an E-
NOTE
Line Service The corresponding VLAN forwarding table items need to be configured for the
source port and sink port.
Operation Description
Operation Description
A.6.6.5 Optional.
Setting the
Advanced
Attributes
of Ethernet
Ports
Operation Description
A.6.7.4 Optional.
Setting the NOTE
Advanced l For the ISU2/ISX2, it is recommended that you set Speed
Attributes Transmission at L2 and Speed Transmission at L3 to
of IF_ETH Enabled, if the corresponding permission to enable the two
Ports functions is already obtained.
l When Speed Transmission at L3 is set to Enabled,
Encapsulation Type of the ISU2 and ISX2 boards cannot be set
to Null.
l Set Speed Transmission at L2 and Speed Transmission at L3
consistently for both ends of a radio link.
Operation Description
A.7.7.2 Required if the default mappings for the DS domain are inapplicable.
Modifying the Set the related parameters according to the network plan.
Mapping
Relationships You can learn the default mappings for the DS domain by referring to A.
for the DS 7.7.10 Querying the DS Domain of a Port.
Domain
A.7.7.3 Required if the trusted packet type of the port is different from the default
Changing the trusted packet type (C-VLAN priority) applied to the DS domain.
Ports Applied Set the related parameters according to the network plan.
to a DS Domain
and Their
Trusted Packet
Types
A.7.7.4 Required if you need to apply QoS policies other than DS and port shaping
Creating a Port for a specific port.
Policy Set the related parameters according to the network plan.
A.7.7.6 Required if you need to perform the ACL, CoS, CAR or shaping operation
Creating for a specific flow over the port.
Traffic Set the related parameters according to the network plan.
Operation Description
A.7.7.8 Required if you need to limit the egress bandwidth that an Ethernet service
Configuring occupies.
Port Shaping Set the related parameters according to the network plan.
Operation Description
A.7.8.1 Required for the NEs where the two Ethernet ports involved in the service
Creating an test are located. Set the parameters as follows:
MD l Set Maintenance Domain Name and Maintenance Domain Level to
the same values for the NEs.
l For an Ethernet service between two edge nodes on the transport
network, it is recommended that Maintenance Domain Level takes its
default value of 4. For an Ethernet service between two internal NEs
on the transport network, set Maintenance Domain Level to a value
smaller than 4. 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 of an Ethernet service between two
internal NEs on the transport network.
A.7.8.2 Required for the NEs where the two Ethernet ports involved in the service
Creating an test are located. Set the parameters as follows:
MA 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 NEs.
l Set Relevant Service to the same service for the NEs.
l It is recommended that you set CC Test Transmit Period to 1s.
Operation Description
A.7.8.3 Required for the NEs where the two Ethernet ports involved in the service
Creating test are located. Set the parameters as follows:
MEPs l Set Maintenance Association Name to the value of Maintenance
Association Name that is set in the preceding step.
l Set Board and Port to the Ethernet ports that are involved in the service
test.
l Set MP ID to different values for MEPs in the same MD.
l If the OAM information initiated by the MEP travels through the packet
switching unit on the local NE, set Direction of the MEP to Ingress.
Otherwise, set Direction to Egress.
l Set CC Status to Active, as the MEP ID is used to identify the MEP
during the LB test.
A.7.8.4 Required for the NE where the Ethernet ports involved in the OAM
Creating operation are located. Set the parameters as follows:
Remote MEPs l Set Maintenance Domain Name to the value of Maintenance
in an MA Domain Name that is set in the preceding step.
l Set Maintenance Association Name to the value of Maintenance
Association Name that is set in the preceding step.
l To ensure that an MEP can respond to the OAM operations initiated
by the other MEPs in the same MA, you need to set the other MEPs as
the remote MEPs.
Perform an LB Required.
test to test the The LB test result should show that no packet loss occurs.
Ethernet
service
configurations
Configuration Flowchart
Figure 8-21 provides the procedure for configuring QinQ-based E-Line services.
Optional
Configuring Ethernet
ports
Configuring IF_ETH
ports
Configuring LAGs
Configuring E-Line
services
Configuring QoS
Verifying Ethernet
service configurations
End
Operation Description
Operation Description
Operation Description
A.7.2.1 Required if LAG protection is configured for FE/GE ports or for the
Creating a Integrated IP radio that works in N+0/XPIC mode. Set the parameters as
LAG follows:
NOTE
For ISU2/ISX2 boards, if they have been added to a PLA group during radio link
configuration, the LAG does not need to be configured.
l Set LAG Type to the same value as that at the opposite end. Generally,
set LAG Type to Static at both ends.
l For FE/GE ports, set Load Sharing to the same value as that at the
opposite end. It is recommended that you set Load Sharing to Non-
Sharing at both ends, if the LAG is configured only to provide
protection. It is recommended that you set Load Sharing to Sharing
at both ends, if the LAG is configured to increase the bandwidth.
l Set Load Sharing to Sharing at both ends, if Integrated IP radio works
in N+0/XPIC mode and uses LAG protection.
l Set Revertive Mode to the same value as that at the opposite end.
Generally, set Revertive Mode to Revertive at both ends. This
parameter is valid only to LAGs whose Load Sharing is set to Non-
Sharing.
l It is recommended that the main and slave ports take the same settings
at both ends. In this case, you can set System Priority as required. It
is recommended that this parameter take its default value. This
parameter is valid only to static LAGs.
l For an air interface LAG, to enable microwave signal degrade to trigger
LAG switching, set Switch LAG upon Air Interface SD to
Enabled.
l Set Main Board, Main Port, and Selected Standby Ports according
to the network plan. It is recommended that the main and slave ports
take the same settings at both ends.
NOTE
Set the AM attributes to the same value for the microwave ports in a LAG.
Operation Description
A.7.3.1 Required.
Configuring Set the parameters according to the network planning information.
the QinQ Link
A.7.3.4 Required.
Configuring Set the parameters according to the network planning information.
UNI-NNI E-
Line Services
(Carried by
QinQ Links)
Operation Description
A.7.7.2 Required if the default mappings for the DS domain are inapplicable.
Modifying the Set the related parameters according to the network plan.
Mapping
Relationships You can learn the default mappings for the DS domain by referring to A.
for the DS 7.7.10 Querying the DS Domain of a Port.
Domain
A.7.7.3 Required if the trusted packet type of the port is different from the default
Changing the trusted packet type (C-VLAN priority) applied to the DS domain.
Ports Applied Set the related parameters according to the network plan.
to a DS Domain
and Their
Trusted Packet
Types
A.7.7.4 Required if you need to apply QoS policies other than DS and port shaping
Creating a Port for a specific port.
Policy Set the related parameters according to the network plan.
A.7.7.6 Required if you need to perform the ACL, CoS, CAR or shaping operation
Creating for a specific flow over the port.
Traffic Set the related parameters according to the network plan.
Operation Description
A.7.7.8 Required if you need to limit the egress bandwidth that an Ethernet service
Configuring occupies.
Port Shaping Set the related parameters according to the network plan.
Operation Description
A.7.8.1 Required for the NEs where the two Ethernet ports involved in the service
Creating an test are located. Set the parameters as follows:
MD l Set Maintenance Domain Name and Maintenance Domain Level to
the same values for the NEs.
l For an Ethernet service between two edge nodes on the transport
network, it is recommended that Maintenance Domain Level takes its
default value of 4. For an Ethernet service between two internal NEs
on the transport network, set Maintenance Domain Level to a value
smaller than 4. 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 of an Ethernet service between two
internal NEs on the transport network.
A.7.8.2 Required for the NEs where the two Ethernet ports involved in the service
Creating an test are located. Set the parameters as follows:
MA 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 NEs.
l Set Relevant Service to the same service for the NEs.
l It is recommended that you set CC Test Transmit Period to 1s.
Operation Description
A.7.8.3 Required for the NEs where the two Ethernet ports involved in the service
Creating test are located. Set the parameters as follows:
MEPs l Set Maintenance Association Name to the value of Maintenance
Association Name that is set in the preceding step.
l Set Board and Port to the Ethernet ports that are involved in the service
test.
l Set MP ID to different values for MEPs in the same MD.
l If the OAM information initiated by the MEP travels through the packet
switching unit on the local NE, set Direction of the MEP to Ingress.
Otherwise, set Direction to Egress.
l Set CC Status to Active, as the MEP ID is used to identify the MEP
during the LB test.
A.7.8.4 Required for the NE where the Ethernet ports involved in the OAM
Creating operation are located. Set the parameters as follows:
Remote MEPs l Set Maintenance Domain Name to the value of Maintenance
in an MA Domain Name that is set in the preceding step.
l Set Maintenance Association Name to the value of Maintenance
Association Name that is set in the preceding step.
l To ensure that an MEP can respond to the OAM operations initiated
by the other MEPs in the same MA, you need to set the other MEPs as
the remote MEPs.
Perform an LB Required.
test to test the The LB test result should show that no packet loss occurs.
Ethernet
service
configurations
Figure 8-22 Configuration flow chart (IEEE 802.1d bridge-based E-LAN services)
Required Start
Optional
Configuring Ethernet ports
Configuring LAGs
Configuring QoS
End
Operation Description
A.6.6.5 Required when you need to enable the port self-loop test and
Setting the automatic loopback shutdown functions or to enable the
Advanced broadcast packet suppression function.
Attributes Set Loopback Check, Loopback Port Shutdown,
of Ethernet Broadcast Packet Suppression, and Broadcast Packet
Ports Suppression Threshold according to the actual
requirements.
Operation Description
A.6.7.4 Optional.
Setting the When the IF_ETH port transmits an Ethernet service that
Advanced permits bit errors, such as a voice service or a video service,
Attributes you can set Error Frame Discard Enabled to Disabled.
of IF_ETH
NOTE
Ports
l For the ISU2/ISX2, it is recommended that you set Speed
Transmission at L2 and Speed Transmission at L3 to
Enabled, if the corresponding permission to enable the two
functions is already obtained.
l When Speed Transmission at L3 is set to Enabled,
Encapsulation Type of the ISU2 and ISX2 boards cannot be set
to Null.
l Set Speed Transmission at L2 and Speed Transmission at L3
consistently for both ends of a radio link.
Operation Description
A.7.2.1 Required if LAG protection is configured for FE/GE ports or for the
Creating a Integrated IP radio that works in N+0/XPIC mode. Set the parameters as
LAG follows:
NOTE
For ISU2/ISX2 boards, if they have been added to a PLA group during radio link
configuration, the LAG does not need to be configured.
l Set LAG Type to the same value as that at the opposite end. Generally,
set LAG Type to Static at both ends.
l For FE/GE ports, set Load Sharing to the same value as that at the
opposite end. It is recommended that you set Load Sharing to Non-
Sharing at both ends, if the LAG is configured only to provide
protection. It is recommended that you set Load Sharing to Sharing
at both ends, if the LAG is configured to increase the bandwidth.
l Set Load Sharing to Sharing at both ends, if Integrated IP radio works
in N+0/XPIC mode and uses LAG protection.
l Set Revertive Mode to the same value as that at the opposite end.
Generally, set Revertive Mode to Revertive at both ends. This
parameter is valid only to LAGs whose Load Sharing is set to Non-
Sharing.
l It is recommended that the main and slave ports take the same settings
at both ends. In this case, you can set System Priority as required. It
is recommended that this parameter take its default value. This
parameter is valid only to static LAGs.
l For an air interface LAG, to enable microwave signal degrade to trigger
LAG switching, set Switch LAG upon Air Interface SD to
Enabled.
l Set Main Board, Main Port, and Selected Standby Ports according
to the network plan. It is recommended that the main and slave ports
take the same settings at both ends.
NOTE
Set the AM attributes to the same value for the microwave ports in a LAG.
Operation Description
A.7.1.1 Required when an Ethernet ring needs to be protected and service loops
Creating need to be avoided on the Ethernet ring.
Ethernet Ring
Protection
Instances
A.7.1.2 Setting Required if the values of the default parameters of the ERPS timers need
the Parameters to be changed.
of Ethernet Set Hold-Off Time(ms), Guard Time(ms), WTR Time(mm:ss), and
Ring Protocol Packet Transmit Interval(s) according to the actual requirements. Set
these parameters to the same values for all the NEs on the network.
Operation Description
Operation Description
A.7.4.1 Required if you need to set certain MAC address entries not
Creating a to age.
Static MAC Set the parameters according to the network planning
Address information.
Entry
Operation Description
A.7.7.2 Required if the default mappings for the DS domain are inapplicable.
Modifying the Set the related parameters according to the network plan.
Mapping
Relationships You can learn the default mappings for the DS domain by referring to A.
for the DS 7.7.10 Querying the DS Domain of a Port.
Domain
A.7.7.3 Required if the trusted packet type of the port is different from the default
Changing the trusted packet type (C-VLAN priority) applied to the DS domain.
Ports Applied Set the related parameters according to the network plan.
to a DS Domain
and Their
Trusted Packet
Types
Operation Description
A.7.7.4 Required if you need to apply QoS policies other than DS and port shaping
Creating a Port for a specific port.
Policy Set the related parameters according to the network plan.
A.7.7.6 Required if you need to perform the ACL, CoS, CAR or shaping operation
Creating for a specific flow over the port.
Traffic Set the related parameters according to the network plan.
A.7.7.8 Required if you need to limit the egress bandwidth that an Ethernet service
Configuring occupies.
Port Shaping Set the related parameters according to the network plan.
Operation Description
A.7.8.1 Required for the NEs where the two Ethernet ports involved in the service
Creating an test are located. Set the parameters as follows:
MD l Set Maintenance Domain Name and Maintenance Domain Level to
the same values for the NEs.
l For an Ethernet service between two edge nodes on the transport
network, it is recommended that Maintenance Domain Level takes its
default value of 4. For an Ethernet service between two internal NEs
on the transport network, set Maintenance Domain Level to a value
smaller than 4. 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 of an Ethernet service between two
internal NEs on the transport network.
Operation Description
A.7.8.2 Required for the NEs where the two Ethernet ports involved in the service
Creating an test are located. Set the parameters as follows:
MA 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 NEs.
l Set Relevant Service to the same service for the NEs.
l It is recommended that you set CC Test Transmit Period to 1s.
A.7.8.3 Required for the NEs where the two Ethernet ports involved in the service
Creating test are located. Set the parameters as follows:
MEPs l Set Maintenance Association Name to the value of Maintenance
Association Name that is set in the preceding step.
l Set Board and Port to the Ethernet ports that are involved in the service
test.
l Set MP ID to different values for MEPs in the same MD.
l If the OAM information initiated by the MEP travels through the packet
switching unit on the local NE, set Direction of the MEP to Ingress.
Otherwise, set Direction to Egress.
l Set CC Status to Active, as the MEP ID is used to identify the MEP
during the LB test.
A.7.8.4 Required for the NE where the Ethernet ports involved in the OAM
Creating operation are located. Set the parameters as follows:
Remote MEPs l Set Maintenance Domain Name to the value of Maintenance
in an MA Domain Name that is set in the preceding step.
l Set Maintenance Association Name to the value of Maintenance
Association Name that is set in the preceding step.
l To ensure that an MEP can respond to the OAM operations initiated
by the other MEPs in the same MA, you need to set the other MEPs as
the remote MEPs.
Perform an LB Required.
test to test the The LB test result should show that no packet loss occurs.
Ethernet
service
configurations
Configuration Flowchart
Figure 8-23 provides the procedure for configuring IEEE 802.1q bridge-based E-LAN services.
Optional
Configure Ethernet ports.
Configure LAGs.
Configure QoS
End
The detailed information about the procedure in the flow chart is provided as follows.
Operation Description
A.6.6.5 Required when you need to enable the port self-loop test and
Setting the automatic loopback shutdown functions or to enable the
Advanced broadcast packet suppression function.
Attributes Set Loopback Check, Loopback Port Shutdown,
of Ethernet Broadcast Packet Suppression, and Broadcast Packet
Ports Suppression Threshold according to the requirements.
Operation Description
A.6.7.4 Optional.
Setting the When the IF_ETH port transmits an Ethernet service that
Advanced permits bit errors, such as a voice service or a video service,
Attributes you can set Error Frame Discard Enabled to Disabled.
of IF_ETH
NOTE
Ports
l For the ISU2/ISX2, it is recommended that you set Speed
Transmission at L2 and Speed Transmission at L3 to
Enabled, if the corresponding permission to enable the two
functions is already obtained.
l When Speed Transmission at L3 is set to Enabled,
Encapsulation Type of the ISU2 and ISX2 boards cannot be set
to Null.
l Set Speed Transmission at L2 and Speed Transmission at L3
consistently for both ends of a radio link.
Operation Description
A.7.2.1 Required if LAG protection is configured for FE/GE ports or for the
Creating a Integrated IP radio that works in N+0/XPIC mode. Set the parameters as
LAG follows:
NOTE
For ISU2/ISX2 boards, if they have been added to a PLA group during radio link
configuration, the LAG does not need to be configured.
l Set LAG Type to the same value as that at the opposite end. Generally,
set LAG Type to Static at both ends.
l For FE/GE ports, set Load Sharing to the same value as that at the
opposite end. It is recommended that you set Load Sharing to Non-
Sharing at both ends, if the LAG is configured only to provide
protection. It is recommended that you set Load Sharing to Sharing
at both ends, if the LAG is configured to increase the bandwidth.
l Set Load Sharing to Sharing at both ends, if Integrated IP radio works
in N+0/XPIC mode and uses LAG protection.
l Set Revertive Mode to the same value as that at the opposite end.
Generally, set Revertive Mode to Revertive at both ends. This
parameter is valid only to LAGs whose Load Sharing is set to Non-
Sharing.
l It is recommended that the main and slave ports take the same settings
at both ends. In this case, you can set System Priority as required. It
is recommended that this parameter take its default value. This
parameter is valid only to static LAGs.
l For an air interface LAG, to enable microwave signal degrade to trigger
LAG switching, set Switch LAG upon Air Interface SD to
Enabled.
l Set Main Board, Main Port, and Selected Standby Ports according
to the network plan. It is recommended that the main and slave ports
take the same settings at both ends.
NOTE
Set the AM attributes to the same value for the microwave ports in a LAG.
Operation Description
A.7.1.1 Required when an Ethernet ring needs to be protected and service loops
Creating need to be avoided on the Ethernet ring.
Ethernet Ring
Protection
Instances
A.7.1.2 Setting Required if the values of the default parameters of the ERPS timers need
the Parameters to be changed.
of Ethernet Set Hold-Off Time(ms), Guard Time(ms), WTR Time(mm:ss), and
Ring Protocol Packet Transmit Interval(s) according to the actual requirements. Set
these parameters to the same values for all the NEs on the network.
Table 8-34 Procedure for configuring IEEE 802.1q bridge-based E-LAN services
Operation Description
Operation Description
A.7.4.1 Required if you need to set certain MAC address entries not
Creating a to age.
Static MAC Set the parameters according to the network planning
Address information.
Entry
Operation Description
A.7.7.2 Required if the default mappings for the DS domain are inapplicable.
Modifying the Set the related parameters according to the network plan.
Mapping
Relationships You can learn the default mappings for the DS domain by referring to A.
for the DS 7.7.10 Querying the DS Domain of a Port.
Domain
A.7.7.3 Required if the trusted packet type of the port is different from the default
Changing the trusted packet type (C-VLAN priority) applied to the DS domain.
Ports Applied Set the related parameters according to the network plan.
to a DS Domain
and Their
Trusted Packet
Types
Operation Description
A.7.7.4 Required if you need to apply QoS policies other than DS and port shaping
Creating a Port for a specific port.
Policy Set the related parameters according to the network plan.
A.7.7.6 Required if you need to perform the ACL, CoS, CAR or shaping operation
Creating for a specific flow over the port.
Traffic Set the related parameters according to the network plan.
A.7.7.8 Required if you need to limit the egress bandwidth that an Ethernet service
Configuring occupies.
Port Shaping Set the related parameters according to the network plan.
Operation Description
A.7.8.1 Required for the NEs where the two Ethernet ports involved in the service
Creating an test are located. Set the parameters as follows:
MD l Set Maintenance Domain Name and Maintenance Domain Level to
the same values for the NEs.
l For an Ethernet service between two edge nodes on the transport
network, it is recommended that Maintenance Domain Level takes its
default value of 4. For an Ethernet service between two internal NEs
on the transport network, set Maintenance Domain Level to a value
smaller than 4. 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 of an Ethernet service between two
internal NEs on the transport network.
Operation Description
A.7.8.2 Required for the NEs where the two Ethernet ports involved in the service
Creating an test are located. Set the parameters as follows:
MA 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 NEs.
l Set Relevant Service to the same service for the NEs.
l It is recommended that you set CC Test Transmit Period to 1s.
A.7.8.3 Required for the NEs where the two Ethernet ports involved in the service
Creating test are located. Set the parameters as follows:
MEPs l Set Maintenance Association Name to the value of Maintenance
Association Name that is set in the preceding step.
l Set Board and Port to the Ethernet ports that are involved in the service
test.
l Set MP ID to different values for MEPs in the same MD.
l If the OAM information initiated by the MEP travels through the packet
switching unit on the local NE, set Direction of the MEP to Ingress.
Otherwise, set Direction to Egress.
l Set CC Status to Active, as the MEP ID is used to identify the MEP
during the LB test.
A.7.8.4 Required for the NE where the Ethernet ports involved in the OAM
Creating operation are located. Set the parameters as follows:
Remote MEPs l Set Maintenance Domain Name to the value of Maintenance
in an MA Domain Name that is set in the preceding step.
l Set Maintenance Association Name to the value of Maintenance
Association Name that is set in the preceding step.
l To ensure that an MEP can respond to the OAM operations initiated
by the other MEPs in the same MA, you need to set the other MEPs as
the remote MEPs.
Perform an LB Required.
test to test the The LB test result should show that no packet loss occurs.
Ethernet
service
configurations
Configuration Flowchart
Figure 8-24 provides the procedure for configuring IEEE 802.1ad bridge-based E-LAN
services.
Optional
Configuring Ethernet ports
Configuring LAGs
Configuring QoS
End
The detailed information about the procedure in the flow chart is provided as follows.
Operation Description
A.6.6.5 Required when you need to enable the port self-loop test and
Setting the automatic loopback shutdown functions or to enable the
Advanced broadcast packet suppression function.
Attributes Set Loopback Check, Loopback Port Shutdown,
of Ethernet Broadcast Packet Suppression, and Broadcast Packet
Ports Suppression Threshold according to the requirements.
Operation Description
A.6.7.4 Optional.
Setting the When the IF_ETH port transmits an Ethernet service that
Advanced permits bit errors, such as a voice service or a video service,
Attributes you can set Error Frame Discard Enabled to Disabled.
of IF_ETH
NOTE
Ports
l For the ISU2/ISX2, it is recommended that you set Speed
Transmission at L2 and Speed Transmission at L3 to
Enabled, if the corresponding permission to enable the two
functions is already obtained.
l When Speed Transmission at L3 is set to Enabled,
Encapsulation Type of the ISU2 and ISX2 boards cannot be set
to Null.
l Set Speed Transmission at L2 and Speed Transmission at L3
consistently for both ends of a radio link.
Operation Description
A.7.2.1 Required if LAG protection is configured for FE/GE ports or for the
Creating a Integrated IP radio that works in N+0/XPIC mode. Set the parameters as
LAG follows:
NOTE
For ISU2/ISX2 boards, if they have been added to a PLA group during radio link
configuration, the LAG does not need to be configured.
l Set LAG Type to the same value as that at the opposite end. Generally,
set LAG Type to Static at both ends.
l For FE/GE ports, set Load Sharing to the same value as that at the
opposite end. It is recommended that you set Load Sharing to Non-
Sharing at both ends, if the LAG is configured only to provide
protection. It is recommended that you set Load Sharing to Sharing
at both ends, if the LAG is configured to increase the bandwidth.
l Set Load Sharing to Sharing at both ends, if Integrated IP radio works
in N+0/XPIC mode and uses LAG protection.
l Set Revertive Mode to the same value as that at the opposite end.
Generally, set Revertive Mode to Revertive at both ends. This
parameter is valid only to LAGs whose Load Sharing is set to Non-
Sharing.
l It is recommended that the main and slave ports take the same settings
at both ends. In this case, you can set System Priority as required. It
is recommended that this parameter take its default value. This
parameter is valid only to static LAGs.
l For an air interface LAG, to enable microwave signal degrade to trigger
LAG switching, set Switch LAG upon Air Interface SD to
Enabled.
l Set Main Board, Main Port, and Selected Standby Ports according
to the network plan. It is recommended that the main and slave ports
take the same settings at both ends.
NOTE
Set the AM attributes to the same value for the microwave ports in a LAG.
Operation Description
A.7.1.1 Required when an Ethernet ring needs to be protected and service loops
Creating need to be avoided on the Ethernet ring.
Ethernet Ring
Protection
Instances
A.7.1.2 Setting Required if the values of the default parameters of the ERPS timers need
the Parameters to be changed.
of Ethernet Set Hold-Off Time(ms), Guard Time(ms), WTR Time(mm:ss), and
Ring Protocol Packet Transmit Interval(s) according to the actual requirements. Set
these parameters to the same values for all the NEs on the network.
Table 8-40 Procedure for configuring IEEE 802.1ad bridge-based E-LAN services
Operation Description
Operation Description
A.7.4.1 Required if you need to set certain MAC address entries not
Creating a to age.
Static MAC Set the parameters according to the network planning
Address information.
Entry
Operation Description
A.7.7.2 Required if the default mappings for the DS domain are inapplicable.
Modifying the Set the related parameters according to the network plan.
Mapping
Relationships You can learn the default mappings for the DS domain by referring to A.
for the DS 7.7.10 Querying the DS Domain of a Port.
Domain
A.7.7.3 Required if the trusted packet type of the port is different from the default
Changing the trusted packet type (C-VLAN priority) applied to the DS domain.
Ports Applied Set the related parameters according to the network plan.
to a DS Domain
and Their
Trusted Packet
Types
Operation Description
A.7.7.4 Required if you need to apply QoS policies other than DS and port shaping
Creating a Port for a specific port.
Policy Set the related parameters according to the network plan.
A.7.7.6 Required if you need to perform the ACL, CoS, CAR or shaping operation
Creating for a specific flow over the port.
Traffic Set the related parameters according to the network plan.
A.7.7.8 Required if you need to limit the egress bandwidth that an Ethernet service
Configuring occupies.
Port Shaping Set the related parameters according to the network plan.
Operation Description
A.7.8.1 Required for the NEs where the two Ethernet ports involved in the service
Creating an test are located. Set the parameters as follows:
MD l Set Maintenance Domain Name and Maintenance Domain Level to
the same values for the NEs.
l For an Ethernet service between two edge nodes on the transport
network, it is recommended that Maintenance Domain Level takes its
default value of 4. For an Ethernet service between two internal NEs
on the transport network, set Maintenance Domain Level to a value
smaller than 4. 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 of an Ethernet service between two
internal NEs on the transport network.
Operation Description
A.7.8.2 Required for the NEs where the two Ethernet ports involved in the service
Creating an test are located. Set the parameters as follows:
MA 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 NEs.
l Set Relevant Service to the same service for the NEs.
l It is recommended that you set CC Test Transmit Period to 1s.
A.7.8.3 Required for the NEs where the two Ethernet ports involved in the service
Creating test are located. Set the parameters as follows:
MEPs l Set Maintenance Association Name to the value of Maintenance
Association Name that is set in the preceding step.
l Set Board and Port to the Ethernet ports that are involved in the service
test.
l Set MP ID to different values for MEPs in the same MD.
l If the OAM information initiated by the MEP travels through the packet
switching unit on the local NE, set Direction of the MEP to Ingress.
Otherwise, set Direction to Egress.
l Set CC Status to Active, as the MEP ID is used to identify the MEP
during the LB test.
A.7.8.4 Required for the NE where the Ethernet ports involved in the OAM
Creating operation are located. Set the parameters as follows:
Remote MEPs l Set Maintenance Domain Name to the value of Maintenance
in an MA Domain Name that is set in the preceding step.
l Set Maintenance Association Name to the value of Maintenance
Association Name that is set in the preceding step.
l To ensure that an MEP can respond to the OAM operations initiated
by the other MEPs in the same MA, you need to set the other MEPs as
the remote MEPs.
Perform an LB Required.
test to test the The LB test result should show that no packet loss occurs.
Ethernet
service
configurations
As shown in Figure 8-25, NE1 is a terminal station of a backhaul network. The service
requirements are as follows:
l NE1 transparently transmits the Ethernet services from the BTS to NE2 in point-to-point
manner.
l DSCP flags are used to identify the priorities of the Ethernet services from the BTS.
To meet the preceding requirements, point-to-point transparently transmitted E-line services are
configured; in addition, corresponding QoS processing is configured.
Backhaul network
The connections of Ethernet links shown in Figure 8-25 are described as follows.
Between NE1 and the BTS 1-EM6T-3 Configure this port to access
services from the BTS.
Ethernet Port
Table 8-44 provides the information about the Ethernet port involved in the service.
Parameter 1-EM6T-3
NOTE
l In this example, the GE port on the BTS works in the auto-negotiation mode. Hence, the GE port that accesses
the BTS must work in the auto-negotiation mode. If the peer Ethernet port works in another mode, the local
Ethernet port must work in the same mode. The working modes of the Ethernet ports inside the network are
planned as auto-negotiation.
l In this example, to ensure that the Ethernet frames that carry more than one tag such as QinQ can traverse
the equipment, the maximum frame length is set to 1536 (bytes). If the equipment needs to transmit jumbo
frames with a greater length, set the maximum frame length according to the actual length of a jumbo frame.
Normally, if the equipment is interconnected with BTSs, the maximum frame length can also assume its
default value of 1522.
l Generally, the flow control function is enabled only when the NE or the peer equipment is inadequate for
QoS processing. The planning information of flow control must be the same for the equipment at both ends.
Parameter 3-IFU2-1
Parameter NE1
Service ID 1
Direction UNI-UNI
QoS (DiffServ)
DS is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the BTS
services be allocated according to the service type. Then, the transmission network creates the
corresponding DS domain according to the allocated VLAN priority or DSCP value. Each
Ethernet port involved in the service must use the same DS configuration.
In this example, the BTS services are allocated with corresponding DSCP values according to
the service type, and the NEs allocate the PHB service classes according to the DSCP value, as
shown in Table 8-47. Each Ethernet port involved in the service uses the same DS configuration.
CS7 56 -
CS6 48 -
AF4 32 -
AF1 8 -
NOTE
l During the mapping of the PHB service class, CS7 or CS6 is not recommended, because CS7 or CS6 may
be used to transmit Ethernet protocol packets or inband DCN packets on the NE.
l The default mapping relationships for the DS domain comply with the network planning requirements and
therefore do not need to be modified.
l The required trusted packet type is not the C-VLAN priority but DSCP value. Therefore, the trusted packet
type needs to be modified for service-associated Ethernet ports applied in the default DS domain.
Table 8-48 lists the queue scheduling mode used by each Ethernet port involved in the service
in this example.
CS7 SP
CS6 SP
EF SP
BE SP
Procedure
Step 1 See A.7.3.2 Configuring UNI-UNI E-Line Services and configure the E-Line services.
Parameter Value
Service ID 1
Parameter Value
Direction UNI-UNI
----End
Procedure
Step 1 See A.6.6.1 Setting the Basic Attributes of Ethernet Ports and set the general attributes of
the Ethernet port.
Parameter Value
1-EM6T-3
----End
Procedure
Step 1 Follow instructions in A.7.7.2 Modifying the Mapping Relationships for the DS Domain and
change the mapping relationships for the DS domain.
The values for the related parameters that need to be set in the main interface are provided as
follows.
Parameter Value
Mapping Relation ID 1
The values for the related parameters that need to be set in the Ingress Mapping Relation tab
page are provided as follows.
AF11
AF21
AF31
AF41
EF
CS6
CS7
The values for the related parameters that need to be set in the Egress Mapping Relation tab
page are provided as follows.
AF11
AF21
AF31
AF41
EF
CS6
CS7
NOTE
l The AF1 is classified into three sub service classes, namely, AF11, AF12, and AF13, only one of which is
valid. In this example, the AF11 is used. It is the same case with the AF2, AF3, and AF4.
l The default mapping relationships for the DS domain comply with the network planning requirements and
therefore do not need to be modified.
Step 2 Follow instructions in A.7.7.3 Changing the Ports Applied to a DS Domain and Their
Trusted Packet Types and change the ports that are applied to the DS domain and their trusted
packet types.
1-EM6T-3 ip-dscp
3-IFU2-1
NOTE
The required trusted packet type is not the C-VLAN priority but DSCP value. Therefore, the trusted packet type
needs to be modified for service-associated Ethernet ports applied in the default DS domain.
Step 3 Follow instructions in A.7.7.4 Creating a Port Policy and create the port policy.
The values for the WRR scheduling policy parameters are provided as follows.
Parameter Value
Policy ID 2
The values for the port policy parameters are provided as follows.
Parameter Value
Policy ID 1
Step 4 Follow instructions in A.7.7.7 Setting the Port That Uses the Port Policy and set the ports that
use the port policy.
The values for the related parameters are provided as follows.
Parameter Value
Port_Comm
Port 1-EM6T-3
3-IFU2-1
----End
Procedure
Step 1 See A.7.8.1 Creating an MD and create an MD.
The values for the related parameters are provided as follows.
Parameter Value
NE1
Parameter Value
NE1
Parameter Value
NE1
VLAN - -
MP ID 101 102
NE1
Step 5 See perform an LB test to test the Ethernet service configurations and test the E-Line service.
Use MEP ID 101 as the source maintenance point and MEP ID 102 as the sink maintenance
point to perform the LB test.
No packet loss occurs.
----End
l BTS11, BTS12, and BTS15 provide FE ports whose port rate is 100 Mbit/s.
l Services transmitted by each BTS carry VLAN IDs, and VLAN IDs on the entire network
are planned in a unified manner.
l VLAN priorities are configured on each BTS according to service types.
To meet the preceding requirements, VLAN-based E-Line services are configured for service
transmission on each NE; in addition, corresponding QoS processing is configured.
BTS12
VLAN 110
FE
R4
GE
NE14 Packet network
FE
NE13 NE12 NE11
R4
FE
NE16 NE15 BTS11
VLAN 100
R4
BTS15
VLAN 120
The connections of Ethernet links shown in Figure 8-26 are described as follows.
Parameter 1-EM6T-1
Parameter 1-EM6T-3
Parameter 1-EM6T-3
NOTE
l In this example, the FE ports on all the BTSs work in auto-negotiation mode. Therefore, the FE/GE port of
each NE that accesses services must work in auto-negotiation mode. If the peer Ethernet port works in
another mode, the local Ethernet port must work in the same mode. The working modes of the Ethernet ports
inside the network are planned as auto-negotiation.
l In this example, to ensure that the Ethernet frames that carry more than one tag such as QinQ can traverse
the equipment, the maximum frame length is set to 1536 (bytes). If the equipment needs to transmit jumbo
frames with a greater length, set the maximum frame length according to the actual length of a jumbo frame.
Normally, if the equipment is interconnected with BTSs, the maximum frame length can also assume its
default value of 1522.
l Normally, the flow control function is enabled only when the NE or the peer equipment is inadequate for
QoS processing. The planning information of flow control must be the same for the equipment at both ends.
l In this example, all the services carry VLAN IDs. Therefore, the tag attributes of all the ports are tag aware.
Tag attribute Tag aware Tag aware Tag aware Tag aware
Parameter 3-ISU2-1
Figure 8-27 Information about VLAN-based E-Line services (in an end-to-end mode)
Links-1: NE11 - NE12 - NE13 -NE15-NE16
C:100
RNC-BTS11
1-EM6T-1(C:100) 1-EM6T-3(C:100)
C:120 C:120 C:120 C:120
RNC-BTS15
1-EM6T-1(C:120) 1-EM6T-3(C:120)
C:110 C:110
RNC-BTS12
1-EM6T-1(C:110)
Links-2: NE13-NE14
NE13 NE14
1-EM6T-1 3-ISU2-1 3-ISU2-1
C:110 C:110
RNC-BTS12
1-EM6T-3(C:110)
C: C-VLAN S: S-VLAN
Pass through
Add/Drop
Foward
Table 8-63 to Table 8-67 provide the planning information of the VLAN-based E-Line services.
Parameter NE12
Service ID 1 2
Parameter NE13
Service ID 1 2
Parameter NE4
BTS12 to NE13
Service ID 1
Parameter NE15
NE16 to NE13
Service ID 1
Parameter NE16
BTS15 to NE15
Service ID 1
Parameter NE16
BTS15 to NE15
QoS (DiffServ)
DS is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the BTS
services be allocated by the service type. Then, the transmission network creates the
corresponding DS domain according to the allocated VLAN priority or DSCP value. Each
Ethernet port involved in the service must use the same DS configuration.
In this example, the BTS services are allocated with corresponding VLAN priorities according
to the service type, and the NEs allocate the PHB service classes according to the VLAN priority,
as provided in Table 8-68. Each Ethernet port involved in the service uses the same DS
configuration.
CS7 7 -
CS6 6 -
AF4 4 -
AF1 1 -
NOTE
l During the mapping of the PHB service class, CS7 or CS6 is not recommended, because CS7 or CS6 may
be used to transmit Ethernet protocol packets or inband DCN packets on the NE.
l The default mapping relationships for the DS domain comply with the network planning requirements and
therefore do not need to be modified.
l The default trusted packet type for each port that is applied for the default DS domain is C-VLAN priority
and therefore does not need to be modified.
Table 8-69 lists the queue scheduling mode used by each Ethernet port involved in the service
in this example.
CS7 SP
CS6 SP
EF SP
BE SP
Procedure
Step 1 See A.7.3.2 Configuring UNI-UNI E-Line Services and configure the E-Line services.
l The values for the related parameters of NE12 are provided as follows.
Parameter Value
Service ID 1 2
Parameter Value
l The values for the related parameters of NE13 are provided as follows.
Parameter Value
Service ID 1 2
l The values for the related parameters of NE14 are provided as follows.
Parameter Value
BTS12 to NE13
Service ID 1
Direction UNI-UNI
l The values for the related parameters of NE16 are provided as follows.
Parameter Value
BTS15 to NE15
Service ID 1
Direction UNI-UNI
Parameter Value
BTS15 to NE15
----End
Procedure
Step 1 See A.6.6.1 Setting the Basic Attributes of Ethernet Ports and set the general attributes of
Ethernet ports.
l The values for the related parameters of NE12 are provided as follows.
Parameter Value
1-EM6T-1 1-EM6T-3
l The values for the related parameters of NE13 are provided as follows.
Parameter Value
1-EM6T-1
l The values for the related parameters of NE14 are provided as follows.
Parameter Value
1-EM6T-3
l The values for the related parameters of NE16 are provided as follows.
Parameter Value
1-EM6T-3
----End
Procedure
Step 1 Follow instructions in A.7.7.2 Modifying the Mapping Relationships for the DS Domain and
change the mapping relationships for the DS domain.
NOTE
The actual mapping relationships for the default DS domain comply with the network planning information.
Therefore, you can skip this step.
The values for the related parameters that need to be set in the main interface are provided as
follows.
Parameter Value
Mapping Relation ID 1
The values for the related parameters that need to be set in the Ingress Mapping Relation tab
page are provided as follows.
1 AF11
2 AF21
3 AF31
4 AF41
5 EF
6 CS6
7 CS7
The values for the related parameters that need to be set in the Egress Mapping Relation tab
page are provided as follows.
AF11 1
AF21 2
AF31 3
AF41 4
EF 5
CS6 6
CS7 7
NOTE
The AF1 is classified into three sub service classes, namely, AF11, AF12, and AF13, only one of which is valid.
In this example, the AF11 is used. It is the same case with the AF2, AF3, and AF4.
Step 2 Follow instructions in A.7.7.3 Changing the Ports Applied to a DS Domain and Their
Trusted Packet Types and change the ports that are applied to the DS domain and their trusted
packet types.
NOTE
The actual ports that are applied to the default DS domain and their trusted packet types comply with the network
planning information. Therefore, you can skip this step.
l The values for the related parameters of NE12 are provided as follows.
1-EM6T-1 CVLAN
1-EM6T-3
3-ISU2-1
l The values for the related parameters of NE13 are provided as follows.
3-ISU2-1 CVLAN
4-ISU2-1
1-EM6T-1
l The values for the related parameters of NE14 are provided as follows.
3-ISU2-1 CVLAN
1-EM6T-3
l The values for the related parameters of NE15 are provided as follows.
3-ISU2-1 CVLAN
4-ISU2-1
l The values for the related parameters of NE16 are provided as follows.
1-EM6T-3 CVLAN
3-ISU2-1
Step 3 Follow instructions in A.7.7.4 Creating a Port Policy and create the port policy.
The values for the WRR scheduling policy parameters of NE12 to NE16 are provided as follows.
Parameter Value
Policy ID 2
The values for the port policy parameters of NE12 to NE16 are provided as follows.
Parameter Value
Policy ID 1
Step 4 Follow instructions in A.7.7.7 Setting the Port That Uses the Port Policy and set the ports that
use the port policy.
l The values for the related parameters of NE12 are provided as follows.
Parameter Value
Port 1-EM6T-1
1-EM6T-3
3-ISU2-1
l The values for the related parameters of NE13 are provided as follows.
Parameter Value
Port 3-ISU2-1
4-ISU2-1
1-EM6T-1
l The values for the related parameters of NE14 are provided as follows.
Parameter Value
Port 3-ISU2-1
l The values for the related parameters of NE15 are provided as follows.
Parameter Value
Port 3-ISU2-1
4-ISU2-1
l The values for the related parameters of NE16 are provided as follows.
Parameter Value
Port 3-ISU2-1
----End
Procedure
Step 1 See A.7.8.1 Creating an MD and configure the MD for NE12, NE14, and NE16.
Parameter Value
Maintenance 4 4 4
Domain Level
Step 2 See A.7.8.2 Creating an MA and create the maintenance association (MA) for NE12, NE14,
and NE16.
l The values for the relevant parameters of NE12 are provided as follows.
l Parameter Value
Relevant 1- 1- 1- 1-
Service BTS11toNE11 NE13toNE11_ NE13toNE11_ NE13toNE11_
_Vline Vline Vline Vline
CC Test 1s 1s 1s 1s
Transmit
Period
l The values for the relevant parameters of NE14 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE16 are provided as follows.
Parameter Value
Step 3 See A.7.8.3 Creating MEPs and create the MEP for NE12, NE14, and NE16.
l The values for the related parameters of NE12 are provided as follows.
Parameter Value
l The values for the related parameters of NE14 are provided as follows.
Parameter Value
Board 1-EM6T-3
Port 1-EM6T-3
VLAN 110
MP ID 401
Direction Ingress
CC Status Active
l The values for the related parameters of NE16 are provided as follows.
Parameter Value
Board 1-EM6T
Port 1-EM6T-3
VLAN 120
MP ID 601
Direction Ingress
CC Status Active
Step 4 See A.7.8.4 Creating Remote MEPs in an MA and create the remote MEP points for NE12,
NE14, and NE16.
The values for the related parameters of NE12 are provided as follows.
Parameter Value
The values for the related parameters of NE14 are provided as follows.
Parameter Value
The values for the related parameters of NE16 are provided as follows.
Parameter Value
Parameter Value
Step 5 See perform an LB test to test the Ethernet service configurations and test the E-Line services
on NE12.
l Perform the LB test by considering the MEP whose MEP ID is 200 as the source MEP and
the MEP whose MEP ID is 201 as the sink MEP.
l Perform the LB test by considering the MEP whose MEP ID is 202 as the source MEP and
the MEP whose MEP ID is 401 as the sink MEP.
l Perform the LB test by considering the MEP whose MEP ID is 205 as the source MEP and
the MEP whose MEP ID is 601 as the sink MEP.
There should be no packets lost during the LB tests.
----End
Based on 6.5 Configuration Example (Radio Links on the Hybrid Radio Chain Network),
configure Ethernet services according to the following requirements:
To meet the preceding requirements, QinQ-based E-Line services are configured for service
transmission on each NE; in addition, corresponding QoS processing is configured.
FE
R4
RNC
GE
NE14 GE
FE
NE13 NE12 NE11 SVLAN
200,201,202
R4
FE BTS11
NE15 SVLAN 200
NE16
R4
BTS15
SVLAN 202
NOTE
In this example, the RNC must be capable of processing S-VLAN tags.
The connections of Ethernet links shown in Figure 8-28 are described as follows.
Between NE11 and 1-EM6T-1 Main port of a LAG Configure these ports
the RNC to transmit backhaul
1-EM6T-2 Slave port of a LAG services from BTSs.
Parameter 1-EM6T-1
Parameter 1-EM6T-1
Parameter 1-EM6T-3
Parameter 1-EM6T-3
NOTE
l In this example, the FE ports on all the BTSs work in auto-negotiation mode. Therefore, the FE/GE port of
each NE that accesses services must work in auto-negotiation mode. If the peer Ethernet port works in
another mode, the local Ethernet port must work in the same mode. The working modes of the Ethernet ports
inside the network are planned as auto-negotiation.
l In this example, to ensure that the Ethernet frames that carry more than one tag such as QinQ can traverse
the equipment, the maximum frame length is set to 1536 (bytes). If the equipment needs to transmit jumbo
frames with a greater length, set the maximum frame length according to the actual length of a jumbo frame.
l Normally, the flow control function is enabled only when the NE or the peer equipment is inadequate for
QoS processing. The planning information of flow control must be the same for the equipment at both ends.
l In this example, all the NNI ports are connected to Huawei equipment. Therefore, the QinQ type domain of
the NNI ports assumes the default value of 0x88a8.
Parameter 3-ISU2-1
NOTE
All the IF_ETH ports are connected to Huawei equipment. Therefore, it is recommended that you need to set
the QinQ type domain to 0x88a8 for the IF_ETH ports.
To improve the reliability of service transmission, NE11 and the RNC are interconnected through
the LAG formed by two GE links. Table 8-87 provides the planning information.
Parameter NE11
NOTE
In this example, the bandwidth of the Ethernet services is much lower than the bandwidth of a GE port. Therefore,
you need not configure the LAG to the load-sharing mode for increasing the bandwidth.
Figure 8-29 shows the planning information of the QinQ-based E-Line services.
S:200
RNC-BTS11
1-EM6T-1(S:200) 1-EM6T-3(null)
S:202 S:202 S:202 S:202
RNC-BTS15
1-EM6T-1(S:202) 1-EM6T-3(null)
S:201 S:201
RNC-BTS12
1-EM6T-1(S:201)
Links-2: NE13-NE14
NE13 NE14
1-EM6T-1 3-ISU2-1 3-ISU2-1
S:201 S:201
RNC-BTS12
1-EM6T-3(null)
C: C-VLAN S: S-VLAN
Pass through
Add/Drop
Foward
Table 8-88 to Table 8-93 provide the planning information of the QinQ-based E-Line services.
Parameter NE11
Service ID 1 2 3
Source port - - -
Source C-VLANs - - -
Parameter NE12
Service ID 1 2 3
Source C-VLANs - - -
Parameter NE13
Service ID 1 2
Source port - -
Source C-VLANs - -
Parameter NE14
BTS12 to NE13
Service ID 1
Source C-VLANs -
Parameter NE15
BTS15 to NE13
Service ID 1
Source port -
Source C-VLANs -
Parameter NE16
BTS15 to NE15
Service ID 1
Source C-VLANs -
QoS (DiffServ)
DS is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the BTS
services be allocated by the service type. Then, the transmission network creates the
corresponding DS domain according to the allocated VLAN priority or DSCP value. Each
Ethernet port involved in the service must use the same DS configuration.
In this example, the BTS services are allocated with corresponding VLAN priorities according
to the service type, and the NEs allocate the PHB service classes according to the VLAN priority,
as provided in Table 8-94. Each Ethernet port involved in the service uses the same DS
configuration.
CS7 7 -
CS6 6 -
AF4 4 -
AF1 1 -
NOTE
l During the mapping of the PHB service class, CS7 or CS6 is not recommended, because CS7 or CS6 may
be used to transmit Ethernet protocol packets or inband DCN packets on the NE.
l The default mapping relationships for the DS domain comply with the network planning requirements and
therefore do not need to be modified.
l The default trusted packet type for each port that is applied for the default DS domain is C-VLAN priority
and therefore needs to be modified as required.
Table 8-95 lists the queue scheduling mode used by each Ethernet port involved in the service
in this example.
CS7 SP
CS6 SP
EF SP
BE SP
Procedure
Step 1 See A.6.6.1 Setting the Basic Attributes of Ethernet Ports and set the basic attributes of
Ethernet ports.
l The values for the related parameters of NE11 are provided as follows.
Parameter Value
1-EM6T-1 1-EM6T-2
l The values for the related parameters of NE12 are provided as follows.
Parameter Value
1-EM6T-3 1-EM6T-1
l The values for the related parameters of NE13 are provided as follows.
Parameter Value
1-EM6T-1
l The values for the related parameters of NE14 are provided as follows.
Parameter Value
1-EM6T-3
l The values for the related parameters of NE16 are provided as follows.
Parameter Value
1-EM6T-3
Step 2 See A.6.6.3 Setting the Layer 2 Attributes of Ethernet Ports and set Layer 2 attributes of
Ethernet ports
l The values for the related parameters of NE11 are provided as follows.
Parameter Value
1-EM6T-1 1-EM6T-2
l The values for the related parameters of NE12 are provided as follows.
Parameter Value
1-EM6T-3 1-EM6T-1
l The values for the related parameters of NE13 are provided as follows.
Parameter Value
1-EM6T-1
l The values for the related parameters of NE14 are provided as follows.
Parameter Value
1-EM6T-3
l The values for the related parameters of NE16 are provided as follows.
Parameter Value
1-EM6T-3
Step 3 See A.6.7.1 Setting the Basic Attributes of IF_ETH Ports and set the basic attributes of
IF_ETH ports.
l The values for the related parameters of NE11 are provided as follows.
Parameter Value
3-ISU2-1 5-ISU2-1
l The values for the related parameters of NE12 are provided as follows.
Parameter Value
3-ISU2-1 5-ISU2-1
l The values for the related parameters of NE13 are provided as follows.
Parameter Value
l The values for the related parameters of NE14 are provided as follows.
Parameter Value
3-ISU2-1 5-ISU2-1
l The values for the related parameters of NE15 are provided as follows.
Parameter Value
l The values for the related parameters of NE16 are provided as follows.
Parameter Value
3-ISU2-1
Step 4 See A.6.7.2 Setting the Layer 2 Attributes of IF_ETH Ports and set the Layer 2 attributes of
IF_ETH ports.
l The values for the related parameters of NE11 are provided as follows.
Parameter Value
3-ISU2-1 5-ISU2-1
l The values for the related parameters of NE12 are provided as follows.
Parameter Value
3-ISU2-1 5-ISU2-1
l The values for the related parameters of NE13 are provided as follows.
Parameter Value
l The values for the related parameters of NE14 are provided as follows.
Parameter Value
3-ISU2-1 5-ISU2-1
l The values for the related parameters of NE15 are provided as follows.
Parameter Value
l The values for the related parameters of NE16 are provided as follows.
Parameter Value
3-ISU2-1
----End
Procedure
Step 1 See A.7.2.1 Creating a LAG and create the LAG for NE11.
The values for the required parameters that are set in the main interface are as follows.
Parameter Value
The values for the related parameters that need to be set in Port Setting are as follows.
Parameter Value
----End
Procedure
Step 1 See A.7.3.4 Configuring UNI-NNI E-Line Services (Carried by QinQ Links) and configure
the E-Line services.
l The values for the related parameters of NE11 are provided as follows.
The values for the required parameters that are set in the main interface are as follows.
Parameter Value
Service ID 1 2 3
Source VLAN - - -
ID
Parameter Value
QinQ Link ID 1 2 3
Parameter Value
l The values for the related parameters of NE12 are provided as follows.
The values for the required parameters that are set in the main interface are as follows.
Parameter Value
Service ID 1 2 3
Source VLAN ID - - -
Parameter Value
QinQ Link 1 2 3 4 5
ID
Parameter Value
l The values for the related parameters of NE13 are provided as follows.
The values for the required parameters that are set in the main interface are as follows.
Parameter Value
Service ID 1 2
Parameter Value
QinQ Link ID 1 2 3 4
Parameter Value
l The values for the related parameters of NE14 are provided as follows.
The values for the required parameters that are set in the main interface are as follows.
Parameter Value
BTS12 to NE13
Service ID 1
Parameter Value
BTS12 to NE13
Direction UNI-NNI
Source VLAN ID -
Parameter Value
BTS12 to NE13
QinQ Link ID 1
Port 3-ISU2-1
S-Vlan ID 201
Parameter Value
l The values for the related parameters of NE15 are provided as follows.
The values for the required parameters that are set in the main interface are as follows.
Parameter Value
BTS15 to NE13
Service ID 1
Parameter Value
BTS15 to NE13
Direction NNI-NNI
Parameter Value
BTS15 to NE13
QinQ Link ID 1 2
Parameter Value
Enable Port - -
l The values for the related parameters of NE16 are provided as follows.
Parameter Value
BTS15 to NE15
Service ID 1
Direction UNI-NNI
Parameter Value
BTS15 to NE15
Source VLAN ID -
QinQ Link ID 1
Port 3-ISU2-1
S-Vlan ID 202
----End
Procedure
Step 1 Follow instructions in A.7.7.2 Modifying the Mapping Relationships for the DS Domain and
change the mapping relationships for the DS domain.
The values for the required parameters that are set in the main interface are as follows.
Parameter Value
Mapping Relation ID 1
The values for the related parameters that need to be set in the Ingress Mapping Relation tab
page are provided as follows.
1 1 AF11
2 2 AF21
3 3 AF31
4 4 AF41
5 5 EF
6 6 CS6
7 7 CS7
The values for the related parameters that need to be set in the Egress Mapping Relation tab
page are provided as follows.
AF11 1 1
AF21 2 2
AF31 3 3
AF41 4 4
EF 5 5
CS6 6 6
CS7 7 7
NOTE
l The AF1 is classified into three sub service classes, namely, AF11, AF12, and AF13, only one of which is
valid. In this example, the AF11 is used. It is the same case with the AF2, AF3, and AF4.
l The default mapping relationships for the DS domain comply with the network planning requirements and
therefore do not need to be modified.
Step 2 Follow instructions in A.7.7.3 Changing the Ports Applied to a DS Domain and Their
Trusted Packet Types and change the ports that are applied to the DS domain and their trusted
packet types.
l The values for the related parameters of NE11 are provided as follows.
3-ISU2-1 SVLAN
1-EM6F-1 CVLAN
l The values for the related parameters of NE12 are provided as follows.
1-EM6T-3 CVLAN
1-EM6T-1 SVLAN
3-ISU2-1 SVLAN
l The values for the related parameters of NE13 are provided as follows.
3-ISU2-1 SVLAN
4-ISU2-1 SVLAN
1-EM6T-1 SVLAN
l The values for the related parameters of NE14 are provided as follows.
1-EM6T-3 CVLAN
3-ISU2-1 SVLAN
l The values for the related parameters of NE15 are provided as follows.
3-ISU2-1 SVLAN
4-ISU2-1 SVLAN
l The values for the related parameters of NE16 are provided as follows.
3-ISU2-1 SVLAN
1-EM6T-3 CVLAN
Step 3 Follow instructions in A.7.7.4 Creating a Port Policy and create the port policy.
The values for the WRR scheduling policy parameters of NE11 to NE16 are provided as follows.
Parameter Value
Policy ID 2
The values for the port policy parameters of NE11 to NE16 are provided as follows.
Parameter Value
Policy ID 1
Step 4 Follow instructions in A.7.7.7 Setting the Port That Uses the Port Policy and set the ports that
use the port policy.
l The values for the related parameters of NE11 are provided as follows.
Parameter Value
Port 3-ISU2-1
1-EM6T-1
l The values for the related parameters of NE12 are provided as follows.
Parameter Value
Port 1-EM6T-1
l The values for the related parameters of NE13 are provided as follows.
Parameter Value
Port 3-ISU2-1
4-ISU2-1
1-EM6T-1
l The values for the related parameters of NE14 are provided as follows.
Parameter Value
Port 3-ISU2-1
l The values for the related parameters of NE15 are provided as follows.
Parameter Value
Port 3-ISU2-1
l The values for the related parameters of NE16 are provided as follows.
Parameter Value
Port 3-ISU2-1
----End
Procedure
Step 1 See A.7.8.1 Creating an MD and configure the MD for NE11, NE12, NE14, and NE16.
Parameter Value
Maintenance 4 4 4 4
Domain Level
Step 2 See A.7.8.2 Creating an MA and configure the MA for NE11, NE12, NE14, and NE16.
l The values for the related parameters of NE11 are provided as follows.
Parameter Value
CC Test Transmit 1s 1s 1s
Period
l The values for the related parameters of NE12 are provided as follows.
Parameter Value
l The values for the related parameters of NE14 are provided as follows.
Parameter Value
l The values for the related parameters of NE16 are provided as follows.
Parameter Value
Parameter
l The values for the related parameters of NE12 are provided as follows.
Parameter Value
Board 1-EM6T
Port 1-EM6T-3
VLAN -
MP ID 201
Direction Ingress
CC Status Active
l The values for the related parameters of NE14 are provided as follows.
Parameter Value
Board 1-EM6T
Port 1-EM6T-3
VLAN -
MP ID 401
Direction Ingress
CC Status Active
l The values for the related parameters of NE16 are provided as follows.
Parameter Value
Board 1-EM6T
Port 1-EM6T-3
VLAN -
MP ID 601
Direction Ingress
CC Status Active
Step 4 See A.7.8.4 Creating Remote MEPs in an MA and create the remote MEPs of the MA for
NE11, NE12, NE14, and NE16.
The values for the related parameters of NE11 are provided as follows.
Parameter Value
The values for the related parameters of NE12 are provided as follows.
Parameter Value
The values for the related parameters of NE14 are provided as follows.
Parameter Value
The values for the related parameters of NE16 are provided as follows.
Parameter Value
----End
Based on 6.6 Configuration Example (Radio Links on the Hybrid Radio Ring Network),
configure Ethernet services according to the following requirements:
To meet the preceding requirements, IEEE 802.1d bridge-based E-LAN services are configured
to implement transmission of the BTS services; in addition, the functions of detecting looped
services and suppressing broadcast packets, ERPS protection, and QoS processing are
configured. See Figure 8-30.
Packet network
NE21
FE
FE
ERPS
R4 R4
BTS21 NE22 NE24 BTS24
802.1d bridge
802.1d bridge
FE
NE23 R4
802.1d bridge
BTS23
The connections of Ethernet links shown in Figure 8-30 are described as follows.
Between NE21 and 4-ISU2-1 East port of an ERPS Configure this port to
NE22 ring node transmit Ethernet
services on Hybrid
radio.
Between NE22 and 4-ISU2-1 East port of an ERPS Configure this port to
NE23 ring node transmit Ethernet
services on Hybrid
radio.
Between NE24 and 4-ISU2-1 East port of an ERPS Configure these ports
NE21 ring node to transmit Ethernet
Main IF board of a 1 services on Hybrid
+1 SD protection radio.
group
Parameter 1-EM6F-3
Parameter 1-EM6T-3
Parameter 1-EM6T-3
Parameter 1-EM6T-3
NOTE
l In this example, the FE ports on all the BTSs work in auto-negotiation mode. Therefore, the FE/GE port of
each NE that accesses services must work in auto-negotiation mode. If the peer Ethernet port works in
another mode, the local Ethernet port must work in the same mode. The working modes of the Ethernet ports
inside the network are planned as auto-negotiation.
l In this example, to ensure that the Ethernet frames that carry more than one tag such as QinQ can traverse
the equipment, the maximum frame length is set to 1536 (bytes). If the equipment needs to transmit jumbo
frames with a greater length, set the maximum frame length according to the actual length of a jumbo frame.
Normally, if the equipment is interconnected with BTSs, the maximum frame length can also assume its
default value of 1522.
ERPS ID 1 1 1 1
Entity level 4 (default value) 4 (default value) 4 (default value) 4 (default value)
Guard time 500 ms (default 500 ms (default 500 ms (default 500 ms (default
value) value) value) value)
NOTE
l In this example, all the services are aggregated on NE21. Therefore, the NE that is farthest from NE21 needs
to function as the RPL owner. In this way, when the ring network is normal, the traffic carried on each link
is relatively even.
l The control VLAN needs to use a VLAN that is not used by any service. It is recommended that the control
VLAN use VLAN 4093.
l The packet transmit interval, entity level, WTR time, guard time, and hold-off time generally assume their
default values.
Table 8-109 provides the planning information of IEEE 802.1a bridge-based E-LAN services.
Service ID 1 1 1 1
QoS (DiffServ)
DS is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the BTS
services be allocated by the service type. Then, the transmission network creates the
corresponding DS domain according to the allocated VLAN priority or DSCP value. Each
Ethernet port involved in the service must use the same DS configuration.
In this example, the BTS services are allocated with corresponding VLAN priorities according
to the service type, and the NEs allocate the PHB service classes according to the VLAN priority,
as provided in Table 8-110. Each Ethernet port involved in the service uses the same DS
configuration.
CS7 7 -
CS6 6 -
AF4 4 -
AF1 1 -
NOTE
l During the mapping of the PHB service class, CS7 or CS6 is not recommended, because CS7 or CS6 may
be used to transmit Ethernet protocol packets or inband DCN packets on the NE.
l The default mapping relationships for the DS domain comply with the network planning requirements and
therefore do not need to be modified.
l The default trusted packet type for each port that is applied for the default DS domain is C-VLAN priority
and therefore does not need to be modified.
Table 8-111 lists the queue scheduling mode used by each Ethernet port involved in the service
in this example.
CS7 SP
CS6 SP
EF SP
BE SP
Procedure
Step 1 See A.6.6.1 Setting the Basic Attributes of Ethernet Ports and set the basic attributes of
Ethernet ports.
l The values for the related parameters of NE21 are provided as follows.
Parameter Value
1-EM6F-3
l The values for the related parameters of NE22 and NE24 are provided as follows.
Parameter Value
1-EM6T-3
l The values for the related parameters of NE23 are provided as follows.
Parameter Value
1-EM6T-3
Step 2 See A.6.6.5 Setting the Advanced Attributes of Ethernet Ports and set the advanced attributes
of Ethernet ports.
l The values for the related parameters of NE21 are provided as follows.
Parameter Value
1-EM6F-3
Parameter Value
1-EM6F-3
l The values for the related parameters of NE22 and NE24 are provided as follows.
Parameter Value
1-EM6T-3
l The values for the related parameters of NE23 are provided as follows.
Parameter Value
1-EM6T-3
Step 3 See A.6.7.1 Setting the Basic Attributes of IF_ETH Ports and set the basic attributes of the
IF_ETH ports.
l The values for the related parameters of NE22 are provided as follows.
Parameter Value
l The values for the related parameters of NE23 are provided as follows.
Parameter Value
3-ISU2-1 4-ISU2-1
l The values for the related parameters of NE24 are provided as follows.
Parameter Value
Step 4 See A.6.7.4 Setting the Advanced Attributes of IF_ETH Ports and set the advanced attributes
of the IF_ETH ports.
l The values for the related parameters of NE22 and NE23 are provided as follows.
Parameter Value
3-ISU2-1 4-ISU2-1
Broadcast Packet 30 30
Suppression Threshold
l The values for the related parameters of NE24 are provided as follows.
Parameter Value
Broadcast Packet 30 30 30
Suppression
Threshold
----End
Procedure
Step 1 See A.7.1.1 Creating Ethernet Ring Protection Instances and create the ERPS instance.
Parameter Value
ERPS ID 1 1 1 1
----End
Procedure
Step 1 See A.7.3.9 Configuring IEEE 802.1d Bridge-Based E-LAN Services and configure the E-
LAN services.
l Parameters of NE21
The values for the related parameters that need to be set in the main interface are provided
as follows.
Parameter Value
Service ID 1
Self-Learning Enabled
MAC Address
Parameter Value
The values for the related parameters that need to be set in the Get UNI Port tab page are
provided as follows.
Port
1-EM6F-3
3-ISU2-1
4-ISU2-1
Parameter Value
Service ID 1
Self-Learning Enabled
MAC Address
The values for the related parameters that need to be set in the Get UNI Port tab page are
provided as follows.
Port
1-EM6T-3
3-ISU2-1
4-ISU2-1
l Parameters of NE23
The values for the related parameters that need to be set in the main interface are provided
as follows.
Parameter Value
Service ID 1
Self-Learning Enabled
MAC Address
The values for the related parameters that need to be set in the Get UNI Port tab page are
provided as follows.
Port
1-EM6T-3
3-ISU2-1
4-ISU2-1
----End
Procedure
Step 1 Follow instructions in A.7.7.2 Modifying the Mapping Relationships for the DS Domain and
change the mapping relationships for the DS domain.
NOTE
The actual mapping relationships for the default DS domain comply with the network planning information.
Therefore, you can skip this step.
The values for the related parameters that need to be set in the main interface are provided as
follows.
Parameter Value
Mapping Relation ID 1
The values for the related parameters that need to be set in the Ingress Mapping Relation tab
page are provided as follows.
1 AF11
2 AF21
3 AF31
4 AF41
5 EF
6 CS6
7 CS7
The values for the related parameters that need to be set in the Egress Mapping Relation tab
page are provided as follows.
AF11 1
AF21 2
AF31 3
AF41 4
EF 5
CS6 6
CS7 7
NOTE
AF1 is classified into three sub service classes, namely, AF11, AF12, and AF13, only one of which is valid at
a time. In this example, AF11 is used. It is the same case with the AF2, AF3, and AF4.
Step 2 Follow instructions in A.7.7.3 Changing the Ports Applied to a DS Domain and Their
Trusted Packet Types and change the ports that are applied to the DS domain and their trusted
packet types.
NOTE
The actual ports that are applied to the default DS domain and their trusted packet types comply with the network
planning information. Therefore, you can skip this step.
l The values for the related parameters of NE21 are provided as follows.
1-EM6F-3 CVLAN
3-ISU2-1
4-ISU2-1
l The values for the related parameters of NE22 are provided as follows.
1-EM6T-3 CVLAN
3-ISU2-1
4-ISU2-1
l The values for the related parameters of NE23 are provided as follows.
1-EM6T-3 CVLAN
3-ISU2-1
4-ISU2-1
l The values for the related parameters of NE24 are provided as follows.
Port Packet Type
1-EM6T-3 CVLAN
3-ISU2-1
4-ISU2-1
Step 3 Follow instructions in A.7.7.4 Creating a Port Policy and create the port policy.
The values for the WRR scheduling policy parameters of each NE are provided as follows.
Parameter Value
Policy ID 2
The values for the port policy parameters of each NE are provided as follows.
Parameter Value
Policy ID 1
Step 4 Follow instructions in A.7.7.7 Setting the Port That Uses the Port Policy and set the ports that
use the port policy.
l The values for the related parameters of NE21 are provided as follows.
Parameter Value
Port 1-EM6F-3
3-ISU2-1
4-ISU2-1
l The values for the related parameters of NE22 and NE24 are provided as follows.
Parameter Value
Port 1-EM6T-3
3-ISU2-1
4-ISU2-1
l The values for the related parameters of NE23 are provided as follows.
Parameter Value
Port 1-EM6T-3
3-ISU2-1
4-ISU2-1
----End
Procedure
Step 1 See A.7.8.1 Creating an MD and create the MDs.
Parameter Value
Maintenance 4 4 4 4
Domain Level
Parameter Value
CC Test 1s 1s 1s 1s
Transmit
Period
Parameter Value
VLAN - - - -
Step 4 See A.7.8.4 Creating Remote MEPs in an MA and create the remote MEP points.
The values for the related parameters of NE21 are provided as follows.
Parameter Value
Parameter Value
The values for the related parameters of NE22 are provided as follows.
Parameter Value
The values for the related parameters of NE23 are provided as follows.
Parameter Value
The values for the related parameters of NE24 are provided as follows.
Parameter Value
----End
Based on 6.5 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 BTS11 and BTS12 belong to domain 1; BTS15 belongs to domain 2. The BTSs in a domain
have the same VLAN ID and the data from different domains is isolated from each other
by using the VLAN IDs.
l VLAN priorities are configured on each BTS according to service types.
l The functions of detecting looped services and suppressing broadcast packets need to be
provided on the network.
To meet the preceding requirements, IEEE 802.1q bridge-based E-LAN services are configured
for service transmission on each NE; in addition, the functions of detecting looped services and
suppressing broadcast packets, and QoS processing are configured.
BTS12
VLAN 100 BTS11
VLAN 100
Domain 1
FE
VLAN 100
R4
R4
FE
NE14
GE
Packet network
Domain 2
VLAN 110
FE
NE16 NE15
R4
BTS15
VLAN 110
The connections of Ethernet links shown in Figure 8-31 are described as follows.
Broadcast packet 30 30
suppression threshold
Parameter 1-EM6T-1
Parameter 1-EM6T-3
Parameter 1-EM6T-3
NOTE
l In this example, the FE ports on all the BTSs work in auto-negotiation mode. Therefore, the FE/GE port of
each NE that accesses services must work in auto-negotiation mode. If the peer Ethernet port works in
another mode, the local Ethernet port must work in the same mode. The working modes of the Ethernet ports
inside the network are planned as auto-negotiation.
l In this example, to ensure that the Ethernet frames that carry more than one tag such as QinQ can traverse
the equipment, the maximum frame length is set to 1536 (bytes). If the equipment needs to transmit jumbo
frames with a greater length, set the maximum frame length according to the actual length of a jumbo frame.
Normally, if the equipment is interconnected with BTSs, the maximum frame length can also assume its
default value of 1522.
l In this example, all the services carry VLAN IDs. Therefore, the tag attributes of all the ports are tag aware.
Tag attribute Tag aware Tag aware Tag aware Tag aware
Parameter 3-ISU2-1
Table 8-126 provides the planning information of IEEE 802.1q bridge-based E-LAN services.
Service ID 1 1 1 1 1
NOTE
QoS (DiffServ)
DS is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the BTS
services be allocated by the service type. Then, the transmission network creates the
corresponding DS domain according to the allocated VLAN priority or DSCP value. Each
Ethernet port involved in the service must use the same DS configuration.
In this example, the BTS services are allocated with corresponding VLAN priorities according
to the service type, and the NEs allocate the PHB service classes according to the VLAN priority,
as provided in Table 8-127. Each Ethernet port involved in the service uses the same DS
configuration.
CS7 7 -
CS6 6 -
AF4 4 -
AF1 1 -
NOTE
l During the mapping of the PHB service class, CS7 or CS6 is not recommended, because CS7 or CS6 may
be used to transmit Ethernet protocol packets or inband DCN packets on the NE.
l The default mapping relationships for the DS domain comply with the network planning requirements and
therefore do not need to be modified.
l The default trusted packet type for each port that is applied for the default DS domain is C-VLAN priority
and therefore does not need to be modified.
Table 8-128 lists the queue scheduling mode used by each Ethernet port involved in the service
in this example.
CS7 SP
CS6 SP
EF SP
BE SP
Procedure
Step 1 See A.6.6.1 Setting the Basic Attributes of Ethernet Ports and set the basic attributes of
Ethernet ports.
l The values for the related parameters of NE12 are provided as follows.
Parameter Value
1-EM6T-1 1-EM6T-3
l The values for the related parameters of NE13 are provided as follows.
Parameter Value
1-EM6T-1
l The values for the related parameters of NE14 are provided as follows.
Parameter Value
1-EM6T-3
l The values for the related parameters of NE16 are provided as follows.
Parameter Value
1-EM6T-3
Parameter Value
1-EM6T-3
Step 2 See A.6.6.3 Setting the Layer 2 Attributes of Ethernet Ports and set the Layer 2 attributes of
Ethernet ports.
l The values for the related parameters of NE12 are provided as follows.
Parameter Value
1-EM6T-1 1-EM6T-3
l The values for the related parameters of NE13 are provided as follows.
Parameter Value
1-EM6T-1
l The values for the related parameters of NE14 are provided as follows.
Parameter Value
1-EM6T-3
l The values for the related parameters of NE16 are provided as follows.
Parameter Value
1-EM6T-3
Step 3 See A.6.6.5 Setting the Advanced Attributes of Ethernet Ports and set the advanced attributes
of Ethernet ports.
l The values for the related parameters of NE12 are provided as follows.
Parameter Value
1-EM6T-1 1-EM6T-3
Broadcast Packet 30 30
Suppression Threshold
l The values for the related parameters of NE13 are provided as follows.
Parameter Value
1-EM6T-1
l The values for the related parameters of NE14 are provided as follows.
Parameter Value
1-EM6T-3
l The values for the related parameters of NE16 are provided as follows.
Parameter Value
1-EM6T-3
Step 4 See A.6.7.1 Setting the Basic Attributes of IF_ETH Ports and set the basic attributes of
IF_ETH ports.
l The values for the related parameters of NE12 are provided as follows.
Parameter Value
3-ISU2-1 5-ISU2-1
l The values for the related parameters of NE13 are provided as follows.
Parameter Value
l The values for the related parameters of NE14 are provided as follows.
Parameter Value
3-ISU2-1 5-ISU2-1
l The values for the related parameters of NE15 are provided as follows.
Parameter Value
l The values for the related parameters of NE16 are provided as follows.
Parameter Value
3-ISU2-1
Step 5 See A.6.7.2 Setting the Layer 2 Attributes of IF_ETH Ports and set the Layer 2 attributes of
IF_ETH ports.
l The values for the related parameters of NE12 are provided as follows.
Parameter Value
3-ISU2-1 5-ISU2-1
l The values for the related parameters of NE13 are provided as follows.
Parameter Value
l The values for the related parameters of NE14 are provided as follows.
Parameter Value
3-ISU2-1 5-ISU2-1
l The values for the related parameters of NE15 are provided as follows.
Parameter Value
l The values for the related parameters of NE16 are provided as follows.
Parameter Value
3-ISU2-1
Step 6 See A.6.7.4 Setting the Advanced Attributes of IF_ETH Ports and set the advanced attributes
of the IF_ETH ports.
l The values for the related parameters of NE12 are provided as follows.
Parameter Value
3-ISU2-1 5-ISU2-1
Parameter Value
3-ISU2-1 5-ISU2-1
Broadcast Packet 30 30
Suppression Threshold
l The values for the related parameters of NE13 are provided as follows.
Parameter Value
Broadcast 30 30 30 30
Packet
Suppression
Threshold
l The values for the related parameters of NE14 are provided as follows.
Parameter Value
3-ISU2-1 5-ISU2-1
Broadcast Packet 30 30
Suppression Threshold
l The values for the related parameters of NE15 are provided as follows.
Parameter Value
Broadcast Packet 30 30 30
Suppression
Threshold
l The values for the related parameters of NE16 are provided as follows.
Parameter Value
3-ISU2-1
----End
Procedure
Step 1 See A.7.3.10 Configuring IEEE 802.1q Bridge-Based E-LAN Services and configure the E-
LAN services.
l Parameters of NE12
The values for the related parameters that need to be set in the main interface are provided
as follows.
Parameter Value
Service ID 1
Self-Learning Enabled
MAC Address
The values for the related parameters that need to be set in the Get UNI Port tab page are
provided as follows.
1-EM6T-3 100
l Parameters of NE13
The values for the related parameters that need to be set in the main interface are provided
as follows.
Parameter Value
Service ID 1
Self-Learning Enabled
MAC Address
The values for the related parameters that need to be set in the Get UNI Port tab page are
provided as follows.
3-ISU2-1 100
4-ISU2-1 110
l Parameters of NE14
The values for the related parameters that need to be set in the main interface are provided
as follows.
Parameter Value
Service ID 1
The values for the related parameters that need to be set in the Get UNI Port tab page are
provided as follows.
1-EM6T-3 100
3-ISU2-1 100
l Parameters of NE15
The values for the related parameters that need to be set in the main interface are provided
as follows.
Parameter Value
Service ID 1
Parameter Value
Enable Port - -
Working Mode - -
The values for the related parameters that need to be set in the Get UNI Port tab page are
provided as follows.
3-ISU2-1 110
4-ISU2-1 110
l Parameters of NE16
The values for the related parameters that need to be set in the main interface are provided
as follows.
Parameter Value
Service ID 1
The values for the related parameters that need to be set in the Get UNI Port tab page are
provided as follows.
1-EM6T-3 110
3-ISU2-1 110
----End
Procedure
Step 1 Follow instructions in A.7.7.2 Modifying the Mapping Relationships for the DS Domain and
change the mapping relationships for the DS domain.
NOTE
The actual mapping relationships for the default DS domain comply with the network planning information.
Therefore, you can skip this step.
The values for the related parameters that need to be set in the main interface are provided as
follows.
Parameter Value
Mapping Relation ID 1
The values for the related parameters that need to be set in the Ingress Mapping Relation tab
page are provided as follows.
1 AF11
2 AF21
3 AF31
4 AF41
5 EF
6 CS6
7 CS7
The values for the related parameters that need to be set in the Egress Mapping Relation tab
page are provided as follows.
AF11 1
AF21 2
AF31 3
AF41 4
EF 5
CS6 6
CS7 7
NOTE
The AF1 is classified into three sub service classes, namely, AF11, AF12, and AF13, only one of which is valid.
In this example, the AF11 is used. It is the same case with the AF2, AF3, and AF4.
Step 2 Follow instructions in A.7.7.3 Changing the Ports Applied to a DS Domain and Their
Trusted Packet Types and change the ports that are applied to the DS domain and their trusted
packet types.
NOTE
The actual ports that are applied to the default DS domain and their trusted packet types comply with the network
planning information. Therefore, you can skip this step.
l The values for the related parameters of NE12 are provided as follows.
1-EM6T-1 CVLAN
1-EM6T-3
3-ISU2-1
l The values for the related parameters of NE13 are provided as follows.
3-ISU2-1 CVLAN
4-ISU2-1
1-EM6T-1
l The values for the related parameters of NE14 are provided as follows.
3-ISU2-1 CVLAN
1-EM6T-3
l The values for the related parameters of NE15 are provided as follows.
3-ISU2-1 CVLAN
4-ISU2-1
l The values for the related parameters of NE16 are provided as follows.
1-EM6T-3 CVLAN
3-ISU2-1
Step 3 Follow instructions in A.7.7.4 Creating a Port Policy and create the port policy.
The values for the WRR scheduling policy parameters of NE12 to NE16 are provided as follows.
Parameter Value
Policy ID 2
The values for the port policy parameters of NE12 to NE16 are provided as follows.
Parameter Value
Policy ID 1
Parameter Value
Step 4 Follow instructions in A.7.7.7 Setting the Port That Uses the Port Policy and set the ports that
use the port policy.
l The values for the related parameters of NE12 are provided as follows.
Parameter Value
Port 1-EM6T-1
1-EM6T-3
3-ISU2-1
l The values for the related parameters of NE13 are provided as follows.
Parameter Value
Port 3-ISU2-1
4-ISU2-1
1-EM6T-1
l The values for the related parameters of NE14 are provided as follows.
Parameter Value
Port 3-ISU2-1
l The values for the related parameters of NE15 are provided as follows.
Parameter Value
Port 3-ISU2-1
4-ISU2-1
l The values for the related parameters of NE16 are provided as follows.
Parameter Value
Port 3-ISU2-1
----End
Procedure
Step 1 See A.7.8.1 Creating an MD and create the MDs for NE12, NE14, and NE16.
Parameter Value
Maintenance 4 4 4
Domain Level
Step 2 See A.7.8.2 Creating an MA and create the MAs for NE12, NE14, and NE16.
l The values for the related parameters of NE12 are provided as follows.
Parameter Value
CC Test Transmit 1s 1s 1s
Period
l The values for the related parameters of NE14 are provided as follows.
Parameter Value
l The values for the related parameters of NE16 are provided as follows.
Parameter Value
Step 3 See A.7.8.3 Creating MEPs and create the MEPs for NE12, NE14, and NE16.
l The values for the related parameters of NE12 are provided as follows.
Parameter Value
l The values for the related parameters of NE14 are provided as follows.
Parameter Value
Board 1-EM6T-3
Port 1-EM6T-3
VLAN 110
MP ID 401
Direction Ingress
CC Status Active
l The values for the related parameters of NE16 are provided as follows.
Parameter Value
Board 1-EM6T
Port 1-EM6T-3
VLAN 120
MP ID 601
Direction Ingress
CC Status Active
Step 4 See A.7.8.4 Creating Remote MEPs in an MA and create the remote MEPs for NE12, NE14,
and NE16.
The values for the related parameters of NE12 are provided as follows.
Parameter Value
The values for the related parameters of NE14 are provided as follows.
Parameter Value
The values for the related parameters of NE16 are provided as follows.
Parameter Value
Parameter Value
----End
FE
FE
ERPS
R4 R4
NE22 NE24
802.1ad bridge
802.1ad bridge
FE
NE23
802.1ad bridge R4
BTS13
CVLAN 110
SVLAN 200
The connections of Ethernet links shown in Figure 8-32 are described as follows.
Between NE21 and 4-ISU2-1 East port of an ERPS Configure this port to
NE22 ring node transmit Native
Ethernet services on
Hybrid radio.
Between NE22 and 4-ISU2-1 East port of an ERPS Configure this port to
NE23 ring node transmit Ethernet
services on Hybrid
radio.
Between NE24 and 4-ISU2-1 East port of an ERPS Configure these ports
NE21 ring node to transmit Ethernet
Main IF board of a 1 services on Hybrid
+1 SD protection radio.
group
Broadcast packet 30 30
suppression threshold
Parameter 1-EM6T-3
Parameter 1-EM6T-3
Parameter 1-EM6T-3
NOTE
l In this example, the FE/GE ports on all the BTSs/RNC work in auto-negotiation mode. Therefore, the FE/
GE port of each NE that accesses services must work in auto-negotiation mode. If the peer Ethernet port
works in another mode, the local Ethernet port must work in the same mode. The working modes of the
Ethernet ports inside the network are planned as auto-negotiation.
l In this example, to ensure that the Ethernet frames that carry more than one tag such as QinQ can traverse
the equipment, the maximum frame length is set to 1536 (bytes). If the equipment needs to transmit jumbo
frames with a greater length, set the maximum frame length according to the actual length of a jumbo frame.
NOTE
All the IF_ETH ports are connected to Huawei equipment. Therefore, it is recommended that you set the QinQ
type domain to 0x88a8 for the IF_ETH ports.
ERPS ID 1 1 1 1
Entity level 4 (default value) 4 (default value) 4 (default value) 4 (default value)
Guard time 500 ms (default 500 ms (default 500 ms (default 500 ms (default
value) value) value) value)
NOTE
l In this example, all the services are aggregated on NE21. Therefore, the NE that is farthest from NE21 needs
to function as the RPL owner. In this way, when the ring network is normal, the traffic carried on each link
is relatively even.
l The control VLAN needs to use a VLAN that is not used by any service. It is recommended that the control
VLAN use VLAN 4093.
l The packet transmit interval, entity level, WTR time, guard time, and hold-off time generally assume their
default values.
Service ID 1 1 1 1
Mounted UNI 1-EM6T-3 (C- 1-EM6T-3 (C- 1-EM6T-3 (C- 1-EM6T-3 (C-
port VLAN ID: 100, VLAN ID: 100) VLAN ID: 110) VLAN ID: 100)
110) (S-VLAN (S-VLAN ID: (S-VLAN ID: (S-VLAN ID:
ID: 200) 200) 200) 201)
1-EM6T-4 (C-
VLAN ID: 100)
(S-VLAN ID:
201)
Mounted NNI 3-ISU2-1 (S- 3-ISU2-1 (S- 3-ISU2-1 (S- 3-ISU2-1 (S-
port VLAN ID: 200, VLAN ID: 200, VLAN ID: 200, VLAN ID: 200,
201) 201) 201) 201)
4-ISU2-1 (S- 4-ISU2-1 (S- 4-ISU2-1 (S- 4-ISU2-1 (S-
VLAN ID: 200, VLAN ID: 200, VLAN ID: 200, VLAN ID: 200,
201) 201) 201) 201)
QoS (DiffServ)
DS is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the BTS
services be allocated by the service type. Then, the transmission network creates the
corresponding DS domain according to the allocated VLAN priority or DSCP value. Each
Ethernet port involved in the service must use the same DS configuration.
In this example, the BTS services are allocated with corresponding VLAN priorities according
to the service type, and the NEs allocate the PHB service classes according to the VLAN priority,
as provided in Table 8-143. Each Ethernet port involved in the service uses the same DS
configuration.
CS7 7 -
CS6 6 -
AF4 4 -
AF1 1 -
NOTE
l During the mapping of the PHB service class, CS7 or CS6 is not recommended, because CS7 or CS6 may
be used to transmit Ethernet protocol packets or inband DCN packets on the NE.
l The default mapping relationships for the DS domain comply with the network planning requirements and
therefore do not need to be modified.
l The default trusted packet type for each port that is applied for the default DS domain is C-VLAN priority
and therefore needs to be modified as required.
Table 8-144 lists the queue scheduling mode used by each Ethernet port involved in the service
in this example.
CS7 SP
CS6 SP
EF SP
BE SP
Procedure
Step 1 See A.6.6.1 Setting the Basic Attributes of Ethernet Ports and set the basic attributes of
Ethernet ports.
l The values for the related parameters of NE21 are provided as follows.
Parameter Value
1-EM6T-1 1-EM6T-2
l The values for the related parameters of NE22 are provided as follows.
Parameter Value
1-EM6T-3
l The values for the related parameters of NE23 are provided as follows.
Parameter Value
1-EM6T-3
l The values for the related parameters of NE24 are provided as follows.
Parameter Value
1-EM6T-3
Parameter Value
1-EM6T-3
Step 2 See A.6.6.3 Setting the Layer 2 Attributes of Ethernet Ports and set the Layer 2 attributes of
Ethernet ports.
The values for the related parameters of NE21 are provided as follows.
Parameter Value
1-EM6T-1 1-EM6T-2
The values for the related parameters of NE22 are provided as follows.
Parameter Value
1-EM6T-3
The values for the related parameters of NE23 are provided as follows.
Parameter Value
1-EM6T-3
The values for the related parameters of NE24 are provided as follows.
Parameter Value
1-EM6T-3
Step 3 See A.6.6.5 Setting the Advanced Attributes of Ethernet Ports and set the advanced attributes
of Ethernet ports.
l The values for the related parameters of NE21 are provided as follows.
Parameter Value
1-EM6T-1 1-EM6T-2
Broadcast Packet 30 30
Suppression Threshold
l The values for the related parameters of NE22 and NE24 are provided as follows.
Parameter Value
1-EM6T-3
l The values for the related parameters of NE23 are provided as follows.
Parameter Value
1-EM6T-3
Step 4 See A.6.7.1 Setting the Basic Attributes of IF_ETH Ports and set the attributes of the IF_ETH
ports.
l The values for the related parameters of NE21 are provided as follows.
Parameter Value
l The values for the related parameters of NE22 are provided as follows.
Parameter Value
3-ISU2-1 4-ISU2-1
l The values for the related parameters of NE23 are provided as follows.
Parameter Value
3-ISU2-1 4-ISU2-1
l The values for the related parameters of NE24 are provided as follows.
Parameter Value
Step 5 See A.6.7.4 Setting the Advanced Attributes of IF_ETH Ports and set the advanced attributes
of the IF_ETH ports.
l The values for the related parameters of NE21 are provided as follows.
Parameter Value
Broadcast Packet 30 30 30
Suppression
Threshold
l The values for the related parameters of NE22 and NE23 are provided as follows.
Parameter Value
3-ISU2-1 4-ISU2-1
Broadcast Packet 30 30
Suppression Threshold
l The values for the related parameters of NE24 are provided as follows.
Parameter Value
Broadcast Packet 30 30 30
Suppression
Threshold
----End
Procedure
Step 1 See A.7.1.1 Creating Ethernet Ring Protection Instances and create the ERPS instance.
The values for the required parameters are provided as follows.
Parameter Value
ERPS ID 1 1 1 1
----End
Procedure
Step 1 See A.7.3.11 Configuring IEEE 802.1ad Bridge-Based E-LAN Services and configure the
E-LAN services.
l Parameters of NE21
The values for the related parameters that need to be set in the main interface are provided
as follows.
Parameter Value
Service ID 1
Self-Learning Enabled
MAC Address
The values for the related parameters that need to be set in the Get UNI Port tab page are
provided as follows.
The values for the related parameters that need to be set in the Get NNI Port tab page are
provided as follows.
l Parameters of NE22
The values for the related parameters that need to be set in the main interface are provided
as follows.
Parameter Value
Service ID 1
Self-Learning Enabled
MAC Address
The values for the related parameters that need to be set in the Get UNI Port tab page are
provided as follows.
The values for the related parameters that need to be set in the Get NNI Port tab page are
provided as follows.
l Parameters of NE23
The values for the related parameters that need to be set in the main interface are provided
as follows.
Parameter Value
Service ID 1
Self-Learning Enabled
MAC Address
The values for the related parameters that need to be set in the Get UNI Port tab page are
provided as follows.
Port Port Type C-VLAN S-VLAN
The values for the related parameters that need to be set in the Get NNI Port tab page are
provided as follows.
Port Port Type C-VLAN S-VLAN
l Parameters of NE24
The values for the related parameters that need to be set in the main interface are provided
as follows.
Parameter Value
Service ID 1
Self-Learning Enabled
MAC Address
The values for the related parameters that need to be set in the Get UNI Port tab page are
provided as follows.
The values for the related parameters that need to be set in the Get NNI Port tab page are
provided as follows.
----End
Procedure
Step 1 Follow instructions in A.7.7.2 Modifying the Mapping Relationships for the DS Domain and
change the mapping relationships for the DS domain.
The values for the related parameters that need to be set in the main interface are provided as
follows.
Parameter Value
Mapping Relation ID 1
The values for the related parameters that need to be set in the Ingress Mapping Relation tab
page are provided as follows.
1 1 AF11
2 2 AF21
3 3 AF31
4 4 AF41
5 5 EF
6 6 CS6
7 7 CS7
The values for the related parameters that need to be set in the Egress Mapping Relation tab
page are provided as follows.
AF11 1 1
AF21 2 2
AF31 3 3
AF41 4 4
EF 5 5
CS6 6 6
CS7 7 7
NOTE
l The AF1 is classified into three sub service classes, namely, AF11, AF12, and AF13, only one of which is
valid. In this example, the AF11 is used. It is the same case with the AF2, AF3, and AF4.
l The default mapping relationships for the DS domain comply with the network planning requirements and
therefore do not need to be modified.
Step 2 Follow instructions in A.7.7.3 Changing the Ports Applied to a DS Domain and Their
Trusted Packet Types and change the ports that are applied to the DS domain and their trusted
packet types.
l The values for the related parameters of NE21 are provided as follows.
3-ISU2-1 SVLAN
4-ISU2-1 SVLAN
1-EM6T-1 CVLAN
1-EM6T-2
l The values for the related parameters of NE22 are provided as follows.
1-EM6T-3 CVLAN
3-ISU2-1 SVLAN
4-ISU2-1 SVLAN
l The values for the related parameters of NE23 are provided as follows.
1-EM6T-3 CVLAN
3-ISU2-1 SVLAN
4-ISU2-1 SVLAN
l The values for the related parameters of NE24 are provided as follows.
1-EM6T-3 CVLAN
3-ISU2-1 SVLAN
4-ISU2-1 SVLAN
Step 3 Follow instructions in A.7.7.4 Creating a Port Policy and create the port policy.
The values for the WRR scheduling policy parameters of NE21 to NE24 are provided as follows.
Parameter Value
Policy ID 2
The values for the port policy parameters of NE21 to NE24 are provided as follows.
Parameter Value
Policy ID 1
Step 4 Follow instructions in A.7.7.7 Setting the Port That Uses the Port Policy and set the ports that
use the port policy.
The values for the related parameters of NE21 to NE24 are provided as follows.
Parameter Value
Port 3-ISU2-1
4-ISU2-1
----End
Procedure
Step 1 See A.7.8.1 Creating an MD and create the MDs.
Parameter Value
Maintenance 4 4 4 4
Domain Level
Parameter Value
CC Test 1s 1s 1s 1s
Transmit
Period
Parameter Value
l The values for the related parameters of NE22 are provided as follows.
Parameter Value
Board 1-EM6T
Port 1-EM6T-3
VLAN 100
MP ID 201
Direction Ingress
CC Status Active
l The values for the related parameters of NE23 are provided as follows.
Parameter Value
Board 1-EM6T
Port 1-EM6T-3
VLAN 110
MP ID 301
Direction Ingress
Parameter Value
CC Status Active
l The values for the related parameters of NE24 are provided as follows.
Parameter Value
Board 1-EM6T
Port 1-EM6T-3
VLAN 100
MP ID 401
Direction Ingress
CC Status Active
Step 4 See A.7.8.4 Creating Remote MEPs in an MA and create the remote MEPs.
The values for the related parameters of NE21 are provided as follows.
Parameter Value
The values for the related parameters of NE22 are provided as follows.
Parameter Value
The values for the related parameters of NE23 are provided as follows.
Parameter Value
The values for the related parameters of NE24 are provided as follows.
Parameter Value
----End
Based on 6.5 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 It is unknown whether the Ethernet services on each BTS carry a VLAN ID or whether the
carried VLAN IDs conflict. Therefore, in this example, the point-to-point transparently
transmitted E-Line services are configured to implement point-to-point transparent service
transmission, and the IEEE 802.1d bridge-based E-LAN services are configured to
implement service convergence.
l DSCP values are configured on each BTS according to service types.
l The BTSs need not communicate with each other.
FE
R4
GE
NE14 PSN
FE
NE13 NE12 NE11
R4
BTS11
FE
NE16 NE15
R4
BTS15
Point-to-point transparently
transmitted E-Line service
The connections of Ethernet links shown in Figure 8-33 are described as follows.
Broadcast packet 30 30
suppression threshold
Parameter 1-EM6T-1
Parameter 1-EM6T-3
Parameter 1-EM6T-3
NOTE
l In this example, the planned encapsulation type is null because whether the Ethernet services on each BTS
carry a VLAN ID or whether the carried VLAN IDs conflict is unknown.
l In this example, the FE/GE ports on all the BTSs/BSC work in the auto-negotiation mode. Therefore, the
FE/GE port of each NE that accesses services must work in the auto-negotiation mode. If the peer Ethernet
port works in another mode, the local Ethernet port must work in the same mode. The working modes of
the Ethernet ports inside the network are planned as auto-negotiation.
l In this example, to ensure that the Ethernet frames that carry more than one tag such as QinQ can traverse
the equipment, the maximum frame length is set to 1536 (bytes). If the equipment needs to transmit jumbo
frames with a greater length, set the maximum frame length according to the actual length of a jumbo frame.
Normally, if the equipment is interconnected with BTSs, the maximum frame length can also assume its
default value of 1522.
l Generally, the flow control function is enabled only if the local NE or opposite equipment has insufficient
QoS capabilities. The planning information of flow control must be the same for the equipment at both ends.
Parameter 3-ISU2-1
Table 8-159 Information about point-to-point transparently transmitted E-Line services (NE14)
Parameter NE14
BTS12 to NE13
Service ID 1
Source C-VLANs -
Sink C-VLANs -
Table 8-160 Information about point-to-point transparently transmitted E-Line services (NE15)
Parameter NE15
NE16 to NE13
Service ID 1
Parameter NE15
NE16 to NE13
Source C-VLANs -
Sink C-VLANs -
Table 8-161 Information about point-to-point transparently transmitted E-Line services (NE16)
Parameter NE16
BTS15 to NE15
Service ID 1
Source C-VLANs -
Sink C-VLANs -
Table 8-162 Information about IEEE 802.1d bridge-based E-LAN services (NE12)
Parameter NE12
Service ID 1
Parameter NE12
Table 8-163 Information about IEEE 802.1d bridge-based E-LAN services (NE13)
Parameter NE3
Service ID 1
QoS (DiffServ)
DS is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the BTS
services be allocated according to the service type. Then, the transmission network creates the
corresponding DS domain according to the allocated VLAN priority or DSCP value. Each
Ethernet port involved in the service must use the same DS configuration.
In this example, the BTS services are allocated with corresponding DSCP values according to
the service type, and the NEs allocate the PHB service classes according to the DSCP value, as
shown in Table 8-164. Each Ethernet port involved in the service uses the same DS
configuration.
CS7 56 -
CS6 48 -
AF4 32 -
AF1 8 -
NOTE
l During the mapping of the PHB service class, CS7 or CS6 is not recommended, because CS7 or CS6 may
be used to transmit Ethernet protocol packets or inband DCN packets on the NE.
l The default mapping relationships for the DS domain comply with the network planning requirements and
therefore do not need to be modified.
l The required trusted packet type is not the C-VLAN priority but DSCP value. Therefore, the trusted packet
type needs to be modified for service-associated Ethernet ports applied in the default DS domain.
Table 8-165 lists the queue scheduling mode used by each Ethernet port involved in the service
in this example.
CS7 SP
CS6 SP
EF SP
BE SP
Procedure
Step 1 See A.6.6.1 Setting the Basic Attributes of Ethernet Ports and set the basic attributes of
Ethernet ports.
l The values for the related parameters of NE12 are provided as follows.
Parameter Value
1-EM6T-3 1-EM6T-1
Parameter Value
1-EM6T-3 1-EM6T-1
l The values for the related parameters of NE13 are provided as follows.
Parameter Value
1-EM6T-1
l The values for the related parameters of NE14 are provided as follows.
Parameter Value
1-EM6T-3
l The values for the related parameters of NE16 are provided as follows.
Parameter Value
1-EM6T-3
Parameter Value
1-EM6T-3
Step 2 See A.6.6.5 Setting the Advanced Attributes of Ethernet Ports and set the advanced attributes
of Ethernet ports.
l The values for the related parameters of NE12 are provided as follows.
Parameter Value
1-EM6T-3 1-EM6T-1
Broadcast Packet 30 30
Suppression Threshold
l The values for the related parameters of NE13 are provided as follows.
Parameter Value
1-EM6T-1
Step 3 See A.6.7.1 Setting the Basic Attributes of IF_ETH Ports and set the basic attributes of
IF_ETH ports.
l The values for the related parameters of NE12 are provided as follows.
Parameter Value
3-ISU2-1 5-ISU2-1
l The values for the related parameters of NE13 are provided as follows.
Parameter Value
l The values for the related parameters of NE14 are provided as follows.
Parameter Value
3-ISU2-1 5-ISU2-1
l The values for the related parameters of NE15 are provided as follows.
Parameter Value
l The values for the related parameters of NE16 are provided as follows.
Parameter Value
3-ISU2-1
Step 4 See A.6.7.4 Setting the Advanced Attributes of IF_ETH Ports and set the advanced attributes
of the IF_ETH ports.
l The values for the related parameters of NE12 are provided as follows.
Parameter Value
3-ISU2-1 5-ISU2-1
Parameter Value
3-ISU2-1 5-ISU2-1
Broadcast Packet 30 30
Suppression Threshold
l The values for the related parameters of NE13 are provided as follows.
Parameter Value
Broadcast 30 30 30 30
Packet
Suppression
Threshold
----End
Procedure
Step 1 See A.7.3.2 Configuring UNI-UNI E-Line Services and configure the E-Line services on NE14
to NE16.
l The values for the related parameters of NE14 are provided as follows.
Parameter Value
BTS12 to NE13
Service ID 1
Direction UNI-UNI
Source VLAN ID -
Parameter Value
BTS12 to NE13
Sink VLAN ID -
l The values for the related parameters of NE15 are provided as follows.
Parameter Value
NE16 to NE13
Service ID 1
Direction UNI-UNI
Source VLAN ID -
Sink VLAN ID -
Enable Port - -
Working Mode - -
l The values for the related parameters of NE16 are provided as follows.
Parameter Value
BTS15 to NE15
Service ID 1
Direction UNI-UNI
Parameter Value
BTS15 to NE15
Source VLAN ID -
Sink VLAN ID -
Step 2 See A.7.3.9 Configuring IEEE 802.1d Bridge-Based E-LAN Services and configure the E-
LAN services on NE12 and NE13.
The values for the related parameters of NE12 that need to be set in the main interface are
provided as follows.
Parameter Value
Service ID 1
Self-Learning Enabled
MAC Address
The values for the related parameters that need to be set in the Get UNI Port tab page are
provided as follows.
Port
1-EM6T-1
1-EM6T-3
Port
3-ISU2-1
The values for the related parameters that need to be set in the Split Horizon Group tab page
are provided as follows.
1 1-EM6T-1, 1-EM6T-3
The values for the related parameters of NE13 that need to be set in the main interface are
provided as follows.
Parameter Value
Service ID 1
Self-Learning Enabled
MAC Address
The values for the related parameters that need to be set in the Get UNI Port tab page are
provided as follows.
Port
1-EM6T-1
3-ISU2-1
4-ISU2-1
The values for the related parameters that need to be set in the Split Horizon Group tab page
are provided as follows.
1 3-ISU2-1, 4-ISU2-1
----End
Procedure
Step 1 Follow instructions in A.7.7.2 Modifying the Mapping Relationships for the DS Domain and
change the mapping relationships for the DS domain.
The values for the related parameters that need to be set in the main interface are provided as
follows.
Parameter Value
Mapping Relation ID 1
The values for the related parameters that need to be set in the Ingress Mapping Relation tab
page are provided as follows.
8 AF11
16 AF21
24 AF31
32 AF41
40 EF
48 CS6
56 CS7
The values for the related parameters that need to be set in the Egress Mapping Relation tab
page are provided as follows.
AF11 8
AF21 16
AF31 24
AF41 32
EF 40
CS6 48
CS7 56
NOTE
l The AF1 is classified into three sub service classes, namely, AF11, AF12, and AF13, only one of which is
valid. In this example, the AF11 is used. It is the same case with the AF2, AF3, and AF4.
l The default mapping relationships for the DS domain comply with the network planning requirements and
therefore do not need to be modified.
Step 2 Follow instructions in A.7.7.3 Changing the Ports Applied to a DS Domain and Their
Trusted Packet Types and change the ports that are applied to the DS domain and their trusted
packet types.
l The values for the related parameters of NE12 are provided as follows.
1-EM6T-3 ip-dscp
1-EM6T-1
3-IFU2-1
l The values for the related parameters of NE13 are provided as follows.
3-IFU2-1 ip-dscp
4-IFU2-1
1-EM6T-1
l The values for the related parameters of NE14 are provided as follows.
3-IFU2-1 ip-dscp
1-EM6T-3
l The values for the related parameters of NE15 are provided as follows.
3-IFU2-1 ip-dscp
4-IFU2-1
l The values for the related parameters of NE16 are provided as follows.
1-EM6T-3 ip-dscp
3-IFU2-1
Step 3 Follow instructions in A.7.7.4 Creating a Port Policy and create the port policy.
The values for the WRR scheduling policy parameters of NE12 to NE16 are provided as follows.
Parameter Value
Policy ID 2
The values for the port policy parameters of NE12 to NE16 are provided as follows.
Parameter Value
Policy ID 1
Step 4 Follow instructions in A.7.7.7 Setting the Port That Uses the Port Policy and set the ports that
use the port policy.
l The values for the related parameters of NE12 are provided as follows.
Parameter Value
Port 1-EM6T-1
1-EM6T-3
3-ISU2-1
l The values for the related parameters of NE13 are provided as follows.
Parameter Value
Port 3-ISU2-1
4-ISU2-1
1-EM6T-1
l The values for the related parameters of NE14 are provided as follows.
Parameter Value
Port 3-ISU2-1
l The values for the related parameters of NE15 are provided as follows.
Parameter Value
Port 3-ISU2-1
4-ISU2-1
l The values for the related parameters of NE16 are provided as follows.
Parameter Value
Port 3-ISU2-1
----End
Procedure
Step 1 See A.7.8.1 Creating an MD and configure the MD for NE12, NE14, and NE16.
Parameter Value
Maintenance 4 4 4
Domain Level
Step 2 See A.7.8.2 Creating an MA and create the MAs for NE12, NE14, and NE16.
l The values for the related parameters of NE12 are provided as follows.
Parameter Value
l The values for the related parameters of NE14 are provided as follows.
Parameter Value
l The values for the related parameters of NE16 are provided as follows.
Parameter Value
Step 3 See A.7.8.3 Creating MEPs and configure the MEPs for NE12, NE14, and NE16.
l The values for the related parameters of NE12 are provided as follows.
Parameter Value
VLAN - -
MP ID 201 200
l The values for the related parameters of NE14 are provided as follows.
Parameter Value
Board 1-EM6T-3
Port 1-EM6T-3
VLAN -
MP ID 401
Direction Ingress
CC Status Active
l The values for the related parameters of NE16 are provided as follows.
Parameter Value
Board 1-EM6T
Port 1-EM6T-3
VLAN -
Parameter Value
MP ID 601
Direction Ingress
CC Status Active
Step 4 See A.7.8.4 Creating Remote MEPs in an MA and create the remote MEP points for NE12,
NE14, and NE16.
The values for the related parameters of NE12 are provided as follows.
Parameter Value
The values for the related parameters of NE14 are provided as follows.
Parameter Value
The values for the related parameters of NE16 are provided as follows.
Parameter Value
l Perform the LB test by considering the MEP whose MEP ID is 200 as the source MEP and
the MEP whose MEP ID is 401 as the sink MEP.
l Perform the LB test by considering the MEP whose MEP ID is 200 as the source MEP and
the MEP whose MEP ID is 601 as the sink MEP.
There should be no packet lost during the LB tests.
----End
EoS/EoPDH-based Ethernet services are classified into EPL services, EVPL services, EPLAN
services, and EVPLAN services.
As shown in Figure 9-1, the ports mounted to the EoS plane are classified into the following
types:
VCTRUNK1 … VCTRUNK8
VC-4
Encapsulating Cross-
/Mapping unit connect unit
TDM plane
PORT9 PORT10
Ethernet Packet
…
switching switching
unit unit
FE PORT8
GE GE
VCTRUNK1 … VCTRUNK16
TDM
plane
9.1.3 VCTRUNK
When Ethernet services need to be transmitted in EoS or EoPDH mode, you need to configure
the Ethernet services between corresponding FE/GE ports and VCTRUNKs on Ethernet boards.
In EoS applications, the rate of a standard VC container does not adapt to that of Ethernet
services. If you directly map Ethernet services into a standard VC container, transmission
bandwidth is lavishly used. To solve this problem, the virtual concatenation technology is used
to concatenate standard VCs to a VCG that adapts to the rate of Ethernet services. Similarly, in
EoPDH applications, the virtual concatenation technology is used to concatenate PDHs to a
VCG that adapts to the rate of Ethernet services.
The EFP8 is an EoPDH Ethernet board and provides VCTRUNKs binding E1 pathsb.
NOTE
a: For the EMS6, only VC-12s in VC4-4s can be bound with VCTRUNKs.
b: On the NMS, VCTRUNKs that bind E1 paths are displayed as VCTRUNKs that bind VC-12 paths.
9.1.4 Hub/Spoke
For convergence services, mutual access between non-central stations and central stations is
needed but mutual access between non-central stations is not needed. Therefore, a port that is
mounted to a bridge needs to be configured as a Hub port or a Spoke port.
l Hub port
– Hub ports can access each other.
– A Hub port and a Spoke port can access each other.
l Spoke port
– Spoke ports cannot access each other.
– A Spoke port and a Hub port can access each other.
NOTE
A mounted port is a Hub port by default. You can configure a mounted port of a central station to a Hub
port, and a mounted port of a non-central station to a Spoke port. This ensures that a central station can
communicate with any non-central station, but non-central stations cannot communicate with each other.
Service Model
Table 9-1 describes the point-to-point transparently transmitted EPL service model.
Typical Application
Figure 9-3 shows the typical application scenarios of the point-to-point transparently transmitted
EPL service model.
Ethernet service 1 gains access to NE1 through port 1, regardless of whether the Ethernet service
carries an unknown VLAN ID or does not carry a VLAN ID. Port 1 processes the received
packets and transparently transmits Ethernet service 1 to port 3. Port 3 then processes the received
packets and transmits Ethernet service 1 to NE2.
Service Model
Table 9-2 shows the models of VLAN-based EVPL services.
Model 1 PORT (source) UNI (source) Enabled (source) The source port
PORT (sink) UNI (sink) Enabled (sink) processes a received
Ethernet frame
based on its TAG
attribute, and sends
the processed
Ethernet frame to
the sink port. The
sink port processes
the Ethernet frame
based on its TAG
attribute, and sends
the processed
Ethernet frame.
Typical Applications
Figure 9-4 shows a typical application of service model 1.
Service 1 and service 2 that carry unknown VLAN ID are transmitted to NE1 through port 1 and
port 2 respectively. Port 1 and port 2 process the received packets based on their TAG attributes.
Port 1 transmits service 1 to port 3, and port 2 transmits service 2 to port 4. Port 3 and port 4
process the received packets based on their TAG attributes. Then, port 3 and port 4 respectively
send service 1 and service 2 to NE2.
NOTE
The application of service model 1 is similar to point-to-point transparent transmission of Ethernet services.
The difference is that ports need to process packets based on their TAG attributes in the application of
service model 1.
Figure 9-5 shows a typical application of service model 2. Service 1 and service 2 that carry
different VLAN IDs are transmitted to NE1 through port 1 and port 2 respectively. They share
a transmission channel at port 3 and are separated by using VLANs.
On NE1, port 1 and port 2 process the received packets based on their TAG attributes. Port 1
sends service 1 to port 3, and port 2 sends service 2 to port 3. Port 3 processes the received
packets based on their TAG attributes, and sends service 1 and service 2 to NE2. Service 1 and
service 2 carry different VLAN IDs, so they can be transmitted through the same port, port 3.
Service Model
Table 9-3 shows the main models of QinQ-based EVPL services.
Model 1 PORT (source) C-Aware (source) Adding S-VLAN The source port adds
PORT+S-VLAN S-Aware (sink) tags (C-Aware port) S-VLAN tags to all
(sink) the received
Ethernet packets,
and transmits the
packets to the sink
port.
Model 2 PORT+C-VLAN C-Aware (source) Adding S-VLAN The source port adds
(source) S-Aware (sink) tags (C-Aware port) S-VLAN tags to all
PORT+C-VLAN the received
+S-VLAN (sink) Ethernet packets
that carry the
specified C-VLAN
tag, and transmits
the packets to the
sink port.
Typical Applications
Figure 9-6 shows a typical application of service model 1.
Service 1 and service 2 include tagged frames and untagged frames. Service 1 and service 2 are
transmitted to NE1 through port 1 and port 2 respectively. Port 1 adds the corresponding S-
VLAN tag to service 1, and port 2 adds the corresponding S-VLAN tag to service 2. Port 1 and
port 2 respectively transmit service 1 and service 2 to port 3. Then, port 3 transmits service 1
and service 2 to NE2.
NE2 processes service 1 and service 2 in the same way as NE1.
Strip S-VLAN Label Add S-VLAN Label Add S-VLAN Label Strip S-VLAN Label
NE 1 NE 2
Port 1 Port 1
Service 1 EVPL Service 1
Port 3 Transmission Port 3 EVPL
VLAN ID: 100 Network VLAN ID: 100
Service 2 L EVP Service 2
VLAN ID: 200 EVP L
Port 2 Port 2 VLAN ID: 200
by using the S-VLAN tags. On NE1, port 1 and port 2 respectively transmit service 1 and service
2 to port 3 transparently. Port 3 transmits service 1 and service 2 to NE2 at the same time because
service 1 and service 2 carry different S-VLAN tags.
NE2 processes service 1 and service 2 in the same way as NE1.
NE 1 NE 2
Port 1 Port 1
E-Line
Service 1
Port 3 Transmission Port 3 E-Line Service 1
S-VLAN ID: 100 Network S-VLAN ID: 100
Service 2 e E-Lin Service 2
S-VLAN ID: 100 E-Lin e
Port 2 Port 2 S-VLAN ID: 100
Service Model
Table 9-4 shows the model of 802.1D bridge-based EPLAN services.
Typical Applications
Figure 9-10 shows a typical application of the model of 802.1D bridge-based EPLAN services.
The transmission network needs to carry A services received by NE2 and NE3. A services are
converged and switched at the convergence node NE1. A services do not need to be separated.
Therefore, an 802.1D bridge is configured on NE1 to schedule services.
Port 2 Port 1
User A2
NE 1 Transmission
Network
Port 1 Port 2
User A1
Port 3
802.1d bridge NE 3
Transmission
Network
Port 1
User A3
Port 2
Service Model
Table 9-5 shows the model of 802.1Q bridge-based EVPLAN services.
NOTE
a: A VLAN filter table must be configured for checking VLAN tags. If the VLAN ID carried by a packet
is not defined in the VLAN filter table, the packet is discarded.
Typical Applications
Figure 9-11 shows a typical application of the model of 802.1Q bridge-based EVPLAN services.
The transmission network needs to carry G and H services received by NE2 and NE3. The two
services are converged and switched on NE1. G and H services use different VLAN tags.
Therefore, an 802.1Q bridge is configured on the NEs and is divided into multiple sub-switching
domains based on VLANs. In this manner, the two services are separated.
VLAN 100
Port 1
User G2
Port 3
NE 1
VLAN 200
Transmission Port 2
VLAN 100
Port 1 Network User H2
User G1
Port 3
802.1q bridge
VLAN 200
Port 2 Port 4
User H1 NE 3
Transmission
VLAN 100
Network
802.1q bridge Port 1
User G3
VLAN 200
Port 3 Port 2
User H3
802.1q bridge
NOTE
You can also configure 9.1.5.2 VLAN-based EVPL Services on NE2 and NE3 for service access.
Service Model
Table 9-6 lists the models of 802.1ad bridge-based EVPLAN services.
NOTE
a: When Bridge Learning Mode is set to IVL, a VLAN filter table must be configured for checking VLAN
tags. If the VLAN ID carried by a packet is not defined in the VLAN filter table, the packet is discarded.
Typical Applications
Model 1 is usually used in practice. Figure 9-12 shows a typical application. The transmission
network needs to carry G and H services received by NE2 and NE3. The two services are
converged and switched on NE1. G and H services use the same C-VLAN tag. Therefore,
different S-VLAN tags need to be added to the two services for separating them.
NE 2
SVLAN 300
Port 1
User G2
CVLAN 100
Port 3
SVLAN 400
NE 1 Port 2
Transmission User H2
SVLAN 300 Network CVLAN 100
Port 1 Port 3
User G1 802.1ad bridge
CVLAN 100
SVLAN 400
NE 3
Port 2
User H1
CVLAN 100 Port 4 SVLAN 300
Transmission
Port 1
Network
802.1ad bridge User G3
CVLAN 100
SVLAN 400
Port 3 Port 2
NE 1 User H3
CVLAN 100
Strip S-VLAN Label Add S-VLAN Label
NOTE
You can also configure 9.1.5.3 QinQ-based EVPL Services on NE2 and NE3 for service access.
Configuration Flowchart
Figure 9-13 provides the procedure for configuring point-to-point transparently transmitted EPL
services.
Required Start
Optional
Configuring Ethernet Ports
Configuring LAGs
Configuring QoS
End
Operation Description
A.8.5.1 l You need to set Basic Attributes. Set the parameters as follows:
Configuring – For ports to be used, set Enabled/Disabled to Enabled. For ports
External not to be used, set Enabled/Disabled to Disabled.
Ethernet Ports
– For Ethernet ports that are connected to external equipment, set
Working Mode to the same value as that of the external equipment
(generally, the working mode of the external equipment is auto-
negotiation). For Ethernet ports used for connection within the
network, set Working Mode to Auto-Negotiation.
– When jumbo frames are transmitted, set Maximum Frame
Length according to the actual length of a jumbo frame. Otherwise,
it is recommended that Maximum Frame Length take the default
value.
l Click the Flow Control tab to set parameters if the flow control
function is enabled on the external equipment to which the Ethernet
port is connected:
– When the external equipment uses the non-auto-negotiation flow
control function, set Non-Autonegotiation Flow Control Mode to
Enable Symmetric Flow Control.
– When the external equipment uses the auto-negotiation flow control
function, set Autonegotiation Flow Control Mode to Enable
Symmetric/Dissymmetric Flow Control.
l You need to set TAG Attributes. For a point-to-point transparently
transmitted EPL service, set Entry Detection to Disabled.
l For a point-to-point transparently transmitted EPL service, set Port
Attributes in the Network Attributes tab page to UNI.
l Determine whether to set Advanced Attributes according to actual
requirements.
Operation Description
Operation Description
A.8.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.
Table 9-9 Procedure for configuring point-to-point transparently transmitted EPL services
Operation Description
Operation Description
A.8.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.8.8.2 Required if you need to perform CAR or CoS operations for a specific flow
Creating the over a port.
CAR Set CAR or CoS parameters and bind the configured CARs or CoSs to the
corresponding flows according to the network plan.
A.8.8.3
Creating the
CoS
A.8.8.4
Binding the
CAR/CoS
Operation Description
A.8.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.
Operation Description
A.8.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.8.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.8.9.3 Creating MPs Required for NEs where the two Ethernet ports involved in the service test are located.
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
Configuration Flowchart
Figure 9-14 provides the procedure for configuring VLAN-based EVPL services.
Required Start
Optional
Configuring Ethernet Ports
Configuring LAGs
Configuring QoS
End
Operation Description
A.8.5.1 l You need to set Basic Attributes. Set the parameters as follows:
Configuring – For ports to be used, set Enabled/Disabled to Enabled. For ports
External not to be used, set Enabled/Disabled to Disabled.
Ethernet Ports
– For Ethernet ports that are connected to external equipment, set
Working Mode to the same value as that of the external equipment
(generally, the working mode of the external equipment is auto-
negotiation). For Ethernet ports used for connection within the
network, set Working Mode to Auto-Negotiation.
– When jumbo frames are transmitted, set Maximum Frame
Length according to the actual length of a jumbo frame. Otherwise,
it is recommended that Maximum Frame Length take the default
value.
l Click the Flow Control tab if the flow control function is enabled on
the external equipment to which the Ethernet port is connected. Set the
parameters as follows:
– When the external equipment uses the non-auto-negotiation flow
control function, set Non-Autonegotiation Flow Control Mode to
Enable Symmetric Flow Control.
– When the external equipment uses the auto-negotiation flow control
function, set Autonegotiation Flow Control Mode to Enable
Symmetric/Dissymmetric Flow Control.
l You need to set TAG Attributes.
– For a VLAN-based EVPL service, set Entry Detection to
Enabled.
– Set TAG, Default VLAN ID, and VLAN Priority according to the
plan. Default VLAN ID and VLAN Priority are valid only when
TAG is Access or Hybrid.
l For a VLAN-based EVPL service, set Port Attributes in the Network
Attributes tab page to UNI.
l Determine whether to set Advanced Attributes according to actual
requirements.
Operation Description
Operation Description
A.8.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.
Operation Description
Operation Description
A.8.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.8.8.2 Required if you need to perform CAR or CoS operations for a specific flow
Creating the over a port.
CAR Set CAR or CoS parameters and bind the configured CARs or CoSs to the
corresponding flows according to the network plan.
A.8.8.3
Creating the
CoS
A.8.8.4
Binding the
CAR/CoS
Operation Description
A.8.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.
Operation Description
A.8.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.8.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.8.9.3 Creating MPs Required for NEs where the two Ethernet ports involved in the service test are located.
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
Configuration Flowchart
Figure 9-15 provides the procedure for configuring QinQ-based EVPL services.
Required Start
Optional
Configuring Ethernet Ports
Configuring LAGs
Configuring QoS
End
Operation Description
A.8.5.1 l You need to set Basic Attributes. Set the parameters as follows:
Configuring – For ports to be used, set Enabled/Disabled to Enabled. For ports
External not to be used, set Enabled/Disabled to Disabled.
Ethernet Ports
– For Ethernet ports that are connected to external equipment, set
Working Mode to be the same value as that of the external
equipment (generally, the working mode of the external equipment
is auto-negotiation). For Ethernet ports used for connection within
the network, set Working Mode to Auto-Negotiation.
– When jumbo frames are transmitted, set Maximum Frame
Length according to the actual length of a jumbo frame. Otherwise,
it is recommended that Maximum Frame Length take the default
value.
l Click the Flow Control tab if the flow control function is enabled on
the external equipment to which the Ethernet port is connected. Set the
parameters as follows:
– When the external equipment uses the non-auto-negotiation flow
control function, set Non-Autonegotiation Flow Control Mode to
Enable Symmetric Flow Control.
– When the external equipment uses the auto-negotiation flow control
function, set Autonegotiation Flow Control Mode to Enable
Symmetric/Dissymmetric Flow Control.
l For a QinQ-based EVPL service, set Port Attributes in the Network
Attributes tab page to C-Aware or S-Aware.
l Determine whether to set Advanced Attributes according to actual
requirements.
Operation Description
Operation Description
A.8.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.
Operation Description
Operation Description
A.8.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.8.8.2 Required if you need to perform CAR or CoS operations for a specific flow
Creating the over a port.
CAR Set CAR or CoS parameters and bind the configured CARs or CoSs to the
corresponding flows according to the network plan.
A.8.8.3
Creating the
CoS
A.8.8.4
Binding the
CAR/CoS
Operation Description
A.8.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.
Operation Description
A.8.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.8.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.8.9.3 Creating MPs Required for NEs where the two Ethernet ports involved in the service test are located.
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
Configuration Flowchart
Figure 9-16 provides the procedure for configuring IEEE 802.1d bridge-based EPLAN services.
Required Start
Optional
Configuring Ethernet Ports
Configuring LAGs
Configuring QoS
End
Operation Description
A.8.5.1 l You need to set Basic Attributes. Set the parameters as follows:
Configuring – For ports to be used, set Enabled/Disabled to Enabled. For ports
External not to be used, set Enabled/Disabled to Disabled.
Ethernet Ports
– For Ethernet ports that are connected to external equipment, set
Working Mode to be the same value as that of the external
equipment (generally, the working mode of the external equipment
is auto-negotiation). For Ethernet ports used for connection within
the network, set Working Mode to Auto-Negotiation.
– When jumbo frames are transmitted, set Maximum Frame
Length according to the actual length of a jumbo frame. Otherwise,
it is recommended that Maximum Frame Length take the default
value.
l Click the Flow Control tab if the flow control function is enabled on
the external equipment to which the Ethernet port is connected. Set the
parameters as follows:
– When the external equipment uses the non-auto-negotiation flow
control function, set Non-Autonegotiation Flow Control Mode to
Enable Symmetric Flow Control.
– When the external equipment uses the auto-negotiation flow control
function, set Autonegotiation Flow Control Mode to Enable
Symmetric/Dissymmetric Flow Control.
l For an IEEE 802.1d bridge-based EPLAN service, set Port
Attributes in the Network Attributes tab page to UNI.
l To enable the broadcast packet suppression function, you need to set
Advanced Attributes.
Set the relevant parameters according to the network plan.
Operation Description
Operation Description
A.8.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.
Table 9-24 Procedure for configuring IEEE 802.1d bridge-based EPLAN services
Operation Description
A.8.4.1 Required if you need to set certain MAC address entries not
Creating a to age.
Static MAC The parameters need to be set according to the network plan.
Address
Entry
A.8.3.3 Changing the Ports Required if you need to change a port connected to a VB,
Connected to a VB enabled status of a port connected to a VB, or Hub/Spoke
attribute of a port connected to a VB.
Operation Description
A.8.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.8.8.2 Required if you need to perform CAR or CoS operations for a specific flow
Creating the over a port.
CAR Set CAR or CoS parameters and bind the configured CARs or CoSs to the
corresponding flows according to the network plan.
A.8.8.3
Creating the
CoS
A.8.8.4
Binding the
CAR/CoS
A.8.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.
Operation Description
A.8.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.8.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.8.9.3 Creating MPs Required for NEs where the two Ethernet ports involved in the service test are located.
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
Configuration Flowchart
Figure 9-17 provides the procedure for configuring IEEE 802.1q bridge-based EVPLAN
services.
Required Start
Optional
Configuring Ethernet Ports
Configuring LAGs
Configuring QoS
End
Operation Description
A.8.5.1 l You need to set Basic Attributes. Set the parameters as follows:
Configuring – For ports to be used, set Enabled/Disabled to Enabled. For ports
External not to be used, set Enabled/Disabled to Disabled.
Ethernet Ports
– For Ethernet ports that are connected to external equipment, set
Working Mode to the same value as that of the external equipment
(generally, the working mode of the external equipment is auto-
negotiation). For Ethernet ports used for connection within the
network, set Working Mode to Auto-Negotiation.
– When jumbo frames are transmitted, set Maximum Frame
Length according to the actual length of a jumbo frame. Otherwise,
it is recommended that Maximum Frame Length take the default
value.
l Click the Flow Control tab if the flow control function is enabled on
the external equipment to which the Ethernet port is connected. Set the
parameters as follows:
– When the external equipment uses the non-auto-negotiation flow
control function, set Non-Autonegotiation Flow Control Mode to
Enable Symmetric Flow Control.
– When the external equipment uses the auto-negotiation flow control
function, set Autonegotiation Flow Control Mode to Enable
Symmetric/Dissymmetric Flow Control.
l You need to set TAG Attributes.
Set TAG, Default VLAN ID, and VLAN Priority according to the
plan. Default VLAN ID and VLAN Priority are valid only when
TAG is Access or Hybrid.
l For an IEEE 802.1q bridge-based EVPLAN service, set Port
Attributes in the Network Attributes tab page to UNI.
l To enable the broadcast packet suppression function, you need to set
Advanced Attributes.
Set the relevant parameters according to the network plan.
Operation Description
Operation Description
A.8.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.
Table 9-29 Procedure for configuring IEEE 802.1q bridge-based EVPLAN services
Operation Description
A.8.4.1 Required if you need to set certain MAC address entries not
Creating a to age.
Static MAC Set the parameters according to the network plan.
Address
Entry
A.8.3.3 Changing the Ports Required if you need to change a port connected to a VB,
Connected to a VB enabled status of a port connected to a VB, or Hub/Spoke
attribute of a port connected to a VB.
Operation Description
A.8.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.8.8.2 Required if you need to perform CAR or CoS operations for a specific flow
Creating the over a port.
CAR Set CAR or CoS parameters and bind the configured CARs or CoSs to the
corresponding flows according to the network plan.
A.8.8.3
Creating the
CoS
A.8.8.4
Binding the
CAR/CoS
A.8.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.
Operation Description
A.8.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.8.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.8.9.3 Creating MPs Required for NEs where the two Ethernet ports involved in the service test are located.
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
Configuration Flowchart
Figure 9-18 provides the procedure for configuring IEEE 802.1ad bridge-based EVPLAN
services.
Required Start
Optional
Configuring Ethernet Ports
Configuring LAGs
Configuring QoS
End
Operation Description
A.8.5.1 l You need to set Basic Attributes. Set the parameters as follows:
Configuring – For ports to be used, set Enabled/Disabled to Enabled. For ports
External not to be used, set Enabled/Disabled to Disabled.
Ethernet Ports
– For Ethernet ports that are connected to external equipment, set
Working Mode to the same value as that of the external equipment
(generally, the working mode of the external equipment is auto-
negotiation). For Ethernet ports used for connection within the
network, set Working Mode to Auto-Negotiation.
– When jumbo frames are transmitted, set Maximum Frame
Length according to the actual length of a jumbo frame. Otherwise,
it is recommended that Maximum Frame Length take the default
value.
l Click the Flow Control tab if the flow control function is enabled on
the external equipment to which the Ethernet port is connected. Set the
parameters as follows:
– When the external equipment uses the non-auto-negotiation flow
control function, set Non-Autonegotiation Flow Control Mode to
Enable Symmetric Flow Control.
– When the external equipment uses the auto-negotiation flow control
function, set Autonegotiation Flow Control Mode to Enable
Symmetric/Dissymmetric Flow Control.
l For an IEEE 802.1ad bridge-based EVPLAN service, set Port
Attributes in the Network Attributes tab page to C-Aware or S-
Aware.
l To enable the broadcast packet suppression function, you need to set
Advanced Attributes.
Set the relevant parameters according to the network plan.
Operation Description
Operation Description
A.8.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.
Table 9-34 Procedure for configuring IEEE 802.1ad bridge-based EVPLAN services
Operation Description
A.8.3.4 Creating the VLAN Required if you set Bridge Switch Mode to IVL/Ingress
Filtering Table Filter Enable.
Set VLAN ID(e.g.1,3-6) and Selected forwarding ports
according to the network plan.
A.8.4.1 Required if you need to set certain MAC address entries not
Creating a to age.
Static MAC Set the parameters according to the network plan.
Address
Entry
Operation Description
A.8.3.3 Changing the Ports Required if you need to change a port connected to a VB,
Connected to a VB enabled status of a port connected to a VB, or Hub/Spoke
attribute of a port connected to a VB.
Operation Description
A.8.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.8.8.2 Required if you need to perform CAR or CoS operations for a specific flow
Creating the over a port.
CAR Set CAR or CoS parameters and bind the configured CARs or CoSs to the
corresponding flows according to the network plan.
A.8.8.3
Creating the
CoS
A.8.8.4
Binding the
CAR/CoS
A.8.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.
Operation Description
A.8.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.8.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.8.9.3 Creating MPs Required for NEs where the two Ethernet ports involved in the service test are located.
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
Based on 6.3 Configuration Example (Radio Links on the TDM Radio Chain Network),
configure the Ethernet services on the TDM radio chain network shown in Figure 9-19,
according to the following requirements:
l In this example, few Ethernet services are transmitted only on BTS13 and BTS14. To meet
the service requirements, the radio network does not need to be upgraded and the EoS mode
is used to transmit Ethernet services.
l BTS13 requires 4 Mbit/s Ethernet service bandwidth, and BTS14 requires 10 Mbit/s
Ethernet service bandwidth.
l Ethernet services transmitted by BTS13 and BTS14 carry VLAN tags, and VLAN IDs on
the entire network are planned in a unified manner.
l FE links to the BSC are configured with LAG protection.
l QoS processing is not required.
l Figure 9-20 shows the board configuration of each NE on the radio network.
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
CST CST
IF1
NE6
IF1 NE6
IF1 IF1
SP3S EMS6 SP3S
NE16 NE15 FE E1
E1
BTS14
BTS15
NOTE
If Ethernet services need to be encapsulated in E1s for transmission (in this example, the Ethernet services need
to traverse the E1 service cable between NE12 and NE13), the EFP8 is required. Configure the EFP8 in the
similar way for configuring the EMS6.
Between NE11 and the BSC 4-EMS6-PORT1 (main port l Aggregates the Ethernet
of a LAG) services from BTS13 and
BTS14 to the BSC.
4-EMS6-PORT2 (slave port
l Uses a load non-sharing
of a LAG)
LAG, improving link
reliability.
Between NE11 and NE12 3-IF1 (main IF board of a 1+1 Transmits Ethernet services
HSB protection group) encapsulated in STM-1.
Between NE12 and NE11 3-IF1 (main IF board of a 1+1 Transmits Ethernet services
HSB protection group) encapsulated in STM-1.
Between NE13 and NE14 3-IF1 (main IF board of a 1+1 Transmits Ethernet services
HSB protection group) encapsulated in STM-1.
Between NE13 and NE15 4-IF1 (main IF board of a 1+1 Transmits Ethernet services
HSB protection group) encapsulated in STM-1.
Between NE14 and NE13 3-IF1 (main IF board of a 1+1 Transmits Ethernet services
HSB protection group) encapsulated in STM-1.
Between NE15 and NE13 4-IF1 (main IF board of a 1+1 Transmits Ethernet services
HSB protection group) encapsulated in STM-1.
Parameter 4-EMS6-PORT1
Parameter 4-EMS6-PORT1
Parameter 1-EMS6-PORT1
NOTE
l In this example, the FE ports on all the BTSs/BSC work in auto-negotiation mode. Therefore, the FE
ports on the NEs that receive services from and transmit services to the BTSs/BSC must also work in
auto-negotiation mode. If the peer Ethernet ports work in another mode, enable the local Ethernet ports
to work in a consistent mode. Ethernet ports within a network should work in auto-negotiation mode.
l Generally, the flow control function is enabled only when the NE or the peer NE is incapable of QoS
processing. The flow control planning must be consistent at both ends.
l In this example, all the Ethernet services carry VLAN tags. Therefore, the TAG attributes of all the
ports are Tag Aware.
l In this example, the planned maximum frame length uses the default value 1522. If required, change
the maximum frame length according to the requirements of the specific BTS.
LCAS Enabled
LCAS Enabled
To improve service transmission reliability, NE11 and the BSC are interconnected through the
LAG formed by two FE links. Table 9-48 provides the planning information.
Parameter NE11
NOTE
In this example, 14 Mbit/s Ethernet services are transmitted, and the bandwidth is much lower than the
bandwidth of an FE port. Therefore, you do not need to configure the LAG to load-sharing mode to increase
the bandwidth.
Ethernet services received by each BTS carry the specific VLAN ID. Therefore, you need to
configure VLAN-based EVPL services in this example. Table 9-49 to Table 9-51 provide the
service planning information.
Board 4-EMS6
Board 1-EMS6
Timeslot Allocation
Figure 9-21 shows the timeslots that are allocated to the TDM radio-based Ethernet services
according to the service planning information. 7.1.4 TDM Timeslot Planning Schemes
describes the meanings of the timeslot allocation diagram and how to plan the timeslot allocation
diagram.
Figure 9-21 Timeslot allocation diagram (Ethernet services based on TDM radio)
Links-1: NE11 - NE12 - NE13 -NE15-NE16
Station NE11 NE12 NE13 NE15 NE16
Timeslot 3-IF1 3-IF1 1-SL1D-1 1-SL1D-1 4-IF1 4-IF1 3-IF1 3-IF1
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
As shown in Figure 9-21, the information about the timeslots that the TDM radio-based Ethernet
services occupy on each NE is as follows:
– The Ethernet services occupy the sixth and seventh VC-12 timeslots on the link between
the IF1 board in slot 3 of NE11 and the first optical port on the SL1D board in slot 1 of
NE13.
– The Ethernet services occupy the first and second VC-12 timeslots on the link from the
IF1 board in slot 3 of NE13 to the IF1 board in slot 3 of NE14.
Parameter Value
Source port 1
Sink port 1
Parameter Value
Source port 1
Sink port 1
Parameter Value
Parameter Value
Source port 1 1
Sink port 1 1
Parameter Value
Source port 1
Sink port 1
Parameter Value
Source port 1
Sink port 1
Procedure
Step 1 See A.8.5.1 Configuring External Ethernet Ports and configure the Ethernet external ports.
l The values for the relevant parameters of NE11 are provided as follows.
Parameter Value
4-EMS6-PORT1 4-EMS6-PORT2
Parameter Value
4-EMS6-PORT1 4-EMS6-PORT2
l The values for the relevant parameters of NE14 are provided as follows.
Parameter Value
4-EMS6-PORT1
Enabled/Disabled Enabled
l The values for the relevant parameters of NE15 are provided as follows.
Parameter Value
1-EMS6-PORT1
Enabled/Disabled Enabled
Parameter Value
1-EMS6-PORT1
Step 2 See A.8.5.2 Configuring VCTRUNKs on an Ethernet Board and configure the VCTRUNKs.
l The values for the relevant parameters of NE11 are provided as follows.
Parameter Value
4-EMS6-VCTRUNK1 4-EMS6-VCTRUNK2
l The values for the relevant parameters of NE14 are provided as follows.
Parameter Value
4-EMS6-VCTRUNK1
Level VC-12-Xv
Direction Bidirectional
l The values for the relevant parameters of NE15 are provided as follows.
Parameter Value
1-EMS6-VCTRUNK1
Level VC-12-Xv
Direction Bidirectional
----End
Procedure
Step 1 See A.8.2.1 Creating a LAG and create the LAG.
The values for the relevant parameters of NE11 are provided as follows.
Parameter Value
4-EMS6
LAG No 1
Step 2 See A.8.2.2 Setting Parameters for LAGs and set the parameters for LAGs.
The values for the relevant parameters of NE11 are provided as follows.
Parameter Value
4-EMS6
LAG No 1
----End
Procedure
Step 1 See A.8.3.1 Creating Ethernet Private Line Services and create the Ethernet private line
service.
l The values for the relevant parameters of NE11 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE14 are provided as follows.
Parameter Value
Board 4-EMS6
Direction Bidirectional
Parameter Value
l The values for the relevant parameters of NE15 are provided as follows.
Parameter Value
Board 1-EMS6
Direction Bidirectional
----End
Procedure
Step 1 On NE11, NE14, and NE15, see A.5.1 Creating the Cross-Connections of Point-to-Point
Services and create the service cross-connections.
l The values for the relevant parameters of NE11 are provided as follows.
Parameter Value
Level VC12
Direction Bidirectional
Source 4-EMS6
Source Port 1
Parameter Value
Sink 3-IF1
Sink Port 1
l The values for the relevant parameters of NE12 are provided as follows.
Parameter Value
Level VC12
Direction Bidirectional
Source 3-IF1
Source Port 1
Sink 1-SL1D
Sink Port 1
l The values for the relevant parameters of NE13 are provided as follows.
Parameter Value
Source Port 1 1
Sink Port 1 1
Parameter Value
l The values for the relevant parameters of NE14 are provided as follows.
Parameter Value
Level VC12
Direction Bidirectional
Source 4-EMS6
Source Port 1
Sink 3-IF1
Sink Port 1
l The values for the relevant parameters of NE15 are provided as follows.
Parameter Value
Level VC12
Direction Bidirectional
Source 1-EMS6
Source Port 1
Sink 4-IF1
Sink Port 1
----End
Procedure
Step 1 On NE11, NE14, and NE15, see A.8.9.1 Creating MDs and create the maintenance domain.
Parameter Value
Maintenance 4 4 4
Domain Level
Step 2 On NE11, NE14, and NE15, see A.8.9.2 Creating MAs and create the maintenance association.
l The values for the relevant parameters of NE11 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE14 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE15 are provided as follows.
Parameter Value
Step 3 On NE11, NE14, and NE15, see A.8.9.3 Creating MPs and create the maintenance points.
l The values for the relevant parameters of NE11 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE14 are provided as follows.
Parameter Value
Node 4-EMS6-PORT1
VLAN ID 120
MEP ID 401
Type MEP
CC Status Activate
l The values for the relevant parameters of NE15 are provided as follows.
Parameter Value
Node 1-EMS6-PORT1
Parameter Value
VLAN ID 130
MEP ID 501
Type MEP
CC Status Activate
----End
On the network shown in Figure 9-22, all the Ethernet services from BTS11-BTS15 are
aggregated through Hybrid radio links to NE11, traverse the leased TDM network, and then are
transmitted to the BSC. Based on 6.3 Configuration Example (Radio Links on the TDM
Radio Chain Network), configure the Ethernet services according to the following
requirements:
l NE11 uses the EFP8 board to receive Ethernet services from and transmit Ethernet services
to BTS16.
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 actual networking scenarios, NE17 can also be OptiX MSTP equipment that supports 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 transmitted by each BTS carry VLAN tags, and VLAN IDs on the entire
network are planned in a unified manner. Therefore, the VLAN-based E-Line services are
configured for service transmission in this example.
l VLAN priorities are configured on each BTS according to service types and QoS processing
is required.
l Figure 9-23 shows the board configuration of each NE on the radio network.
NOTE
This section describes only how to configure Ethernet services on NE11 and NE17. For details on how to
configure Ethernet services on NE12 to NE16, see 8.4 Configuration Example (VLAN-Based E-Line
Service).
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
CSH
CSH CSH
ISU2 NE6
NE6
ISU2 NE6
ISU2 ISU2
EFP8
SP3D
EM6T SP3S EM6T SP3S
NE16 NE15 NE17 FE
FE E1
BTS15 BSC
NOTE
In this example, 20 E1 lines are used to transmit Ethernet services only. In actual networking scenarios,
extra E1 lines need to be leased for transmitting E1 services.
Parameter 4-EFP8-PORT10
NOTE
l In this example, all the services carry VLAN tags. Therefore, the TAG attributes of all the ports are Tag
Aware.
l In the case of the EFP8 board, the flow control function is enabled only when the NE or the peer equipment
is inadequate for QoS processing. The planning information of flow control must be the same for the
equipment at both ends.
l In this example, the maximum frame length is planned to be the default value, 1522. If required, change the
maximum frame length according to the requirements of the specific BTS.
Table 9-61 provides the planning information about the Ethernet service.
Service ID 1
QoS (DiffServ)
DS is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the BTS
services be allocated by the service type. Then, the transmission network creates the
corresponding DS domain according to the allocated VLAN priority or DSCP value. Each
Ethernet port involved in the service must use the same DS configuration.
In this example, the BTS services are allocated with corresponding VLAN priorities according
to the service type, and the NEs allocate the PHB service classes according to the VLAN priority,
as provided in Table 9-62. Each Ethernet port involved in the service uses the same DS
configuration.
CS7 7 -
CS6 6 -
AF4 4 -
AF1 1 -
NOTE
l During the mapping of the PHB service class, CS7 or CS6 is not recommended, because CS7 or CS6 may
be used to transmit Ethernet protocol packets or inband DCN packets on the NE.
l The default mapping relationships for the DS domain comply with the network planning requirements and
therefore do not need to be modified.
l The default trusted packet type for each port that is applied for the default DS domain is C-VLAN priority
and therefore does not need to be modified.
Table 9-63 lists the queue scheduling mode used by each Ethernet port involved in the service
in this example.
CS7 SP
CS6 SP
EF SP
BE SP
Parameter 4-EFP8-PORT1
Parameter 4-EFP8-PORT1
NOTE
l In this example, the FE ports on all the BTSs/BSC work in auto-negotiation mode. Therefore, the FE
ports on the NEs that receive services from and transmit services to the BTSs/BSC must also work in
auto-negotiation mode. If the peer Ethernet ports work in another mode, enable the local Ethernet ports
to work in a consistent mode. Ethernet ports within a network should work in auto-negotiation mode.
l Generally, the flow control function is enabled only when the NE or the peer NE is incapable of QoS
processing. The flow control planning must be consistent at both ends.
l In this example, all the Ethernet services carry VLAN tags. Therefore, the TAG attributes of all the
ports are Tag Aware.
l In this example, the planned maximum frame length uses the default value 1522. If required, change
the maximum frame length according to the requirements of the specific BTS.
According to the information about the VCTRUNKs in this example, you need to configure the
two VCTRUNKs into a load-sharing LAG to increase the bandwidth. Table 9-68 and Table
9-69 provide the planning information of LAGs.
Parameter NE11
Revertive mode -
Parameter NE17
Revertive mode -
Parameter NE17
LAGs are created on NE1 and NE7 in this example. Therefore, you need to configure services
only on the main ports. Table 9-70 and Table 9-71 provide the service planning information.
Parameter NE11
Parameter NE17
Board 4-EFP8
Parameter NE17
In this example, VC-12 timeslot cross-connections are set up between the first to twentieth
VC-12 timeslots (bound with VCTRUNKs) in VC4-1 on the 4-EFP8 board and the first to
twentieth ports on the 2-SP3D board. Table 9-72 and Table 9-73 provide the information about
cross-connections of the Ethernet services.
Parameter Value
Source port 1
Sink port -
Sink VC4 -
Parameter Value
Parameter Value
Source port 1
Sink port -
Sink VC4 -
QoS (Flow)
Traffic classification is the prerequisite for configuring QoS of the EFP8 board. In this example,
VLAN-based EVPL services are created. Therefore, you need to create PORT+VLAN-based
flows. Table 9-74 and Table 9-75 provide the planning information of flows.
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 the BTS services, CoS with the ID of 1 schedules BTS services with different
VLAN priorities into egress queues with different forwarding priorities.
QoS (CAR)
In this example, CAR need not be configured.
QoS (CoS)
In this example, the BTS services are configured with corresponding VLAN priorities or DSCPs
based on the service types. The EFP8 board performs CoS processing for a BTS service
according to its VLAN priority or DSCP.
In this example, BTSs allocate VLAN priorities to services according to the service types.
Therefore, you need to configure CoS on Ethernet ports that receive services from and transmit
services to the BTSs, according to the service types. Table 9-76 and Table 9-77 provide the
CoS planning information.
Table 9-76 CoS attributes of the EFP8 board (NE11 and NE17)
Parameter Value
CoS ID 1
Table 9-77 CoS parameters and corresponding BTS service types of the EFP8 board (NE11 and
NE17)
NOTE
Queue 8 (namely, CoS priority 7) is the 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 so that high-priority services can be
scheduled in time.
Procedure
Step 1 See A.7.3.2 Configuring UNI-UNI E-Line Services and create the E-Line services.
The values for the relevant parameters of NE11 are provided as follows.
Parameter Value
Service ID 1
Direction UNI-UNI
----End
Procedure
Step 1 See A.6.6.1 Setting the Basic Attributes of Ethernet Ports and set the basic attributes of
Ethernet ports.
The values for the relevant parameters of NE11 are provided as follows.
Parameter Value
4-EFP8-PORT10
----End
Procedure
Step 1 See A.7.7.2 Modifying the Mapping Relationships for the DS Domain and modify the
mapping relationships for the DS domain.
NOTE
The mapping relationship defined in the default DS domain is the same as the mapping relationship defined in
the DS domain that is created in this step. Therefore, you can skip this step.
The values for the related parameters that need to be set in the main interface are provided as
follows.
Parameter Value
Mapping Relation ID 1
The values for the related parameters that need to be set in the Ingress Mapping Relation tab
page are provided as follows.
1 AF11
2 AF21
3 AF31
4 AF41
5 EF
6 CS6
7 CS7
The values for the related parameters that need to be set in the Egress Mapping Relation tab
page are provided as follows.
AF11 1
AF21 2
AF31 3
AF41 4
EF 5
CS6 6
CS7 7
NOTE
The AF1 is classified into three sub service classes, namely, AF11, AF12, and AF13, only one of which is valid.
In this example, the AF11 is used. It is the same case with the AF2, AF3, and AF4.
Step 2 A.7.7.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types and
change the ports that are applied to the DS domain and their trusted packet types.
NOTE
The actual ports that are applied to the default DS domain and their trusted packet types comply with the network
planning information. Therefore, you can skip this step.
The values for the related parameters of NE12 are provided as follows.
3-ISU2-1 CVLAN
4-EFP8-PORT10
Step 3 See A.7.7.4 Creating a Port Policy and create the port policy.
The values for the WRR scheduling policy parameters of NE11 are provided as follows.
Parameter Value
Policy ID 2
The values for the port policy parameters of NE11 are provided as follows.
Parameter Value
Policy ID 1
Parameter Value
Step 4 See A.7.7.7 Setting the Port That Uses the Port Policy and set the ports that use the port policy.
The values for the relevant parameters of NE11 are provided as follows.
Parameter Value
Port 3-ISU2-1
4-EFP8-PORT10
----End
Procedure
Step 1 See A.8.5.1 Configuring External Ethernet Ports and configure the Ethernet external ports.
l The values for the relevant parameters of NE11 are provided as follows.
Parameter Value
4-EFP8-PORT1 4-EFP8-PORT9
Parameter Value
4-EFP8-PORT1 4-EFP8-PORT9
l The values for the relevant parameters of NE17 are provided as follows.
Parameter Value
4-EFP8-PORT1
Enabled/Disabled Enabled
Step 2 See A.8.5.2 Configuring VCTRUNKs on an Ethernet Board and configure the VCTRUNKs.
l The values for the relevant parameters of NE11 are provided as follows.
Parameter Value
4-EFP8-VCTRUNK1 4-EFP8-VCTRUNK2
l The values for the relevant parameters of NE17 are provided as follows.
Parameter Value
4-EFP8-VCTRUNK1 4-EFP8-VCTRUNK2
----End
Procedure
Step 1 See A.8.2.1 Creating a LAG and create the LAGs.
l The values for the relevant parameters of NE11 are provided as follows.
Parameter Value
4-EFP8
LAG No 1
l The values for the relevant parameters of NE17 are provided as follows.
Parameter Value
4-EFP8
LAG No 1
Step 2 See A.8.2.2 Setting Parameters for LAGs and set the parameters for LAGs.
l The values for the relevant parameters of NE11 are provided as follows.
Parameter Value
4-EFP8
LAG No 1
l The values for the relevant parameters of NE17 are provided as follows.
Parameter Value
4-EFP8
LAG No 1
----End
Procedure
Step 1 See A.8.3.1 Creating Ethernet Private Line Services and create the Ethernet private line
services.
l The values for the relevant parameters of NE11 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE17 are provided as follows.
Parameter Value
Board 4-EFP8
Direction Bidirectional
----End
Procedure
Step 1 See A.5.1 Creating the Cross-Connections of Point-to-Point Services and create the service
cross-connections.
l The values for the relevant parameters of NE11 are provided as follows.
Parameter Value
Level VC12
Direction Bidirectional
Source 4-EFP8
Source Port 1
Sink 2-SP3D
Sink Port -
Sink VC4 -
l The values for the relevant parameters of NE17 are provided as follows.
Parameter Value
Level VC-12
Direction Bidirectional
Source 4-EFP8
Source Port 1
Sink 2-SP3D
Sink Port -
Sink VC4 -
----End
Procedure
Step 1 See A.8.8.1 Creating a Flow and create the flows.
l The values for the relevant parameters of NE11 are provided as follows.
Parameter Value
4-EFP8
l The values for the relevant parameters of NE17 are provided as follows.
Parameter Value
4-EFP8
Step 2 See A.8.8.3 Creating the CoS and create the CoS.
l The values for the relevant parameters of NE11 are provided as follows.
Parameter Value
4-EFP8
CoS ID 1
l The values for the relevant parameters of NE17 are provided as follows.
Parameter Value
4-EFP8
CoS ID 1
Step 3 See A.8.8.4 Binding the CAR/CoS and bind the CAR/CoS.
l The values for the relevant parameters of NE11 are provided as follows.
Parameter Value
4-EFP8
Bound CAR - - - -
Bound CoS 1 1 1 1
l The values for the relevant parameters of NE17 are provided as follows.
Parameter Value
4-EFP8
Bound CAR - - - -
Bound CoS 1 1 1 1
----End
Procedure
Step 1 See A.8.9.1 Creating MDs and create the maintenance domain on NE11 and NE17.
Parameter Value
NE11 NE17
Maintenance Domain 4 4
Level
Step 2 See A.8.9.2 Creating MAs and create the maintenance domain on NE11 and NE17.
l The values for the relevant parameters of NE11 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE17 are provided as follows.
Parameter Value
Parameter Value
Step 3 See A.8.9.3 Creating MPs and create the maintenance domain on NE11 and NE17.
l The values for the relevant parameters of NE11 are provided as follows.
Parameter Value
Node 4-EFP8-PORT1
VLAN ID 150
MEP ID 101
Type MEP
CC Status Activate
l The values for the relevant parameters of NE17 are provided as follows.
Parameter Value
Parameter Value
----End
Figure 10-1 shows the MPLS network architecture. On an MPLS network, LSRs on the network
edge are called label edge routers (LERs), and LSRs within the network range are called core
LSRs. An LER may have one or more adjacent non-LSR nodes, but all the adjacent nodes of a
core LSR are LSRs.
MPLS
LER
network
Other
MPLS
Other
network
LER MPLS
LSR network
Core LSR LSR
LER
LER
Other
MPLS
network Packet transmission equipment
On an MPLS network, each LSR has a unique identifier; that is, a 16-byte LSR ID. An LSR ID
can be based on the IPv4 address or IPv6 address.
NOTE
Currently, the OptiX RTN 950 supports only LSR IDs based on the IPv4 address.
10.1.2 LSP
Label switched paths (LSPs), also called MPLS tunnels, are classified into various types
depending on different classification criteria.
equivalence class (FEC). The path along which an FEC travels through the MPLS network is
called an LSP, or an MPLS tunnel.
To provide a unified interface for upper-level applications of an LSP, the system needs to assign
an ID to the LSP. This ID is called an LSP ID or tunnel ID. An LSP ID is 4-byte long, and is
only valid for the local LSR.
An LSP is unidirectional. As shown in Figure 10-2, LSRs on an LSP can be classified into the
following types:
l Ingress
An LSP ingress node pushes a label onto the packet for MPLS packet encapsulation and
forwarding. One LSP has only one ingress node.
l Transit
An LSP transit node swaps labels and forwards MPLS packets according to the label
forwarding table. One LSP may have one or more transits nodes.
l Egress
An LSP egress node pops the label and recovers the packet for forwarding. One LSP has
only one egress node.
MPLS
network
Other
MPLS Other
network MPLS
Ingress Transit network
Transit Egress
LSP
LSP Types
LSPs are classified into various types depending on different classification criteria. For details,
see Table 10-1.
Setup mode Static tunnel A static tunnel is set The OptiX RTN 950
up according to the supports static
data configurations. tunnels.
LSP mode Uniform When an egress node The OptiX RTN 950
pops the MPLS supports the Pipe
tunnel label, it mode only.
renews the packet
scheduling priority
according to the EXP
field in the label.
MPLS APS is a function that protects MPLS tunnels based on the APS protocol. MPLS APS
improves reliability for service transmission in tunnels. With this function, when the working
tunnel is faulty, the service can be switched to the preconfigured protection tunnel.
The MPLS APS function supported by the OptiX RTN 950 has the following characteristics:
In MPLS APS, the MPLS OAM mechanism is used to detect faults in tunnels, and the ingress
and egress nodes exchange APS protocol packets to achieve protection switching. As shown in
Figure 10-3, when the MPLS OAM mechanism detects a fault in the working tunnel, the service
is switched to the protection tunnel for transmission.
Working Tunnel
Ingress Egress
Protection Tunnel
Transit
Protect switching
Transit
Working Tunnel
Ingress Egress
Protection Tunnel
Transit
Service
Start Start
Required
Set the QoS policy for Set the QoS policy for
MPLS ports MPLS ports
End End
Table 10-2 Procedure for setting MPLS port attributes (not using VLAN sub-interfaces)
Operation Description
Operation Description
Table 10-3 Procedure for configuring MPLS ports (using VLAN sub-interfaces)
Operation Description
Operation Description
Operation Description
Operation Description
A.7.2.1 Required if LAG protection is configured for FE/GE ports or for the
Creating a Integrated IP radio that works in N+0/XPIC mode. Set the major
LAG parameters as follows:
NOTE
For ISU2/ISX2 boards, if they have been added to a PLA group during radio link
configuration, the LAG does not need to be configured.
l Set LAG Type to the same value as that of the opposite equipment.
Generally, set LAG Type to Static for the equipment at both ends.
l For FE/GE ports, set Load Sharing to the same value as that of the
opposite equipment. If the LAG is configured to provide protection, it
is recommended that you set Load Sharing to Non-Sharing for the
equipment at both ends. If the LAG is configured to provide protection
and to increase bandwidth, it is recommended that you set Load
Sharing to Sharing for the equipment at both ends.
l When the Integrated IP radio works in N+0/XPIC mode and uses LAG
protection, set Load Sharing to Sharing for the equipment at both
ends.
l Set Revertive Mode to the same value as that of the opposite
equipment. Generally, set Revertive Mode to Revertive for the
equipment at both ends. This parameter is valid only to the non-sharing
LAG.
l It is recommended that you set these parameters to the same values for
the main and slave ports of the LAGs at both ends. In this case, you can
set System Priority as desired. It is recommended that this parameter
take its default value. This parameter is valid only to the static LAG.
l During the configuration of a LAG at air interfaces, if LAG switching
needs to be triggered when signals on the radio link deteriorate, set
Switch LAG upon Air Interface SD to Enabled.
l Set Main Board, Main Port, and Selected Standby Ports according
to the plan. It is recommended that you set this parameter to the same
value for the main and slave ports of the LAGs at both ends.
NOTE
Set the AM attributes to the same value for the microwave ports in a LAG.
Operation Description
A.9.2.1 Setting Basic MPLS Required. Set the major parameters as follows:
Attributes l Set LSR ID according to the plan and ensure that the
value is unique on the entire network.
l Set Start of Global Label Space according to the
plan. On an MPLS network, global label spaces of
NEs are recommended to overlap each other if
possible.
A.9.1.1 Creating ARP Static Required when the dynamic ARP protocol cannot obtain
Entries the next-hop MAC address (for example, when
traversing an L2 network). Set the major parameters as
follows:
l ARP List IP Address: Set this parameter to the IP
address of the next-hop port.
l ARP List MAC: Set this parameter to the MAC
address of the next-hop port.
Operation Description
A.9.2.7 Setting MPLS OAM Required when you need to configure an MPLS APS
Parameters protection group.
l For a bidirectional MPLS tunnel, set the major
parameters as follows:
– Set OAM Status to Enabled for a tunnel where
an OAM test needs to be performed.
– It is recommended that you set Detection Mode
to Auto-Sensing.
– When you need to create an MPLS APS
protection group, set Detection Packet Type to
FFD and set Packet Detection Interval(ms) to
3.3. This ensures that the switching time is less
than 100 ms.
– Set SD Threshold(%) and SF Threshold(%)
according to actual requirements.
l For the ingress node of a unidirectional MPLS
tunnel, set the major parameters as follows:
– Set OAM Status to Enabled for a tunnel where
an OAM test needs to be performed.
– When you need to create an MPLS APS
protection group, set Detection Packet Type to
FFD and set Packet Detection Interval(ms) to
3.3. This ensures that the switching time is less
than 100 ms.
– Select the corresponding reverse tunnel.
l For the egress node of a unidirectional MPLS tunnel,
set the major parameters as follows:
– Set OAM Status to Enabled for a tunnel where
an OAM test needs to be performed.
– It is recommended that you set Detection Mode
to Auto-Sensing.
– Select the corresponding reverse tunnel.
– Set SD Threshold(%) and SF Threshold(%)
according to actual requirements.
Operation Description
A.9.3.1 Creating an MPLS APS Required when you need to configure protection for
Protection Group services carried on an MPLS tunnel.
l The protection tunnel must be created.
l When creating an APS protection group, set
Protocol Status to Disabled. Start the protocol only
when the APS protection group is successfully
created on nodes at both ends.
l Set the parameters of the protection group according
to the plan.
Operation Description
Configuring A.7.7.2 When the default mapping between the DS domain and the
the DiffServ Modifying PHBs does not meet network requirements, perform this
the operation to change the mapping.
Mapping
Relationshi
ps for the
DS Domain
A.7.7.3 Required.
Changing Set Packet Type for each MPLS port to MPLS-EXP.
the Ports
Applied to a
DS Domain
and Their
Trusted
Packet
Types
Operation Description
A.7.7.8 Configuring Port Required when the shaping function needs to be configured.
Shaping Set the parameters according to the network plan.
Operation Description
A.9.2.7 Setting MPLS OAM Required if you need to enable the MPLS OAM function
Parameters to check the tunnel status before an MPLS APS
protection group is created.
When you need to check availability of an MPLS tunnel,
it is recommended that you set Detection Packet
Type to CV.
All base station services need to be transmitted through a PSN to the BSC and RNC. Based on
6.7 Configuration Example (Radio Links on the 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-5.
2-EM6F-1(to NE11)
2-EM6F-2(to NE31)
GE GE
NE32
1-EM6F-1(to NE32)
NE11 NE31
2-EM6F-1(to NE21) GE 1-EM6F-2(to NE21)
NE21 GE
2-EM6F-2(to NE32)
1-EM6F-1(to NE31)
1-EM6F-2(to NE11)
Table 10-9 to Table 10-12 provide the information about each NNI port involved in the service.
NOTE
l Appropriate port names facilitate future maintenance. It is recommended that you name ports on the entire
network in a unified manner.
l In this example, all GE ports on the packet network are set to the auto-negotiation mode.
l The maximum frame length for each MPLS port is set to 1620, because an Ethernet frame carrying MPLS
packet is longer than a Native Ethernet frame.
l Generally, the flow control function is enabled only when the local NE or opposite equipment has insufficient
QoS capabilities. The planning information of flow control must be the same for the equipment at both ends.
l An MPLS port does not carry E-LAN services, so the loopback check, loopback port shutdown, and
broadcast packet suppression functions do not need to be enabled for Ethernet ports.
Basic NE Configuration
Before creating an MPLS tunnel, you need to assign an LSR ID for each NE as its unique ID on
the network. See Table 10-13.
Start of global 0 0 0 0
label space
NOTE
The LSR ID of NE32 planned in this example is the same as that planned in 10.4 Configuration Example
(MPLS Tunnels with No Protection).
L:1501 ID:1501 L:1501 L:1507 L:1507 L:1501 L:1501 L:1507 ID:1507 L:1507
L:1502 L:1502 L:1508 L:1508 L:1502 L:1502 L:1508 L:1508
L:1505 ID:1503 L:1505 L:1509 L:1509 L:1503 L:1503 L:1509 ID:1509 L:1509
L:1506 L:1506 L:1510 L:1510 L:1504 L:1504 L:1510 L:1510
L:1503 ID:1511 L:1503 L:1511 L:1511 L:1505 L:1505 L:1511 ID:1505 L:1511
L:1504 L:1504 L:1512 L:1512 L:1506 L:1506 L:1512 L:1512
Ingress/Egress
L: Label
Working tunnel
Protection tunnel
NOTE
l Next Hop Address represents the port IP address of the next-hop node. In Figure 10-6, the IP addresses
under board names are port IP addresses.
l Generally, it is recommended that you set CIR(kbit/s) to No Limit. If you need to enable the CES
CAC function or limit the PW bandwidth, set this parameter to be the same as the planned tunnel
bandwidth.
Paramete Between NE31 and Between NE31 and Between NE31 and
r NE32 NE11 NE21
Parameter Between NE31 and Between NE31 and Between NE31 and
NE32 NE11 NE21
Hold-off time 0 0 0
Hold-off time 0
Hold-off time 0
Hold-off time 0
NOTE
In this example, MPLS APS is configured as the only protection scheme on the packet ring network.
Therefore, set Hold-off Time(100ms) to 0.
NOTE
The NEs in this example and in 10.4 Configuration Example (MPLS Tunnels with No Protection) are on the
same MPLS network, so the QoS planning for the NEs is the same.
QoS (DiffServ)
Differentiated service (DiffServ) configuration is essential to QoS configuration. For the OptiX
RTN 950, all the ports that transmit a service must be in the same DS domain. Therefore, DiffServ
information is planned in a unified manner. Table 10-23 lists the mapping between the DS
domain and PHB service classes.
CS7 7 56 7 -
CS6 6 48 6 -
EF 5 40 5 Real-time voice
service and
signaling
service (R99
conversational
and R99
streaming
services)
AF4 4 32 4 -
AF1 1 8 1 -
BE 0 0 0 HSDPA data
services (HSPA
interactive and
HSPA
background
services)
NOTE
During the mapping of the PHB service class, CS7 is not recommended, because CS7 may be used to transmit
Ethernet protocol packets or inband DCN packets on the NE.
The default mapping relationships for the DS domain comply with the network planning requirements and
therefore do not need to be modified. Set the type of trusted packet at an MPLS interface to MPLS EXP.
Table 10-24 lists the queue scheduling mode used by each Ethernet port involved in the service
in this example.
CS7 SP
CS6 SP
EF SP
BE SP
Procedure
Step 1 See A.6.6.1 Setting the Basic Attributes of Ethernet Ports and set the basic port attributes.
l The values for the related parameters of NE31 are provided as follows.
Parameter Value
1-EM6F-1 1-EM6F-2
l The values for the related parameters of NE32 are provided as follows.
Parameter Value
2-EM6F-1 2-EM6F-2
l The values for the related parameters of NE11 are provided as follows.
Parameter Value
2-EM6F-1 2-EM6F-2
l The values for the related parameters of NE21 are provided as follows.
Parameter Value
1-EM6F-1 1-EM6F-2
Step 2 See A.6.6.4 Setting Layer 3 Attributes of Ethernet Ports and set the Layer 3 attributes of the
ports.
l The values for the related parameters of NE31 are provided as follows.
Parameter Value
1-EM6F-1 1-EM6F-2
l The values for the related parameters of NE32 are provided as follows.
Parameter Value
2-EM6F-1 2-EM6F-2
l The values for the related parameters of NE11 are provided as follows.
Parameter Value
2-EM6F-1 2-EM6F-2
l The values for the related parameters of NE21 are provided as follows.
Parameter Value
1-EM6F-1 1-EM6F-2
----End
Procedure
Step 1 See A.9.2.1 Setting Basic MPLS Attributes and set the LSR ID for each NE.
The values for the related parameters of each NE are provided as follows.
Parameter Value
Start of Global 0 0 0 0
Label Space
Step 2 See A.9.2.3 Creating a Bidirectional MPLS Tunnel and create unidirectional MPLS tunnels.
1. Create the working MPLS tunnels.
l The values for the related parameters of NE31 are provided as follows.
Parameter Value
In Board/Logic - - -
Interface Type
In Port - - -
Forward In Label - - -
Reverse Out - - -
Label
Out Port 1 1 2
Source Node - - -
Parameter Value
l The values for the related parameters of NE32 are provided as follows.
Parameter Value
In Port 2 2
Out Port - 1
EXP None -
Parameter Value
l The values for the related parameters of NE11 are provided as follows.
Parameter Value
Tunnel ID 1503
CIR(kbit/s) No Limit
In Port 2
Out Port -
Reverse In Label -
Sink Node -
EXP None
l The values for the related parameters of NE21 are provided as follows.
Parameter Value
Tunnel ID 1505
CIR(kbit/s) No Limit
In Port 1
Out Port -
Reverse In Label -
Sink Node -
EXP None
Parameter Value
Parameter Value
In Board/Logic - - -
Interface Type
In Port - - -
Forward In Label - - -
Reverse Out - - -
Label
Out Port 2 2 1
Source Node - - -
l The values for the related parameters of NE32 are provided as follows.
Parameter Value
Parameter Value
In Port 1 2
Out Port - 1
EXP None -
l The values for the related parameters of NE11 are provided as follows.
Parameter Value
Parameter Value
In Port 1 1 2
Out Port - 2 1
EXP None - -
l The values for the related parameters of NE21 are provided as follows.
Parameter Value
In Port 2 1
Parameter Value
Out Port - 2
EXP None -
----End
Procedure
Step 1 See A.9.2.7 Setting MPLS OAM Parameters and set MPLS OAM parameters.
l The values for the related parameters of NE31 are provided as follows.
Paramet Value
er
Between NE31 and Between NE31 and Between NE31 and
NE32 NE11 NE21
Paramet Value
er
Between NE31 and Between NE31 and Between NE31 and
NE32 NE11 NE21
l The values for the related parameters of NE32 are provided as follows.
Parameter Value
l The values for the related parameters of NE11 are provided as follows.
Parameter Value
l The values for the related parameters of NE21 are provided as follows.
Step 2 See A.9.3.1 Creating an MPLS APS Protection Group and create the MPLS APS protection
group.
l The values for the related parameters of NE31 are provided as follows.
Parameter Value
WTR Time(m) 5 5 5
Hold-off Time 0 0 0
(100ms)
l The values for the related parameters of NE32 are provided as follows.
Parameter Value
WTR Time(m) 5
Hold-off Time(100ms) 0
l The values for the related parameters of NE11 are provided as follows.
Parameter Value
WTR Time(m) 5
Hold-off Time(100ms) 0
l The values for the related parameters of NE21 are provided as follows.
Parameter Value
WTR Time(m) 5
Hold-off Time(100ms) 0
Step 3 See A.9.3.4 Enabling/Disabling MPLS APS Protection and start/stop the MPLS APS protocol.
If Protocol Status is Enabled, the MPLS APS protocol is enabled for the NE where the MPLS
APS protection group is configured.
----End
Procedure
Step 1 Follow instructions in A.7.7.3 Changing the Ports Applied to a DS Domain and Their
Trusted Packet Types and change the ports that are applied to the DS domain and their trusted
packet types.
The values for the related parameters that need to be set are provided as follows.
Parameter Value
Parameter Value
Step 2 Follow instructions in A.7.7.4 Creating a Port Policy and create the port policy.
The values for the WRR scheduling policy parameters of each NE are provided as follows.
Parameter Value
Policy ID 2
The values for the port policy parameters of each NE are provided as follows.
Parameter Value
Policy ID 1
Step 3 Follow instructions in A.7.7.7 Setting the Port That Uses the Port Policy and set the ports that
use the port policy.
l The values for the related parameters of NE31 are provided as follows.
Parameter Value
Port 1-EM6F-1
1-EM6F-2
l The values for the related parameters of NE32 are provided as follows.
Parameter Value
Port 2-EM6F-1
2-EM6F-2
l The values for the related parameters of NE11 are provided as follows.
Parameter Value
Port 2-EM6F-1
2-EM6F-2
l The values for the related parameters of NE21 are provided as follows.
Parameter Value
Port 1-EM6F-1
1-EM6F-2
----End
Procedure
Step 1 For MPLS tunnels configured in an MPLS APS protection group, see A.9.2.10 Querying LSP
Running Status and query the LSP running status.
Normally, each MPLS tunnel is available.
----End
All base station services need to be transmitted through a PSN to the BSC and RNC. Based on
6.7 Configuration Example (Radio Links on the Packet Network), configure MPLS tunnels
on Packet radio links according to the following actual requirements:
l Bidirectional MPLS tunnels need to be configured between NE32 and NE33 and between
NE32 and NE34.
l MPLS APS is not configured for any tunnel on Packet radio links.
l NNI ports used on the Packet radio links are shown in Figure 10-7. The radio link between
NE32 and NE33 is configured with PLA protection.
3-ISU2-1(to NE34)
4-ISX2-1(to NE32)
6-ISX2-1(to NE32)
NE34
NE33
3-ISU2-1(to NE33)
PLA
3-ISX2-1(to NE33)
5-ISX2-1(to NE33)
GE GE
NE32
NE11 NE31
GE NE21 GE
NOTE
To fully use tunnel resources, MPLS tunnels are created only between NE33 and NE32 and between NE34 and
NE32 in this example and then MS-PW can be created by considering NE32 as the S-PE to transmit services
from NE33 and NE34 to NE31. See Figure 10-8. In actual applications, you can also create MPLS tunnels
between NE34 and NE31 and between NE33 and NE31 to transmit base station services to NE31; in addition,
you can configure MPLS APS for the MPLS tunnels.
NE34
NE33
GE GE
NE32
NE11 NE31
GE NE21 GE
Working Tunnel
Protection Tunnel
Table 10-25 to Table 10-27 provide the information about each NNI port on the Packet radio
links that are used for configuring the MPLS tunnel.
NOTE
In this example, PLA protection is configured for the radio links between NE32 and NE33. Therefore, you
need to configure IF_ETH port information only for the main radio link.
Parameter 3-ISX2-1
Parameter 3-ISX2-1
IP mask 255.255.255.252
Parameter 3-ISU2
IP mask 255.255.255.252
Basic NE configuration
Before creating an MPLS tunnel, you need to assign an LSR ID for each NE to uniquely identify
it on the network. See Table 10-28.
NOTE
The LSR ID of NE32 planned in this example is the same as that planned in 10.3 Configuration Example
(MPLS Tunnels with MPLS APS Protection).
Ingress/Egress
L: Label
Working tunnel
NOTE
The NEs in this example and the NEs in 10.3 Configuration Example (MPLS Tunnels with MPLS APS
Protection) are on the same MPLS network. Therefore, the QoS planning in this example is the same as that in
10.3 Configuration Example (MPLS Tunnels with MPLS APS Protection).
QoS (DiffServ)
Differentiated service (DiffServ) configuration is essential to QoS configuration. For the OptiX
RTN 950, all the ports that transmit a service must be in the same DS domain. Therefore, DiffServ
information is planned in a unified manner. Table 10-30 lists the mapping between the DS
domain and PHB service classes.
CS7 7 56 7 -
CS6 6 48 6 -
EF 5 40 5 Real-time voice
service and
signaling
service (R99
conversational
and R99
streaming
services)
AF4 4 32 4 -
AF1 1 8 1 -
BE 0 0 0 HSDPA data
services (HSPA
interactive and
HSPA
background
services)
NOTE
During the mapping of the PHB service class, CS7 is not recommended, because CS7 may be used to transmit
Ethernet protocol packets or inband DCN packets on the NE.
The default mapping relationships for the DS domain comply with the network planning requirements and
therefore do not need to be modified. Set the type of trusted packet at an MPLS interface to MPLS EXP.
Table 10-31 lists the queue scheduling mode used by each Ethernet port involved in the service
in this example.
CS7 SP
CS6 SP
EF SP
BE SP
Procedure
Step 1 See A.6.7.1 Setting the Basic Attributes of IF_ETH Ports and set the basic attributes of
IF_ETH ports.
l The values for the related parameters of NE32 are provided as follows.
Parameter Value
3-ISX2-1
Name conn_NE33
l The values for the related parameters of NE33 are provided as follows.
Parameter Value
3-ISU2-1 4-ISX2-1
l The values for the related parameters of NE34 are provided as follows.
Parameter Value
3-ISU2-1
Name conn_NE33
Step 2 See A.6.7.3 Setting Layer 3 Attributes of IF_ETH Ports and set the Layer 3 attributes of
IF_ETH ports.
l The values for the related parameters of NE32 are provided as follows.
Parameter Value
3-ISU2-1
IP Address 46.1.64.17
IP Mask 255.255.255.252
l The values for the related parameters of NE33 are provided as follows.
Parameter Value
3-ISU2-1 4-ISU2-1
l The values for the related parameters of NE34 are provided as follows.
Parameter Value
3-ISU2-1
IP Address 46.1.64.22
IP Mask 255.255.255.252
----End
Procedure
Step 1 See A.9.2.1 Setting Basic MPLS Attributes and set the LSR ID for each NE.
The values for the related parameters of each NE are provided as follows.
Parameter Value
Start of Global 0 0 0
Label Space
Step 2 See A.9.2.3 Creating a Bidirectional MPLS Tunnel and create unidirectional MPLS tunnels.
l The values for the related parameters of NE32 are provided as follows.
Parameter Value
In Board/Logic Interface - -
Type
In Port - -
Forward In Label - -
Out Port 1 1
Source Node - -
l The values for the related parameters of NE33 are provided as follows.
Parameter Value
Parameter Value
In Port 1 1
Out Port - 1
EXP None -
l The values for the related parameters of NE34 are provided as follows.
Parameter Value
Tunnel ID 1515
CIR(kbit/s) No Limit
In Port 1
Parameter Value
Out Port -
Reverse In Label -
Sink Node -
EXP None
----End
Procedure
Step 1 Follow instructions in A.7.7.3 Changing the Ports Applied to a DS Domain and Their
Trusted Packet Types and change the ports that are applied to the DS domain and their trusted
packet types.
The values for the related parameters that need to be set are provided as follows.
Parameter Value
Step 2 Follow instructions in A.7.7.4 Creating a Port Policy and create the port policy.
The values for the WRR scheduling policy parameters of each NE are provided as follows.
Parameter Value
Policy ID 2
The values for the port policy parameters of each NE are provided as follows.
Parameter Value
Policy ID 1
Step 3 Follow instructions in A.7.7.7 Setting the Port That Uses the Port Policy and set the ports that
use the port policy.
l The values for the related parameters of NE32 are provided as follows.
Parameter Value
Port 3-ISU2
l The values for the related parameters of NE33 are provided as follows.
Parameter Value
Port 3-ISU2
4-ISU2
l The values for the related parameters of NE34 are provided as follows.
Parameter Value
Port 3-ISU2
----End
Procedure
Step 1 If MPLS APS protection is not configured for these MPLS tunnels on the Packet radio links,
see A.9.2.7 Setting MPLS OAM Parameters to enable the MPLS OAM function to check the
tunnel status.
l The values for the related parameters of NE32 are provided as follows.
Parameter Value
l The values for the related parameters of NE33 are provided as follows.
Parameter Value
Tunnel ID 1513
l The values for the related parameters of NE34 are provided as follows.
Parameter Value
Tunnel ID 1515
Step 2 See A.9.2.10 Querying LSP Running Status and query the LSP running status.
Normally, each MPLS tunnel is available.
----End
In this example (as shown in Figure 10-10), two MPLS tunnels need to traverse the L2 network
and therefore transmit services from BTS1 and BTS2 to the BSC. The VLAN sub-interfaces of
ports for carrying the MPLS tunnels on NE1, NE2, and NE4 need to be enabled and be assigned
with VLAN IDs. When planning the VLAN IDs for the VLAN sub-interfaces, ensure that they
are different from the VLAN IDs carried by services in the L2 network so that the services carried
on the MPLS tunnels do not conflict with services in the L2 network.
The services from BTS1 and BTS2 are aggregated on the MPLS port on NE1 and then transmitted
to the BSC, so the VLAN sub-interfaces transmitting the services must have different VLAN
IDs to separate the services.
L2 network BTS1
VLAN=4060
VL NE2 NE3
BSC NE1 A N=
40
90
NE4
MPLS Tunnel 2
Figure 10-11 shows information about the MPLS ports on the network. The VLAN sub-
interfaces of ports for carrying the MPLS tunnels on NE1, NE2, and NE4 are enabled so that
the MPLS tunnels can traverse the L2 network.
3-ISU2-1(to NE3)
4-EM6T-1(to NE1)
VLAN=4060
VL NE2 NE3
NE1 AN
=4
09
0
3-ISU2-1(to NE4)
NE4
3-ISU2-1(to NE5)
NE5
4-EM6T-1(to NE1)
MPLS Tunnel 1
MPLS Tunnel 2
Table 10-32 shows the information about all MPLS ports carrying the MPLS tunnels which
traverse the L2 network.
Parameter 3-EM6T-1
IP mask - 255.255.255.252
Parameter 3-ISU2-1
Parameter 3-ISU2-1
IP mask 255.255.255.252
IP mask - 255.255.255.252
Parameter 3-ISU2-1
IP mask 255.255.255.252
Table 10-37 to Table 10-39 show the information about all VLAN sub-interfaces carrying the
MPLS tunnels which traverse the L2 network.
Parameter Value
Port 1 2
Parameter Value
Port 1
Name conn_NE1_subvlan
IP address 46.1.64.2
IP mask 255.255.255.252
Parameter Value
Port 1
Name conn_NE1_subvlan
IP address 46.1.64.12
IP mask 255.255.255.252
Basic NE Configuration
Before creating an MPLS tunnel, you need to assign an LSR ID for each NE to uniquely identify
it on the network. See Table 10-40.
Start of 0 0 0 0 0
global label
space
Based on Table 10-41, Figure 10-12 shows the specific tunnel information.
Links: NE1-NE4-NE5
Ingress/Egress
L: Label
Working tunnel
QoS (DiffServ)
Differentiated service (DiffServ) configuration is essential to QoS configuration. For the OptiX
RTN 950, all the ports that transmit a service must be in the same DS domain. Therefore, DiffServ
information is planned in a unified manner. Table 10-42 lists the mapping between the DS
domain and PHB service classes.
CS7 7 56 7 -
CS6 6 48 6 -
EF 5 40 5 Real-time voice
service and
signaling
service (R99
conversational
and R99
streaming
services)
AF4 4 32 4 -
AF1 1 8 1 -
BE 0 0 0 HSDPA data
services (HSPA
interactive and
HSPA
background
services)
NOTE
During the mapping of the PHB service class, CS7 is not recommended, because CS7 may be used to transmit
Ethernet protocol packets or inband DCN packets on the NE.
The default mapping relationships for the DS domain comply with the network planning requirements and
therefore do not need to be modified. Set the type of trusted packet at an MPLS interface to MPLS EXP.
CS7 SP
CS6 SP
EF SP
BE SP
Procedure
Step 1 Follow instructions in A.6.6.1 Setting the Basic Attributes of Ethernet Ports and set the basic
Ethernet port attributes.
l The values for the related parameters of NE1 are provided as follows.
Parameter Value
3-EM6T-1
Name conn_NE1NE2
l The values for the related parameters of NE2 are provided as follows.
Parameter Value
3-EM6T-1
Name conn_NE1
l The values for the related parameters of NE4 are provided as follows.
Parameter Value
3-EM6T-1
Name conn_NE1
Step 2 Follow instructions in A.6.7.1 Setting the Basic Attributes of IF_ETH Ports and set the basic
IF_ETH port attributes.
l The values for the related parameters of NE2 are provided as follows.
Parameter Value
3-ISU2-1
Name conn_NE3
l The values for the related parameters of NE3 are provided as follows.
Parameter Value
3-ISU2-1
Name conn_NE2
l The values for the related parameters of NE4 are provided as follows.
Parameter Value
3-ISU2-1
Name conn_NE5
l The values for the related parameters of NE5 are provided as follows.
Parameter Value
3-ISU2-1
Name conn_NE4
Step 3 Follow instructions in A.6.7.3 Setting Layer 3 Attributes of IF_ETH Ports and set the L3
IF_ETH port attributes.
l The values for the related parameters of NE2 are provided as follows.
Parameter Value
3-ISX2-1
IP Address 46.1.64.5
IP Mask 255.255.255.252
l The values for the related parameters of NE3 are provided as follows.
Parameter Value
3-ISU2-1
IP Address 46.1.64.6
IP Mask 255.255.255.252
l The values for the related parameters of NE4 are provided as follows.
Parameter Value
3-ISU2-1
IP Address 46.1.64.15
IP Mask 255.255.255.252
l The values for the related parameters of NE5 are provided as follows.
Parameter Value
3-ISU2-1
IP Address 46.1.64.16
IP Mask 255.255.255.252
----End
Procedure
Step 1 Follow instructions in A.6.10 Creating VLAN Sub-Interfaces and create VLAN sub-
interfaces.
The values for the related parameters of NE1 are provided as follows.
Parameter Value
Port 1 2
The values for the related parameters of NE2 are provided as follows.
Parameter Value
Port 1
Name conn_NE1_subvlan
Board 3-EM6T
Port 3-EM6T-1(PORT-1)
VLAN 4060
IP Address 46.1.64.2
IP Mask 255.255.255.252
The values for the related parameters of NE4 are provided as follows.
Parameter Value
Port 1
Name conn_NE1_subvlan
Board 3-EM6T
Port 3-EM6T-1(PORT-1)
VLAN 4090
IP Address 46.1.64.12
IP Mask 255.255.255.252
----End
Procedure
Step 1 Follow instructions in A.9.2.1 Setting Basic MPLS Attributes and set the basic MPLS
attributes.
The values for the related parameters of each NE are provided as follows.
Parameter Value
Start of 0 0 0 0 0
Global
Label Space
Step 2 Follow instructions in A.9.2.3 Creating a Bidirectional MPLS Tunnel and create bidirectional
MPLS tunnels.
l The values for the related parameters of NE1 are provided as follows.
Parameter Value
In Board/Logic Interface - -
Type
In Port - -
Forward In Label - -
Parameter Value
Source Node - -
LSP Mode - -
l The values for the related parameters of NE2 are provided as follows.
Parameter Value
Tunnel ID 1001
CIR(kbit/s) No limit
In Port 1(VEther-conn_NE1_subvlan)
Parameter Value
EXP None
LSP Mode -
l The values for the related parameters of NE3 are provided as follows.
Parameter Value
Tunnel ID 1001
CIR(kbit/s) No limit
In Port 1(conn_NE2-1)
Out Board/Logic -
Interface Type
Out Port -
Reverse In Label -
Sink Node -
EXP None
LSP Mode -
l The values for the related parameters of NE4 are provided as follows.
Parameter Value
Tunnel ID 1002
CIR(kbit/s) No limit
In Port 1(VEther-conn_NE1_subvlan)
EXP None
LSP Mode -
l The values for the related parameters of NE5 are provided as follows.
Parameter Value
Tunnel ID 1002
Parameter Value
CIR(kbit/s) No limit
In Port 1(conn_NE2-1)
Out Board/Logic -
Interface Type
Out Port -
Reverse In Label -
Sink Node -
EXP None
LSP Mode -
----End
Procedure
Step 1 Follow instructions in A.7.7.3 Changing the Ports Applied to a DS Domain and Their
Trusted Packet Types and change the DS-enabled ports and their trusted packet types.
Parameter Value
Step 2 Follow instructions in A.7.7.4 Creating a Port Policy and change the port policy.
The values for the WRR scheduling policy parameters of each NE are provided as follows.
Parameter Value
Policy ID 2
The values for the port policy parameters of each NE are provided as follows.
Parameter Value
Policy ID 1
Step 3 Follow instructions in A.7.7.7 Setting the Port That Uses the Port Policy and set the ports that
use the specified port policy.
l The values for the related parameters of NE1 are provided as follows.
Parameter Value
Port 3-EM6T-1
l The values for the related parameters of NE2 are provided as follows.
Parameter Value
Port 3-EM6T-1
3-ISU2-1
l The values for the related parameters of NE3 are provided as follows.
Parameter Value
Port 3-ISU2-1
l The values for the related parameters of NE4 are provided as follows.
Parameter Value
Port 3-EM6T-1
3-ISU2-1
l The values for the related parameters of NE5 are provided as follows.
Parameter Value
Port 3-ISU2-1
----End
Procedure
Step 1 If MPLS APS protection is not configured for these MPLS tunnels on the Packet radio links,
see A.9.2.7 Setting MPLS OAM Parameters to enable the MPLS OAM function to check the
tunnel status.
l The values for the related parameters of NE1 are provided as follows.
Parameter Value
l The values for the related parameters of NE2 are provided as follows.
Parameter Value
Tunnel ID 1001
l The values for the related parameters of NE3 are provided as follows.
Parameter Value
Tunnel ID 1001
l The values for the related parameters of NE4 are provided as follows.
Parameter Value
Tunnel ID 1002
l The values for the related parameters of NE5 are provided as follows.
Parameter Value
Tunnel ID 1002
Step 2 See A.9.2.10 Querying LSP Running Status and query the LSP running status.
Normally, each MPLS tunnel is available.
----End
The procedure and method of configuring PWE3 services vary with types of PWE3 services.
This section uses an ATM service carried on MS-PWs of a PSN as an example to describe how
to configure ATM services according to service planning information. In this example, services
are encapsulated in 1-to-1 VCC mode.
11.11 Configuration Example (E-Line Services Carried on PWs and Transmitting the Ethernet
Services Aggregated from the Hybrid Microwave Network)
This section considers E-Line services carried on PWs and transmitting the Ethernet services
aggregated from the Hybrid microwave network as an example to describe how to configure E-
Line services carried on PWs.
Application Example
Circuit emulation service (CES) is mainly used to transmit mobile backhauled services and
enterprise private line services. As shown in Figure 11-1, a 2G base station or an enterprise
private line connects to the OptiX RTN 950 through a TDM line. The OptiX RTN 950
encapsulates the TDM signals into packets, and then transmits the packets to the opposite end
through a PW on the PSN.
Backebone
layer IP/MPLS Backebone
Network
Convergence
BSC BSC
layer
Access
layer
Emulation Modes
The OptiX RTN 950 supports CES services in structured emulation mode and non-structured
emulation mode.
l The structured emulation mode is the CESoPSN mode. The equipment is aware of the frame
structure, framing mode, and timeslot information in the TDM circuit.
l The non-structured emulation mode is the SAToP mode. The equipment is not aware of
the frame structure. Instead, the equipment considers the TDM signals as consecutive bit
streams, and then emulates and transparently transmits the TDM signals.
As shown in Figure 11-2, the OptiX RTN 950 in CESoPSN mode supports the compression of
idle 64 kbit/s timeslots in TDM E1 signals to save transmission bandwidth.
0 1
BTS 2 3
... 2
9 30
31
PW
1 2 29 0 1 2 3 ... 29 30 31
0 1 2 3 ... 29 30 31
30 3 1
... 29 0 1 2 3 ... 29 30 31
1 2 3 PW
0 1 3 30 31
BTS
BSC
PW
0 1 2 3 ... 29 30 31 1 2 3
BTS
Service Clocks
Clock information is an important feature of TDM services. The OptiX RTN 950 supports the
retiming clocks and CES ACR clocks of CES services.
In retiming synchronization mode, the system clocks of all PEs on the network are synchronized.
The system clock of a PE is considered as the service transmit clock (retiming). As shown in
Figure 11-3, the system clock of BTS synchronizes itself with the service clock of PE. In this
manner, all PEs and CEs are synchronous, and the transmit clocks of TDM services on all CEs
and PEs are synchronous.
E1 E1
BTS PE PE BSC
CES
Clock synchronization
In ACR mode, the clock is extracted from the TDM interface on the PE on the ingress side. On
the PE on the egress side, the clock of the emulated TDM service is recovered based on the clock
information in the CES service. Figure 11-4 shows the retiming synchronization mode of CES
service clocks.
E1 E1
PE PE
BTS BSC
CES
Clock synchronization
Application Example
ATM/IMA services are mainly backhauled services of base stations. With the ATM/IMA E1
technology, the ATM services from NodeB are transmitted to the OptiX RTN 950. On the OptiX
RTN 950, PWE3 emulation is performed for the ATM services. Then, the services are
transmitted over PWs in MPLS tunnels across the PSN towards the RNC. Before being sent to
the RNC, the services are decapsulated on the OptiX PTN/RTN equipment. Figure 11-5 shows
the application example.
NodeB
RTN PTN RNC
PSN
l One-to-one VCC mapping scheme: One VCC is mapped into one PW.
l N-to-one VCC mapping scheme: N (N≤32) VCCs are mapped into one PW.
l One-to-one VPC mapping scheme: One VPC is mapped into one PW.
l N-to-one VPC mapping scheme: N (N≤32) VPCs are mapped into one PW.
l On one PW, a maximum of 31 ATM cells can be concatenated.
l ATM transparent service.
Service Models
Table 11-1 defines the PW-carried E-Line service models.
Model 3 PORT (source) UNI-NNI Layer 2 (source) IEEE 802.1q or A UNI port
PW (sink) Layer 3 (sink) QinQ (source) processes the
- (sink) received packets
based on its tag
attribute or
QinQ type field,
and then sends
the packets to
the NNI side for
transmission on
PWs.
AC PW2 AC
NE1 LSP NE2 RNC
Packet transmission
equipment
AC PW2 AC
NE1 LSP NE2 RNC
Packet transmission
equipment
On the UNI side of NE1, service 1 is received by port 1 and service 2 is received by port 2. On
the NNI side of NE1, service 1 and service 2 are transmitted separately on two PWs.
PSN
NodeB 1
AC AC
PW1
AC PW2 AC
NE1 LSP NE2 RNC
Service Model
Table 11-2 defines the PW-carried E-AGGR service models.
NOTE
a: Encapsulation Type must be set to the same value for all UNI ports in model 1.
As shown in Figure 11-9, service 1 is present between NodeB 1 and the RNC, service 2 is present
between NodeB 2 and the RNC, service 3 is present between NodeB 3 and the RNC, and service
4 is present between NodeB 4 and the RNC. The four services need to be transmitted over a
PSN. Service 1 and service 2 are aggregated at NE1. Service 3 and service 4 are aggregated at
NE2. PW1 carrying service 1 and service 2 and PW2 carrying service 3 and service 4 are
aggregated at NE3.
Service 1
Port: 1
VLAN ID: 100 Service 1
NodeB 1
AC Port: 1
Service 2 VLAN ID: 100
Port: 2 PSN Service 2
VLAN ID: 200 AC Port: 1
PW1
VLAN ID: 200
NE1 LSP1
Service 3 AC
NodeB 2
Port: 1 PW2 NE3 Service 3 RNC
VLAN ID: 300 Port: 1
LSP2 VLAN ID: 300
AC
Service 4
NodeB 3
NE2 Port: 1
AC
VLAN ID: 400
Service 4
UNI NNI NNI UNI
Port: 2
NodeB 4 VLAN ID: 400
On the UNI side of NE1, service 1 is received by port 1 and service 2 is received by port 2. On
the NNI side of NE1, service 1 and service 2 are aggregated to the same PW for transmission.
In this manner, multipoint-to-point service aggregation is implemented.
NE2 processes service 3 and service 4 in the same manner as NE1 processes service 1 and service
2.
On the NNI side of NE3, PW1 carrying service 1 and service 2 and PW2 carrying service 3 and
service 4 are aggregated. On the UNI side of NE3, the four services are sent out through port 1.
In this manner, multipoint-to-point service aggregation is implemented.
As shown in Figure 11-10, service 1 and service 2 carry the same VLAN ID. PW1 carrying
service 1 and PW2 carrying service 2 are aggregated at NE3. For isolated service transmission,
the VLAN ID of service 1 is changed from 100 to 200 on NE1.
On the UNI side of NE1, service 1 is received by port 1. On the NNI side of NE1, service 1 is
aggregated to PW1 for transmission and VLAN ID swapping. After the VLAN ID swapping,
service 1 carries a VLAN ID different from that of service 2 and is therefore isolated from service
2 during transmission.
PSN Service 1
Port: 1
AC
NodeB 1 PW1 VLAN ID: 200
NE1
LSP1
AC
NE3 Service 2 RNC
PW2
AC
Port: 1
LSP2 VLAN ID: 100
Service 2
NodeB 2 Port: 1 NE2
Service 2
VLAN ID: 100
PW: 2
UNI NNI VLAN ID: 100 NNI UNI
11.1.2 MS-PW
A PW that is carried in a PSN tunnel is called a single-segment PW (SS-PW). If a PW is carried
in multiple PSN tunnels, the PW is called a multi-segment PW (MS-PW).
NOTE
For the SS-PW network reference model, see PWE3 Network Reference Model.
Emulated service
MS-PW
PSN PSN
Native tunnel tunnel Native
service 1 2 service
CE1 CE2
PW2 PW4
AC AC
PW switching point
NOTE
PSN tunnels are available in several types, but the OptiX RTN 950 supports only MPLS tunnels. In this
document, PWE3 is based on MPLS tunnels (LSPs), unless otherwise specified.
In the preceding network reference model, T-PE1 and T-PE2 provide PWE3 services to CE1
and CE2. The PWs are carried in two PSN tunnels, and constitute the MS-PW.
The two tunnels (PSN tunnel 1 and PSN tunnel 2) that are used to carry PWs reside in different
PSN domains. PSN tunnel 1 extends from T-PE1 to S-PE1, and PSN tunnel 2 extends from S-
PE1 to T-PE2. Labels of PW1 carried in PSN tunnel 1 and PW3 carried in PSN tunnel 2 are
swapped at S-PE1. Similarly, labels of PW2 carried in PSN tunnel 1 and PW4 carried in PSN
tunnel 2 are swapped at S-PE1.
MS-PW Application
Compared with the SS-PW, the MS-PW has the following characteristics:
The following paragraphs and figures compare the application scenarios of the SS-PW and MS-
PW to show that it is easier for the MS-PW to implement segment-based protection for tunnels.
Figure 11-12 shows the SS-PW networking mode. The services between PE1 and PE2 are
transmitted on PW1 carried in MPLS tunnel 1. Both MPLS tunnel 1 and MPLS tunnel 2 are
configured with 1:1 protection. Protection, however, fails to be provided if disconnection faults
occur on different sides of the operator device (called the P device).
PW1 PW1
PE1 P PE2
PW1 PW1
MPLS tunnel 2
Packet transmission equipment
NOTE
The PWs are invisible to the P device on a PSN; the P device provides transparent transport in tunnels.
Figure 11-13 shows the MS-PW networking mode. The services between T-PE1 and T-PE2 are
transmitted on PW1 carried in MPLS tunnel 1 and PW2 carried on MPLS tunnel 2. The paired
tunnels (MPLS tunnel 1 and MPLS tunnel 3; MPLS tunnel 2 and MPLS tunnel 4) are configured
with 1:1 protection. In this configuration, protection can still be provided even when
disconnection faults occur on different sides of the S-PE1 device.
PW1 PW2
T-PE1 S-PE1 T-PE2
MPLS tunnel 3 MPLS tunnel 4
Optional
Configure UNI ports
Configure CES
services
Configure PW APS
End
NOTE
By default, CES services use the retiming mode to transmit clock. Therefore, it is unnecessary to describe
the retiming mode in this topic. If CES services need to use the CES ACR mode to transmit clock, configure
the mode according to Configuration Procedure in the OptiX RTN 950 V100R003C00 Radio Transmission
System Feature Description.
Operation Remarks
Operation Remarks
Operation Remarks
A.9.6.1 Creating CES Setting the general Required. Set the parameters as
Services attributes of services follows:
l Set Service ID(e.g.1,3-6), Service
name, Source Board, Source
Low Channel(e.g.1,3-6), and
Source 64K Timeslot(e.g.1,3-6)
according to service planning
information.
Source 64K Timeslot(e.g.1,3-6) is
valid only for the CESoPSN mode.
If the Frame Mode at the opposite
end is set to 30, the source 64 kbit/
s timeslots at the local end must
include the 16th timeslot.
l Set Priority. Priority indicates the
PHB service class for CES
services.
– The default PHB service class
for CES services is EF.
– If CES services are transmitted
on the ISU2/ISX2, set the PHB
service class to CS7 to decrease
the CES service transmission
delay and jitters.
l Set Mode to UNI-NNI.
l Set Protection Type for a PW
according to network planning
information.
l Optional.
When creating a CES service, you
can set UNI port parameters.
Operation Remarks
Operation Remarks
A.13.2 Testing E1 Services by Test CES services at each E1 port by using BER testers.
Using a BER Tester The BER testers that support Nx64 kbit/s are required
to test CES services in CESoPSN mode.
Optional
Set UNI port attributes of Set UNI port attributes of
ATM/IMA E1 services Fractional E1 services
End End
Operation Description
Operation Description
Operation Description
Operation Description
Operation Description
Operation Description
A.9.9.3 Creating an ATM Policy Required for services that are not
transparently transmitted ATM services. Set
parameters according to the type of the ATM
service access equipment.
l Set Policy ID. Alternatively, you can
select Automatically Assign so that the
policy ID is automatically assigned.
l Select or assign a value for Policy
Name.
l Set Service Type according to service
planning information.
l Set Traffic Type and corresponding
traffic parameters based on Service
Type.
l Set the enabled status of Enable Traffic
Frame Discarding Flag and UPC/NPC
according to planning information.
A.9.8.1 Creating ATM Setting service Set the basic attributes for ATM
Services attributes services. Required. Set the
parameters as follows:
l Set Service ID and Service
Name.
l Set Direction to UNIs-NNI.
l Set Connection Type.
If services are transmitted based
on VP connections, set
Connection Type to PVP. If
services are transmitted based on
VC connections, set Connection
Type to PVC. If services are
transparently transmitted over
ports, set Connection Type to
Port Transparent.
Operation Description
Operation Description
A.13.4 Testing ATM Services Use the ATM OAM function to test ATM
service connectivity.
NOTE
The OptiX RTN 950 does not support ATM OAM
tests on transparently transmitted services (PORT-
TRANS) over an ATM port. Therefore, it is
recommended that you initiate an ATM OAM test
on a CE (for example, a BTS or RNC) of a PSN so
that ATM OAM packets can be transparently
transmitted through the OptiX RTN 950 to the
opposite CE on the PSN. In this manner, an ATM
service connectivity test is implemented.
Configuration Flowchart
Figure 11-16 provides the procedure for configuring E-Line services carried by PWs on a per-
NE basis.
Optional
Configure Ethernet ports.
Configure LAGs.
Configure a PW APS
protection group.
Configure QoS.
End
Operation Description
A.6.6.1 Setting Required when Ethernet ports are used to receive and transmit Ethernet
the Basic services. Set parameters for the Ethernet ports that receive and transmit
Attributes of Ethernet services as follows:
Ethernet Ports l Set Enable Port to Enabled.
l Set Port Mode to Layer 2.
l Set Encapsulation Type to 802.1Q.
l For an Ethernet port that is connected to external equipment (BTS or
RNC), set Working Mode to the same value as that of the external
equipment (generally, the working mode of the external equipment is
auto-negotiation). For an Ethernet port within the network, set
Working Mode to Auto-Negotiation.
l When jumbo frames are transmitted, set Max Frame Length (byte)
according to the actual length of the jumbo frames. If no jumbo frame
is transmitted, it is recommended that you set Max Frame Length
(byte) to 1536.
A.6.6.2 Required when the flow control function is enabled on the external
Configuring equipment to which the Ethernet port is connected. Set the major
the Traffic parameters as follows:
Control of l When the external equipment uses the non-auto-negotiation flow
Ethernet Ports control function, set Non-Autonegotiation Flow Control Mode to
Enabled.
l When the external equipment uses the auto-negotiation flow control
function, set Auto-Negotiation Flow Control Mode to Enabled.
Operation Description
A.6.7.1 Setting Required when IF_ETH ports are used to receive and transmit Ethernet
the Basic services. Set parameters for the IF_ETH ports that receive and transmit
Attributes of Ethernet services as follows:
IF_ETH Ports l Set Port Mode to Layer 2.
l Set Encapsulation Type to 802.1Q.
Operation Description
A.7.2.1 Required if LAG protection is configured for FE/GE ports or for the
Creating a Integrated IP radio that works in N+0/XPIC mode. Set the parameters as
LAG follows:
NOTE
For ISU2/ISX2 boards, if they have been added to a PLA group during radio link
configuration, the LAG does not need to be configured.
l Set LAG Type to the same value as that at the opposite end. Generally,
set LAG Type to Static at both ends.
l For FE/GE ports, set Load Sharing to the same value as that at the
opposite end. It is recommended that you set Load Sharing to Non-
Sharing at both ends, if the LAG is configured only to provide
protection. It is recommended that you set Load Sharing to Sharing
at both ends, if the LAG is configured to increase the bandwidth.
l Set Load Sharing to Sharing at both ends, if Integrated IP radio works
in N+0/XPIC mode and uses LAG protection.
l Set Revertive Mode to the same value as that at the opposite end.
Generally, set Revertive Mode to Revertive at both ends. This
parameter is valid only to LAGs whose Load Sharing is set to Non-
Sharing.
l It is recommended that the main and slave ports take the same settings
at both ends. In this case, you can set System Priority as required. It
is recommended that this parameter take its default value. This
parameter is valid only to static LAGs.
l For an air interface LAG, to enable microwave signal degrade to trigger
LAG switching, set Switch LAG upon Air Interface SD to
Enabled.
l Set Main Board, Main Port, and Selected Standby Ports according
to the network plan. It is recommended that the main and slave ports
take the same settings at both ends.
NOTE
Set the AM attributes to the same value for the microwave ports in a LAG.
Table 11-13 Procedure for configuring UNI-NNI E-Line services carried by PWs
Operation Description
A.7.3.5 Required.
Configuring Set the major parameters of E-Line services as follows:
UNI-NNI E-
Line Services l Set Direction to UNI-NNI.
(Carried by l Set BPDU to Not Transparently transmitted.
PWs) l Set Source Interface and Source VLAN ID according to the network
planning information.
l Set Bearer Type to PW.
l It is recommended that you set Protection Type to No Protection.
Although a PW protection scheme needs to be created, it is
recommended that you create it after creating E-Line services carried
by PWs.
Set the major parameters for a PW in the General Attributes tab as
follows:
l Set PW ID according to the service planning information.
l Set PW Signaling Type to Static.
l PW Type indicates whether to add P-TAG when Ethernet frames are
encapsulated on a PW. When no request is proposed to add VLAN IDs,
set this parameter to Ethernet. When a request is proposed to add
VLAN IDs, set this parameter to Ethernet Tagged Mode. In the
Advanced Attributes tab page, set Request VLAN to be added.
l Set PW Ingress Label/Source Port and PW Egress Label/Sink
Port according to the service planning information.
l Set Tunnel Type to MPLS.
l Select the Tunnel that carries PWs according to the service planning
information.
Set the major parameters for a PW in the Advanced Attributes tab as
follows:
l The control word is not supported during ETH PWE3 packet
encapsulation on the OptiX RTN 950. Therefore, set Control Word to
No Use.
l Set Control Channel Type to Alert Label.
l Set VCCV Verification Mode to Ping.
Set the major parameters for a PW in the QoS tab as follows:
l Set Bandwidth Limit for a PW according to the service planning
information. Its default value is Disabled.
l To enable Bandwidth Limit to take effect for a PW, first configure a
maximum bandwidth for the tunnel that carries the PW.
Operation Description
Operation Description
A.7.7.2 Required.
Modifying the If the mappings that are planned between the packet priority and PHB
Mapping service classes for base stations or interconnected equipment are different
Relationships from the mappings that are configured for the default DS domain of the
for the DS OptiX RTN equipment, change the mappings of the OptiX RTN equipment
Domain to be the same as the mappings planned for the base stations or
interconnected equipment.
A.7.7.3 Required.
Changing the l If the packet priority type (namely, the trusted packet type) supported
Ports Applied by base stations or interconnected equipment is different from the
to a DS Domain trusted packet type (C-VLAN priority, by default) for the default DS
and Their domain of the OptiX RTN equipment, change the trusted packet type
Trusted Packet of the UNI port in the DS domain that receives the Ethernet service
Types packets to be the same as the trusted packet type of the base stations or
interconnected equipment.
l When transmitting the PW-carried UNI-NNI E-Line service packets,
an NNI port supports only packets with the MPLS EXP priority.
Therefore, you need to change the trusted packet type of the NNI port
in the default DS domain to MPLS EXP.
A.7.7.4 Required when you need to apply QoS policies other than DiffServ and
Creating a Port port shaping for a specific port.
Policy Set the related parameters according to the network planning information.
A.7.7.6 Required when you need to perform the CAR or shaping operation for a
Creating specific flow over the port.
Traffic Set the related parameters according to the network planning information.
Operation Description
A.7.7.8 Required if you need to limit the egress bandwidth that an Ethernet service
Configuring occupies.
Port Shaping Set the related parameters according to the network planning information.
Operation Description
A.7.8.1 Required for the NEs where the two Ethernet ports involved in the service
Creating an test are located. Set the parameters as follows:
MD l Set Maintenance Domain Name and Maintenance Domain Level to
the same values for the NEs.
l For an Ethernet service between two edge nodes on the transport
network, it is recommended that Maintenance Domain Level takes its
default value of 4. For an Ethernet service between two internal NEs
on the transport network, set Maintenance Domain Level to a value
smaller than 4. 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 of an Ethernet service between two
internal NEs on the transport network.
A.7.8.2 Required for the NEs where the two Ethernet ports involved in the service
Creating an test are located. Set the parameters as follows:
MA 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 NEs.
l Set Relevant Service to the same service for the NEs.
l It is recommended that you set CC Test Transmit Period to 1s.
Operation Description
A.7.8.3 Required for the NEs where the two Ethernet ports involved in the service
Creating test are located. Set the parameters as follows:
MEPs l Set Maintenance Association Name to the value of Maintenance
Association Name that is set in the preceding step.
l Set Board and Port to the Ethernet ports that are involved in the service
test.
l Set MP ID to different values for MEPs in the same MD.
l If the OAM information initiated by the MEP travels through the packet
switching unit on the local NE, set Direction of the MEP to Ingress.
Otherwise, set Direction to Egress.
l Set CC Status to Active, as the MEP ID is used to identify the MEP
during the LB test.
A.7.8.4 Required for the NE where the Ethernet ports involved in the OAM
Creating operation are located. Set the parameters as follows:
Remote MEPs l Set Maintenance Domain Name to the value of Maintenance
in an MA Domain Name that is set in the preceding step.
l Set Maintenance Association Name to the value of Maintenance
Association Name that is set in the preceding step.
l To ensure that an MEP can respond to the OAM operations initiated
by the other MEPs in the same MA, you need to set the other MEPs as
the remote MEPs.
Perform an LB Required.
test to test the The LB test result should show that no packet loss occurs.
Ethernet
service
configurations
Configuration Flowchart
Figure 11-17 shows the procedure for configuring PW-carried E-AGGR services.
Start
Required
Configure LAGs.
Configure a PW APS
protection group.
Configure QoS.
End
Operation Description
A.6.6.1 Setting Required when Ethernet ports are used to receive and transmit Ethernet
the Basic services. Set parameters for the Ethernet ports that receive and transmit
Attributes of Ethernet services as follows:
Ethernet Ports l Set Enable Port to Enabled.
l Set Port Mode to Layer 2.
l Set Encapsulation Type to 802.1Q.
l For an Ethernet port that is connected to external equipment (BTS or
RNC), set Working Mode to the same value as that of the external
equipment (generally, the working mode of the external equipment is
auto-negotiation). For an Ethernet port within the network, set
Working Mode to Auto-Negotiation.
l When jumbo frames are transmitted, set Max Frame Length (byte)
according to the actual length of the jumbo frames. If no jumbo frame
is transmitted, it is recommended that you set Max Frame Length
(byte) to 1536.
A.6.6.2 Required when the flow control function is enabled on the external
Configuring equipment to which the Ethernet port is connected. Set the major
the Traffic parameters as follows:
Control of l When the external equipment uses the non-auto-negotiation flow
Ethernet Ports control function, set Non-Autonegotiation Flow Control Mode to
Enabled.
l When the external equipment uses the auto-negotiation flow control
function, set Auto-Negotiation Flow Control Mode to Enabled.
Operation Description
A.6.7.1 Setting Required when IF_ETH ports are used to receive and transmit Ethernet
the Basic services. Set parameters for the IF_ETH ports that receive and transmit
Attributes of Ethernet services as follows:
IF_ETH Ports l Set Port Mode to Layer 2.
l Set Encapsulation Type to 802.1Q.
Operation Description
A.7.2.1 Required if LAG protection is configured for FE/GE ports or for the
Creating a Integrated IP radio that works in N+0/XPIC mode. Set the parameters as
LAG follows:
NOTE
For ISU2/ISX2 boards, if they have been added to a PLA group during radio link
configuration, the LAG does not need to be configured.
l Set LAG Type to the same value as that at the opposite end. Generally,
set LAG Type to Static at both ends.
l For FE/GE ports, set Load Sharing to the same value as that at the
opposite end. It is recommended that you set Load Sharing to Non-
Sharing at both ends, if the LAG is configured only to provide
protection. It is recommended that you set Load Sharing to Sharing
at both ends, if the LAG is configured to increase the bandwidth.
l Set Load Sharing to Sharing at both ends, if Integrated IP radio works
in N+0/XPIC mode and uses LAG protection.
l Set Revertive Mode to the same value as that at the opposite end.
Generally, set Revertive Mode to Revertive at both ends. This
parameter is valid only to LAGs whose Load Sharing is set to Non-
Sharing.
l It is recommended that the main and slave ports take the same settings
at both ends. In this case, you can set System Priority as required. It
is recommended that this parameter take its default value. This
parameter is valid only to static LAGs.
l For an air interface LAG, to enable microwave signal degrade to trigger
LAG switching, set Switch LAG upon Air Interface SD to
Enabled.
l Set Main Board, Main Port, and Selected Standby Ports according
to the network plan. It is recommended that the main and slave ports
take the same settings at both ends.
NOTE
Set the AM attributes to the same value for the microwave ports in a LAG.
Operation Description
A.7.3.6 Required.
Creating E- l An E-AGGR service can have more than one Source but can have only
AGGR one Sink. Configure the sources and sink for an E-AGGR service in
Services different aggregation scenarios as follows:
– For an E-AGGR service aggregating services from multiple UNI
ports to a PW, configure these UNI ports as Source and the PW as
Sink.
– For an E-AGGR service aggregating services from multiple PWs
to one UNI port, configure these PWs as Source and the UNI port
as Sink.
– Regardless of whether VLAN ID swapping is required by an E-
AGGR service, a VLAN forwarding table needs to be configured.
Configure a VLAN forwarding table according to the network plan.
– Set the other parameters according to the network plan.
l If VLAN ID swapping is required for PW-carried E-Line services,
change the E-Line services to an E-AGGR service. Configure the E-
AGGR service as follows:
– It is recommended that you configure the UNI port as Source and
the PW as Sink.
– Configure a VLAN forwarding table according to the network plan.
– Set the other parameters according to the network plan.
NOTE
On a packet switched network (PSN), if Ethernet services carried on PEs are point-
to-point services from one UNI port to a PW and require no VLAN ID swapping,
configure the Ethernet services as E-Line services carried on PWs on a per-NE basis.
Operation Description
A.7.7.2 Required.
Modifying the If the mappings that are planned between the packet priority and PHB
Mapping service classes for base stations or interconnected equipment are different
Relationships from the mappings that are configured for the default DS domain of the
for the DS OptiX RTN equipment, change the mappings of the OptiX RTN equipment
Domain to be the same as the mappings planned for the base stations or
interconnected equipment.
A.7.7.3 Required.
Changing the l If the packet priority type (namely, the trusted packet type) supported
Ports Applied by base stations or interconnected equipment is different from the
to a DS Domain trusted packet type (C-VLAN priority, by default) for the default DS
and Their domain of the OptiX RTN equipment, change the trusted packet type
Trusted Packet of the UNI port in the DS domain that receives the Ethernet service
Types packets to be the same as the trusted packet type of the base stations or
interconnected equipment.
l When transmitting the PW-carried UNI-NNI E-Line service packets,
an NNI port supports only packets with the MPLS EXP priority.
Therefore, you need to change the trusted packet type of the NNI port
in the default DS domain to MPLS EXP.
A.7.7.4 Required when you need to apply QoS policies other than DiffServ and
Creating a Port port shaping for a specific port.
Policy Set the related parameters according to the network planning information.
A.7.7.6 Required when you need to perform the CAR or shaping operation for a
Creating specific flow over the port.
Traffic Set the related parameters according to the network planning information.
A.7.7.8 Required if you need to limit the egress bandwidth that an Ethernet service
Configuring occupies.
Port Shaping Set the related parameters according to the network planning information.
Operation Description
A.7.8.1 Required for the NEs where the two Ethernet ports involved in the service
Creating an test are located. Set the parameters as follows:
MD l Set Maintenance Domain Name and Maintenance Domain Level to
the same values for the NEs.
l For an Ethernet service between two edge nodes on the transport
network, it is recommended that Maintenance Domain Level takes its
default value of 4. For an Ethernet service between two internal NEs
on the transport network, set Maintenance Domain Level to a value
smaller than 4. 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 of an Ethernet service between two
internal NEs on the transport network.
A.7.8.2 Required for the NEs where the two Ethernet ports involved in the service
Creating an test are located. Set the parameters as follows:
MA 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 NEs.
l Set Relevant Service to the same service for the NEs.
l It is recommended that you set CC Test Transmit Period to 1s.
A.7.8.3 Required for the NEs where the two Ethernet ports involved in the service
Creating test are located. Set the parameters as follows:
MEPs l Set Maintenance Association Name to the value of Maintenance
Association Name that is set in the preceding step.
l Set Board and Port to the Ethernet ports that are involved in the service
test.
l Set MP ID to different values for MEPs in the same MD.
l If the OAM information initiated by the MEP travels through the packet
switching unit on the local NE, set Direction of the MEP to Ingress.
Otherwise, set Direction to Egress.
l Set CC Status to Active, as the MEP ID is used to identify the MEP
during the LB test.
Operation Description
A.7.8.4 Required for the NE where the Ethernet ports involved in the OAM
Creating operation are located. Set the parameters as follows:
Remote MEPs l Set Maintenance Domain Name to the value of Maintenance
in an MA Domain Name that is set in the preceding step.
l Set Maintenance Association Name to the value of Maintenance
Association Name that is set in the preceding step.
l To ensure that an MEP can respond to the OAM operations initiated
by the other MEPs in the same MA, you need to set the other MEPs as
the remote MEPs.
Perform an LB Required.
test to test the The LB test result should show that no packet loss occurs.
Ethernet
service
configurations
Based on 10.3 Configuration Example (MPLS Tunnels with MPLS APS Protection),
configure CES services according to the following requirements for BTS22 shown in Figure
11-18.
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, the cross-connect loop
between PDH ports and Smart E1 ports is not required.
NOTE
l Proper port names facilitate maintenance operations. A uniform style is recommended for defining port
names.
l If customers have no requirements for transmitting services with some of the timeslots, CES services adopt
the SAToP mode and the E1 frame format always adopts the unframe mode.
Service ID 201
64 kbit/s timeslot - -
Priority EF EF
PW ID 201
Service ID 202
64 kbit/s timeslot - -
Priority EF EF
PW ID 202
NOTE
l OptiX RTN 950 supports point-to-point CES services only. That is, one PW cannot carry services from
multiple E1 ports.
l CES services can adopt the CESoPSN or SAToP mode. The SAToP mode is adopted unless otherwise
required. If customers require the CESoPSN mode, they need to specify the required 64 kbit/s timeslots.
The advanced attributes of CES services take default values on both PEs if CES services are transmitted only
on Huawei equipment. If Huawei equipment communicates CES services with third-party equipment, the
advanced attributes of CES services need to be negotiated according to the default values listed in Table
11-27. Ensure that the parameters take the same values on both PEs.
Procedure
Step 1 See A.9.6.1 Creating CES Services and create CES services.
l Parameters of NE21
The values for the related parameters that need to be set in the main interface are as follows.
Parameter NE21
Parameter NE21
Priority EF EF
The values for the related parameters that need to be set in Port Attribute are as follows.
Parameter NE21
6-ML1-1 6-ML1-2
The values for the basic PW attributes that need to be set in the PW tab are as follows.
Parameter NE21
PW ID 201 202
The values for the Advanced Attributes that need to be set in the PW tab are as follows.
Parameter NE21
l Parameters of NE31
The values for the related parameters that need to be set in the main interface are as follows.
Parameter NE31
Priority EF EF
The values for the related parameters that need to be set in Port Attribute are as follows.
Parameter NE31
2-ML1-1 6-ML1-2
The values for the basic PW attributes that need to be set in the PW tab are as follows.
Parameter NE31
PW ID 201 202
The values for the Advanced Attributes that need to be set in the PW tab are as follows.
Parameter NE31
----End
Procedure
Step 1 See A.13.2 Testing E1 Services by Using a BER Tester and test E1 services by using BER
testers.
It is recommended that you connect BER testers to NE31 and perform loopbacks on NE21.
----End
Based on 10.3 Configuration Example (MPLS Tunnels with MPLS APS Protection),
configure the CES services according to the following requirements for BTS35 and BTS36
shown in Figure 11-19.
Working tunnel
(ID=1509)
GE GE
NE32
NE11 NE31
E1
GE GE
NE21 BSC
E1
BTS36 BTS35
Parameter 4-ML1-1
NOTE
l Proper port names facilitate maintenance operations. A uniform style is recommended for defining port
names.
l In CESoPSN mode, the E1 frame format and E1 frame mode in UNI port information must be the same as
those on the access equipment. Generally, the E1 frame mode of base stations is PCM31. The E1 frame
format is double for base stations of earlier types and is CRC-4 multiframe for base stations of later types.
During deployment, the E1 frame format of base stations can be set to CRC-4 multiframe first. If the actual
E1 frame format is double, the E1 port will report the LMFA alarm.
l If CES services are converged through the Hybrid radio network, UNI port parameters need to be planned
according to the configuration of BTSs because E1 services are transmitted in Native mode on the Hybrid
radio network.
Service ID 203
Priority EF EF
PW ID 203
Service ID 204
Priority EF EF
PW ID 204
NOTE
l Fractional CES services must adopt the CESoPSN mode. Therefore, you need to know the allocation of E1
timeslots in advance.
l If the allocation of E1 timeslots is the same on the BSC side and the BTS side, as in this example, the E1
that transmits the services of BTS35 and BTS36 with the same timeslot allocation on the BSC side can be
considered a common CES service.
The advanced attributes of CES services take default values on both PEs if CES services are transmitted only
on Huawei equipment. If Huawei equipment communicates CES services with third-party equipment, the
advanced attributes of CES services need to be negotiated according to the default values listed in Table
11-33. Ensure that the parameters take the same values on both PEs.
Procedure
Step 1 See A.9.6.1 Creating CES Services and create CES services.
l Parameters of NE11
The values for the related parameters that need to be set in the main interface are as follows.
Parameter NE11
Priority EF EF
The values for the related parameters that need to be set in the Port Attributes tab page are
as follows.
Parameter NE11
4-ML1-1
Frame Mode 31
The values for the basic PW attributes that need to be set in the PW tab are as follows.
Parameter NE11
PW ID 203 204
The values for the Advanced Attributes that need to be set in the PW tab are as follows.
Parameter NE11
l Parameters of NE31
The values for the related parameters that need to be set in the main interface are as follows.
Parameter NE31
Priority EF EF
Parameter NE31
The values for the related parameters that need to be set in Port Attributes are as follows.
Parameter NE31
2-ML1-3 2-ML1-4
Frame Mode 31 31
The values for the basic PW attributes that need to be set in the PW tab are as follows.
Parameter NE31
PW ID 203 204
The values for the Advanced Attributes that need to be set in the PW tab are as follows.
Parameter NE31
----End
Procedure
Step 1 See A.13.2 Testing E1 Services by Using a BER Tester and test E1 services by using BER
testers.
l Because the CES services under test adopt the CESoPSN mode, BER testers must be used
for testing nx64 kbit/s services according to timeslot allocation.
l It is recommended that you connect BER testers to NE31 and perform loopbacks on NE11.
The test results should be no bit errors.
----End
Based on 10.4 Configuration Example (MPLS Tunnels with No Protection), configure CES
services according to the following requirements for BTS32 shown in 10.3 Configuration
Example (MPLS Tunnels with MPLS APS Protection).
NE31 E1
NE11
GE GE
NE21
BSC
Parameter 2-ML1-1
Parameter 2-ML1-1
Parameter 2-ML1-5
NOTE
l Proper port names facilitate maintenance operations. A uniform style is recommended for defining port
names.
l In CESoPSN mode, the E1 frame format and E1 frame mode in UNI port information must be the same as
those on the access equipment. Generally, the E1 frame mode of base stations is PCM31. The E1 frame
format is double for base stations of earlier types and is CRC-4 multiframe for base stations of later types.
During deployment, the E1 frame format of base stations can be set to CRC-4 multiframe first. If the actual
E1 frame format is double, the E1 port will report the LMFA alarm.
l If CES services are converged through the Hybrid radio network, UNI port parameters need to be planned
according to the configuration of BTSs because E1 services are transmitted in Native mode on the Hybrid
radio network.
PW ID 205 206
NOTE
l OptiX RTN 950 supports point-to-point CES services only. That is, one PW cannot carry services from
multiple E1 ports.
l CES services can adopt the CESoPSN or SAToP mode. The SAToP mode is adopted unless otherwise
required. If customers require the CESoPSN mode, they need to specify the required 64 kbit/s timeslots. In
this example, the CESoPSN mode is adopted because the allocation of 64 kbit/s timeslots is specified, PWs
are carried on radio links, and the radio bandwidth is better utilized.
l The default PHB service class for CES services is EF. If CES services are transmitted on the ISU2/ISX2,
set the PHB service class to CS7 to decrease the CES service transmission delay and jitters.
l If an MS-PW is used, the label values of the first segment and the last segment must be different.
The advanced attributes of CES services take default values on both PEs if CES services are transmitted only
on Huawei equipment. If Huawei equipment communicates CES services with third-party equipment, the
advanced attributes of CES services need to be negotiated according to the default values listed in Table
11-38. Ensure that the parameters take the same values on both PEs.
Procedure
Step 1 See A.9.6.1 Creating CES Services and create CES services.
l Parameters of NE33
The values for the related parameters that need to be set in the main interface are as follows.
Parameter NE33
Mode UNI-NNI
Priority CS7
PW Type CESoPSN
The values for the related parameters that need to be set in the Port Attributes tab page are
as follows.
Parameter NE33
2-ML1-1
Frame Mode 31
The values for the basic PW attributes that need to be set in the PW tab are as follows.
Parameter NE33
PW ID 205
The values for the Advanced Attributes that need to be set in the PW tab are as follows.
Parameter NE33
l Parameters of NE31
The values for the related parameters that need to be set in the main interface are as follows.
Parameter NE31
Mode UNI-NNI
Parameter NE31
Priority CS7
PW Type CESoPSN
The values for the related parameters that need to be set in the Port Attributes tab page are
as follows.
Parameter NE31
2-ML1-1
Frame Mode 31
The values for the basic PW attributes that need to be set in the PW tab are as follows.
Parameter NE31
PW ID 206
The values for the Advanced Attributes that need to be set in the PW tab are as follows.
Parameter NE31
The values for the related parameters that need to be set in the main interface are as follows.
Parameter NE32
ID 901
Name bts32_ces_service_mspw
Parameter NE32
PW ID 205 206
The values for related parameters that need to be set in Advanced Attributes are as follows.
The other parameters take their default values.
Parameter NE32
----End
Procedure
Step 1 See A.13.2 Testing E1 Services by Using a BER Tester and test E1 services by using BER
testers.
l Because the CES services under test adopt the CESoPSN mode, BER testers must be used
for testing nx64 kbit/s services according to timeslot allocation.
l It is recommended that you connect BER testers to NE31 and perform loopbacks on NE11.
The test results should be no bit errors.
----End
Based on 10.3 Configuration Example (MPLS Tunnels with MPLS APS Protection),
configure information about ATM services transmitted from BTS13 and BTS14 according to
the following network planning information (as shown in Figure 11-21):
l Each BTS has real-time voice services, signaling services (CBR services), HSDPA data
services (UBR services), OM and HSDPA real-time services (rt-VBR services), and R99
non-real-time services (nrt-VBR services).
Working tunnel
(ID=1503)
GE GE
NE32
E1
NE11 NE31
Hybrid radio chain RNC
network GE
NE21 GE
E1 E1 E1 loo p
R99
BTS13 R99
BTS14
NOTE
If E1 services are received directly from Smart E1 ports, you need not connect the Smart E1 ports with
corresponding PDH ports with E1 cables.
11.6.2 ServicePlanning
You need to plan the corresponding parameter information before service configuration.
Table 11-40 and Table 11-41 provide planning information about UNI ports.
NOTE
l Appropriate port names facilitate future maintenance. It is recommended that you name ports on the
entire network in a unified manner.
l As specified in ITU-T G.804, ATM service ports use the CRC-4 multiframe format and PCM30 frame
mode by default. The E1 frame format and frame mode must be the same as those at the opposite end.
l ATM services are converged from a Hybrid radio chain network. On the Hybrid radio chain network,
E1 services are transmitted in Native E1 mode. Therefore, set the information about the UNI ports
based on BTS configurations.
Minimum - 1
number of
activated links
Differential - 25
delay tolerance
NOTE
l If carried over a single E1, ATM services from a BTS are generally transmitted and received through
a single UNI port. In this case, the IMA protocol needs to be disabled. If carried over multiple E1s,
ATM services from a BTS are transmitted and received through IMA trunks.
l Normally, set the IMA protocol version, IMA frame length, IMA symmetric mode, and differentiated
delay tolerance of an NE (with IMA protocol enabled) to the same values as those of its interconnected
equipment. Normally, the BTS/RNC configurations are as follows:
l IMA protocol version: 1.1
l IMA frame length: 128
l IMA symmetric mode: symmetrical mode and symmetrical operation
l The differentiated delay tolerance: 25
l The clock modes must be the same at both ends of an IMA trunk. The default clock mode for a BTS
is ITC. Therefore, the clock mode is set to ITC for the NE that is interconnected with the BTS and the
NE at the opposite end of the IMA link.
Mapping Information Between ATM Service Types and ATM Service Classes
Table 11-44 provides the mapping information between ATM service types and the ATM
service classes.
Table 11-44 Mapping information between ATM service types and the ATM service classes
CBR EF
rt-VBR AF3
nrt-VBR AF2
UBR BE
This mapping table is consistent with "DefaultAtmCosMap". Therefore, you can use the default
CoS mapping table during service configuration.
NE11 uses one E1 to receive and transmit BTS13 services and use four E1s to receive and
transmit BTS14 services. Both BTS13 services and BTS14 services contain CBR, UBR, rt-VBR,
and ntr-VBR services. An ATM policy needs to be configured for each type of service; therefore,
up to eight ATM policies need to be configured on NE11. Eight ATM policies also need to be
configured on NE31.
Policy ID 1 2 3 4
Clp0Pcr(cell/s) - - - -
Clp0Scr(cell/s) - - - -
Clp01Mcr(cell/ - - - -
s)
Policy ID 5 6 7 8
Clp0Pcr(cell/s) - - - -
Clp0Scr(cell/s) - - - -
Clp01Mcr(cell/ - - - -
s)
Table 11-47 Service information (ATM services from BTS13 and BTS14)
Service bts13_bts14_atmservice
name
Service 101
ID
Service UNIs-NNI
type
Connect PVC
ion type
Protecti No protection
on type
Service 4-ML1
board
Source 13 13 13 13 14 14 14 14
VPI
Source 33 34 35 36 33 34 35 36
VCI
Sink 13 13 13 13 14 14 14 14
VPI
Sink 33 34 35 36 33 34 35 36
VCI
Upstrea 1 2 3 4 5 6 7 8
m QoS (1e1_cbr (1e1_rt (1e1_n (1e1_u (4e1_c (4e1_rt (4e1_n (4e1_u
Policy ) vbr) rtvbr) br) br) vbr) rtvbr) br)
Downst 1 2 3 4 5 6 7 8
ream (1e1_cbr (1e1_rt (1e1_n (1e1_u (4e1_c (4e1_rt (4e1_n (4e1_u
QoS ) vbr) rtvbr) br) br) vbr) rtvbr) br)
policy
Service 2-ML1
board
Service TRUNK1
port
Source 13 13 13 13 14 14 14 14
VPI
Source 33 34 35 36 33 34 35 36
VCI
Sink 13 13 13 13 14 14 14 14
VPI
Sink 33 34 35 36 33 34 35 36
VCI
Upstrea 1 2 3 4 5 6 7 8
m QoS (1e1_cbr (1e1_rt (1e1_n (1e1_u (4e1_c (4e1_rt (4e1_n (4e1_u
policy ) vbr) rtvbr) br) br) vbr) rtvbr) br)
Downst 1 2 3 4 5 6 7 8
ream (1e1_cbr (1e1_rt (1e1_n (1e1_u (4e1_c (4e1_rt (4e1_n (4e1_u
QoS ) vbr) rtvbr) br) br) vbr) rtvbr) br)
policy
PW information
PW ID 101
PW 101/101
ingress/
egress
label
Tunnel 1503
Control No Use
Word
VCCV Ping
Verifica
tion
Mode
CoS DefaultAtmCosMap
mappin
g
Procedure
Step 1 See A.6.4.1 Setting Basic Attributes of Smart E1 Ports and set the general attributes of Smart
E1 ports.
l The values for the related parameters of NE11 are provided as follows.
Parameter NE11
l The values for the related parameters of NE31 are provided as follows.
Parameter NE31
2-ML1-6 to 2-ML1-13
Step 2 See A.6.4.2 Setting Advanced Attributes of Smart E1 Ports and set the advanced attributes
of Smart E1 ports.
l The values for the related parameters of NE11 are provided as follows.
Parameter NE11
Frame Mode 30 30
l The values for the related parameters of NE31 are provided as follows.
Parameter NE31
2-ML1-6 to 2-ML1-13
Frame Mode 30
----End
Procedure
Step 1 See A.9.7.1 Binding ATM TRUNKs and bind the ATM trunk.
l The values for the related parameters for NE11 are provided as follows.
Parameter NE11
Level E1 E1
l The values for the related parameters for NE31 are provided as follows.
Parameter NE31
Level E1
Step 2 See A.9.7.2 Configuring an IMA group and create an IMA group.
l The values for the related parameters of NE11 are provided as follows.
Parameter NE11
l The values for the related parameters of NE31 are provided as follows.
Parameter NE31
Step 3 See A.9.7.3 Setting ATM Port Parameters and set ATM port parameters.
l The values for the related parameters of NE11 are provided as follows.
Parameter NE11
l The values for the related parameters of NE31 are provided as follows.
Parameter NE31
Name conn_rnc_trunk1
----End
Procedure
Step 1 See A.9.9.3 Creating an ATM Policy and create ATM policies.
Policy ID 1 2 3 4
Policy ID 5 6 7 8
----End
Procedure
Step 1 See A.9.8.1 Creating ATM Services and create ATM services.
l Parameters of NE11:
The values for the related parameters that need to be set in the main interface are as follows.
Parameter NE11
Service ID 101
Direction UNIs-NNI
Connection PVC
Type
The values for the related parameters that need to be set in the Configure Connection tab
page are provided as follows.
Param NE11
eter
ATM Services from BTS13 and BTS14
Source 4- 4- 4- 4- 4- 4- 4- 4-
Port ML1-1 ML1-1 ML1-1 ML1-1 ML1-2 ML1-2 ML1-2 ML1-2
(TRU (TRU (TRU (TRU (TRU (TRU (TRU (TRU
NK1) NK1) NK1) NK1) NK2) NK2) NK2) NK2)
Source 4- 4- 4- 4- 4- 4- 4- 4-
Bind ML1- ML1- ML1- ML1- ML1- ML1- ML1- ML1-
Path (2) (2) (2) (2) (3-6) (3-6) (3-6) (3-6)
Source 13 13 13 13 14 14 14 14
VPI
(eg.
35,36-
39)
Source 33 34 35 36 33 34 35 36
VCI
(eg.
35,36-
39)
Sink 13 13 13 13 14 14 14 14
VPI
(eg.
35,36-
39)
Sink 33 34 35 36 33 34 35 36
VCI
(eg.
35,36-
39)
Uplink 1 2 3 4 5 6 7 8
Policy
Down 1 2 3 4 5 6 7 8
link
Policy
In the Configure PW dialog box, the values for the related parameters that need to be set in
the General Attributes tab page are provided as follows.
Parameter NE11
PW ID 101
PW Signaling Static
Type
PW Incoming 101
Label
PW Outgoing 101
Label
In the Configure PW dialog box, the values for the related parameters that need to be set in
the Advanced Attributes tab page are provided as follows.
Parameter NE11
VCCV Ping
Verification
Mode
The values for the related parameters that need to be set in the CoS Mapping tab page are
provided as follows.
Parameter NE11
PW ID 101
l Parameters of NE31:
The values for the related parameters that need to be set in the main interface are as follows.
Parameter NE31
Service ID 101
Direction UNIs-NNI
Connection PVC
Type
The values for the related parameters that need to be set in the Configure Connection tab
page are provided as follows.
Param NE31
eter
ATM Services from BTS13 and BTS14
Source 2- 2- 2- 2- 2- 2- 2- 2-
Port ML1-1 ML1-1 ML1-1 ML1-1 ML1-1 ML1-1 ML1-1 ML1-1
(TRU (TRU (TRU (TRU (TRU (TRU (TRU (TRU
NK1) NK1) NK1) NK1) NK1) NK1) NK1) NK1)
Source 2- 2- 2- 2- 2- 2- 2- 2-
Bind ML1- ML1- ML1- ML1- ML1- ML1- ML1- ML1-
Path (6-13) (6-13) (6-13) (6-13) (6-13) (6-13) (6-13) (6-13)
Source 13 13 13 13 14 14 14 14
VPI
(eg.
35,36-
39)
Source 33 34 35 36 33 34 35 36
VCI
(eg.
35,36-
39)
Param NE31
eter
ATM Services from BTS13 and BTS14
Sink 13 13 13 13 14 14 14 14
VPI
(eg.
35,36-
39)
Sink 33 34 35 36 33 34 35 36
VCI
(eg.
35,36-
39)
Uplink 1 2 3 4 5 6 7 8
Policy
Down 1 2 3 4 5 6 7 8
link
Policy
In the Configure PW dialog box, the values for the relevant parameters that need to be set
in the General Attributes tab page are provided as follows.
Parameter NE31
PW ID 101
PW Signaling Static
Type
PW Incoming 101
Label
PW Outgoing 101
Label
In the Configure PW dialog box, the values for the related parameters that need to be set in
the Advanced Attributes tab page are provided as follows.
Parameter NE31
VCCV Ping
Verification
Mode
The values for the related parameters that need to be set in the CoS Mapping tab page are
provided as follows.
Parameter NE31
PW ID 101
----End
Procedure
Step 1 See A.13.4 Testing ATM Services and verify the ATM service configurations.
The "success" verification result should be displayed.
----End
GE GE
NE32
NE31 E1
NE11
GE NE21 GE
l RNC
nne
tu )
g 5
k i n 1 50
E1 or =
W (ID
R99 R99
BTS37 BTS38
11.7.2 ServicePlanning
You need to plan the corresponding parameter information before service configuration.
Parameter 6-ML1-3
A UNI port that transmits the fractional ATM service is described as a serial port.Table 11-50
provides the planning information about serial ports.
Paramete Serial Port Where BTS37 Services Serial Port Where BTS38 Services
r Are Located Are Located
NOTE
l Appropriate port names facilitate future maintenance. It is recommended that you name ports on the
entire network in a unified manner.
l The E1 frame format and frame mode must be the same as those of service access equipment.
l For an E1 port that transmits Fractional ATM services, set the E1 frame mode to PCM31.
IMA protocol - -
version
IMA frame - -
length
IMA symmetric - -
mode
Differentiated - -
delay tolerance
Clock mode - -
Differentiated delay 25
tolerance
NOTE
l If one E1 is divided into several timeslots to transmit ATM services from BTSs, the Fractional ATM
mode is used and the IMA protocol is disabled in most cases.
l Normally, set the IMA protocol version, IMA frame length, IMA symmetric mode, and differentiated
delay tolerance of an NE (with IMA protocol enabled) to the same values as those of its interconnected
equipment. Normally, the BTS/RNC configurations are as follows:
l IMA protocol version: 1.1
l IMA frame length: 128
l IMA symmetric mode: symmetrical mode and symmetrical operation
l The differentiated delay tolerance: 25
l The clock modes must be the same at both ends of an IMA trunk. The default clock mode for a BTS
is ITC. Therefore, the clock mode is set to ITC for the NE that is interconnected with the BTS and the
NE at the opposite end of the IMA link.
Mapping Information Between ATM Service Types and ATM Service Classes
Table 11-54 provides the mapping information between ATM service types and the ATM
service classes.
Table 11-54 Mapping information between ATM service types and the ATM service classes
CBR EF
rt-VBR AF3
nrt-VBR AF2
UBR BE
This mapping table is consistent with "DefaultAtmCosMap". Therefore, you can use the default
CoS mapping table during service configuration.
Table 11-55 shows the planning information about the ATM policy.
Policy ID 9 10 11 12
Clp0Pcr (cell/s) - - - -
Clp0Scr (cell/s) - - - -
Clp01Mcr (cell/ - - - -
s)
Table 11-56 Service information (ATM services from BTS37 and BTS38)
Service bts37_bts38_fracatmservice
name
Service 102
ID
Service UNIs-NNI
type
Connect PVC
ion type
Protecti No protection
on type
Source NE21
NE
Service 6-ML1
board
Source 37 37 37 37 38 38 38 38
VPI
Source 33 34 35 36 33 34 35 36
VCI
Sink 37 37 37 37 38 38 38 38
VPI
Sink 33 34 35 36 33 34 35 36
VCI
Upstrea 9 10 11 12 9 10 11 12
m QoS
policy
Downstr 9 10 11 12 9 10 11 12
eam
QoS
policy
Service 2-ML1
board
Source 37 37 37 37 38 38 38 38
VPI
Source 33 34 35 36 33 34 35 36
VCI
Sink 37 37 37 37 38 38 38 38
VPI
Sink 33 34 35 36 33 34 35 36
VCI
Upstrea 9 10 11 12 9 10 11 12
m QoS
policy
Downstr 9 10 11 12 9 10 11 12
eam
QoS
policy
PW information
PW ID 102
PW 102/102
ingress/
egress
label
Tunnel 1505
Control No Use
Word
VCCV Ping
Verifica
tion
Mode
CoS DefaultAtmCosMap
mappin
g
Procedure
Step 1 See A.6.4.1 Setting Basic Attributes of Smart E1 Ports and set the general attributes of Smart
E1 ports.
l The values for the related parameters of NE21 are provided as follows.
Parameter NE21
6-ML1-3
Name conn_bts37_bts38_frac
l The values for the related parameters of NE31 are provided as follows.
Parameter NE31
2-ML1-6 to 2-ML1-13
Step 2 See A.6.4.2 Setting Advanced Attributes of Smart E1 Ports and set the advanced attributes
of Smart E1 ports.
l The values for the related parameters of NE21 are provided as follows.
Parameter Value
6-ML1-3
Frame Mode 31
l The values for the related parameters of NE31 are provided as follows.
Parameter NE31
2-ML1-6 to 2-ML1-13
Frame Mode 30
Step 3 See A.6.5.1 Creating Serial Ports and configure serial ports on NE21.
The values for the serial port parameters are provided as follows.
Parameter NE21
Port 1 2
Step 4 See A.6.5.2 Setting Basic Attributes of Serial Ports and set the basic attributes of serial ports
on NE21.
The values for basic attributes of serial ports that need to be set are as follows.
Parameter NE21
conn_bts37_sp01 conn_bts38_sp02
----End
Procedure
Step 1 See A.9.7.1 Binding ATM TRUNKs and bind the ATM trunk.
l The values for the related parameters of NE21 are provided as follows.
Parameter Value
Parameter Value
l The values for the related parameters for NE31 are provided as follows.
Parameter NE31
Level E1
Step 2 See A.9.7.2 Configuring an IMA group and create an IMA group.
l The values for the IMA group parameters of NE21 are provided as follows.
Parameter NE21
l The values for the related parameters of NE31 are provided as follows.
Parameter NE31
Parameter NE31
Step 3 See A.9.7.3 Setting ATM Port Parameters and set the ATM port parameters.
l The values for the ATM port parameters of NE21 are provided as follows.
Parameter NE21
l The values for the related parameters of NE31 are provided as follows.
Parameter NE31
Name conn_rnc_trunk1
----End
Procedure
Step 1 See A.9.9.3 Creating an ATM Policy and create the ATM policy.
The values for the related parameters of NE21 and NE31 are provided as follows.
Policy ID 9 10 11 12
----End
Procedure
Step 1 See A.9.8.1 Creating ATM Services and create ATM services.
l Parameters of NE21:
The values for the related parameters that need to be set in the main interface are as follows.
Parameter NE21
Service ID 102
Direction UNIs-NNI
Connection PVC
Type
The values for the related parameters that need to be set in the Configure Connection tab
page are provided as follows.
Param NE21
eter
ATM Services from BTS37 and BTS38
Source 6- 6- 6- 6- 6- 6- 6- 6-
Port ML1-1 ML1-1 ML1-1 ML1-1 ML1-2 ML1-2 ML1-2 ML1-2
(TRU (TRUN (TRU (TRU (TRU (TRUN (TRU (TRU
NK1) K1) NK1) NK1) NK2) K2) NK2) NK2)
Source 6- 6- 6- 6- 6- 6- 6- 6-
Bind ML1- ML1- ML1- ML1- ML1- ML1- ML1- ML1-
Path (1) (1) (1) (1) (2) (2) (2) (2)
Source 37 37 37 37 38 38 38 38
VPI
(eg.
35,36-
39)
Source 33 34 35 36 33 34 35 36
VCI
(eg.
35,36-
39)
Param NE21
eter
ATM Services from BTS37 and BTS38
Sink 37 37 37 37 38 38 38 38
VPI
(eg.
35,36-
39)
Sink 33 34 35 36 33 34 35 36
VCI
(eg.
35,36-
39)
Uplin 9 10 11 12 9 10 11 12
k
Policy
Down 9 10 11 12 9 10 11 12
link
Policy
In the Configure PW dialog box, the values for the relevant parameters that need to be set
in the General Attributes tab page are provided as follows.
Param NE21
eter
ATM Services from BTS37 and BTS38
PW ID 102
PW Static
Signali
ng
Type
PW 102
Incom
ing
Label
PW 102
Outgoi
ng
Label
Param NE21
eter
ATM Services from BTS37 and BTS38
Ingres 1505
s
Tunne
l
In the Configure PW dialog box, the values for the related parameters that need to be set in
the Advanced Attributes tab page are provided as follows.
Parameter NE21
VCCV Ping
Verification
Mode
The values for the relevant parameters that need to be set in the CoS Mapping tab page are
provided as follows.
Param NE21
eter
ATM Services from BTS37 and BTS38
PW ID 102
CoS DefaultAtmCosMap
Mappi
ng
l Parameters of NE31:
The values for the related parameters that need to be set in the main interface are as follows.
Parameter NE31
Service ID 102
Direction UNIs-NNI
Parameter NE31
Connection PVC
Type
The values for the related parameters that need to be set in the Configure Connection tab
page are provided as follows.
Param NE31
eter
ATM Services from BTS37 and BTS38
Source 2- 2- 2- 2- 2- 2- 2- 2-
Port ML1-1 ML1-1 ML1-1 ML1-1 ML1-1 ML1-1 ML1-1 ML1-1
(TRU (TRU (TRU (TRU (TRU (TRU (TRU (TRU
NK1) NK1) NK1) NK1) NK1) NK1) NK1) NK1)
Source 2- 2- 2- 2- 2- 2- 2- 2-
Bind ML1- ML1- ML1- ML1- ML1- ML1- ML1- ML1-
Path (6-13) (6-13) (6-13) (6-13) (6-13) (6-13) (6-13) (6-13)
Source 37 37 37 37 38 38 38 38
VPI
(eg.
35,36-
39)
Source 33 34 35 36 33 34 35 36
VCI
(eg.
35,36-
39)
Sink 37 37 37 37 38 38 38 38
VPI
(eg.
35,36-
39)
Param NE31
eter
ATM Services from BTS37 and BTS38
Sink 33 34 35 36 33 34 35 36
VCI
(eg.
35,36-
39)
Uplink 9 10 11 12 9 10 11 12
Policy
Down 9 10 11 12 9 10 11 12
link
Policy
In the Configure PW dialog box, the values for the relevant parameters that need to be set
in the General Attributes tab page are provided as follows.
Param NE31
eter
ATM Services from BTS37 and BTS38
PW ID 102
PW Static
Signali
ng
Type
PW 102
Incom
ing
Label
PW 102
Outgoi
ng
Label
Ingres 1505
s
Tunne
l
In the Configure PW dialog box, the values for the related parameters that need to be set in
the Advanced Attributes tab page are provided as follows.
Parameter NE31
VCCV Ping
Verification
Mode
The values for the relevant parameters that need to be set in the CoS Mapping tab page are
provided as follows.
Param NE31
eter
ATM Services from BTS37 and BTS38
PW ID 102
CoS DefaultAtmCosMap
Mappi
ng
----End
Procedure
Step 1 See A.13.4 Testing ATM Services and verify the ATM service configurations.
The verification result should be "success".
----End
about ATM services transmitted from BTS34 according to the following network planning
information (as shown in Figure 11-23):
Wo
rki n
(ID g tu n
NE34 =1 5 n
1 5) el
W
or
ki
E1 NE33 ID ng t
=1 u n
R99 50 ne
1 l
BTS34 GE GE
NE32
E1
NE11 NE31
GE GE
NE21 RNC
11.8.2 ServicePlanning
You need to plan the corresponding parameter information before service configuration.
Table 11-58 and Table 11-59 provide planning information about UNI ports.
Differentiated delay 25
tolerance
Differentiated delay 25
tolerance
NOTE
l If carried over a single E1, ATM services from a NodeB are transmitted and received through UNI
ports. In this case, the IMA protocol needs to be disabled. If carried over multiple E1s, ATM services
from a NodeB are transmitted and received through IMA trunks.
l Normally, set the IMA protocol version, IMA frame length, IMA symmetric mode, and differentiated
delay tolerance of an NE (with IMA protocol enabled) to the same values as those of its interconnected
equipment. Normally, the BTS/RNC configurations are as follows:
l IMA protocol version: 1.1
l IMA frame length: 128
l IMA symmetric mode: symmetrical mode and symmetrical operation
l The differentiated delay tolerance: 25
l The clock modes must be the same at both ends of an IMA trunk. The default clock mode for a BTS
is ITC. Therefore, the clock mode is set to ITC for the NE that is interconnected with the BTS and the
NE at the opposite end of the IMA link.
Mapping Information Between ATM Service Types and ATM Service Classes
Table 11-62 provides the mapping information between ATM service types and the ATM
service classes.
Table 11-62 Mapping information between ATM service types and the ATM service classes
CBR EF
rt-VBR AF3
nrt-VBR AF2
UBR BE
This mapping table is consistent with "DefaultAtmCosMap". Therefore, you can use the default
CoS mapping table during service configuration.
Policy ID 5 6 7 8
Clp0Pcr (cell/s) - - - -
Clp0Scr (cell/s) - - - -
Clp01Mcr (cell/ - - - -
s)
Source VPI 34
Source VCI 33
Sink VPI 34
Sink VCI 33
Source VPI 34
Source VCI 33
Sink VPI 34
Sink VCI 33
PW information
PW ID 103 104
Source VPI 34
Source VCI 34
Sink VPI 34
Sink VCI 34
Source VPI 34
Source VCI 34
Sink VPI 34
Sink VCI 34
PW information
PW ID 105 106
Source VPI 34
Source VCI 35
Sink VPI 34
Sink VCI 35
Source VPI 34
Source VCI 35
Sink VPI 34
Sink VCI 35
PW information
PW ID 107 108
Source VPI 34
Source VCI 36
Sink VPI 34
Sink VCI 36
Source VPI 34
Source VCI 36
Sink VPI 34
Sink VCI 36
PW information
PW ID 109 110
Procedure
Step 1 See A.6.4.1 Setting Basic Attributes of Smart E1 Ports and set general attributes of Smart E1
ports.
l The values for the related parameters of NE34 are provided as follows.
Parameter NE34
2-ML1-1 to 2-ML1-4
l The values for the related parameters of NE31 are provided as follows.
Parameter NE31
2-ML1-6 to 2-ML1-13
Step 2 See A.6.4.2 Setting Advanced Attributes of Smart E1 Ports and set advanced attributes of
Smart E1 ports.
l The values for the related parameters of NE34 are provided as follows.
Parameter NE34
2-ML1-1 to 2-ML1-4
Frame Mode 30
l The values for the related parameters of NE31 are provided as follows.
Parameter NE31
2-ML1-6 to 2-ML1-13
Frame Mode 30
----End
Procedure
Step 1 See A.9.7.1 Binding ATM TRUNKs and bind ATM trunks.
l The values for the related parameters of NE34 are provided as follows.
Parameter NE34
Level E1
l The values for the related parameters for NE31 are provided as follows.
Parameter NE31
Level E1
Step 2 See A.9.7.2 Configuring an IMA group and configure an IMA group.
l The values for the related parameters of NE34 are provided as follows.
Parameter NE34
l The values for the related parameters of NE31 are provided as follows.
Parameter NE31
Step 3 See A.9.7.3 Setting ATM Port Parameters and set ATM port parameters.
l The values for the related parameters of NE34 are provided as follows.
Parameter NE34
Name conn_bts34_trunk1
l The values for the related parameters of NE31 are provided as follows.
Parameter NE31
Name conn_rnc_trunk1
----End
Procedure
Step 1 See A.9.9.3 Creating an ATM Policy and create ATM policies.
The values for the related parameters of NE34 and NE31 are provided as follows,
Policy ID 5 6 7 8
----End
Procedure
Step 1 See A.9.8.1 Creating ATM Services and create ATM services.
l Parameters of NE34:
The values for the related parameters that need to be set in the main interface are as follows.
Pa NE34
ra
m CBR Services rt-VBR Services nrt-VBR UBR Services
ete from BTS34 from BTS34 Services from from BTS34
r BTS34
The values for the related parameters that need to be set in the Configure Connection tab
page are provided as follows.
Parameter NE34
Parameter NE34
Source VPI 34 34 34 34
(eg.35,36-39)
Source VCI 33 34 35 36
(eg.35,36-39)
Sink VPI(eg. 34 34 34 34
35,36-39)
Sink VCI(eg. 33 34 35 36
35,36-39)
Uplink Policy 5 6 7 8
Down link 5 6 7 8
Policy
In the Configure PW dialog box, the values for the relevant parameters that need to be set
in the General Attributes tab page are provided as follows.
Parameter NE34
In the Configure PW dialog box, the values for the related parameters that need to be set in
the Advanced Attributes tab page are provided as follows.
Parameter NE34
Control Word Must use Must use Must use Must use
Control CW CW CW CW
Channel Type
The values for the relevant parameters that need to be set in the CoS Mapping tab page are
provided as follows.
Parameter NE34
l Parameters of NE31:
The values for the related parameters that need to be set in the main interface are as follows.
Parameter NE31
The values for the related parameters that need to be set in the Configure Connection tab
page are provided as follows.
Parameter NE31
Source VPI 34 34 34 34
(eg.35,36-39)
Source VCI 33 34 35 36
(eg.35,36-39)
Sink VPI(eg. 34 34 34 34
35,36-39)
Sink VCI(eg. 33 34 35 36
35,36-39)
Uplink Policy 5 6 7 8
Down link 5 6 7 8
Policy
In the Configure PW dialog box, the values for the relevant parameters that need to be set
in the General Attributes tab page are provided as follows.
Parameter NE31
Parameter NE31
In the Configure PW dialog box, the values for the related parameters that need to be set in
the Advanced Attributes tab page are provided as follows.
Parameter NE31
Control Word Must use Must use Must use Must use
Control CW CW CW CW
Channel Type
The values for the related parameters that need to be set in the CoS Mapping tab page are
provided as follows.
Parameter NE31
Parameter NE32
ID 902
Name bts34_cbrservice_mspw
The values for the related parameters that need to be set in the PW Basic Attributes tab page
are provided as follows.
Parameter NE32
PW ID 103 104
PW Type ATM one to one VCC cell ATM one to one VCC cell
transport transport
In the Configure PW dialog box, the values for the related parameters that need to be set in
the Advanced Attributes tab page are provided as follows.
Parameter NE32
Parameter NE32
Parameter NE32
ID 903
Name bts34_rtvbrservice_mspw
The values for the related parameters that need to be set in the PW Basic Attributes tab page
are provided as follows.
Parameter NE32
PW ID 105 106
PW Type ATM one to one VCC cell ATM one to one VCC cell
transport transport
In the Configure PW dialog box, the values for the related parameters that need to be set in
the Advanced Attributes tab page are provided as follows.
Parameter NE32
Parameter NE32
ID 904
Name bts34_nrtvbrservice_mspw
The values for the related parameters that need to be set in the PW Basic Attributes tab page
are provided as follows.
Parameter NE32
PW ID 107 108
PW Type ATM one to one VCC cell ATM one to one VCC cell
transport transport
In the Configure PW dialog box, the values for the related parameters that need to be set in
the Advanced Attributes tab page are provided as follows.
Parameter NE32
Parameter NE32
ID 905
Name bts34_ubrservice_mspw
The values for the related parameters that need to be set in the PW Basic Attributes tab page
are provided as follows.
Parameter NE32
PW ID 109 110
PW Type ATM one to one VCC cell ATM one to one VCC cell
transport transport
In the Configure PW dialog box, the values for the related parameters that need to be set in
the Advanced Attributes tab page are provided as follows.
Parameter NE32
----End
Procedure
Step 1 See A.13.4 Testing ATM Services and verify ATM service configurations.
The verification result should be "success".
----End
l Services from BTS13 and BTS14 are directly transmitted to NE11. The RNC uses different
E1 ports to receive services from different BTSs. For specific ATM service port
information, see Table 11-68.
l A bidirectional tunnel (ID: 1503), which has a protection tunnel, is available between NE11
and NE31. This tunnel and its corresponding information have been configured in 10.3
Configuration Example (MPLS Tunnels with MPLS APS Protection).
l The NEs need not perform traffic management for ATM services.
Working tunnel
(ID=1503)
GE GE
NE32
E1
NE11 NE31
RNC
GE
E1 NE21 GE
E1
R99
BTS13 R99
BTS14
11.9.2 ServicePlanning
You need to plan the corresponding parameter information before service configuration.
Table 11-69 and Table 11-70 provide planning information about UNI ports.
NOTE
l Appropriate port names facilitate future maintenance. It is recommended that you name ports on the
entire network in a unified manner.
l The E1 frame format and frame mode must be the same as those of service access equipment. As
specified in ITU-T G.804, ATM service ports use the default CRC-4 multiframe format and the PCM30
frame mode.
Minimum - 1
number of
activated links
Differentiated - 25
delay tolerance
Differentiated - 25
delay tolerance
NOTE
l If carried over a single E1, ATM services from a BTS are transmitted and received through UNI ports.
In this case, the IMA protocol needs to be disabled. If carried over multiple E1s, ATM services from
a BTS are transmitted and received through IMA trunks.
l Normally, set the IMA protocol version, IMA frame length, IMA symmetric mode, and differentiated
delay tolerance of an NE (with IMA protocol enabled) to the same values as those of its interconnected
equipment. Normally, the BTS/RNC configurations are as follows:
l IMA protocol version: 1.1
l IMA frame length: 128
l IMA symmetric mode: symmetrical mode and symmetrical operation
l The differentiated delay tolerance: 25
l The clock modes must be the same at both ends of an IMA trunk. The default clock mode for a BTS
is ITC. Therefore, the clock mode is set to ITC for the NE that is interconnected with the BTS and the
NE at the opposite end of the IMA link.
In this example, the PHB service class is set to EF for transparently transmitted ATM services
to ensure reliable transmission of medium- and high-priority services. The PHB service class
for transparently transmitted ATM services, however, is defined as BE in the default ATM CoS
mapping table. Therefore, a new ATM CoS mapping table needs to be created.
Parameter Value
NE11 NE31
Mapping table ID 2
Service ID 101
PW information
PW ID 101
PW ingress/ 101/101
egress label
Tunnel 1503
VCCV Ping
Verification
Mode
Service ID 112
PW information
PW ID 112
PW ingress/ 112/112
egress label
Tunnel 1503
VCCV Ping
Verification
Mode
Procedure
Step 1 See A.6.4.1 Setting Basic Attributes of Smart E1 Ports and set general attributes of Smart E1
ports.
l The values for the related parameters of NE11 are provided as follows.
Parameter NE11
l The values for the related parameters of NE31 are provided as follows.
Parameter NE31
Step 2 See A.6.4.2 Setting Advanced Attributes of Smart E1 Ports and set advanced attributes of
Smart E1 ports.
l The values for the related parameters of NE11 are provided as follows.
Parameter NE11
Frame Mode 30 30
l The values for the related parameters of NE31 are provided as follows.
Parameter NE31
Frame Mode 30 30
----End
Procedure
Step 1 See A.9.7.1 Binding ATM TRUNKs and bind the ATM trunk.
l The values for the related parameters for NE11 are provided as follows.
Parameter NE11
Level E1 E1
l The values for the related parameters for NE31 are provided as follows.
Parameter NE31
Level E1 E1
Step 2 See A.9.7.2 Configuring an IMA group and create an IMA group.
l The values for the related parameters of NE11 are provided as follows.
Parameter NE11
Parameter NE11
l The values for the related parameters of NE31 are provided as follows.
Parameter NE31
Step 3 See A.9.7.3 Setting ATM Port Parameters and set ATM port parameters.
l The values for the related parameters of NE11 are provided as follows.
Parameter NE11
l The values for the related parameters of NE31 are provided as follows.
Parameter NE31
----End
Procedure
Step 1 See A.9.9.1 Creating an ATM-DiffServ Domain and create the ATM DS domain.
Parameter Value
Mapping Relation ID 2
PORT-TRANS EF
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
Procedure
Step 1 See A.9.8.1 Creating ATM Services and create ATM services.
l Parameters of NE11:
The values for the related parameters that need to be set in the main interface are as follows.
Parame NE11
ter
ATM Services from BTS13 ATM Services from BTS14
The values for the related parameters that need to be set in the Configure Connection tab
page are provided as follows.
Parameter NE11
In the Configure PW dialog box, the values for the relevant parameters that need to be set
in the General Attributes tab page are provided as follows.
Parame NE11
ter
ATM Services from BTS13 ATM Services from BTS14
PW ID 101 112
PW Static Static
Signalin
g Type
PW 101 112
Incomin
g Label
Parame NE11
ter
ATM Services from BTS13 ATM Services from BTS14
PW 101 112
Outgoin
g Label
In the Configure PW dialog box, the values for the related parameters that need to be set in
the Advanced Attributes tab page are provided as follows.
Parame NE11
ter
ATM Services from BTS13 ATM Services from BTS14
The values for the related parameters that need to be set in the CoS Mapping tab page are
provided as follows.
Parame NE11
ter
ATM Services from BTS13 ATM Services from BTS14
PW ID 101 112
l Parameters of NE31:
The values for the related parameters that need to be set in the main interface are as follows.
Parame NE31
ter
ATM Services from BTS13 ATM Services from BTS14
The values for the related parameters that need to be set in the Configure Connection tab
page are provided as follows.
Parameter NE31
In the Configure PW dialog box, the values for the relevant parameters that need to be set
in the General Attributes tab page are provided as follows.
Parame NE31
ter
ATM Services from BTS13 ATM Services from BTS14
PW ID 101 112
PW Static Static
Signali
ng Type
Parame NE31
ter
ATM Services from BTS13 ATM Services from BTS14
PW 101 112
Incomi
ng
Label
PW 101 112
Outgoi
ng
Label
In the Configure PW dialog box, the values for the related parameters that need to be set in
the Advanced Attributes tab page are provided as follows.
Parame NE31
ter
ATM Services from BTS13 ATM Services from BTS14
The values for the related parameters that need to be set in the CoS Mapping tab page are
provided as follows.
Parame NE31
ter
ATM Services from BTS13 ATM Services from BTS14
PW ID 101 112
----End
Procedure
Step 1 The OptiX RTN 950 does not support ATM OAM tests on transparently transmitted services
(PORT-TRANS) over an ATM port. Therefore, it is recommended that you initiate an ATM
OAM test on a CE (for example, a BTS or RNC) of a PSN so that ATM OAM packets can be
transparently transmitted through the OptiX RTN 950 to the opposite CE on the PSN. In this
manner, an ATM service connectivity test is implemented.
----End
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: 310) at BTS31, which are received by NE32, need to be
transmitted to the RNC. A bidirectional working tunnel (ID: 1501), which has a protection
tunnel, is available between NE32 and NE31. Ethernet services carried on PWs connected
to BTS31 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
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 11-25 Networking diagram (E-Line services carried on PWs, a simple example)
NE34
BTS33 NE33
FE
BTS31
R4
FE R4
Working Tunnel
(ID=1501)
GE NE32 GE
GE
NE21 GE
GE
Hybrid radio ring network
RNC
Table 11-76 provides the information about UNI ports of E-Line services carried on PWs.
Table 11-77 provides the information about the Ethernet ports on NE32.
Parameter NE32
2-EM6F-3
Table 11-78 provides the information about the Ethernet ports on NE31.
Parameter NE31
4-EM6T-1 4-EM6T-2
NOTE
l In this example, all GE ports on the packet network work in auto-negotiation mode. Therefore, FE ports on
all NEs, which receive Ethernet services from BTSs, need to work in auto-negotiation mode. If Ethernet
ports at BTSs, which are connected to FE ports, work in other modes, FE ports at the local end need to work
in the corresponding modes.
l In this example, to ensure that the Ethernet frames that carry more than one tag such as QinQ can traverse
the equipment, the maximum frame length is set to 1536 (bytes). If the equipment needs to transmit jumbo
frames with a greater length, set the maximum frame length according to the actual length of a jumbo frame.
l Generally, the flow control function is enabled only when the local NE or opposite equipment has insufficient
QoS capabilities. The planning information of flow control must be the same for the equipment at both ends.
l In this example, no loopback check, loopback port shutdown, or broadcast packet suppression function is
enabled.
To improve service transmission reliability, NE31 and the RNC are interconnected through the
LAG formed by two GE links. Table 11-79 provides the planning information.
Parameter NE31
NOTE
In this example, the bandwidth of the Ethernet services is lower than the bandwidth of a GE port. Therefore,
you do not need to configure the LAG to the load-sharing mode for increased bandwidth utilization.
Table 11-80 provides the planning information about E-Line services carried by PWs.
Bearer Type PW PW
NOTE
For per-NE service configuration, the service name needs to be planned manually. For end-to-end service
configuration, the Web LCT automatically generates the service name based on naming rules.
PW ID 303 303
NOTE
In this example, the service ID, PW ID, PW ingress label, and PW egress label are manually planned. For end-
to-end service configuration, the Web LCT automatically sets these parameters.
In this example, the tunnel has already been planned when you plan MPLS tunnels. Therefore, you need to
select only the tunnel that carries the PWs.
QoS (DiffServ)
DiffServ is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the
BTS services be allocated by the service type. Then, the transmission network creates the
corresponding DiffServ domain according to the allocated VLAN priority, DSCP value, or
MPLS EXP value. Each Ethernet port involved in the service must use the same DiffServ
configuration.
In this example, the BTS services are allocated corresponding C-VLAN priorities by service
type, and PW-carried UNI-NNI E-Line services are configured on the transmission network.
DiffServ planning has been completed for the transmission network during MPLS tunnel
planning. In this example, you only need to set the trusted packet types of the UNI and NNI
ports to C-VLAN priority and MPLS EXP respectively. This setting results in the mapping from
the C-VLAN priority of the UNI-side BTS services to the MPLS EXP value on the NNI side of
the transmission network, therefore achieving end-to-end QoS control on the transmission
network.
Table 11-82 lists the queue scheduling mode used by each Ethernet port involved in the service
in this example.
CS7 SP
CS6 SP
EF SP
BE SP
Procedure
Step 1 See A.6.6.1 Setting the Basic Attributes of Ethernet Ports and set the general attributes of
the UNI ports.
l The values for the general attribute parameters of the UNI port of NE32 are provided as
follows.
Parameter NE32
2-EM6F-3
l The values for the general attribute parameters of the UNI port of NE31 are provided as
follows.
Parameter NE31
4-EM6T-1 4-EM6T-2
Parameter NE31
4-EM6T-1 4-EM6T-2
Step 2 See A.6.6.3 Setting the Layer 2 Attributes of Ethernet Ports and set the Layer 2 attributes of
the UNI ports.
l The values for the Layer 2 attribute parameters of the UNI port of NE32 are provided as
follows.
Parameter NE32
2-EM6F-3
l The values for the Layer 2 attribute parameters of the UNI port of NE31 are provided as
follows.
Parameter NE31
4-EM6T-1 4-EM6T-2
----End
Procedure
Step 1 See A.7.2.1 Creating a LAG and create a LAG.
The values for the relevant parameters that need to be set in the main interface are provided as
follows.
Parameter Value
Parameter Value
The values for the relevant parameters that need to be set in the Port Setting tab page are as
follows.
Parameter Value
Main Port 1
----End
Procedure
Step 1 See A.7.3.5 Configuring UNI-NNI E-Line Services (Carried by PWs) and configure the E-
Line services.
l Parameters of NE32
The values for the relevant parameters that need to be set in the main interface are as follows.
Parameter NE32
Service ID 303
Direction UNI-NNI
Bearer Type PW
The values for the relevant parameters that need to be set in the PW tab page are provided
as follows.
Parameter NE32
PW ID 303
PW Type Ethernet
Direction Bidirectional
PW Incoming Label 40
PW Outgoing Label 40
The values for the relevant parameters that need to be set in the Advanced Attributes dialog
box are provided as follows.
Parameter NE32
l Parameters of NE31
The values for the relevant parameters that need to be set in the main interface are as follows.
Parameter NE31
Service ID 303
Direction UNI-NNI
Bearer Type PW
In the Configure PW dialog box, the values for the relevant parameters that need to be set
in the General Attributes tab page are provided as follows.
Parameter NE31
PW ID 303
PW Type Ethernet
Direction Bidirectional
PW Incoming Label 40
PW Outgoing Label 40
The values for the relevant parameters that need to be set in the Advanced Attributes dialog
box are provided as follows.
Parameter NE31
----End
Procedure
Step 1 Follow instructions in A.7.7.2 Modifying the Mapping Relationships for the DS Domain and
set the trusted packet types of the UNI and NNI ports on NE32 and NE31 that transmit the UNI-
NNI ETH PWE3 services to C-VLAN and MPLS EXP respectively.
1. Select the default DS domain for the OptiX RTN equipment.
NOTE
In this example, the planned mapping between the trusted packet type (C-VLAN priority) and the PHB
service class queues for BTSs is the same as the mapping in the default DS domain of the OptiX RTN
equipment. Therefore, the default DS domain settings are used.
Parameter Value
Mapping Relation ID 1
2. Set the trusted packet type of the UNI ports on NE32 and NE31 to C-VLAN.
Parameter Value
NE32 NE31
NOTE
For an NNI port that transmits a PW-carried E-Line service, set Packet Type trusted by the NNI port to
MPLS EXP.
Step 2 Follow instructions in A.7.7.4 Creating a Port Policy and create the port policy.
The values for the WRR scheduling policy parameters of UNI ports on NE31 and NE32 are
provided as follows.
Parameter Value
Policy ID 2
The values for the port policy parameters of UNI ports on NE31 and NE32 are provided as
follows.
Parameter Value
Policy ID 1
Parameter Value
Step 3 Follow instructions in A.7.7.7 Setting the Port That Uses the Port Policy and set the ports that
use the port policy.
The values for the related parameters of UNI ports of NE32 and NE31 are provided as follows.
Parameter Value
NE32 NE31
----End
Procedure
Step 1 See A.7.8.1 Creating an MD and create the MDs for NE31 and NE32.
Parameter Value
NE31 NE32
Maintenance Domain 4 4
Level
Step 2 See A.7.8.2 Creating an MA and create an MA for NE31 and NE32.
Parameter Value
NE31 NE32
Step 3 See A.7.8.3 Creating MEPs and create MEPs for NE31 and NE32.
Parameter Value
NE31 NE32
MP ID 310 320
Step 4 See A.7.8.4 Creating Remote MEPs in an MA and create the remote MEPs for NE31 and
NE32.
Parameter Value
NE31 NE32
Parameter Value
NE31 NE32
Perform the LB test by considering the MEP whose MP ID is 310 as the source MEP and the
MEP whose MP ID is 320 as the sink MEP to check the connectivity of the E-Line services
carried on the PWs between NE31 and NE32.
----End
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 On the Hybrid microwave chain network connected to NE11, Ethernet services at BTS11,
BTS12, and BTS13 respectively carry VLAN ID 100, VLAN ID 110, and VLAN ID 120,
and they need to be transmitted to the RNC. A bidirectional working tunnel (ID: 1503),
which has a protection tunnel, is available between NE11 and NE31. Ethernet services
carried on PWs at BTS11, BTS12, and BTS13 are transparently transmitted over the tunnel.
l On the Hybrid microwave ring network connected to NE21, Ethernet services at BTS21,
BTS22, and BTS23 respectively carry VLAN ID 200, VLAN ID 210, and VLAN ID 220,
and they need to be transmitted to the RNC. A bidirectional working tunnel (ID: 1505),
which has a protection tunnel, is available between NE21 and NE31. Ethernet services
carried on PWs at 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
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 11-26 Networking diagram (E-Line services carried on PWs and transmitting the
Ethernet services aggregated from the Hybrid microwave network)
NE34
BTS33 NE33
FE
BTS31
R4
FE R4
BTS11 Working Tunnel
(ID=1503)
GE
GE NE32
R4 NE31 GE
BTS12 Hybrid radio chain network NE11
GE
NE21 GE RNC
R4 BTS13
Working Tunnel
(ID=1505)
BTS21
R4 Hybrid radio ring network
R4
BTS22 BTS23
R4 R4
Table 11-83 provides the information about UNI service ports of E-Line services carried on
PWs.
Parameter NE21
1-EM6F-4
Table 11-85 provides the information about the Ethernet ports on NE31.
Parameter NE31
4-EM6T-1 4-EM6T-2
NOTE
l NE21 cross-connects and loops back the 1-EM6F-3 port to the 1-EM6F-4 port by means of a network cable
to convert Native E-LAN services received by the 1-EM6F-3 port on the Hybrid microwave ring network
to E-Line services carried on PWs.
l In this example, all GE ports on the packet network work in auto-negotiation mode. Therefore, FE ports on
all NEs, which receive Ethernet services from BTSs, need to work in auto-negotiation mode. If Ethernet
ports at BTSs, which are connected to FE ports, work in other modes, FE ports at the local end need to work
in the corresponding modes.
l In this example, to ensure that the Ethernet frames that carry more than one tag such as QinQ can traverse
the equipment, the maximum frame length is set to 1536 (bytes). If the equipment needs to transmit jumbo
frames with a greater length, set the maximum frame length according to the actual length of a jumbo frame.
l Generally, the flow control function is enabled only when the local NE or opposite equipment has insufficient
QoS capabilities. The planning information of flow control must be the same for the equipment at both ends.
l In this example, no loopback check, loopback port shutdown, or broadcast packet suppression function is
enabled for Ethernet ports.
Parameter NE11
3-ISU2-1
To improve service transmission reliability, NE31 and the RNC are interconnected through the
LAG formed by two GE links. Table 11-87 provides the planning information.
Parameter NE31
NOTE
In this example, the bandwidth of the Ethernet services is lower than the bandwidth of a GE port. Therefore,
you do not need to configure the LAG to the load-sharing mode for increased bandwidth utilization.
Table 11-88 provides the planning information about E-Line services carried by PWs.
Bearer Type PW PW PW PW
NOTE
For per-NE service configuration, the service name needs to be planned manually. For end-to-end service
configuration, the Web LCT automatically generates the service name based on naming rules.
PW Ingress 60 60 50 50
Labs/Source
Port
PW Egress 60 60 50 50
Labs/Sink Port
NOTE
In this example, the service ID, PW ID, PW ingress label, and PW egress label are manually planned. For end-
to-end service configuration, the Web LCT automatically sets these parameters.
In this example, the tunnel has already been planned when you plan MPLS tunnels. Therefore, you need to
select only the tunnel that carries the PWs.
QoS (DiffServ)
DiffServ is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the
BTS services be allocated by the service type. Then, the transmission network creates the
corresponding DiffServ domain according to the allocated VLAN priority, DSCP value, or
MPLS EXP value. Each Ethernet port involved in the service must use the same DiffServ
configuration.
In this example, the BTS services are allocated corresponding C-VLAN priorities by service
type, and PW-carried UNI-NNI E-Line services are configured on the transmission network.
DiffServ planning has been completed for the transmission network during MPLS tunnel
planning. In this example, you only need to set the trusted packet types of the UNI and NNI
ports to C-VLAN priority and MPLS EXP respectively. This setting results in the mapping from
the C-VLAN priority of the UNI-side BTS services to the MPLS EXP value on the NNI side of
the transmission network, therefore achieving end-to-end QoS control on the transmission
network.
Table 11-90 lists the queue scheduling mode used by each Ethernet port involved in the service
in this example.
CS7 SP
CS6 SP
EF SP
BE SP
Procedure
Step 1 See A.6.6.1 Setting the Basic Attributes of Ethernet Ports and set the general attributes of
the UNI ports.
l The values for the general attribute parameters of the UNI port of NE21 are provided as
follows.
Parameter NE21
1-EM6F-4
l The values for the general attribute parameters of the UNI port of NE31 are provided as
follows.
Parameter NE31
4-EM6T-1 4-EM6T-2
Step 2 See A.6.6.3 Setting the Layer 2 Attributes of Ethernet Ports and set the Layer 2 attributes of
the UNI ports.
l The values for the Layer 2 attribute parameters of the UNI port of NE21 are provided as
follows.
Parameter NE21
1-EM6F-4
l The values for the Layer 2 attribute parameters of the UNI port of NE31 are provided as
follows.
Parameter NE31
4-EM6T-1 4-EM6T-2
Step 3 See A.6.7.1 Setting the Basic Attributes of IF_ETH Ports and set the general attributes of the
UNI ports.
The values for the general attribute parameters of the UNI port of NE11 are provided as follows.
Parameter NE11
3-ISU2-1
Step 4 See A.6.7.2 Setting the Layer 2 Attributes of IF_ETH Ports and set the Layer 2 attributes of
the UNI ports.
The values for the Layer 2 attribute parameters of the UNI port of NE11 are provided as follows.
Parameter NE11
3-ISU2-1
----End
Procedure
Step 1 See A.7.2.1 Creating a LAG and create a LAG.
The values for the relevant parameters that need to be set in the main interface are provided as
follows.
Parameter Value
Parameter Value
The values for the relevant parameters that need to be set in the Port Setting tab page are as
follows.
Parameter Value
Main Port 1
----End
Procedure
Step 1 See A.7.3.5 Configuring UNI-NNI E-Line Services (Carried by PWs) and configure the E-
Line services.
l Parameters of NE11
The values for the relevant parameters that need to be set in the main interface are as follows.
Parameter NE11
Service ID 301
Direction UNI-NNI
Bearer Type PW
The values for the relevant parameters that need to be set in the PW tab page are provided
as follows.
Parameter NE11
PW ID 301
PW Type Ethernet
Direction Bidirectional
PW Incoming Label 60
PW Outgoing Label 60
The values for the relevant parameters that need to be set in the Advanced Attributes dialog
box are provided as follows.
Parameter NE11
l Parameters of NE21
The values for the relevant parameters that need to be set in the main interface are as follows.
Parameter NE21
Service ID 302
Direction UNI-NNI
Bearer Type PW
Parameter NE21
The values for the relevant parameters that need to be set in the PW tab page are provided
as follows.
Parameter NE21
PW ID 302
PW Type Ethernet
Direction Bidirectional
PW Incoming Label 50
PW Outgoing Label 50
The values for the relevant parameters that need to be set in the Advanced Attributes dialog
box are provided as follows.
Parameter NE21
l Parameters of NE31
The values for the relevant parameters that need to be set in the main interface are as follows.
Parameter NE31
Parameter NE31
Bearer Type PW PW
The values for the relevant parameters that need to be set in the PW tab page are provided
as follows.
Parameter NE31
PW ID 301 302
PW Incoming Label 60 50
PW Outgoing Label 60 50
The values for the relevant parameters that need to be set in the Advanced Attributes dialog
box are provided as follows.
Parameter NE31
----End
Procedure
Step 1 Follow instructions in A.7.7.2 Modifying the Mapping Relationships for the DS Domain and
set the trusted packet types of the UNI and NNI ports on NE11, NE21, and NE31 that transmit
the UNI-NNI ETH PWE3 services to C-VLAN and MPLS EXP respectively.
1. Select the default DS domain for the OptiX RTN equipment.
NOTE
In this example, the planned mapping between the trusted packet type (C-VLAN priority) and the PHB
service class queues for BTSs is the same as the mapping in the default DS domain of the OptiX RTN
equipment. Therefore, the default DS domain settings are used.
Parameter Value
Mapping Relation ID 1
2. Set the trusted packet type of the UNI ports on NE11, NE21, and NE31 to C-VLAN.
Parameter Value
NOTE
For an NNI port that transmits a PW-carried E-Line service, set Packet Type trusted by the NNI port to
MPLS EXP.
Step 2 Follow instructions in A.7.7.4 Creating a Port Policy and create the port policy.
The values for the WRR scheduling policy parameters of UNI ports on NE11, NE21, and NE32
are provided as follows.
Parameter Value
Policy ID 2
The values for the port policy parameters of UNI ports on NE11, NE21, and NE31 are provided
as follows.
Parameter Value
Policy ID 1
Step 3 Follow instructions in A.7.7.7 Setting the Port That Uses the Port Policy and set the ports that
use the port policy.
The values for the related parameters of UNI ports of NE11, NE21, and NE31 are provided as
follows.
Parameter Value
----End
Procedure
Step 1 See A.7.8.1 Creating an MD and create the MDs for NE11, NE21, and NE31.
Parameter Value
Maintenance 4 4 4
Domain Level
Step 2 See A.7.8.2 Creating an MA and create an MA for NE11, NE21, and NE31.
Parameter Value
CC Test 1s 1s 1s 1s
Transmit
Period
Step 3 See A.7.8.3 Creating MEPs and create MEPs for NE11, NE21, and NE31.
Parameter Value
Parameter Value
NOTE
l On NE11, when performing the connectivity check on the E-Line services carried on PWs, use the BTS
service (VLAN ID: 100) received by NE11 as an example.
l On NE21, when performing the connectivity check on the E-Line services carried on PWs, use the BTS
service (VLAN ID: 200) received by NE21 as an example.
Step 4 See A.7.8.4 Creating Remote MEPs in an MA and create the remote MEPs for NE11, NE21,
and NE31.
Parameter Value
Perform the LB test by considering the MEP whose MP ID is 311 as the source MEP and the
MEP whose MP ID is 110 as the sink MEP to check the connectivity of the E-Line services
carried on the PWs between NE31 and NE11.
Perform the LB test by considering the MEP whose MP ID is 312 as the source MEP and the
MEP whose MP ID is 210 as the sink MEP to check the connectivity of the E-Line services
carried on the PWs between NE31 and NE21.
----End
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: 330) at BTS33, which are received by NE34, need to be
transmitted to the RNC.
l The information about the tunnel between NE34 and NE31 is as follows:
– A bidirectional tunnel (ID: 1515), which does not have a protection tunnel, is available
between NE34 and NE32.
– A bidirectional tunnel (ID: 1501), which has a protection tunnel, is available between
NE32 and NE31.
– Ethernet services at BTSs are carried by PWs on the two tunnels, and exchange PW
labels and tunnel labels on NE32.
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 11-27 Networking diagram (E-Line services carried by PWs and transmitting the
Ethernet services aggregated from the Hybrid microwave network)
NE34
BTS33 NE33
FE BTS31
R4
Tunnel
(ID=1515)
R4
FE Working Tunnel
GE (ID=1501)
NE32 GE
GE
Hybrid radio chain network NE31
NE11
GE
NE21 GE RNC
Table 11-91 provides the information about UNI ports of E-Line services carried by PWs.
Table 11-92 provides the information about the Ethernet ports on NE34.
Parameter NE34
1-EM6T-3
Table 11-92 provides the information about the Ethernet ports on NE31.
Parameter NE31
4-EM6T-1 4-EM6T-2
NOTE
l In this example, all GE ports on the packet network work in auto-negotiation mode. Therefore, FE ports on
all NEs, which receive Ethernet services from BTSs, need to work in auto-negotiation mode. If Ethernet
ports at BTSs, which are connected to FE ports, work in other modes, FE ports at the local end need to work
in the corresponding modes.
l In this example, to ensure that the Ethernet frames that carry more than one tag such as QinQ can traverse
the equipment, the maximum frame length is set to 1536 (bytes). If the equipment needs to transmit jumbo
frames with a greater length, set the maximum frame length according to the actual length of a jumbo frame.
l Generally, the flow control function is enabled only if the local NE or opposite equipment has insufficient
QoS capabilities. The planning information of flow control must be the same for the equipment at both ends.
l In this example, no loopback check, loopback port shutdown, or broadcast packet suppression function is
enabled.
To improve service transmission reliability, NE31 and the RNC are interconnected through the
LAG formed by two GE links. Table 11-94 provides the planning information.
Parameter NE31
NOTE
In this example, the bandwidth of the Ethernet services is lower than the bandwidth of a GE port. Therefore,
you do not need to configure the LAG to the load-sharing mode for increased bandwidth utilization.
Table 11-95 provides the planning information about E-Line services carried by PWs.
Bearer Type PW PW
NOTE
For per-NE service configuration, the service name needs to be planned manually. For end-to-end service
configuration, the Web LCT automatically generates the service name based on naming rules.
PW ID 304 305
NOTE
In this example, the service ID, PW ID, PW ingress label, and PW egress label are manually planned. For end-
to-end service configuration, the Web LCT automatically sets these parameters.
In this example, the tunnel has already been planned when you plan MPLS tunnels. Therefore, you need to
select only the tunnel that carries the PWs.
Table 11-97 provides the planning information about MS-PWs connected to NE32.
Parameter NE32
ID 903
Name bts33_e-line_service_mspw
NOTE
l When MS-PWs are used, the label values of Forward PW and Backward PW cannot be the same.
l In end-to-end configuration mode, PW ID, PW Ingress Label, and PW Egress Label can be automatically
allocated and therefore they do not need to be planned.
l In end-to-end configuration mode, MS-PW service ID and PW switching service ID are automatically
allocated and invisible.
QoS (DiffServ)
DiffServ is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the
BTS services be allocated by the service type. Then, the transmission network creates the
corresponding DiffServ domain according to the allocated VLAN priority, DSCP value, or
MPLS EXP value. Each Ethernet port involved in the service must use the same DiffServ
configuration.
In this example, the BTS services are allocated corresponding C-VLAN priorities by service
type, and PW-carried UNI-NNI E-Line services are configured on the transmission network.
DiffServ planning has been completed for the transmission network during MPLS tunnel
planning. In this example, you only need to set the trusted packet types of the UNI and NNI
ports to C-VLAN priority and MPLS EXP respectively. This setting results in the mapping from
the C-VLAN priority of the UNI-side BTS services to the MPLS EXP value on the NNI side of
the transmission network, therefore achieving end-to-end QoS control on the transmission
network.
Table 11-98 lists the queue scheduling mode used by each Ethernet port involved in the service
in this example.
CS7 SP
CS6 SP
EF SP
BE SP
Procedure
Step 1 See A.6.6.1 Setting the Basic Attributes of Ethernet Ports and set the general attributes of
the UNI ports.
l The values for the general attribute parameters of the UNI port of NE34 are provided as
follows.
Parameter NE34
1-EM6T-3
l The values for the general attribute parameters of the UNI port of NE31 are provided as
follows.
Parameter NE31
4-EM6T-1 4-EM6T-2
Step 2 See A.6.6.3 Setting the Layer 2 Attributes of Ethernet Ports and set the Layer 2 attributes of
the UNI ports.
l The values for the Layer 2 attribute parameters of the UNI port of NE34 are provided as
follows.
Parameter NE34
1-EM6T-3
l The values for the Layer 2 attribute parameters of the UNI port of NE31 are provided as
follows.
Parameter NE31
4-EM6T-1 4-EM6T-2
----End
Procedure
Step 1 See A.7.2.1 Creating a LAG and create a LAG.
The values for the relevant parameters that need to be set in the main interface are provided as
follows.
Parameter Value
The values for the relevant parameters that need to be set in the Port Setting tab page are as
follows.
Parameter Value
Main Port 1
Parameter Value
----End
Procedure
Step 1 See A.7.3.5 Configuring UNI-NNI E-Line Services (Carried by PWs) and configure the E-
Line services.
l Parameters of NE34
The values for the relevant parameters that need to be set in the main interface are provided
as follows.
Parameter NE34
Service ID 304
Direction UNI-NNI
Bearer Type PW
The values for the relevant parameters that need to be set in the PW tab page are provided
as follows.
Parameter NE34
PW ID 304
PW Type Ethernet
Direction Bidirectional
PW Incoming Label 20
Parameter NE34
PW Outgoing Label 20
The values for the relevant parameters that need to be set in the Advanced Attributes dialog
box are provided as follows.
Parameter NE34
l Parameters of NE31
The values for the relevant parameters that need to be set in the main interface are provided
as follows.
Parameter NE31
Service ID 305
Direction UNI-NNI
Bearer Type PW
The values for the relevant parameters that need to be set in the PW tab page are provided
as follows.
Parameter NE31
PW ID 305
Parameter NE31
PW Type Ethernet
Direction Bidirectional
PW Incoming Label 30
PW Outgoing Label 30
The values for the relevant parameters that need to be set in the Advanced Attributes dialog
box are provided as follows.
Parameter NE31
Step 2 See A.9.4.2 Creating an MS-PW and configure the E-Line services.
The values for the relevant parameters that need to be set for creating an MS-PW on NE32 are
provided as follows.
Parameter NE32
ID 903
Name bts33_e-line_service_mspw
MTU(bytes) 9000
Parameter NE32
----End
Procedure
Step 1 Follow instructions in A.7.7.2 Modifying the Mapping Relationships for the DS Domain and
set the trusted packet types of the UNI and NNI ports on NE34 and NE31 that transmit the UNI-
NNI ETH PWE3 services to C-VLAN and MPLS EXP respectively.
1. Select the default DS domain for the OptiX RTN equipment.
NOTE
In this example, the planned mapping between the trusted packet type (C-VLAN priority) and the PHB
service class queues for BTSs is the same as the mapping in the default DS domain of the OptiX RTN
equipment. Therefore, the default DS domain settings are used.
Parameter Value
Mapping Relation ID 1
2. Set the trusted packet type of the UNI ports on NE34 and NE31 to C-VLAN.
Parameter Value
NE34 NE31
NOTE
For an NNI port that transmits a PW-carried E-Line service, set Packet Type trusted by the NNI port to
MPLS EXP.
Step 2 Follow instructions in A.7.7.4 Creating a Port Policy and create the port policy.
The values for the WRR scheduling policy parameters of UNI ports on NE31 and NE34 are
provided as follows.
Parameter Value
Policy ID 2
The values for the port policy parameters of UNI ports on NE31 and NE34 are provided as
follows.
Parameter Value
Policy ID 1
Step 3 Follow instructions in A.7.7.7 Setting the Port That Uses the Port Policy and set the ports that
use the port policy.
The values for the relevant parameters of UNI ports of NE34 and NE31 are provided as follows.
Parameter Value
NE34 NE31
----End
Procedure
Step 1 See A.7.8.1 Creating an MD and create the MDs For NE31 and NE34.
Parameter Value
NE31 NE34
Maintenance Domain 4 4
Level
Step 2 See A.7.8.2 Creating an MA and create an MA for NE31 and NE34.
Parameter Value
NE31 NE34
Step 3 See A.7.8.3 Creating MEPs and create MEPs for NE31 and NE34.
Parameter Value
NE31 NE34
Parameter Value
NE31 NE34
MP ID 313 340
Step 4 See A.7.8.4 Creating Remote MEPs in an MA and create the remote MEPs for NE31 and
NE34.
Parameter Value
NE31 NE34
Perform the LB test by considering the MEP whose MP ID is 313 as the source MEP and the
MEP whose MP ID is 340 as the sink MEP to check the connectivity of the E-Line services
carried on the PWs between NE31 and NE34.
----End
After planning and configuring MPLS tunnels, aggregate Ethernet services from BTSs (with
conflicting VLAN IDs) to the RNC by means of PWs. The 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
radio chain network and then to the RNC. The PW-carried BTS Ethernet services are
transparently transmitted over the working tunnel between NE11 and NE31 whose tunnel
ID is 1503.
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
radio ring network and then to the RNC by means of VLAN forwarding. The PW-carried
BTS Ethernet services are transparently transmitted over the working tunnel between NE21
and NE31 whose tunnel ID is 1505.
l At the BTSs, Ethernet services have been configured with specific VLAN priorities based
on service types (real-time voice services, HSDPA real-time services, R99 non-real-time
services, or HSDPA data services). The transmission network provides end-to-end QoS
control based on the VLAN priorities specified at the BTSs.
l The GE ports on NE31, which are connected to the RNC, need to be configured in a link
aggregation group (LAG).
1 BTS21
VLAN 100
R4
R4
2 BTS22
3 BTS23
VLAN 110
VLAN 120
1 2 3 VLAN IDs conflict.
NOTE
Table 11-99 provides the port information about the PW-carried E-Line and E-AGGR services.
Parameter NE21
1-EM6F-4
Parameter NE21
1-EM6F-4
Table 11-101 provides the information about the Ethernet ports on NE31.
Parameter NE31
4-EM6T-1 4-EM6T-2
NOTE
l NE21 cross-connects and loops back the 1-EM6F-3 port to the 1-EM6F-4 port using a network cable to
convert Native E-LAN services received by the 1-EM6F-3 port on the Hybrid microwave ring network to
E-Line services carried on PWs.
l In this example, all GE ports on the packet network work in auto-negotiation mode. Therefore, FE ports on
all NEs, which receive Ethernet services from BTSs, need to work in auto-negotiation mode. If Ethernet
ports at BTSs, which are connected to FE ports, work in other modes, FE ports at the local end need to work
in the corresponding modes.
l In this example, to ensure that the Ethernet packets that carry more than one tag, such as QinQ packets,
traverse OptiX RTN NEs, the maximum frame length is set to 1536 (bytes). If OptiX RTN NEs need to
transmit jumbo packets with a greater length, set the maximum frame length according to the actual length
of a jumbo frame.
l Generally, the flow control function is enabled only if the local NE or opposite NE has insufficient QoS
capabilities. The planning information of flow control must be the same for the NEs at both ends.
l In this example, the loopback check, loopback port shutdown, or broadcast packet suppression function is
not enabled.
Parameter NE11
3-ISU2-1
Parameter NE31
NOTE
In this example, the bandwidth of the Ethernet services is lower than the bandwidth of a GE port. Therefore,
you do not need to configure the LAG to the load-sharing mode for increased bandwidth utilization.
Service ID 1 1
Carrier PW PW
PW ID 301 302
NOTE
In this example, the tunnel has already been planned when you plan MPLS tunnels. You need to select only
the tunnel that carries the PWs.
Parameter Value
Service ID 1
Parameter Value
Location Sink
Port 4-EM6T-1
Parameter Value
PW ID 301 302
Parameter Value
NOTE
In this example, the tunnel has already been planned when you plan MPLS tunnels. You need to select only
the tunnel that carries the PWs.
Table 11-109 Planning information about the VLAN forwarding table (NE31)
Parameter Value
Table 11-110 Planning information about the VLAN forwarding table (NE31)
Parameter Value
QoS (DiffServ)
DiffServ is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the
BTS services be allocated by the service type. Then, the transmission network creates the
corresponding DiffServ domain according to the allocated VLAN priority, DSCP value, or
MPLS EXP value. Each Ethernet port involved in the service must use the same DiffServ
configuration.
In this example, the BTS services are allocated corresponding C-VLAN priorities by service
type, and PW-carried UNI-NNI E-Line services are configured on the transmission network.
DiffServ planning has been completed for the transmission network during MPLS tunnel
planning. In this example, you only need to set the trusted packet types of the UNI and NNI
ports to C-VLAN priority and MPLS EXP respectively. This setting results in the mapping from
the C-VLAN priority of the UNI-side BTS services to the MPLS EXP value on the NNI side of
the transmission network, therefore achieving end-to-end QoS control on the transmission
network.
Table 11-111 lists the queue scheduling mode used by each Ethernet port involved in the service
in this example.
CS7 SP
CS6 SP
EF SP
BE SP
Procedure
Step 1 Follow instructions in A.6.6.1 Setting the Basic Attributes of Ethernet Ports and set the
general attributes of the UNI ports.
l The values for the general attribute parameters of the UNI port of NE21 are provided as
follows.
Parameter NE21
1-EM6F-4
l The values for the general attribute parameters of the UNI port of NE31 are provided as
follows.
Parameter NE31
4-EM6T-1 4-EM6T-2
Parameter NE31
4-EM6T-1 4-EM6T-2
Step 2 Follow instructions in A.6.6.3 Setting the Layer 2 Attributes of Ethernet Ports and set the
Layer 2 attributes of the UNI ports.
l The values for the Layer 2 attribute parameters of the UNI port of NE21 are provided as
follows.
Parameter NE21
1-EM6F-4
l The values for the Layer 2 attribute parameters of the UNI port of NE31 are provided as
follows.
Parameter NE31
4-EM6T-1 4-EM6T-2
Step 3 Follow instructions in A.6.7.1 Setting the Basic Attributes of IF_ETH Ports and set the general
attributes of the UNI ports.
The values for the general attribute parameters of the UNI port of NE11 are provided as follows.
Parameter NE11
3-ISU2-1
Step 4 Follow instructions in A.6.7.2 Setting the Layer 2 Attributes of IF_ETH Ports and set the
Layer 2 attributes of the UNI ports.
The values for the Layer 2 attribute parameters of the UNI port of NE11 are provided as follows.
Parameter NE11
3-ISU2-1
----End
Procedure
Step 1 See A.7.2.1 Creating a LAG and create a LAG.
The values for the relevant parameters that need to be set in the main interface are provided as
follows.
Parameter Value
The values for the relevant parameters that need to be set in the Port Setting tab page are as
follows.
Parameter Value
Main Port 1
----End
Procedure
Step 1 Follow instructions in A.7.3.5 Configuring UNI-NNI E-Line Services (Carried by PWs) and
configure the E-Line services.
l Parameters of NE11
The values for the relevant parameters that need to be set in the main interface are as follows.
Parameter NE11
Service ID 1
Direction UNI-NNI
Bearer Type PW
The values for the relevant parameters that need to be set in the PW tab page are provided
as follows.
Parameter NE11
PW ID 301
PW Type Ethernet
Direction Bidirectional
PW Incoming Label 60
PW Outgoing Label 60
The values for the relevant parameters that need to be set in the Advanced Attributes dialog
box are provided as follows.
Parameter NE11
Parameter NE11
l Parameters of NE21
The values for the relevant parameters that need to be set in the main interface are as follows.
Parameter NE21
Service ID 302
Direction UNI-NNI
Bearer Type PW
The values for the relevant parameters that need to be set in the PW tab page are provided
as follows.
Parameter NE21
PW ID 302
PW Type Ethernet
Direction Bidirectional
PW Incoming Label 50
PW Outgoing Label 50
The values for the relevant parameters that need to be set in the Advanced Attributes dialog
box are provided as follows.
Parameter NE21
Step 2 Follow instructions in A.7.3.6 Creating E-AGGR Services and configure E-AGGR services.
Parameters of NE31:
The values for the related parameters that need to be set in the main interface are provided as
follows.
Parameter Value
Service ID 1
The values for the related parameters that need to be set in the UNI tab page are provided as
follows.
Parameter Value
Location Sink
Port 4-EM6T-1(ORT-1)
The values for the Basic Attributes that need to be set in the NNI tab are as follows.
Parameter Value
PW ID 301 302
PW Incoming Label 60 50
PW Outgoing Label 60 50
Parameter Value
The values for the Advanced Attributes that need to be set in the NNI tab are as follows.
Parameter Value
The values for the related parameters that need to be set in VLAN Forwarding Table item are
as follows.
Parameter Value
----End
Procedure
Step 1 Follow instructions in A.7.7.2 Modifying the Mapping Relationships for the DS Domain and
set the trusted packet type of the UNI ports on NE11, NE21, and NE31 that carry UNI-NNI ETH
PWE3 services and E-AGGR services to C-VLAN.
1. Select the default DS domain for the OptiX RTN equipment.
NOTE
In this example, the planned mapping between the trusted packet type (C-VLAN priority) and the PHB
service class queues for BTSs is the same as the mapping in the default DS domain of the OptiX RTN
equipment. Therefore, the default DS domain settings are used.
Parameter Value
Mapping Relation ID 1
2. Set the trusted packet type of the UNI ports on NE11, NE21, and NE31 to C-VLAN.
Parameter Value
Step 2 Follow instructions in A.7.7.4 Creating a Port Policy and create the port policy.
The values for the WRR scheduling policy parameters of UNI ports on NE11, NE21, and NE31
are provided as follows.
Parameter Value
Policy ID 2
The values for the port policy parameters of UNI ports on NE11, NE21, and NE31 are provided
as follows.
Parameter Value
Policy ID 1
Step 3 Follow instructions in A.7.7.7 Setting the Port That Uses the Port Policy and set the ports that
use the port policy.
The values for the related parameters of UNI ports of NE11, NE21, and NE31 are provided as
follows.
Parameter Value
----End
Procedure
Step 1 Follow instructions in A.7.8.1 Creating an MD and create the MDs for NE11, NE21, and NE31.
Parameter Value
Maintenance 4 4 4
Domain Level
Step 2 Follow instructions in A.7.8.2 Creating an MA and create an MA for NE11, NE21, and NE31.
Parameter Value
Parameter Value
CC Test Transmit 1s 1s 1s
Period
Step 3 Follow instructions in A.7.8.3 Creating MEPs and create MEPs for NE11, NE21, and NE31.
Parameter Value
NOTE
l On NE11, when performing the continuity check on the E-Line services carried on PWs, use the BTS service
(VLAN ID: 100) received by NE11 as an example.
l On NE21, when performing the continuity check on the E-Line services carried on PWs, use the BTS service
(VLAN ID: 100) received by NE21 as an example.
Step 4 Follow instructions in A.7.8.4 Creating Remote MEPs in an MA and create the remote MEPs
for NE11, NE21, and NE31.
Parameter Value
Parameter Value
Perform an LB test by considering the MEP whose MP ID is 311 as the source MEP and the
MEP whose MP ID is 110 as the sink MEP to check whether the Ethernet service between NE31
and NE11 is available.
Perform an LB test by considering the MEP whose MP ID is 311 as the source MEP and the
MEP whose MP ID is 210 as the sink MEP to check whether the Ethernet service between NE31
and NE21 is available.
----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.
l Line clock source: refers to a clock source that is extracted from the received SDH signal.
l Radio clock source: refers to a clock source that is extracted from the received radio signal.
l Tributary clock source: refers to a clock source that is extracted from the received E1 signal.
l Ethernet clock source: refers to a clock source that is extracted from the Ethernet stream.
l External clock source: refers to a clock source that is synchronized with the 2 Mbit/s or 2
MHz signal received at the external clock port.
l Internal clock source: refers to a clock source that is generated through the free-run
oscillation of an NE built-in clock. The internal clock source has the lowest priority.
As shown in Figure 12-1, the radio links between NE1 and NE2 adopt 1+1 HSB protection.
NE2 needs to trace the clock on the radio links to keep synchronized with NE1. In this case, the
clock sources extracted by the main and standby IF boards can be configured in the clock source
priority list. The clock source extracted by the main IF board, however, has a higher priority.
Therefore, if the 1+1 HSB protection switching occurs on the radio links, the clock can be
switched at the same time.
1+1 HSB
configuration
SSM Protection
SSM protection uses the SSM protocol specified in ITU-T G.781 to provide clock protection.
According to the SSM protocol, SDH NEs transmit the SSM by using bits 5-8 of the S1 byte,
to implement automatic protection switching of clock sources and prevent timing loops. The
OptiX RTN 950 supports SSM protection on SDH optical transmission lines, FE/GE links, and
radio links. After SSM protection is enabled on an NE, automatic protection switching of clock
sources follows these rules:
l According to the clock source priority list, the NE selects the clock source of the highest
quality as the synchronization source.
l If multiple clock sources have the same highest quality, the NE selects the source with the
highest priority as the synchronization source.
l The NE broadcasts quality information about the synchronization clock source to its
downstream NEs and also notifies its upstream NE that its own clock source cannot be used
for synchronization.
When the network operates normally, the NEs on the ring select the clock source as follows:
1. NE1 selects the external clock source as the synchronization source and notifies NE2 and
NE4 of the external clock quality.
2. NE2 and NE4 select the clock source from NE1 as the synchronization source and notify
NE1 that the clock sources from NE2 and NE4 are unavailable.
3. After determining that the clock sources from NE2 and NE4 have the same quality, NE3
selects the clock source with a higher priority (the clock source from NE2) as the
synchronization source. In addition, NE3 transmits quality information about the
synchronization source to NE4 and notifies NE2 that the clock source from NE3 is
unavailable.
4. After determining that the clock sources from NE1 and NE3 have the same quality, NE4
selects the clock source with a higher priority (the clock source from NE3) as the
synchronization source. In addition, NE4 transmits quality information about the
synchronization source to NE1 and notifies NE3 that the clock source from NE4 is
unavailable.
5. According to the clock quality in the west and east directions and configured clock source
priorities, NE2, NE3, and NE4 determine that the synchronization source does not need to
be modified. The clock source selection is completed.
When the radio links between NE1 and NE2 become faulty, the NEs on the ring select the clock
source as follows:
1. NE2 selects the internal source as the synchronization source and transmits quality
information about the synchronization source to NE1 and NE3.
2. NE3 selects NE2 as the clock source and notifies NE4 of the clock quality.
3. After determining that the quality of the clock from NE1 is higher than the quality of the
clock from NE3, NE4 selects the clock source from NE1 as the synchronization source. In
addition, NE4 transmits quality information about the synchronization source to NE3 and
notifies NE1 that the clock from NE4 is unavailable.
4. After determining that the quality of the clock from NE4 is higher than the quality of the
clock from NE2, NE3 selects the clock source from NE4 as the synchronization source. In
addition, NE3 transmits quality information about the synchronization source to NE2 and
notifies NE4 that the clock source from NE3 is unavailable.
5. After determining that the quality of the clock from NE3 is higher than the quality of the
internal clock source, NE2 selects the clock source from NE3 as the synchronization source.
In addition, NE2 transmits quality information about the synchronization source to NE1
and notifies NE3 that the clock source from NE2 is unavailable.
6. According to the clock quality in the west and east directions and the configured clock
source priorities, NE2, NE3, and NE4 determine that the synchronization source does not
need to be modified. The clock source selection is completed.
NOTE
SSM protection cannot prevent timing loops. Therefore, when configuring clock sources, ensure that clock
sources do not form a timing loop. For example, configuration of clock sources on NE1 prevents a timing loop,
as shown in Figure 12-2.
E W
W E
West/East/
West/East/
Internal
Internal
NE2 W NE4
E
W E
After extended SSM protection is enabled on an NE, automatic clock switching follows these
rules:
l According to the clock source priority list, the NE selects the clock source of the highest
quality as the synchronization source.
l If the clock ID of a clock source indicates that the clock source is from the local NE, the
clock source is not processed.
l If multiple clock sources have the same highest quality, the NE selects the source with the
highest priority as the synchronization source.
l The NE broadcasts quality information and the clock ID of the synchronization clock source
to its downstream NEs, and also notifies its upstream NE that its own clock source cannot
be used for synchronization.
The clock ID takes a value in the range of 0 to 15. 0 is the default value, indicating that the clock
ID is invalid. After the extended SSM protocol is enabled on the NE, the NE does not select any
clock source with an ID of 0 as its current clock source.
l When the extended SSM is used, the clock ID of an external clock source cannot be
automatically extracted. Therefore, allocate clock IDs to all external clock sources.
l At all the NEs that are connected to external clock sources, allocate clock IDs to the internal
clock sources.
l At all the intersecting nodes of a ring/chain and a ring, allocate clock IDs to the internal
clock sources.
l At all the intersecting nodes of a ring/chain and a ring, allocate clock IDs to the clock
sources that are transmitted to the ring.
l Do not allocate clock IDs to clock sources different from the preceding four types. Their
clock IDs are 0 by default.
l Clock IDs do not determine clock source priorities.
Figure 12-3 is a radio ring where the extended SSM protection is enabled.
E W
W E
West / East /
West / East /
Internal
Internal
NE2 E W NE4
W E
West /
East /
NE3 Extenal 2 /
Master clock Internal
Slave BITS
NOTE
l When extended SSM protection is enabled, clocks can constitute a ring during clock source configuration.
l Extended SSM protection is advantageous in complex clock protection network topologies, for example, in
a network with dual external clocks. Therefore, extended SSM protection is used in only a few scenarios.
l If one clock source is input into the master (source) node (the clock source can be an external
clock, a line clock, or an Ethernet clock), configure this clock source for this node.
l For the other nodes, configure the clock sources from their upper level radio links.
l If 1+1 protection is configured for the upper level radio links of a node, configure two radio
clock sources for this node. The clock source on the active radio link has a higher priority
than the clock source on the standby radio link.
l If a node has multiple upper level radio links (for example, the upper level radio links use
the XPIC or N+1 protection configuration), configure one radio clock source for each radio
link. Allocate priorities to these radio clock sources depending on the radio link status.
l Do not configure synchronization status message (SSM) or extended SSM protection.
Figure 12-4 shows the clock synchronization policy for a chain network.
l On the master node (NE1), one external clock source is input. For NE1, clock source
priorities are allocated in descending order as follows: external clock source > internal clock
source.
l The ISU2 boards in slots 3 and 5 on NE2 form a 1+1 IF protection group, where the ISU2
board in slot 3 functions as the main board; in addition, the radio links between NE1 and
NE2 comprise the two ISU2 boards. For NE2, clock source priorities are allocated in
descending order as follows: 3-ISU2-1 > 5-ISU2-1 > internal clock source.
l The radio link between NE3 and NE2 comprises the ISU2 board in slot 3 on NE3. For NE3,
clock source priorities are allocated in descending order as follows: 3-ISU2-1 > internal
clock source.
l Do not configure SSM or extended SSM protection.
BITS 3-IF1-1/
Extenal/ 3-IF1-1/
5-IF1-1/
Internal Internal
Internal
Clock
Figure 12-5 shows the clock synchronization policy for a tree network.
l On the master node (NE1), the Ethernet link connected to port 1 on the EM6T board in slot
2 provides a clock source. For NE1, clock source priorities are allocated in descending
order as follows: 2-EM6T-1 > internal clock source.
l The ISX2 boards in slots 3 and 5 on NE2 form an XPIC workgroup, where the ISX2 board
in slot 3 uses the vertical polarization mode and the ISX2 board in slot 5 uses the horizontal
polarization mode; in addition, the radio links between NE1 and NE2 comprise the two
ISX2 boards. For NE2, clock source priorities are allocated in descending order as follows:
3-ISX2-1 > 5-ISX2-1 > internal clock source.
l The radio link between NE3 and NE2 comprises the ISU2 board in slot 3 on NE3. For NE3,
clock source priorities are allocated in descending order as follows: 3-ISU2-1 > internal
clock source.
l The radio link between NE4 and NE2 comprises the ISU2 board in slot 3 on NE4. For NE4,
clock source priorities are allocated in descending order as follows: 3-ISU2-1 > internal
clock source.
l The radio link between NE5 and NE4 comprises the ISU2 board in slot 3 on NE5. For NE5,
clock source priorities are allocated in descending order as follows: 3-ISU2-1 > internal
clock source.
l Do not configure SSM or extended SSM protection.
NE3
3-ISU2-1/
NE1 NE2 Internal
NE4 NE5
BSC
2-EM6T-1/ 3-ISX2-1/
Internal 5-ISX2-1/
Internal
Clock 3-ISU2-1/ 3-ISU2-1/
Internal Internal
Figure 12-6 Clock synchronization Policy for a ring network (consisting of Integrated IP
radio only)
BSC NE1
3-EM6T-1/
Internal
E W
W E Eest/
West/
East/ SSM West/
Internal Internal
NE2 W NE4
E
W E
West/
East/
NE3 Internal
Clock
l For a ring network consisting of PDH radio links, the clock synchronization policy should
be planned according to the following principle:
Divide the ring into two chains and configure the clock synchronization policy separately
on each chain.
Figure 12-7 shows the clock synchronization policy for a ring network consisting of only
PDH radio links.
– The ring is divided into two chains: NE1-NE2-NE3 and NE1-NE4.
– NE1, the master node, traces the external clock source. Therefore, the clock source
priorities for NE1 in descending order are: external clock source > internal clock source.
– NE2 traces the clock of NE1. Therefore, the clock source priorities for NE2 in
descending order are: west clock source > internal clock source.
– NE3 traces the clock of NE2. Therefore, the clock source priorities for NE3 in
descending order are: west clock source > internal clock source.
– NE4 traces the clock of NE1. Therefore, the clock source priorities for NE4 in
descending order are: east clock source > internal clock source.
– Do not configure SSM or extended SSM.
Figure 12-7 Clock synchronization policy for a ring network (consisting of PDH radio
links)
BITS NE1
External/
Internal
E W
W E
West/ East/
Internal Internal
NE2 W NE4
E
W E
West/
Internal
NE3
Clock
l On the upper level NE, a clock source (which can be an external clock source, a line clock
source, or an Ethernet clock source) is input.
l A lower-level NE traces the line clock source or the Ethernet clock source of its upper-level
NE, if the service of the lower-level NE is aggregated to the upper-level NE through an
optical transmission line or Ethernet.
l If the service of a lower-level NE is aggregated to the upper-level NE only through the E1
signal, the lower-level NE should trace the tributary clock source (E1 ports 1 and 5 on the
E1 tributary board support the tributary clock source).
l If the service of a lower-level NE is aggregated to the upper-level NE only through the E1
signal and the lower-level NE is connected to many hops of downstream radio links, tracing
the tributary clock source causes pointer justifications or other exceptions. Therefore, the
lower-level NE should trace the external clock source output by its upper level NE.
l Do not configure SSM or extended SSM protection.
Figure 12-8 shows the clock synchronization policy for a tributary port aggregation network.
l On the master node (NE1), one external clock source is input. For NE1, clock source
priorities are allocated in descending order as follows: external clock source > internal clock
source.
l The IF1 boards in slots 3 and 5 on NE2 form 1+1 IF protection, where the IF1 board in slot
3 functions as the main board; in addition, the radio links between NE1 and NE2 comprise
the two IF1 boards. For NE2, clock source priorities are allocated in descending order as
follows: 3-IF1-1 > 5-IF1-1 > internal clock source.
l The services of NE3 are aggregate to NE2 through ports 1 to 4 on the SP3S board in slot
1. For NE3, clock source priorities are allocated in descending order as follows: 1-SP3S-1
> internal clock source.
l NE4 is connected to many hops of downstream radio links. If it traces the tributary clock
source, pointer justifications occur on the downstream nodes. Therefore, NE4 traces the
external clock source output by NE2.
l Do not configure SSM or extended SSM protection.
Figure 12-8 Clock synchronization policy for a port aggregation network (aggregation only
through the tributary port)
NE3
NE1 NE2
1-SP3S-1/
Internal
External/ 3-IF1-1/ NE4
Internal 5-IF1-1/
Internal
External/
Clock Internal
Figure 12-9 shows the clock synchronization policy for transmission across a TDM network.
l The master node NE1 is synchronized with the BSC through the FE port. For NE1, clock
source priorities are allocated in descending order as follows: 3-EFP8-1 > internal clock
source.
NOTE
The FE ports on the EFP8 board (PORT1 to PORT8) support synchronous Ethernet.
l On NE2, the SP3D board in slot 2 provides the E1 link connected to the TDM network,
and this NE is a lower-level node connected to the TDM network. For NE2, clock source
priorities are allocated in descending order as follows: 2-SP3D-1 > internal clock source.
l The ISU2 boards in slots 3 and 5 on NE3 form a 1+1 IF protection group, where the ISU2
board in slot 3 functions as the main board; in addition, the radio links between NE3 and
NE2 comprise the two ISU2 boards. For NE3, clock source priorities are allocated in
descending order as follows: 3-ISU2-1 > 5-ISU2-1 > internal clock source.
l Do not configure SSM or extended SSM protection.
Figure 12-9 Clock synchronization policy for transmission across a TDM network
FE E1 E1 FE
TDM network
Tributary Retiming
When being transmitted by the OptiX RTN 950, the PDH signal must undergo mapping and
demapping processes, during which the jitter occurs. In addition, pointer justifications during
the network transmission process cause the jitter of the PDH signal.
Tributary retiming helps to reduce the jitter of the PDH signal when it is transmitted on a
transmission network. Tributary retiming achieves transmission of the signal that combines the
timing reference signal and the PDH service signal. Hence, the transmitted PDH signal carries
the timing information that is synchronized with the timing reference signal.
Figure 12-10 shows how a BSC transmits the synchronization information to a BTS through
the radio transmission network after the tributary retiming function is enabled. The radio
transmission network extracts the tributary clock from the E1 signal that is transmitted from the
BSC. This tributary clock functions as the synchronization reference clock for the radio
transmission network to be synchronized with the clock of the BSC. The tributary retiming
function is enabled on NE3. In this manner, NE3 transmits the E1 signal that carries the retiming
clock information to the BTS (NE3 selects the system clock as the retiming clock). In addition,
NE3 is synchronized with the BSC. Hence, the BTS can extract the clock signal of the BSC from
the tributary signal.
The basic working principle of tributary retiming is as follows: The tributary signal is written
into a large-capacity first in first output (FIFO), and then the tributary signal is read from the
FIFO through the retiming clock. In this manner, the output signal contains the retiming clock
information, and FIFO eliminates the jitter and wander in the original tributary signal. The OptiX
RTN 950 can select the system clock or the line clock in the uplink E1 signal as the retiming
clock, depending on the specific networking. In general cases, the system clock is selected as
the retiming clock.
E1 E1
BSC
NE3
Write clk
Clock (downlink E1 clk)
E1 E1
FIFO
Read clk
(retiming clk)
When using the tributary retiming function, pay attention to the following points:
l The retiming clock should be synchronized with the clock of the BSC, and the retiming
clock should not undergo mapping and demapping processes.
l The tributary retiming function uses the FIFO. This causes a delay of 125 us or more. Use
this function only when it is necessary.
l The retiming function requires that the entire transmission network should be synchronized
with the service network that requires retiming. If certain NEs on the transmission network
are not synchronized, slips occur.
l The transmission network can meet the retiming requirement of only one service network.
Optional
Configuring clock sources
Modifying parameters of
the output clock
End
A.10.1.3 Optional.
User-
Defined
Clock
Quality
6 A.10.1.6 Modifying the Optional when the external clock port is used to
Parameters of the transmit the clock reference signal for the customer
Clock Output equipment.
Set the parameters according to the requirement of
the customer equipment. In general cases, these
parameters take the default values.
7 A.6.2 Setting the Optional when the output tributary clock requires
Parameters of PDH retiming.
Ports Set Retiming Mode to Retiming Mode of Cross-
Connect Clock for the tributary port.
8 A.10.1.10 Querying the l When a clock subnet uses the internal clock
Clock Synchronization source of an NE as the reference clock, set NE
Status Clock Mode to Free-Run Mode for this NE; set
NE Clock Mode to Tracing Mode for the other
NEs.
l When a clock subnet uses the clock out of the
subnet as the reference clock, set NE Clock
Mode to Tracing Mode for all the NEs.
Based on 6.3 Configuration Example (Radio Links on the TDM Radio Chain Network),
configure the clocks according to the following network planning information (as shown in
Figure 12-12):
l The radio transmission network is directly synchronized with the clock of the upstream
third-party network.
l Clock synchronization signals are transmitted to the BTSs over E1 signals.
BTS2 E1
STM-1 STM-1
E1
NE4
BTS3
E1
NE3 NE2 NE1 BSC
E1 BTS1
E1
NE6 NE5
BTS5 BTS4
Between NE11 and the third- 1-SL1D-1 (working port of a Configure these ports to
party network linear MSP group) synchronize clock signals
with the upstream third-party
1-SL1D-2 (protection port of network.
a linear MSP group)
Between NE12 and NE11 3-IF1 (main IF board of a 1+1 Configure these boards to
HSB protection group) synchronize clock signals
with the upstream third-party
5-IF1 (standby IF board of a network.
1+1 HSB protection group)
Between NE14 and NE13 3-IF1 (main IF board of a 1+1 Configure these boards to
HSB protection group) synchronize clock signals
with the upstream third-party
5-IF1 (standby IF board of a network.
1+1 HSB protection group)
Between NE15 and NE13 4-IF1 (main IF board of a 1+1 Configure these boards to
HSB protection group) synchronize clock signals
with the upstream third-party
6-IF1 (standby IF board of a network.
1+1 HSB protection group)
STM-1 STM-1
NE14
Third party
network
NE13 NE12 NE11
3-IF1-1/ 1-SL1D-1/
1-SL1D-1/ 1-SL1D-2/
5-IF1-1/
Internal Internal
Internal
NE16 NE15
4-IF1-1/
3-IF1-1/ 6-IF1-1/
Internal Internal
Clock
Clock Protection
In this example, a chain network is set up. Thus, only the clock source protection based on
priorities is needed, whereas the SSM or extended SSM protection need not be configured.
Procedure
Step 1 See A.10.1.1 Configuring the Clock Sources and configure the clock sources.
Paramete Value
r
NE1 NE2 NE3 NE4 NE5 NE6
Step 2 See A.10.1.10 Querying the Clock Synchronization Status and query the clock
synchronization status of the NEs.
NE Clock Mode of all the NEs should be Tracing Mode.
----End
Based on 6.4 Configuration Example (Radio Links on the TDM Radio Ring Network),
configure the clocks according to the following network planning information (as shown in
Figure 12-14):
l The radio transmission network is directly synchronized with the clock of the upstream
third-party network.
l Clock synchronization signals are transmitted to the BTSs over E1 signals.
Third party
E1
network NE21
E1
BTS21 E1
BTS22
E1
NE23
BTS23
Between NE21 and the third- 2-SP3S Configure this board for
party network synchronizing NE21 with the
clock of the upstream third-
party network.
Between NE22 and BTS21 2-SP3S The ports are used for
enabling the re-timing
Between NE22 and BTS22 2-SP3S function so that the BTSs can
be more precisely
synchronized with the clock
of the upstream third-party
network.
Between NE23 and BTS23 2-SP3S This port is used for enabling
the re-timing function so that
the BTS can be more
precisely synchronized with
the clock of The ports are
used for enabling the re-
timing function so that the
BTSs can be more precisely
synchronized with the clock
of the upstream third-party
network.
Between NE24 and NE21 4-IF1 (main IF board of a 1+1 Configure these boards to
HSB protection group) synchronize clock signals
with the upstream third-party
6-IF1 (standby IF board of a network.
1+1 HSB protection group)
NE22 NE24
3-IF1-1 4-IF1-1/
Internal 6-IF1-1
Internal
Clock NE23
3-IF1-1/
Internal
Clock Protection
In this example, a PDH radio ring network is set up. Thus, only the clock source protection based
on priorities is needed, whereas the SSM or extended SSM protection need not be configured.
In application, the external clock port, rather than the E1 port, is preferred to transmit the timing reference signal
to a BTS.
Procedure
Step 1 See A.10.1.1 Configuring the Clock Sources and configure the clock sources.
Parameter Value
Step 2 See A.6.2 Setting the Parameters of PDH Ports and set the PDH port parameters.
Parameter Value
Step 3 See A.10.1.10 Querying the Clock Synchronization Status and query the clock
synchronization status of the NEs.
NE Clock Mode of all the NEs should be Tracing Mode.
----End
Based on 6.5 Configuration Example (Radio Links on the Hybrid Radio Chain Network),
configure the clocks according to the following network planning information (as shown in
Figure 12-16):
l The radio transmission network is directly synchronized with the clock of the BSC through
a LAG consisting of two GE links.
l Clock synchronization signals are transmitted to the BTSs over FE signals.
FE
BTS2
GE GE
FE NE4
BTS3
FE
NE3 NE2 NE1 BSC
FE BTS1
FE
NE6 NE5
BTS5 BTS4
Between NE1 and the BSC 1-EM6F-1 (main port of a The ports are used to
LAG) synchronizing NE1 with the
clock of the BSC.
1-EM6F-2 (slave port of a
LAG)
Between NE2 and NE1 3-ISU2 (main IF board of a 1 The ports are used to
+1 HSB protection group) synchronizing NE2 with the
clock of the BSC.
5-ISU2 (standby IF board of
a 1+1 HSB protection group)
Between NE4 and NE3 3-ISU2 (main IF board of a 1 The ports are used to
+1 HSB protection group) synchronizing NE4 with the
clock of the BSC.
5-ISU2 (standby IF board of
a 1+1 HSB protection group)
Between NE5 and NE3 4-ISU2 (main IF board of a 1 The ports are used to
+1 HSB protection group) synchronizing NE5 with the
clock of the BSC.
6-ISU2 (standby IF board of
a 1+1 HSB protection group)
Figure 12-17 Networking diagram (clock for a Hybrid radio chain network)
3-ISU2-1/
5-ISU2-1
Internal
GE
NE4 GE
NOTE
Separately configure the Ethernet clock source for each link in the LAG.
Clock Protection
In this example, a chain network is set up. Thus, only the clock source protection based on
priorities is needed, whereas the SSM or extended SSM protection need not be configured.
Procedure
Step 1 See A.10.1.1 Configuring the Clock Sources and configure the clock sources.
Paramete Value
r
NE1 NE2 NE3 NE4 NE5 NE6
Step 2 See A.10.1.10 Querying the Clock Synchronization Status and query the clock
synchronization status of the NEs.
NE Clock Mode of all the NEs should be Tracing Mode.
----End
Based on 6.6 Configuration Example (Radio Links on the Hybrid Radio Ring Network),
configure the clocks according to the following network planning information (as shown in
Figure 12-18):
l The Hybrid radio transmission network is synchronized with NE21 on the PSN.
l OptiX RTN NEs transmit clock synchronization signals through their E1/FE ports to 2G/
3G base stations.
Packet network
R4
FE NE21
BTS21
FE
R4
BTS22
FE
NE23 R4
BTS23
Between NE22 and NE21 3-ISU2 (high-priority clock Configure these ports to
source, with the SSM implement clock
protocol enabled) synchronization with the
upstream PSN.
Between NE22 and NE23 4-ISU2 (low-priority clock
source, with the SSM
protocol enabled)
Between NE23 and NE22 3-ISU2 (high-priority clock Configure these ports to
source, with the SSM implement clock
protocol enabled) synchronization with the
upstream PSN.
Between NE23 and NE24 4-ISU2 (low-priority clock
source, with the SSM
protocol enabled)
Between NE24 and NE21 4-ISU2 (main IF board in a 1 Configure these ports to
+1 HSB protection group; implement clock
high-priority clock source, synchronization with the
with the SSM protocol upstream PSN.
enabled)
Figure 12-19 Information about clock sources (Hybrid radio ring network)
Packet network
NE21
NE22 NE24
3-ISU2-1/ 4-ISU2-1/
4-ISU2-1/ 6-ISU2-1/
Internal 3-ISU2-1/
Internal
NE23
3-ISU2-1/
4-ISU2-1/
Clock Internal
Clock Protection
The standard SSM protocol is enabled for all NEs on the ring network.
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.
NOTE
CES retiming is the default clock recovery solution for PSNs and therefore does not need to be enabled manually.
NOTE
Synchronous Ethernet is the default clock recovery solution for PSNs and therefore does not need to be enabled
manually.
Procedure
Step 1 See A.10.1.1 Configuring the Clock Sources and configure the clock sources.
Parameter Value
Step 2 See A.10.1.2 Configuring Clock Subnets and configure protection for clock sources.
For NE22 to NE24, the values for the related parameters are provided as follows.
Parameter Value
NOTE
The other parameters take their default values.
Step 3 See A.10.1.10 Querying the Clock Synchronization Status and query the clock
synchronization status.
NE Clock Mode of all NEs should be Tracing Mode.
----End
Based on 4.2 Common Network Scenario of the IP Radio Network, configure the clocks
according to the following network planning information (as shown in Figure 12-20):
l The BSC and RNC are synchronized with an external BITS clock.
l The PSN is synchronized with the same BITS clock as the BSC and RNC. The NEs on the
PSN are synchronized with each other through physical clocks (clocks from microwave
ports or clocks from Ethernet ports using the synchronous Ethernet function).
l The PSN transmits clock synchronization signals through its E1/FE ports to 2G/3G base
stations.
FE
BTS31
R4
BTS32
E1 E1 R4
FE
R99
BTS34 GE GE
NE32
Hybrid radio chain
NE11 NE31
network
E1
GE
NE21 GE
E1
E1
E1
+G
BSC
E
RNC
Between NE31 and a BITS External clock port Configure the external clock
port (CLK/TOD1) on the
CSH board to implement
clock synchronization with
the external BITS clock.
Between NE33 and NE32 4-ISU2 (main IF board in a 1 Configure microwave clocks
+1 HSB protection group) to implement clock
synchronization with the
6-ISU2 (standby IF board of upstream clock.
a 1+1 HSB protection group)
Between NE34 and NE33 3-ISU2 (main IF board in a 1 Configure a microwave clock
+1 HSB protection group) to implement clock
synchronization with the
upstream clock.
BTS31
R4
FE
E1 FE
E1 R4
R99
BTS34 BTS32 GE GE
NE32
GE E1
+G
BSC
E
BTS36 BTS35
R99 R99
BTS37 BTS38
Clock RNC
Clock Protection
The standard SSM protocol is enabled for all NEs on the ring network.
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.
NOTE
CES retiming is the default clock recovery solution for PSNs and therefore does not need to be enabled manually.
NOTE
Synchronous Ethernet is the default clock recovery solution for PSNs and therefore does not need to be enabled
manually.
Procedure
Step 1 See A.10.1.1 Configuring the Clock Sources and configure clock sources.
Paramete Value
r
NE11 NE21 NE31 NE32 NE33 NE34
Step 2 See A.10.1.2 Configuring Clock Subnets and configure protection for clock sources.
For NE11, NE21, and NE31 to NE34, the values for the related parameters are provided as
follows.
Parameter Value
NOTE
The other parameters take their default values.
Step 3 See A.10.1.10 Querying the Clock Synchronization Status and query the clock
synchronization status.
NE Clock Mode of all NEs should be Tracing Mode.
----End
l The transmission network is directly synchronized with the clock of the BSC through FE
ports.
l Clock synchronization signals are transmitted to the BTS over FE ports.
NOTE
This example only describes the clock configuration on NE1 and NE7. For the clock configuration on NE2-
NE6, see 12.5 Configuration Example (Clock for a Hybrid Radio Chain Network).
BTS6
FE
FE
GE
FE NE4 TDM
FE E1 network
NE3 NE2 NE1
E1
FE
FE BTS1
FE
NE6 NE5 NE7
BSC
BTS4
BTS5
E1
CSH
CSH CSH
ISU2 NE6
NE6
ISU2 NE6
ISU2 ISU2
EFP8
SP3D
EM6T SP3S EM6T SP3S
NE6 NE5 NE7 FE
FE E1
BTS5 BSC
The following figure shows the clock link connections of NE1 and NE7.
Figure 12-24 Information about clock sources (Hybrid radio chain network)
3-IFU2-1/
Internal
GE
NE4 TDM
E1 network
NE3 NE2 NE1
1-EM6T-1/ 3-IFU2-1/ 2-SP3D-1/ E1
Internal 5-IFU2-1 Internal
FE
Internal
NE6 NE5
4-IFU2-1/ NE7
3-IFU2-1/ 6-IFU2-1 BSC
Internal Internal 4-EFP8-1/
Internal
Clock
NOTE
This example only describes the clock configuration on NE1 and NE7. For the clock configuration on NE2-
NE6, see 12.5 Configuration Example (Clock for a Hybrid Radio Chain Network).
Clock Protection
In this example, a chain network is set up. Therefore, only the clock source protection based on
priorities is configured and the SSM or extended SSM protection is not configured.
Procedure
Step 1 See A.10.1.1 Configuring the Clock Sources and configure the clock sources.
NE1 NE7
Step 2 See A.10.1.10 Querying the Clock Synchronization Status and query the clock
synchronization status of the NEs.
For all NEs, set NE Clock Mode to Tracing Mode.
----End
The OptiX RTN 950 provides multiple auxiliary ports and functions. These functions require
certain data configuration.
Orderwire
The OptiX RTN 950 supports one orderwire phone so that the operation or maintenance
engineers at different workstations can perform voice communication through microwave or
SDH overhead bytes.
l The orderwire phone numbers of all the NEs on the network must be of the same length.
It is recommended that the orderwire telephone number is a 3-digit number and all orderwire
telephone numbers on the entire network are unique.
l The dialing method of the orderwire phone of each node is dual-tone multifrequency.
l The call waiting time of each node should be set to the same value. If less than 30 nodes
exist in the orderwire subnet, it is recommended that you set the call waiting time to five
seconds. If more than 30 nodes exist in the orderwire subnet, it is recommended that you
set the call waiting time to nine seconds.
l The equipment supports the orderwire group call function. When one set of the OptiX RTN
equipment dials the orderwire group call number "888", the orderwire phones of all the
OptiX equipment on the orderwire subnet ring. When an orderwire phone receives the call,
the orderwire phones on the other NEs stop ringing. In this case, the orderwire point-to-
multipoint group call changes to a point-to-point ordinary orderwire call.
l When the orderwire signals are transmitted over a radio link, they are always transmitted
through one customized overhead byte. When the orderwire signals are transmitted over
SDH fibers, they are transmitted through the E1 or E2 byte.
l By default, all the line ports, IF ports, and unconfigured synchronous data ports on the
equipment function as the orderwire ports. Therefore, in normal cases, the orderwire ports
needs to be configured only at the edge of the orderwire subnet.
l The equipment supports the transmission of orderwire overhead bytes through the 64 kbit/
s synchronous data ports or external clock ports.
l If multiple radio links or optical transmission lines exist between two NEs, the ports
corresponding to these links should be configured as the orderwire ports. In this case, except
for the hybrid radio links in N+1 protection, if one radio link is available between two NEs,
the orderwire transmission between two NEs is normal. When the orderwire signals are
transmitted over the hybrid radio links in N+1 protection, the protection link cannot transmit
the orderwire signals.
l The equipment provides the orderwire ports on the AUX board. For definitions of the pins
on the ports, see the OptiX RTN 950 IDU Hardware Description.
When using the synchronous data service, take the following precautions:
l The synchronous data service is fully transparently transmitted, and the transmission rate
at the port is 64 kbit/s.
l The synchronous data service is clock-sensitive. If the clock is not synchronized, bit errors
occur.
l The ports on the equipment comply with ITU-T G.703.
l When the orderwire signals are transmitted over a radio link, they are always transmitted
through one customized overhead byte. When the orderwire signals are transmitted over
SDH fibers, they are always transmitted through the F1 byte.
l The equipment supports the transmission of the overhead bytes in the synchronous data
service through the external clock ports to realize the service spanning function.
l When the synchronous data service is transmitted over the protected radio links or optical
transmission lines, the synchronous data service is also protected.
l The equipment provides the synchronous data service ports on the AUX. For definitions
of the pins on the ports, see the OptiX RTN 950 IDU Hardware Description.
When using the asynchronous data service, take the following precautions:
l The asynchronous data service is fully transparently transmitted. The transmission rate and
transmission control protocol need not be configured. The transmission rate at the port 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 the RS-232 electrical port that complies with ITU-T V.24/V.28.
l The equipment supports only point-to-point communications.
l When the orderwire signals are transmitted over radio links, they are always transmitted
through one customized overhead byte. When the 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 the overhead bytes in the asynchronous data
service through the external clock ports to realize the service spanning function.
l When the asynchronous data service is transmitted over the protected radio links or optical
transmission lines, the asynchronous data service is also protected.
l The equipment provides the asynchronous data ports on the AUX board. For definitions of
the pins on the ports, see the OptiX RTN 950 IDU Hardware Description.
Wayside E1 Services
The OptiX RTN 950 supports one wayside E1 service. The transmitted overhead bytes in the
STM-1 radio signals can be used for transmitting one wayside E1 service between two sites in
one hop of STM-1 radio link.
When using the wayside E1 service, take the following precautions:
l The wayside E1 service is supported by only STM-1 radio links or E1 radio links.
l The wayside E1 service is fully and transparently transmitted, and the transmission rate at
the port is 2048 kbit/s.
l The wayside E1 service is clock-sensitive. If the clock is not synchronized, bit errors occur.
l The equipment does not support the pass-through of the wayside E1 service. Therefore, the
wayside E1 service is transmitted only between two sites on one hop of radio link.
l When the wayside E1 service is transmitted over the radio links in 1+1 or N+1 protection
mode, the wayside E1 service is also protected.
l The equipment adds or drops the wayside E1 service through the external clock port on the
SCC, cross-connect and clock board. The external clock port complies with ITU-T G.703,
and the impedance on the path is 120 ohms. For definitions of the pins on the external clock
ports, see the OptiX RTN 950DU Hardware Description.
External Alarms
External alarms are also called housekeeping alarms or relay alarms. The OptiX RTN 950
provides 4-input and 2-output external alarms.
Figure 13-1 shows the interface circuit for external alarm input. When the external relay is
switched off, the interface circuit generates a high-level signal. When the external relay is
switched on, the interface circuit generates a low-level signal. The board generates
corresponding alarms based on the level signal. External alarm input mainly achieves access of
the relay alarms generated by the environmental alarm generator.
The interface circuit for external alarm output works in a similar manner as the external system
shown in Figure 13-1. When the specified external alarm output conditions are met, the NE
switches on or switches off the relay depending on the conditions that result in the alarm. When
the specified external alarm output conditions are no longer met, the NE changes the relay to
the reverse of its current state. External alarm output helps to provide equipment alarms to the
centralized alarming device.
The equipment provides external alarm ports on the AUX board. For pin assignments for the
ports, see the OptiX RTN 950 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 7U of 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 11U of space for installing user
equipment.
l OMB: The outdoor mini box (OMB) cabinet supports AC or DC power input. It provides
2U of space for installing user equipment.
NOTE
On the NMS, an outdoor cabinet is named based on its power input mode: An APM30H cabinet is named
APM30 AC, a TCM11H cabinet is named APM30 DC, an OMB (AC power input) cabinet is named OMB
AC, and an OMB (DC power input) cabinet is named OMB DC.
Table 13-1 describes the logical slots of outdoor cabinets supported by the OptiX RTN 950 and
their functions.
The OptiX RTN 950 provides the outdoor cabinet monitoring port on its system control,
switching, and timing board. For pin assignments for the port, see the OptiX RTN 950 IDU
Hardware Description.
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
Table 13-2 Procedures for configuring the function of monitoring the outdoor cabinet
In the networking diagram shown in Figure 13-3, each NE needs to be configured with the
orderwire. Except that the radio links between NE1 and NE2 are configured with 1+1 protection,
all the other radio links are configured with 1+0 non-protection.
1+0
1+1
64kpbs
NE4
1+0
NE3 NE2 NE1
1+0
NE6 NE5
Between NE1 and NE2 3-IFU2 (main IF board) Configure the ports to
implement IF 1+1 protection.
5-IFU2 (standby IF board)
Between NE2 and NE1 3-IFU2 (main IF board) Configure the ports to
implement IF 1+1 protection.
5-IFU2 (standby IF board)
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-IFU2-1
5-IFU2-1
NE Orderwire Port
NE2 3-IFU2-1
5-IFU2-1
F1
NE3 3-IFU2-1
4-IFU2-1
F1
NE4 3-IFU2-1
NE5 3-IFU2-1
4-IFU2-1
NE6 3-IFU2-1
NOTE
l An external clock port can also be used to realize service spanning between NE2 and NE3. In this case, the
external clock port needs to be added to the orderwire port through the NMS.
l Certain orderwire ports are unnecessary. These ports do not, however, affect the orderwire phones if they
do not receive orderwire signaling.
Procedure
Step 1 See A.12.1 Configuring Orderwire and configure the orderwire.
Paramete Value
r
NE1 NE2 NE3 NE4 NE5 NE6
Call 5 5 5 5 5 5
Waiting
Time(s)
Paramete Value
r
NE1 NE2 NE3 NE4 NE5 NE6
----End
In the networking diagram shown in Figure 13-5, the radio network transmits the network
management messages of the third-party equipment. The third-party equipment and the NMS
use the protocol converter to convert the network management messages carried by the Ethernet
network into the network management messages carried by the 64 kbit/s synchronous data
service. Hence, the radio network needs to transparently transmit the corresponding synchronous
data only.
l NE1 and NE6 add or drop 64 kbit/s synchronous data services. NE2, NE3, and NE5 pass
through 64 kbit/s synchronous data services.
l Except that the radio links between NE1 and NE2 are configured with 1+1 protection, all
the other radio links are configured with 1+0 non-protection.
1+0
1+1
3rd party 64kpbs ETH
equipment NE4 64kbps
1+0
NE3 NE2 NE1 64k/ETH
1+0
ETH Converter
64kbps
NE6 NE5
64k/ETH
Converter
Between NE1 and NE2 3-IFU2 (main IF board of a 1 Configure the main IF board
+1 protection group) to transmit synchronous data
services.
Between NE2 and NE1 3-IFU2 (main IF board of a 1 Configure the main IF board
+1 protection group) to transmit synchronous data
services.
l In this example, the TDM service between NE2 and NE3 is forwarded through the E1 line.
Therefore, service spanning is required. The two synchronous data ports between NE2 and
NE3 are interconnected with each other to realize the service spanning function.
l According to the service path, you can obtain the synchronous data service information
provided in Table 13-15.
NE1 F1 3-IFU2-1
NE2 3-IFU2-1 F1
NE3 F1 4-IFU2-1
NE6 3-IFU2-1 F1
NOTE
l The external clock port can also be used to realize service spanning between NE2 and NE3.
l In the case of radio links or SDH optical transmission lines configured with 1+1 protection, only the active
link is configured with the synchronous data service.
Procedure
Step 1 See A.12.2 Configuring the Synchronous Data Service and configure the synchronous data
services.
Parameter Value
----End
In the networking diagram shown in Figure 13-6, the radio network transmits the network
management information of the third-party equipment. The third-party equipment and the NMS
use the protocol converter to convert the network management information carried by the
Ethernet network into the network management information carried by the RS-232 synchronous
data service. Hence, the radio network needs to transparently transmit the corresponding
synchronous data only.
l NE1 and NE6 add or drop asynchronous data services. NE2, NE3, and NE5 pass through
asynchronous data services.
l Except that the radio links between NE1 and NE2 are configured with 1+1 protection, all
the other radio links are configured with 1+0 non-protection.
1+0
1+1
3rd party RS-232 ETH
equipment NE4 RS-232
1+0
NE3 NE2 NE1 RS-232/ETH
1+0
ETH Converter
RS-232
NE6 NE5
RS-232/ETH
Converter
Between NE1 and NE2 3-IFU2 (main IF board of a 1 Configure the main IF board
+1 protection group) to transmit asynchronous
data services.
Between NE2 and NE1 3-IFU2 (main IF board of a 1 Configure the main IF board
+1 protection group) to transmit asynchronous
data services.
NOTE
l The external clock port can also be used to realize service spanning between NE2 and NE3.
l In the case of radio links or SDH optical transmission lines configured with 1+1 protection, only the active
link is configured with the asynchronous data service.
Procedure
Step 1 See A.12.3 Configuring the Asynchronous Data Service and configure the asynchronous data
services.
Parameter Value
----End
According to the service path, you can obtain the wayside E1 service information provided in
Table 13-22.
NOTE
In the case of radio links configured with 1+1 or N+1 protection, only the active link is configured with the
wayside E1 service.
Procedure
Step 1 See A.12.4 Configuring the Wayside E1 Service and configure the wayside E1 service.
Parameter Value
NE1 NE2
----End
In the networking diagram shown in Figure 13-8, the external alarms on NE1 are required as
follows:
l External alarm input port 1 is used for connecting the alarm port on the smoke sensor. When
the alarm port on the smoke sensor is closed, NE1 should report a fire alarm.
l External alarm input port 2 is used for connecting the alarm port on the water sensor. When
the alarm port on the water sensor is closed, NE1 should report a water alarm.
l External alarm input port 3 is used for connecting the alarm port on the magnetic door
switch sensor. When the alarm port on the magnetic door switch sensor is closed, NE1
should report an alarm, indicating that the cabinet door is open.
l External alarm output port 1 is used for connecting the centralized alarming boxes. When
a major or critical alarm is generated on NE1, the alarm output port is closed.
Magnetic door
Centralized
switch sensor
alarming box
NOTE
The OptiX RTN 950 supports the automatic mode and the manual mode. The manual mode is used for
commissioning the output alarms.
Procedure
Step 1 See A.12.5 Configure External Alarms and configure the external alarms.
l The values for the input alarm parameters are provided as follows.
Parameter Value
NE1
Alarm Mode Relay Turns On/ Relay Turns On/ Relay Turns On/
Low Level Low Level Low Level
l The values for the output alarm parameters are provided as follows.
Parameter Value
NE1
----End
In this example, the OptiX RTN 950 is installed in an APM30 AC cabinet. As shown in Figure
13-9, the TOD2 port (CSH) on the OptiX RTN 950 (NE1) is connected to the COM_IN port on
the APM30 AC cabinet. The OptiX RTN 950 supports the function of monitoring the PMU
temperature and humidity information after the upper and lower thresholds for temperature and
humidity alarms of the PMU are configured.
PMU
COM_IN
IDU
TOD2
Procedure
Step 1 Follow the instructions in A.12.6.1 Configuring the Function of an Auxiliary Port .
The values for the related parameters are provided as follows.
Parameter Value
7-CSH-2
Step 2 Follow the instructions in A.12.6.2 Setting the Type of the Outdoor Cabinet.
The values for the related parameters are provided as follows.
Parameter Value
Add the PMU logical board to slot 14 and the TCU logical boards to slots 15 and 16 on the Slot
Layout.
Step 4 Follow the instructions in A.12.6.6 Setting the Temperature and Humidity Alarm
Thresholds for the PMU.
The values for the ambient temperature and humidity parameters are provided as follows.
Parameter NE1-14–PMU
Upper threshold 60 95
Lower threshold -5 5
----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.2.1.1 Creating NEs l Generally, NEs
to perform centralized by Using the Search are created by
management of NEs, Method or A.2.1.2 searching for the
add the target NEs into Creating NEs by Using NE on the NMS.
the NE list. the Manual Method l The manual NE
creation method
is applicable only
when several NEs
need to be created
on a large radio
transmission
network.
Synchronizing After you conduct the A.2.1.8 Synchronizing To ensure that the NE
NE time settings on the NMS, the NE Time time is synchronized
the NE time is correctly, the time
synchronized and time domain of
automatically and the NMS server must
periodically. You can be set correctly.
also synchronize the
NE time manually if
the NE time is lost due
to NE faults.
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, STM-1 count, or
modulation mode is set inconsistently for both ends of an Integrated IP radio link. This alarm should
be cleared immediately. Otherwise, services may be configured unsuccessfully or interrupted.
Changing the You need to change the 1. A.5.6 Deleting Cross- If the capacity of the
radio working radio working mode of Connections existing TDM
mode of a a TDM radio link, if the services exceeds the
TDM radio link TDM radio link does capacity of the TDM
not meet the service radio link after the
capacity requirements. change, you need to
delete the cross-
connections of the
excessive TDM
services.
Changing the You can change the A.3.4 Configuring the In Power Attributes
transmit power transmit power if the IF/ODU Information of the ODU, change
fading margin is of a Radio Link TX Power(dBm) or
insufficient but the parameter values
transmit power can still associated with
be increased. power.
Changing the When the original A.6.8.6 Modifying the l Before using the
modulation modulation scheme Hybrid/AM Attributes new modulation
scheme of a does not meet the scheme, contact
Hybrid radio service requirements, the network
link you need to use another planning
modulation scheme. department to
confirm that the
Hybrid radio link
supports the 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 To adjust the number A.6.8.6 Modifying the l To reduce E1s
number of E1s of E1s and Ethernet Hybrid/AM Attributes with high
on a Hybrid bandwidth, you need to priorities, you
radio link change the number of need to delete the
E1s on the Hybrid corresponding
radio link. cross-connections
before changing
Guarantee E1
Capacity. The
change does not
affect other E1
services or cause
Ethernet service
interruptions.
l To increase E1s
with high
priorities, you
need to add the
corresponding
cross-connections
after changing
Guarantee E1
Capacity. The
change does not
affect other E1
services or cause
Ethernet service
interruptions.
NOTE
The number of
added E1s should
be within the
specified range.
l To reduce E1s
with low
priorities, you
need to delete the
corresponding
cross-connections
before changing
Full E1
Capacity. The
change does not
affect other E1
services or cause
Ethernet service
interruptions.
l To increase E1s
with low
priorities, you
need to add the
corresponding
cross-connections
after changing
Full E1
Capacity. The
change does not
affect other E1
services or cause
Ethernet service
interruptions.
NOTE
The number of
added E1s should
be within the
specified range.
l The
MW_CFG_MIS
MATCH alarm
occurs when the
number of E1
services is
different on both
ends of the radio
link. The alarm
clears when the
number of E1
services is the
same on both ends
of the radio link.
Changing the You can change the A.5.3 Modifying the l When you change
priority of E1 priority of E1 services Priorities of E1 the priority of an
services on a on a Hybrid radio link. Services E1, the E1 is
Hybrid radio interrupted
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.
Changing The Ethernet LAN A.8.3.3 Changing the Ports You need to
logical ports service requirements Connected to a VB add or delete
connected to a change. As a result, the the logical port
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.
A Task Collection
Prerequisites
The equipment is powered on.
Procedure
Step 1 Start the laptop and log in to the operating system.
l The IP address of the laptop is in the same network segment (the default network segment
is 129.9.0.0) as the NE, but their IP addresses are different.
l The subnet mask for the IP address of the laptop is the same as that for the IP address of the
NE (the default subnet mask is 255.255.0.0).
l The default gateway IP address is blank.
Step 3 Use a network cable to connect the Ethernet port of the laptop to the NMS/COM port on the
system control, switching, and timing board.
NMS/COM
NOTICE
Ensure that the network cable is properly connected to the Ethernet port of the laptop and the
NMS/COM port on the system control, switching, and timing board. Otherwise, the equipment
or test tool may be damaged.
NOTE
The NMS/COM port on the system control, switching, and timing board supports the auto-MDI/MDI-X mode.
Therefore, straight-through cables and crossover cables can both be used to set up a connection. For pin
assignments for crossover cables and straight-through cables, see Network Cable in the OptiX RTN 950 Radio
Transmission System IDU Hardware Description.
At this point, the indicators at the Ethernet port and the NMS/COM port are on (green). A
message will be displayed indicating that the network has established a local connection if the
operating system has been configured to do so. If the operating system displays a message
indicating an IP address conflict, change the IP address.
Step 5 Optional: Set the security level of the Internet Explorer to medium or lower.
Step 9 Enter the values of User Name and Password, and then click Login.
l User Name: admin
l Password: admin
If the entered user name and the password are both correct, the NE List page is displayed in the
Internet Explorer.
----End
Prerequisites
The NE user must have the authority of Operation Level or higher.
Procedure
When using the Web LCT, press the F1 key to quickly display the related Online Help page.
----End
Prerequisites
The NE user must have the authority of Operation Level or higher.
Procedure
Step 1 In NE List, select the NE to which you are logged in and click NE Explorer at the lower right
corner.
Function tree
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 The NE user must have the authority of Operation Level 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 through Perform Step 6 to Step 11.
Ethernet cables
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.
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.
NOTE
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.
----End
Prerequisites
l The NE user must have the authority of Operation Level 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.
----End
Related References
B.1.1.2 Parameter Description: NE Creation
A.2.1.3 Logging In to an NE
After an NE is created, you need to log in to the NE before managing the NE.
Prerequisites
l The NE user must have the authority of Operation Level 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
NOTE
----End
Related References
B.1.1.3 Parameter Description: Login to an NE
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l All the boards must be installed correctly.
Procedure
Step 1 Click the Slot Layout tab and click Add Physical Boards.
Based on the slot layout, the NE automatically configures the logical boards that are required
but still not be configured for certain 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.
NOTE
Before deleting the board, delete the data, such as the service, clock, orderwire, and protection, on the
board.
----End
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l All the boards and their SFP modules have been installed correctly.
Context
The following table lists the boards and the supported SFP module types.
Procedure
Step 1 Click the Slot Layout tab.
Step 2 Right-click the target board and choose Path View. The board's path view is displayed.
Step 4 Optional: To add a port and configure the port, perform the following steps:
1. Right-click in the blank field and choose Add Port from the shortcut menu.
2. Set port parameters in Add Port.
3. Click OK.
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 SFP port, you can set the SFP module type in Modify Port mode. For an Ethernet SFP port,
you need to delete the port and add it again if you want to reset the SFP module type. Set the SFP module
when adding the port.
l For an EG4 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
The NE user must have the authority of Operation Level or higher.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > NE
Attribute from the Function Tree.
----End
Related References
B.1.1.4 Parameter Description: NE Attribute_Changing NE IDs
Prerequisites
The NE user must have the authority of Operation Level or higher.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > NE
Attribute from the Function Tree.
----End
Prerequisites
l The NE user must have the authority of Operation Level 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 Step 5.
You set Synchronous Mode to Standard NTP Set the related parameters, and then click
Apply to perform steps 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
Related References
B.1.1.5 Parameter Description: NE Time Synchronization
Prerequisites
The NE user must have the authority of Operation Level or higher.
Procedure
Step 1 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 Set the correct time zone and daylight saving time of the NE depending on the location of the
NE.
----End
Related References
B.1.1.6 Parameter Description: Localization Management of the NE Time
Prerequisites
The NE user must have the authority of Operation Level or higher.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree, and then choose Performance > NE
Performance Monitor Time from the Function Tree.
l Generally, both Set 15-Minute Monitoring and Set 24-Hour Monitoring are enabled.
l 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.
l 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.
4. Click Apply.
----End
Prerequisites
The NE user must have the authority of Maintenance Level or higher.
Procedure
Step 1 In the NE Explorer, select the desired board.
----End
Prerequisites
The NE user must have the authority of Operation Level or higher.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication >
Communication Parameters from the Function Tree.
----End
Related References
B.1.2.1 Parameter Description: NE Communication Parameter Setting
Prerequisites
The NE user must have the authority of Operation Level or higher.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCC
Management from the Function Tree.
NOTE
l On the NMS interface, the first port on the system control, switching, and clock board (like 7-
CST-1) corresponds to its external clock port.
l If the port is connected to the other ECC subnet, Enabled/Disabled is set to Disabled.
l If the port is connected to a third-party network and does not exchange the network management
information with other ports, Enabled/Disabled is set to Disabled.
l Set Protocol Type based on the management protocol used by the DCN solution.
l If a DCC port is a non-backbone area port on the ABR, set IP Address and Subnet Mask of the DCC
port. In addition, it is recommended that you set the interface IP address to be in a network segment
from the NE IP address.
NOTE
Set Protocol Type based on the management protocol used by the DCN solution.
3. Click OK.
----End
Related References
B.1.2.2 Parameter Description: DCC Management_DCC Rate Configuration
Prerequisites
The NE user must have the authority of Operation Level or higher.
The DCC bytes required by the transparent transmission function must not be used.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCC
Management from the Function Tree.
----End
Related References
B.1.2.3 Parameter Description: DCC Management_DCC Transparent Transmission
Management
Prerequisites
The NE user must have the authority of System Level or higher.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCN
Management from the Function Tree.
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. The same VLAN ID must be, however, is used on
the network-wide inband DCN.
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.
----End
Related References
B.1.2.20 Parameter Description: DCN Management_Bandwidth Management
Prerequisites
The NE user must have the authority of System Level or higher.
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
Related References
B.1.2.23 Parameter Description: DCN Management_Packet Control
Prerequisites
The NE user must have the authority of System Level or higher.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCN
Management from the Function Tree.
Step 3 Optional: Select FE/GE, configure the port parameters for the inband DCN function.
NOTE
Step 5 Optional: Select IF, configure the port parameters for the inband DCN function.
NOTE
----End
Related References
B.1.2.21 Parameter Description: DCN Management_Port Setting
Prerequisites
The NE user must have the authority of Operation Level or higher.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Communication >
DCN Management from the Function Tree.
Step 2 Click the Access Control tab.
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
Related References
B.1.2.22 Parameter Description: DCN Management_Access Control
Prerequisites
The NE user must have the authority of Operation Level or higher.
Context
The default extended ECC mode is Auto mode.
Procedure
Step 1 Click an NE in the NE Explorer. Choose Communication > ECC Management from the
Function Tree.
Step 2 Optional: You can disable the Auto mode function of the extended ECC.
1. Click Stop.
A confirmation dialog box is displayed.
2. Click OK.
Step 3 Optional: Set parameters for the extended ECC function in Specified mode at the server end.
1. Set ECC Extended Mode to Specified mode.
2. Set related parameters for the server end.
3. Click Apply.
A confirmation dialog box is displayed.
4. Click OK.
Step 4 Set parameters for the extended ECC function in Specified mode at the client end.
1. Set ECC Extended Mode to Specified mode.
2. Set related parameters for the client end.
3. Click Apply.
A confirmation dialog box is displayed.
4. Click OK.
Before enabling the automatic extended ECC function, you need to clear related parameters that are configured
in Specified mode for the server end and client end.
1. Set ECC Extended Mode to Specified mode.
2. To clear parameters configured for the server end, click Clear Server.
A confirmation dialog box is displayed.
3. Click OK.
4. To clear parameters configured for the client end, click Clear Client.
A confirmation dialog box is displayed.
5. Click OK.
6. Set ECC Extended Mode to Auto mode.
7. Click Apply.
A confirmation dialog box is displayed.
8. Click OK.
----End
Related References
B.1.2.4 Parameter Description: ECC Management_Ethernet Port Extended ECC
Prerequisites
The NE user must have the authority of Operation Level or higher.
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
The created static route has a lower priority than a dynamic route.
----End
Related References
B.1.2.8 Parameter Description: IP Protocol Stack Management_IP Route Management Creation
Prerequisites
The NE user must have the authority of Operation Level or higher.
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
Set the parameters according to the network plan.
----End
Related References
B.1.2.10 Parameter Description: IP Protocol Stack Management_OSPF Parameter Settings
Prerequisites
The NE user must have the authority of System Level or higher.
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
Related References
B.1.2.13 Parameter Description: Management of Multiple OSPF Areas_Adding OSPF Areas
Prerequisites
The NE user must have the authority of System Level or higher.
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.
3. Click OK.
----End
Related References
B.1.2.12 Parameter Description: Management of Multiple OSPF Areas
Prerequisites
The NE user must have the authority of System Level or higher.
Procedure
Step 1 In the NE Explorer, select the desired NE and choose Communication > IP Protocol Stack
Management from the Function Tree.
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
Related References
B.1.2.14 Parameter Description: Management of Multiple OSPF Areas_Adding Routes to Be
Manually Aggregated
Prerequisites
The NE user must have the authority of System Level or higher.
Procedure
Step 1 Optional: Set the interface IP address for the DCC port.
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.
3. Set the IP address and subnet mask for each DCC port.
NOTE
This parameter is available only if Protocol Type of the DCC port is TCP/IP.
4. Click Apply.
Step 2 Optional: Set the interface IP address for the inband DCN port.
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.
3. Select FE/GE or IF and set the IP address and subnet mask for each inband DCN port.
NOTE
This parameter is available only if Protocol Type of the inband DCN port is IP.
4. Click Apply.
----End
Related References
B.1.2.21 Parameter Description: DCN Management_Port Setting
B.1.2.2 Parameter Description: DCC Management_DCC Rate Configuration
Prerequisites
The NE user must have the authority of Operation Level or higher.
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.
Step 3 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 4 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
Related References
B.1.2.12 Parameter Description: Management of Multiple OSPF Areas
Prerequisites
The NE user must have the authority of Operation Level or higher.
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
Related References
B.1.2.11 Parameter Description: IP Protocol Stack_Proxy ARP
Prerequisites
The NE user must have the authority of Operation Level or higher.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > OSI
Management from the Function Tree.
NOTE
When Configuration Role is set to L2, the NE has the functions of the L1 role and the L2 role.
----End
Related References
B.1.2.16 Parameter Description: OSI Management_Network Layer Parameter
Prerequisites
The NE user must have the authority of Operation Level or higher.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > OSI
Management from the Function Tree.
Step 2 Click the OSI Tunnel tab.
Step 3 Click New.
Then, the Create OSI Tunnel dialog box is displayed.
Step 4 Set Remote IP Address and LAPD Actor.
----End
Related References
B.1.2.18 Parameter Description: OSI Management_OSI Tunnel
Prerequisites
The NE user must have the authority of Operation Level or higher.
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree and choose Communication >
OSI Management from the Function Tree.
----End
Related References
B.1.2.19 Parameter Description: OSI Management_OSI Port Parameters
A.2.4.20 Enabling/Disabling the RSTP Protocol When the L2 DCN Solution Is Used
The RSTP protocol improves stability of an L2 DCN.
Prerequisites
The NE user must have the authority of Operation Level or higher.
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.
----End
Related References
B.1.2.24 Parameter Description: L2 DCN Management
Prerequisites
The NE user must have the authority of Operation Level or higher.
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
Related References
B.1.2.5 Parameter Description: NE ECC Link Management
Prerequisites
The NE user must have the authority of System Level or higher.
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
Related References
B.1.2.7 Parameter Description: IP Protocol Stack Management_IP Route Management
Prerequisites
The NE user must have the authority of System Level or higher.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > OSI
Management from the Function Tree.
Step 3 Check whether the information in Link Adjacency Table meets the planning requirements.
Step 4 Click the L1 Routing tab to check whether the information about the L1 routes is correct.
Step 5 Click the L2 Routing tab to check whether the information about the L2 routes is correct.
----End
Related References
B.1.2.17 Parameter Description: OSI Management_Routing Table
Prerequisites
The NE user must have the authority of Operation Level or higher.
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 Test or Trace Route from the drop-down menu.
The Ping Test or Trace Route dialog box is displayed.
----End
Related References
B.1.2.6 Parameter Description: ECC Link Management_Availability Test
Prerequisites
The NE user must have the authority of Operation Level or higher.
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.
----End
Related References
B.1.2.9 Parameter Description: IP Protocol Stack Management_Availability Test
Prerequisites
The NE user must have the authority of Operation Level 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.
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
The NE user must have the authority of Operation Level or higher.
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
The NE user must have the authority of Operation Level or higher.
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
l The NE user must have the authority of System Level or higher.
l An online user can create a user at a lower level.
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.
Step 3 Set the parameters of the NE user according to the network plan.
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
Related References
B.1.3.2 Parameter Description: NE User Management_Creation
Prerequisites
l The NE user must have the authority of System Level or higher.
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.
Step 2 Select the required NE user from the NE user management list, and click Set Password.
The Change Password dialog box is displayed.
----End
Related References
B.1.3.1 Parameter Description: NE User Management
Prerequisites
The NE user must have the authority of Maintenance Level or higher.
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
l The NE user must have the authority of Operation Level or higher.
l The IF boards and the ODUs to which the IF boards are connected must be added on the
Slot Layout.
l The IF boards of an IF 1+1 FD/SD protection group must be configured in two paired slots.
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 service is not interrupted. The board that carries the original
service, however, needs to be set as the working board.
Procedure
Step 1 For an IF 1+1 protection group comprised of ISU2 or ISX2 boards, set IF Service Type to
appropriate values for the main and standby IF boards according to the network plan.
NOTE
l Ensure that the values of IF Service Type set for the main and standby IF boards are the same and meet the
network plan requirements.
l For ISU2 or ISX2 boards, the default value of IF Service Type is Hybrid(Native E1+ETH).
1. In the NE Explorer, select the NE and then choose Configuration > Link
Configuration from the Function Tree.
2. Click the IF/ODU Configuration tab.
3. Changes the values of IF Service Type for the main and standby IF boards according to
the network plan.
4. Click Apply.
Step 2 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link
Configuration from the Function Tree.
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, 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.
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. 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, if Working Mode is set to HSB, it is recommended that you set Enable Reverse
Switching to Disabled; if Working Mode is set to SD, 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.
----End
Related References
B.2.5 Parameter Description: IF 1+1 Protection_Create
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The corresponding XPIC IF boards and the ODUs connected to the XPIC IF boards are
added to the Slot Layout.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link
Configuration from the Function Tree.
NOTE
l Set Link ID-V, Link ID-H, Transmit Power(dBM), Maximum Transmit Power(dBM), and
Transmit Frequency(MHz) according the network plan. Set Link ID-V, Link ID-H, Transmit
Power(dBM), T/R Spacing(MHz), and ATPC Status to the same values for both ends of a link.
l In normal cases, Transmission Status is set to unmute.
----End
Related References
B.2.1 Parameter Description: Link Configuration_XPIC Workgroup_Creation
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The workgroup must be created.
Background Information
The XPIC IF boards (IFX2 and ISX2 boards) support Integrated IP radio, and the AM attributes
can be configured.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link
Configuration from the Function Tree.
NOTE
l When AM 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 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
Related References
B.2.2 Parameter Description: Link Configuration_XPIC
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The IF boards and the ODUs to which the IF boards are connected must be added on the
Slot Layout.
Precautions
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, STM-1
count, or modulation mode is set inconsistently for both ends of an Integrated IP radio link.
This alarm should be cleared immediately. Otherwise, services may be configured
unsuccessfully or interrupted.
Procedure
Step 1 In the NE Explorer, select the NE and then choose Configuration > Link Configuration from
the Function Tree.
l After this operation, the IF board will be reset. Set other IF information after the IF board starts up.
l For ISU2 and ISX2 boards, set IF Service Type appropriately for the ISU2 and ISX2 boards before
configuring IF 1+1 protection, N+1 protection, and XPIC.
2. Set other IF information.
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 When AM Status is set to Disabled, the radio link uses only the specified modulation scheme. In this
case, you need to select Manual Modulation Mode.
l When AM 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.
NOTE
l Power to Be Received(dBm) is used to set the expected receive power of the ODU and is mainly used
in the antenna alignment stage. After this parameter is set, the NE automatically enables the antenna
misalignment indicating function.
l When Power to Be Received(dBm) takes the default value (-10.0), the antenna misalignment
indicating function is disabled.
l In normal cases, it is recommended that you set TX Status to unmute.
----End
Related References
B.2.9 Parameter: Link Configuration_IF/ODU Configuration
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The Slot Layout displays the IF boards and the ODUs to which they connect.
Background Information
l This task configures 1+0 non-protected, XPIC, or 1+1 protected radio links. To configure
N+0 radio links, they must be configured as N 1+0 radio links.
l Link ID, IF Channel Bandwidth, AM, Modulation Mode of the Guaranteed AM
Capacity, Modulation Mode of the Full AM Capacity, and T/R Spacing(MHz) of the
NEs on a hop of radio link are automatically synchronized. That is, if one of the preceding
parameters is modified on an NE, the modification is automatically duplicated on the peer
NE.
Procedure
Step 1 Select an NE from the Object Tree in the NE Explorer. Click the Radio Link Configuration
tab.
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.
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:
1. Select 1+0, and deselect the XPIC check box.
2. Configure the basic attributes of the radio link.
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:
1. Select 1+1.
2. Configure the basic attributes of the radio links.
3. Optional: Click Advanced, and configure the advanced attributes of the radio links.
l To configure XPIC radio links:
1. Select 1+0 and XPIC.
2. 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.3.1 Creating an IF 1+1
Protection Group.
Step 4 Configure IF attributes for the local NE and the peer NE on the radio link.
Step 5 Configure RF attributes for the local NE and the peer NE on the radio link.
l Configure a 1+0 non-protected radio link.
----End
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The IF boards and the ODUs to which the IF boards are connected must be added on the
Slot Layout.
l The IF1 boards must work in the STM-1 mode.
Background Information
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 In the case of Integrated IP radio, the Hybrid/AM attributes must be the same for all the N
+1 radio links in the N+1 protection group.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link
Configuration from the Function Tree.
Step 5 Configure the mapping relation between the board and the slot.
1. Select Working Unit from Select Mapping Direction.
2. Select a port to which a working channel corresponds from Available Boards, and then
click .
3. Repeat Step 5.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 .
----End
Related References
B.2.3 Parameter Description: N+1 Protection_Create
Prerequisites
l The NE user must have the authority of System Level or higher.
l The IF 1+1 protection must be configured.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link
Configuration from the Function Tree.
Step 3 Click Query. In Protection Group, check the IF 1+1 protection groups.
Step 4 Select the IF 1+1 protection group whose protection status needs to be queried.
Step 6 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
Related References
B.2.6 Parameter Description: IF 1+1 Protection
Prerequisites
l The NE user must have the authority of System Level or higher.
l The IF N+1 protection must be configured.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link
Configuration from the Function Tree.
Step 3 Click Query. In Protection Group, check the IF N+1 protection groups.
Step 4 Select the protection group whose protection status needs to be queried.
Step 5 Click Query Switching Status. In Slot Mapping Settings, check the IF N+1 protection status.
----End
Related References
B.2.4 Parameter Description: N+1 Protection
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The IF 1+1 protection must be configured.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link
Configuration from the Function Tree.
Step 3 In Protection Group, select the protection group for protection switching.
Step 4 In Slot Mapping Settings, select a working unit or the protection unit of the protection group,
and then right-click the selected unit.
Step 5 Choose the required switching mode from the shortcut menu.
Step 8 Select the working unit or the protection unit, right-click Query Switching Status and check
whether the switching is successful.
----End
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The IF N+1 protection must be configured.
l The N+1 protection protocol is enabled.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link
Configuration from the Function Tree.
Step 3 In Protection Group, select the protection group for protection switching.
Step 4 In Slot Mapping Settings, select a working unit or the protection unit of the protection group,
and then right-click the selected unit.
Step 5 Choose the required switching mode from the shortcut menu.
Step 8 Click Query Switching Status to check whether the switching operation is successful.
----End
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The IF N+1 protection must be configured.
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 > Link
Configuration from the Function Tree.
Step 3 In Protection Group, select the protection group whose N+1 protection protocol needs to be
started.
----End
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The IF boards and the ODUs to which the IF boards are connected have been added on the
Slot Layout.
l The main and slave IF boards are installed in two paired slots.
l The main and slave IF boards in the PLA group are of the same type.
l No Ethernet service has been configured on the slave IF board.
l The services configured on the member IF boards in the PLA group are of the same type.
l The member IF boards in the PLA group have the same channel spacing.
l Neither member IF board in the PLA group functions as a member in a 1+1 HSB/FD/SD
or N+1 protection group.
l Neither member IF board in the PLA group functions as a member in LAG group.
l The Layer 3 header compression function is disabled for the member IF boards in the PLA
group.
Background Information
l In V100R003C03, PLA aggregates only two links, which means that a PLA group can
contain only one main port and one slave port. The IF boards where the main and slave
ports are located must be installed in two paired slots.
l IF boards are reset (cold) during creation or deletion of a PLA group.
l PLA can work together with adaptive modulation (AM). Member links in a PLA group can
use different Hybrid/AM attributes and modulation modes.
l The two members of an XPIC workgroup can form a PLA group, providing Ethernet service
protection between the vertical and horizontal polarization directions. One member in an
XPIC workgroup and one member in another XPIC workgroup cannot form a PLA group.
l Native TDM services in Integrated IP radio links are irrelevant to the PLA group consisting
of the Integrated IP radio links, and need to be configured separately on the Integrated IP
radio links.
l If a PLA group is configured to provide protection for Ethernet bandwidth on Integrated
IP radio links, subnetwork connection protection (SNCP) can be configured to provide
protection for Native TDM services on the Integrated IP radio links.
l PLA can work together with Ethernet ring protection switching (ERPS). ERPS switching
can be triggered when all links in a PLA group fail or when the number of available links
in a PLA group is smaller than Minimum Number of Activated Member Links.
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 4 Configure the main and slave ports in the PLA group.
1. Select the main IF board from Main Board and select the main port from Main Port.
2. Select the slave IF board from Board and select the slave port from Port.
3. Click .
----End
Related References
B.2.7 Parameter Description: Link Configuration_Creating a PLA Group
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l A PLA group has been configured.
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 group in Physical Link Aggregation List.
NOTE
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
Related References
B.2.8 Parameter Description: Link Configuration_PLA
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The corresponding board must be added on the Slot Layout.
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.
----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.
Related References
B.3.1 Parameter Description: Linear MSP_Creation
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The linear MSP must be configured.
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.
Step 4 Click Query > Query Switching Status In Slot Mapping Settings, query the status of the linear
MSP.
----End
Related References
B.3.2 Parameter Description: Linear MSP
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The linear MSP must be configured.
l The protection protocol is enabled.
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.
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 The NE user must have the authority of System Level or higher.
l The linear MSP must be configured.
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 and check Protocol Status.
----End
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The corresponding source and sink boards must be added on Slot Layout.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Cross-
Connection Configuration from the Function Tree.
Step 2 Click Scheme to change the VC-12 timeslot numbering policy used by the cross-connection.
----End
Related References
B.4.1 Parameter Description: SDH Service Configuration_Creation
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The corresponding source and sink boards must be added on Slot Layout.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Cross-
Connection Configuration from the Function Tree.
Step 2 Click Scheme to change the VC-12 timeslot numbering policy used by the cross-connection.
----End
Related References
B.4.2 Parameter Description: SDH Service Configuration_SNCP Service Creation
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The corresponding source and sink boards must be added in the Slot Layout.
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.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Cross-
Connection Configuration from the Function Tree.
Step 4 Right-click the E1 service and choose Expand from the shortcut menu.
Step 5 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 6 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
l The NE user must have the authority of Operation Level or higher.
l The IFU2, IFX2, ISU2, or ISX2 board is added to Slot Layout.
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.
----End
Related References
B.4.6 Parameter Description: TU_AIS Insertion
B.4.6 Parameter Description: TU_AIS Insertion
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The SNCP protection group must be configured.
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.
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.
Step 5 Set the initiation condition for the protection service. Click OK.
NOTE
It is recommended that you set Initiation Condition of the working service to be the same as Initiation
Condition of the protection service.
----End
Related References
B.4.5 Parameter Description: SNCP Service Control
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The cross-connections of the service must be configured and the service must not be used.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Cross-
Connection Configuration from the Function Tree.
Step 4 Click Query. The queried information should show that the cross-connection is already deleted.
----End
Prerequisites
l The NE user must have the authority of Operation Level 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.
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 > 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 from the shortcut menu.
Step 3 Select the unidirectional service. Right-click the selected service and choose Convert to
SNCP from the shortcut menu.
Then, the Convert to SNCP Service dialog box is displayed.
Step 4 Set the parameters of the SNCP service.
----End
Related References
B.4.3 Parameter Description: SDH Service Configuration_Converting Normal Services Into
SNCP Services
Prerequisites
l The NE user must have the authority of Operation Level 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.
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 > Cross-Connection Configuration from the Function Tree.
Step 2 In Auto-Created Cross-Connection, select the configured service and click Service
Convert.
Step 3 Choose SNCP Protection Service Convert to Non-Protection Service or SNCP Working
Service Convert to Non-Protection Service from the displayed menu.
NOTE
l 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.
l 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.
----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 The NE user must have the authority of System Level or higher.
l TDM services must be configured.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Cross-
Connection Configuration from the Function Tree.
----End
Related References
B.4.4 Parameter Description: SDH Service Configuration
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The SNCP protection group must be configured.
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 Switching Status to check whether the switching operation is
successful.
----End
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The SNCP protection group must be configured.
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.
----End
Related References
B.4.5 Parameter Description: SNCP Service Control
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The corresponding board must be added on the Slot Layout.
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > SDH Interface from the Function Tree.
Step 2 Select By Board/Port(Path), and select Port or VC4 Path from the list box.
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.
1. Choose VC4 Path 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
Related References
B.5.7.1 Parameter Description: SDH Interfaces
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The corresponding board must be added on the Slot Layout.
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > PDH Interface from the Function Tree.
Step 7 Click OK, and then close the dialog box that is displayed indicating the operation result.
----End
Related References
B.5.8.1 Parameter Description: PDH Ports
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The corresponding board must be added on the Slot Layout.
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.
----End
Related References
B.5.9.1 Parameter Description: Regenerator Section Overhead
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The corresponding board must be added on the Slot Layout.
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.
4. Click OK.
5. Click Apply.
A dialog box is displayed for confirmation.
6. Click OK.
3. Click Apply.
3. Click Apply.
A dialog box is displayed for confirmation.
4. Click OK.
----End
Related References
B.5.9.2 Parameter Description: VC-4 POHs
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The corresponding board must be added on the Slot Layout.
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.
5. Click OK.
6. Click Apply.
A dialog box is displayed for confirmation.
7. Click OK.
3. Click Apply.
A dialog box is displayed for confirmation.
4. Click OK.
----End
Related References
B.5.9.3 Parameter Description: VC-12 POHs
Prerequisites
The NE user must have the authority of System Level or higher.
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.
----End
Related References
B.5.1.1 Parameter Description: PDH Ports_Basic Attributes
Prerequisites
The NE user must have the authority of System Level or higher.
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 3 Select the required port and set the parameters for its advanced attributes.
----End
Related References
B.5.1.2 Parameter Description: PDH Ports_Advanced Attributes
Prerequisites
l The NE user must have the authority of System Level or higher.
l The ports that travel services are set to Layer 1.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
Interface Management > Serial Port from the Function Tree.
Step 4 Set the parameters for the serial port according to the planning information.
----End
Related References
B.5.3.2 Parameter Description: Serial Port_Creation of Serial Ports
Prerequisites
l The NE user must have the authority of System Level or higher.
l Serial ports are added.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
Interface Management > Serial Port from the Function Tree.
Step 2 Click the Basic Attributes tab.
Step 3 Select the required port and set the parameters for the serial port according to the planning
information.
----End
Related References
B.5.3.1 Parameter Description: Serial Port_Basic Attributes
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The Ethernet board must be added on the Slot Layout.
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
Related References
B.5.2.1 Parameter Description: Ethernet Interface_Basic Attributes
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The Ethernet board must be added on the Slot Layout.
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 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 The OptiX RTN 950 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 The OptiX RTN 950 supports only two non-auto-negotiation flow control modes, namely, Disabled
mode and Enable Symmetric Flow Control mode.
----End
Related References
B.5.2.2 Parameter Description: Ethernet Interface_Flow Control
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The Ethernet board must be added on the Slot Layout.
l Port Mode of Ethernet ports are set to Layer 2.
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 QinQ Type Domain should be set to the same value for all the ports on the EM6T/EM6TA/EM6F/
EM6FA board.
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.
l When the VLAN priority is required to divide streams or to be used for other purposes, VLAN
Priority is set according to the planning information. In normal cases, it is recommended that you use
the default value.
----End
Related References
B.5.2.3 Parameter Description: Ethernet Interface_Layer 2 Attributes
Prerequisites
l The NE user must have the authority of System Level or higher.
l Port Mode of Ethernet ports are set to Layer 3.
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 2 Click the Layer 3 Attributes tab.
Step 3 Set the parameters for Ethernet ports according to the planning information.
----End
Related References
B.5.2.4 Parameter Description: Ethernet Port_Layer 3 Attributes
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The Ethernet board must be added on the Slot Layout.
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 Advanced Attributes tab.
----End
Related References
B.5.2.5 Parameter Description: Ethernet Interface_Advanced Attributes
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The corresponding IF board must be added to Slot Layout.
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 If Port Mode is Layer 2, Encapsulation Type can be set to Null, 802.1Q, or QinQ.
l If Port Mode is Layer 3, Encapsulation Type can be set to 802.1Q only and the port can carry tunnels.
l If Port Mode is Layer Mix, Encapsulation Type can be set to only 802.1Q or QinQ and the port can
carry both tunnels and Native Ethernet services.
l Encapsulation Type specifies the method of the port to process the received packets.
l If Encapsulation Type is set to Null, the port transparently transmits the received packets.
l If Encapsulation Type is set to 802.1Q, the port identifies the packets that comply with the IEEE
802.1Q standard.
l If Encapsulation Type is set to QinQ, the port identifies the packets that comply with the IEEE 802.1ad
QinQ standard.
----End
Related References
B.5.4.1 Parameter Description: Microwave Interface_Basic Attributes
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The corresponding IF board must be added to Slot Layout.
l The parameter Port Mode is set to Layer 2.
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.
l When the VLAN priority is required to divide streams or to be used for other purposes, VLAN
Priority needs to be set according to the planning information. In normal cases, it is recommended
that you use the default value.
----End
Related References
B.5.4.2 Parameter Description: Microwave Interface_Layer 2 Attributes
Prerequisites
l The NE user must have the authority of System Level or higher.
l Port Mode of the ports on IF boards are set to Layer 3.
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.
----End
Related References
B.5.4.3 Parameter Description: Microwave Interface_Layer 3 Attributes
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The corresponding IF board must be added to Slot Layout.
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
Related References
B.5.4.4 Parameter Description: Microwave Interface_Advanced Attributes
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The corresponding IF board must be added on the Slot Layout.
Context
l The IF1 board is used for TDM microwave.
l The IFU2 and ISU2 boards are general-purpose IF boards.
l The IFX2 and ISX2 boards are general-purpose XPIC IF boards.
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > IF Interface from the Function Tree.
1. Optional:
set IF Service Type according to the network plan. Click Apply.
NOTE
After this operation, the IF board will be reset. Set other IF information after the IF board starts up.
2. Set other general attributes.
1. Optional:
set IF Service Type according to the network plan. Click Apply.
NOTE
After this operation, the IF board will be reset. Set other IF information after the IF board starts up.
2. Set other general attributes.
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 Generally, IF Port Loopback is used to locate the faults that occur at each IF interface. The IF loopback
is used for diagnosis. If this function is enabled, the services at the related ports are affected. In normal
cases, this parameter is set to Non-Loopback.
l 350 MHz Consecutive Wave Status can be set to Start in the commissioning process only. In normal
cases, this parameter is set to Stop. Otherwise, the services are interrupted.
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.
NOTE
l When AM Status is set to Disabled, the radio link uses only the specified modulation scheme. In this
case, you need to select Manual Modulation Mode.
l When AM 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
Related References
B.5.5.1 Parameter Description: IF Interface_IF Attribute
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The corresponding IF board must be added on the Slot Layout.
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.
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > IF Interface from the Function Tree.
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
Related References
B.5.5.2 Parameter Description: IF Interface_ATPC Attribute
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The corresponding IF boards must be added in the Slot Layout.
l The E1 priority function must be enabled.
Background Information
l The OptiX RTN 950 supports the configuration of E1 priorities. The IF boards that support
this function are IFU2, IFX2, ISU2, and ISX2.
l For the ISU2 and ISX2 boards, only the Integrated IP radio that transmits Native E1 services
supports the configuration of E1 priorities.
Procedure
Step 1 In the NE Explorer, select the IF board, and then choose Configuration > IF Interface from
the Function Tree.
----End
Related References
B.5.5.3 Parameter Description: Hybrid_AM Configuration_Advanced Attributes
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The corresponding IF boards must be added in the Slot Layout.
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > IF Interface from the Function Tree.
----End
Related References
B.5.5.1 Parameter Description: IF Interface_IF Attribute
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The corresponding IF board must be added.
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
Related References
B.5.5.4 Parameter Description: ATPC Adjustment Records
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The corresponding IF boards have been added in the Slot Layout.
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 Modulation Mode of 1. Perform Step 5 to disable the AM function,
the Guarantee AM Capacity and change Manually Specified
Modulation Mode to the lowered
Modulation Mode of the Guarantee AM
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.
Step 8 Optional: Change the number of high-priority E1 services (namely, Guarantee E1 Capacity)
in a radio link.
If... Then...
You need to reduce the number of high- 1. Perform A.5.6 Deleting Cross-Connections
priority E1 services to delete unnecessary E1 services.
2. Decrease Guarantee E1 Capacity.
3. Click Apply.
If... Then...
You need to increase the number of 1. Increase Guarantee E1 Capacity.
high-priority E1 services 2. If Enable E1 Priority is Enabled, increase
Full E1 Capacity accordingly.
3. Click Apply.
4. Perform A.5.1 Creating the Cross-
Connections of Point-to-Point Services or A.
5.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 the number of low- 1. Perform A.5.6 Deleting Cross-Connections
priority E1 services to delete unnecessary E1 services.
2. Decrease Full E1 Capacity.
3. Click Apply.
You need to increase the number of low- 1. If Enable E1 Priority is Disabled, change
priority E1 services Enable E1 Priority to Enabled.
2. Increase Full E1 Capacity.
3. Click Apply.
4. Perform A.5.1 Creating the Cross-
Connections of Point-to-Point Services or A.
5.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
Related References
B.5.5.1 Parameter Description: IF Interface_IF Attribute
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The IF boards and the ODUs to which the IF boards are connected must be added on the
Slot Layout.
Procedure
Step 1 Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU
Interface from the Function Tree.
NOTE
l The value of Transmit Frequency(MHz) must not be less than the sum of the minimum transmit
frequency supported by the ODU and a half of the channel spacing, and must not be more than the
difference between the maximum transmit frequency supported by the ODU and a half of the channel
spacing.
l The difference between the transmit frequencies at both ends of a radio link 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
Related References
B.5.6.1 Parameter Description: ODU Interface_Radio Frequency Attribute
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The IF boards and the ODUs to which the IF boards are connected must be added on the
Slot Layout.
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > ODU Interface from the Function Tree.
----End
Related References
B.5.6.3 Parameter Description: ODU Interface_Equipment Information
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The IF boards and the ODUs to which the IF boards are connected must be added on the
Slot Layout.
Procedure
Step 1 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 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 ODU. This parameter cannot be set to a value that exceeds the nominal power rang of the
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 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
Related References
B.5.6.2 Parameter Description: ODU Interface_Power Attributes
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The IF boards and the ODUs to which the IF boards are connected must be added on the
Slot Layout.
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
Related References
B.5.6.4 Parameter Description: ODU Interface_Advanced Attributes
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The corresponding IF boards and the ODUs connected to the IF boards must be added to
the Slot Layout.
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 Advanced Attributes tab.
Step 3 Set Configure Transmission Status for the ODU.
NOTE
----End
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The corresponding IF boards and the ODUs connected to the IF boards must be added to
the Slot Layout.
Procedure
Step 1 Select the ODU from the Object Tree in the NE Explorer. Choose Configuration >
Performance Graph Analyse from the Function Tree.
Step 2 Specify the start time and end time of a specific time span.
Step 4 Click Draw. The historical transmit and receive power curve of the ODU in the specified time
span is displayed.
----End
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The IF boards and the ODUs to which the IF boards are connected have been added in the
Slot Layout.
Procedure
Step 1 In the NE Explorer, select the desired IF board from the Object Tree and then choose
Configuration > IF Interface from the Function Tree.
Step 2 Set the desired query time span by specifying the start time and end time.
Step 3 Set Monitoring Period and SNR Type according to the planning information.
Step 4 Click Draw. Then, the system displays the SNR change curve during the specified time span.
----End
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l Ethernet boards have been added on the Slot Layout.
l Port Mode has been set to Layer Mix for Ethernet ports.
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
Related References
B.5.10 Parameter Description: Ethernet Virtual Interfaces
Prerequisites
l The NE user must have the authority of Operation Level or higher.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protection > ERPS Management.
NOTE
l Only one node on the ring can be set as the RPL owner for each Ethernet ring.
l An RPL owner needs to balance the traffic on each link of an Ethernet ring. Therefore, it is not recommended
that you select a convergence node as an RPL owner. Instead, select the NE that is farthest away from the
convergence node as an RPL owner.
l It is recommended that you set the east port on an RPL owner as an RPL Port.
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
Related References
B.6.2.1 Parameter Description: ERPS Management_Creation
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The ERPS protection instance must be created.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protection > ERPS Management from the Function Tree.
Step 2 Optional: Double-click Control VLAN, and then modify the VLAN ID.
NOTE
Set the parameters according to the network plan. Default values are recommended.
----End
Related References
B.6.2.2 Parameter Description: ERPS Management
Prerequisites
The NE user must have the authority of Operation Level or higher.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protection > ERPS Management from the Function Tree.
Step 2 Click Query.
Step 3 Query the status of the Ethernet ring protocol.
----End
Related References
B.6.2.2 Parameter Description: ERPS Management
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The board on which the LAG port to be created must be added to the Slot Layout.
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.
NOTE
Hold the Ctrl key or the Shift key on the keyboard to select multiple ports.
NOTE
----End
Related References
B.6.2.8 Parameter Description: Ethernet Link Aggregation Management_LAG Creation
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The board on which the LAG to be created must be added to Slot Layout.
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.
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
Related References
B.6.2.9 Parameter Description: Ethernet Link Aggregation_Link Aggregation
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The LAG must be created.
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.
NOTE
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.
----End
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The Ethernet board must be added on the Slot Layout.
l On associated ports, the Encapsulation Type is set to QinQ.
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.
----End
Related References
B.6.1.6 Parameter Description: QinQ Link_Creation
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The Ethernet board must be added on the Slot Layout.
Context
NOTE
For the OptiX RTN 950, the total number of VLAN IDs configured for all E-Line services cannot exceed 1024.
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
Related References
B.6.1.1 Parameter Description: E-Line Service_Creation
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l Ethernet boards have been added on the Slot Layout.
l For ports that carry services, Encapsulation Type has been set to QinQ.
Context
NOTE
For the OptiX RTN 950, the total number of VLAN IDs configured for all E-Line services cannot exceed 1024.
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 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. But, 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.
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
Related References
B.6.1.1 Parameter Description: E-Line Service_Creation
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l Ethernet boards have been added on the Slot Layout.
l For ports that carry services, Encapsulation Type has been set to QinQ.
Context
NOTE
For the OptiX RTN 950, the total number of VLAN IDs configured for all E-Line services cannot exceed 1024.
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. But 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
Related References
B.6.1.1 Parameter Description: E-Line Service_Creation
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The Ethernet board is added on the Slot Layout.
Context
NOTE
l For the OptiX RTN 950, the total number of VLAN IDs configured for all E-Line services cannot exceed
1024.
l For the OptiX RTN 950, the total number of VLAN IDs configured for E-Line services carried by tagged
PWs on the NNI side and E-Aggr services encapsulated in QinQ mode over UNIs cannot 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, 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.9.5.1 Creating a PW APS Protection Group.
----End
Related References
B.6.1.1 Parameter Description: E-Line Service_Creation
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l Ethernet boards have been added on the Slot Layout.
l Encapsulation Type has been set to 802.1Q or QinQ for ports that carry services.
l The MPLS tunnels that carry PWs have been configured.
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.
Context
NOTE
l For the OptiX RTN 950, the total number of VLAN IDs configured for all E-Line services cannot exceed
1024.
l For the OptiX RTN 950, the total number of VLAN IDs configured for E-Line services carried by tagged
PWs on the NNI side and E-Aggr services encapsulated in QinQ mode over UNIs cannot exceed 256.
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 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.
NOTE
Services are forwarded by VLAN ID. Therefore, you need to set the VLAN forwarding attributes
from each Source Interface to its Sink Interface. Both the source and the sink VLAN IDs must be
within the VLAN ID range configured for the service.
3. 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
Related References
B.6.1.7 Parameter Description: E-AGGR Services_Creation
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l Ethernet boards have been added on the Slot Layout.
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.
----End
Related References
B.6.1.3 Parameter Description: VLAN Forwarding Table Items for E-Line Services_Creation
Prerequisites
The NE user must have the authority of Operation Level or higher.
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.
----End
Prerequisites
The NE user must have the authority of Operation Level 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
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
Related References
B.6.1.4 Parameter Description: E-LAN Service_Creation
Prerequisites
The NE user must have the authority of System Level 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 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
Hold the Ctrl key on the key board to select multiple ports.
4. Click OK.
----End
Related References
B.6.1.4 Parameter Description: E-LAN Service_Creation
Prerequisites
The NE user must have the authority of System Level 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 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.
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
Step 5 Configure the ports mounted to the bridge on the NNI side.
1. Click Get NNI Port.
The Get NNI Port dialog box is displayed.
2. Configure the ports mounted to the bridge on the NNI side.
3. Click OK.
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
Related References
B.6.1.4 Parameter Description: E-LAN Service_Creation
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The E-LAN services must be created.
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.
NOTE
----End
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The E-Line service is configured and this service is not used.
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 Select the E-Line service that needs to be deleted and then click Delete.
----End
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l A configured E-LAN service is not required.
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.
----End
Prerequisites
l The E-LAN service must be created.
l The NE user must have the authority of Operation Level 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 On the main interface, select the E-LAN service whose static MAC address entry needs to be
created.
----End
Related References
B.6.1.5 Parameter Description: E-LAN Service
Prerequisites
l The E-LAN service must be created.
l The NE user must have the authority of Operation Level 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 On the main interface, select the E-LAN service whose blacklist entry of MAC addresses needs
to be created.
Step 3 Click the Disabled MAC Address tab.
Step 4 Click New.
The New Disabled MAC Address dialog box is displayed.
Step 5 Configure the blacklist entry of MAC addresses.
----End
Related References
B.6.1.5 Parameter Description: E-LAN Service
Prerequisites
l The E-LAN service must be created.
l The NE user must have the authority of Operation Level 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 On the main interface, select the E-LAN service whose aging parameters of the MAC address
table need to be configured.
Step 4 Configure the status of the aging function and set the aging time.
----End
Related References
B.6.1.5 Parameter Description: E-LAN Service
Prerequisites
l The E-LAN service must be created.
l The NE user must have the authority of Operation Level 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 On the main interface, select the E-LAN service whose dynamic MAC address needs to be
queried or cleared.
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.
----End
Related References
B.6.1.5 Parameter Description: E-LAN Service
Prerequisites
l The E-LAN service must be created.
l The NE user must have the authority of Operation Level 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 On the main interface, select the E-LAN service, the mode for processing whose unknown frame
needs to be set.
Step 4 Set the mode for processing an unknown frame of the E-LAN service.
----End
Related References
B.6.1.5 Parameter Description: E-LAN Service
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The boards where the member ports are located must be added in Slot Layout.
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.
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 the Shift key when selecting
the ports.
4. Click OK.
----End
Related References
B.6.2.3 Parameter Description: MSTP Configuration_Port Group Creation
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The port group must be created.
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.
----End
Related References
B.6.2.5 Parameter Description: MSTP Configuration_ Bridge Parameters
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The port group must be created.
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.
----End
Related References
B.6.2.6 Parameter Description: MSTP Configuration_CIST Parameters
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The MSTP port group must be created.
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.
----End
Related References
B.6.2.7 Parameter Description: MSTP Configuration_Running Information About the CIST
A.7.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
The NE user must have the authority of Operation Level or higher.
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
The NE user must have the authority of Operation Level or higher.
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 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
The NE user must have the authority of Operation Level or higher.
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.
Option Description
If... Then...
Option Description
A member port needs to be added 1. Select the board where the member ports are located
from the drop-down list of Board.
2. Select the port to be added from Available Port
List.
3. Click .
A member port needs to be deleted 1. Select the port to be deleted from Selected Port
List.
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
Related References
B.6.2.4 Parameter Description: MSTP Configuration_Port Group Configuration
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The board of the Ethernet ports must be added on Slot Layout.
Background Information
The OptiX RTN 950 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.
The MPLS EXP value can be modified in the default Diffserv domain (Default Map) only.
Step 5 Configure the mapping relationships between the priorities of ingress packets and PHB service
classes.
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.
NOTE
l The PHB service class refers to the forwarding behavior of the DS node on the behavior aggregate (BA)
operation. The forwarding behavior can meet the specific requirements.
l The PHB service classes are BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The priorities (C_VLAN priority,
S_VLAN priority, DSCP value and MPLS EXP value) contained in the packets of the DS domain and the
eight PHB service classes meet the requirements of the specified or default mapping relationship.
----End
Related References
B.6.4.2 Parameter Description: DiffServ Domain Management_Create
Prerequisites
The NE user must have the authority of Operation Level or higher.
Background Information
The OptiX RTN 950 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.
NOTE
The MPLS EXP value can be modified in the default Diffserv domain (Default Map) only.
l The PHB service class refers to the forwarding behavior of the DS node on the behavior aggregate
(BA) operation. The forwarding behavior can meet the specific requirements.
l The PHB service classes are BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The priorities (C_VLAN
priority, S_VLAN priority, DSCP value and MPLS EXP value) contained in the packets of the DS
domain and the eight PHB service classes meet the requirements of the specified or default mapping
relationship.
3. Click Apply.
l The PHB service class refers to the forwarding behavior of the DS node on the behavior aggregate
(BA) operation. The forwarding behavior can meet the specific requirements.
l The PHB service classes are BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The priorities (C_VLAN
priority, S_VLAN priority, DSCP value and MPLS EXP value) contained in the packets of the DS
domain and the eight PHB service classes meet the requirements of the specified or default mapping
relationship.
3. Click Apply.
----End
Related References
B.6.4.1 Parameter Description: Diffserv Domain Management
A.7.7.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
The NE user must have the authority of Operation Level or higher.
Background Information
The OptiX RTN 950 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 uses the DS 1. Select the board where the application port is
domain located 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 that uses the DS 1. Select the board where the application port is
domain located from the drop-down list of Board.
2. Select the port to be deleted from the port list
of Selected Port.
3. Click .
Option Description
You need to change the packet type Select a new packet type from the drop-down list
identified by the port of Packet Type.
NOTE
Hold the Ctrl key on the key board to select multiple ports.
NOTE
l C-VLAN indicates the client-side VLAN priority, and the value 7 indicates the highest priority.
l S-VLAN indicates the server-side VLAN priority, 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 950 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
Related References
B.6.4.3 Parameter Description: DiffServ Domain Applied Port_Modification
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The board of the Ethernet ports must be added on Slot Layout.
Procedure
Step 1 Optional: Configure the weighted round robin (WRR) scheduling policy.
NOTE
In the default WRR scheduling policy for OptiX RTN 950, AF4, AF3, AF2, and AF1 occupy the same
weight of 25% and other queues occupy the weight of 0%.
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. The Create WRR Policy dialog box is displayed.
3. Set the scheduling weight for each queue.
4. Click OK.
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 950 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 Bandwidth Limit indicates or specifies whether traffic shaping is enabled for an egress queue
corresponding to a PHB service class.
l CIR (kbit/s), PIR (kbit/s), CBS (byte), and PBS (byte) can be set only when Bandwidth Limit is
set to Enabled.
5. Click OK.
----End
Related References
B.6.4.5 Parameter Description: Port Policy
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The port policy must be created.
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,
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 950 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 Bandwidth Limit indicates or specifies whether traffic shaping is enabled for an egress queue corresponding
to a PHB service class.
l CIR (kbit/s), PIR (kbit/s), CBS (byte), and PBS (byte) can be set only when Bandwidth Limit is set to
Enabled.
----End
Related References
B.6.4.4 Parameter Description: Policy Management
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The Ethernet board must be added on the Slot Layout.
l The port policy must be created.
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
Related References
B.6.4.6 Parameter Description: Port Policy_Traffic Classification Configuration
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The Ethernet board must be added on the Slot Layout.
l The port policy must be created.
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.
3. Click OK.
2. Click OK.
----End
Related References
B.6.4.4 Parameter Description: Policy Management
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The Ethernet board must be created on the Slot Layout.
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.
NOTE
If the traffic shaping function is enabled, OptiX RTN 950 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
Related References
B.6.4.7 Parameter Description: Port Shaping Management_Creation
Prerequisites
The NE user must have the authority of Operation Level or higher.
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.
----End
Related References
B.6.4.4 Parameter Description: Policy Management
Prerequisites
The NE user must have the authority of Operation Level or higher.
Background Information
The OptiX RTN 950 has a default DS domain, whose Mapping Relation ID is 1 and Mapping
Relation Name is default map. Before another DS domain is created, all the ports belong to this
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 4 Query the attributes of the DS domain and the mapping relationship between the packet priority
level in the ingress direction and the PHB service class.
Step 7 Query the attributes of the DS domain and the mapping relationship between the priority level
of the packets in the egress direction and the PHB service class.
----End
Related References
B.6.4.1 Parameter Description: Diffserv Domain Management
A.7.8.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 The NE user must have the authority of Operation Level or higher.
l The corresponding board must be added on the Slot Layout.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Service OAM from the Function Tree.
NOTE
----End
Related References
B.6.3.1 Parameter Description: Ethernet Service OAM Management_Maintenance Domain
Creation
A.7.8.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 The NE user must have the authority of Operation Level or higher.
l The MD must be created.
l The Ethernet service must be created.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Service OAM 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.
Click in Relevant Service. Select the corresponding services in the displayed dialog box.
Related References
B.6.3.2 Parameter Description: Ethernet Service OAM Management_Maintenance Association
Creation
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The MA must be created.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Service OAM from the Function Tree.
Step 2 Click the Maintenance Association tab.
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.
Step 4 Set the MEP parameters.
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
Related References
B.6.3.3 Parameter Description: Ethernet Service OAM Management_MEP Creation
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The MA must be created.
Background Information
PORT 10 on the EFP8 board does not support this operation.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Service OAM 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.
Step 5 Set the parameters of the new remote MEP.
NOTE
If other MEPs will initiate OAM operations to an MEP in the same MA, set these MEPs as remote MEPs.
----End
Related References
B.6.3.4 Parameter Description: Ethernet Service OAM Management_Remote MEP Creation
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The MA must be created.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Service OAM 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
Related References
B.6.3.5 Parameter Description: Ethernet Service OAM Management_MIP Creation
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The MEP must be created.
l The remote MEPs must be created.
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 from the Function Tree.
Step 3 Select the MEP where you need to perform the CC test and then choose OAM > Activate
CC.
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.
----End
Prerequisites
l The NE user must have the authority of Operation Level 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.
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 from the Function Tree.
Step 3 Select the maintenance domain and maintenance association for the LB test.
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
Related References
B.6.3.6 Parameter Description: Ethernet Service OAM Management_LB Enabling
Prerequisites
l The NE user must have the authority of Operation Level 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.
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.
l Performing an LT test does not affect services.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Service OAM from the Function Tree.
Step 3 Select the maintenance domain and maintenance association for the LT test.
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
Related References
B.6.3.7 Parameter Description: Ethernet Service OAM Management_LT Enabling
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The source and sink MEPs in the same MD must be created.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Service OAM 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 The NE user must have the authority of Operation Level or higher.
l Native E-Line services that are transmitted based on ports and VLAN IDs have been
created.
l Source and sink maintenance end points (MEPs) in the same maintenance domain (MD)
have been created.
Context
The OptiX RTN 950 uses the RMON function to collect statistics about packet loss ratio, delay,
or delay variation of Ethernet services. This section describes navigation paths to monitoring
packet loss ratio, delay, or delay variation of Ethernet services. Follow instructions in A.11 Using
the RMON to use the RMON function.
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 Right-click an MEP and choose Browse Performance from the shortcut menu.
If... Then...
You want to query the current packet loss Click the Statistics Group tab and set
ratio, delay, or delay variation required parameters.
You want to query the historical packet loss Click the History Group tab and set required
ratio, delay, or delay variation 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 click the
packet loss ratio, delay, or delay variation Event tab and set required parameters.
You want to set the historical performance Click the RMON Setting tab. Then click the
monitoring period for the packet loss ratio, Object tab and set required parameters.
delay, or delay variation
----End
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l E-LAN services have been created.
Context
l Creation of MEPs is not a prerequisite for service loopback detection.
l Service loopback detection and STP/RSTP/MSTP are mutually exclusive.
l If an E-LAN service is mounted to a port that functions as the east and west ERPS port,
loopback tests cannot be performed on the service.
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 port 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 The NE user must have the authority of Operation Level or higher.
l An E-LAN service port has been shut down due to a service loopback.
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 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
The NE user must have the authority of Operation Level or higher.
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.
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Port OAM 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.
----End
Related References
B.6.3.9 Parameter Description: Ethernet Port OAM Management_OAM Parameter
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The OAM auto-discovery operation must successful on the equipment at both ends.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Port OAM from the Function Tree.
Step 3 Select the corresponding port and set Remote Alarm Support for Link Event to Enabled.
----End
Related References
B.6.3.9 Parameter Description: Ethernet Port OAM Management_OAM Parameter
Prerequisites
l The NE user must have the authority of Operation Level 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.
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.
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Port OAM 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
Related References
B.6.3.10 Parameter Description: Ethernet Port OAM Management_OAM Error Frame
Monitoring
Prerequisites
l The NE user must have the authority of Operation Level 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.
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.
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Port OAM from the Function Tree.
Step 2 Click the OAM Parameter tab.
Step 3 Select the port and set Remote Side Loopback Response to Enabled.
NOTE
----End
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The required board is already added on the Slot Layout.
l All the external physical ports on the Ethernet service processing board must be enabled.
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 Advanced Attributes tab.
Step 3 Set Loopback Check to Enabled.
Step 4 Click Apply.
----End
Prerequisites
l The NE user must have the authority of System Level 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.
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 Bind in the lower right corner of the pane based on the type of service network.
Step 5 Set the parameters of the primary and secondary points of LPT.
Step 7 Optional: Reset Recovery Time(s), Hold-Off Time(ms), and Fault Detection Period
(100ms).
----End
Related References
B.6.2.11 Parameter Description: LPT Management_Creating Point-to-Point LPT
B.6.2.10 Parameter Description: LPT Management_Point-to-Point LPT
Prerequisites
l The NE user must have the authority of System Level 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 Services.
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.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT
Management > LPT from the Function Tree.
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).
----End
Related References
B.6.2.10 Parameter Description: LPT Management_Point-to-Point LPT
Prerequisites
l The NE user must have the authority of System Level 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 Services.
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.
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 7 Optional: Reset Recovery Time(s), Hold-Off Time(ms), and Fault Detection Period
(100ms).
----End
Related References
B.6.2.13 Parameter Description: LPT Management_Creating Point-to-Multipoint LPT
B.6.2.12 Parameter Description: LPT Management_Point-to-Multipoint LPT
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The corresponding board must be added to the Slot Layout.
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 The NE user must have the authority of Operation Level or higher.
l An EMS6 board has been added to the Slot Layout.
Procedure
Step 1 In the NE Explorer, select the EMS6 board. Choose Configuration > Ethernet Protection >
ERPS Management.
----End
Prerequisites
l The NE user must have the authority of Operation Level 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
The NE user must have the authority of Operation Level or higher.
Procedure
Step 1 In the NE Explorer, select the EMS6 board. Choose Configuration > Ethernet Protection >
ERPS Management from the Function Tree.
----End
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board where the LAG ports are located must be added in the Slot
Layout.
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.
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
Related References
B.7.2.12 Parameter Description: Ethernet Link Aggregation_Creation of LAGs
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board where the LAG ports are located must be added in the Slot
Layout.
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
Related References
B.7.2.13 Parameter Description: Ethernet Link Aggregation_Link Aggregation
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board where the LAG ports are located must be added in the Slot
Layout.
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 The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
Precautions
For the method of creating QinQ-based Ethernet private line services, see A.8.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.
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 OK.
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
Related References
B.7.1.1 Parameter Description: Ethernet Line Service_Creation
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
Precautions
For the method of creating the IEEE 802.1ad bridge, see A.8.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 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.
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
Related References
B.7.1.4 Parameter Description: Ethernet LAN Service_Creation of Ethernet LAN Services
Based on IEEE 802.1d/802.1q Bridge
Prerequisites
l The NE user must have the authority of Operation Level 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 The NE user must have the authority of Operation Level 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.
5. Click OK.
----End
Related References
B.7.1.7 Parameter Description: VLAN Filtering Table_Creation
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board, and choose Configuration > Ethernet
Service > Ethernet Line Service from the Function Tree.
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 OK.
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
Related References
B.7.1.2 Parameter Description: Ethernet Line Service_Creating QinQ-Based Ethernet Line
Services
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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.
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.
4. Select required items in Available Resources and Available Timeslots and click
.
5. Optional: Repeat Step 5.4 to bind other VC paths.
6. Click OK.
A confirmation dialog box is displayed.
7. Click OK.
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
Related References
B.7.1.5 Parameter Description: Ethernet LAN Service_Creating IEEE 802.1ad Bridge-Based
Ethernet LAN Service
Prerequisites
l The NE user must have the authority of Operation Level 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 The NE user must have the authority of Operation Level 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 The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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
Related References
B.7.1.6 Parameter Description: Ethernet LAN Service
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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.
----End
Related References
B.7.1.6 Parameter Description: Ethernet LAN Service
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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.
3. Click OK.
----End
Related References
B.7.1.8 Parameter Description: Aging Time of MAC Address Table Entries
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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, or Next 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.
----End
Related References
B.7.1.6 Parameter Description: Ethernet LAN Service
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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 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. 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. Check the actual capacity of the MAC address table.
----End
Related References
B.7.1.6 Parameter Description: Ethernet LAN Service
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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.
3. Click Apply.
3. Click Apply.
3. Click Apply.
3. Click Apply.
3. Click Apply.
----End
Related References
B.7.5.1 Parameter Description: Ethernet Port_External Port
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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.
3. Click Apply.
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.
3. Click Apply.
3. Click Apply.
3. Click Apply.
.
5. Optional: Repeat Step 8.4 to bind other VC paths.
6. Click OK.
A confirmation dialog box is displayed.
7. Click OK.
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
Related References
B.7.5.2 Parameter Description: Ethernet Port_Internal Port
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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.
----End
Related References
B.7.5.3 Parameter Description: Type Field of QinQ Frames
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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.8.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 The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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 > Layer-2 Switching Management > Spanning Tree from the Function Tree.
----End
Related References
B.7.2.3 Parameter Description: Spanning Tree_Protocol Enabling
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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 > 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
Related References
B.7.2.4 Parameter Description: Spanning Tree_Bridge Parameters
B.7.2.5 Parameter Description: Spanning Tree_Port Parameters
B.7.2.8 Parameter Description: Spanning Tree_Point-to-Point Attribute
A.8.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 The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
l The Ethernet LAN services must be created.
l The STP or RSTP must be enabled for the bridge.
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.
----End
Related References
B.7.2.6 Parameter Description: Spanning Tree_Bridge Running Information
B.7.2.7 Parameter Description: Spanning Tree_Port Running Information
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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
Related References
B.7.2.9 Parameter Description: IGMP Snooping Protocol_Enabling
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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.
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
Related References
B.7.2.10 Parameter Description: IGMP Snooping Protocol_Creation of Static Multicast Table
Entries
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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
Related References
B.7.2.11 Parameter Description: IGMP Snooping Protocol_Aging Time of Multicast Table
Entries
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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 The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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.
----End
Related References
B.7.4.1 Parameter Description: QoS Management_Creation of Flows
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board, and then choose Configuration > QoS
Management > Flow Management from the Function Tree.
----End
Related References
B.7.4.2 Parameter Description: QoS Management_Creation of CAR
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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
Related References
B.7.4.3 Parameter Description: QoS Management_Creation of CoS
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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
Related References
B.7.4.4 Parameter Description: QoS Management_Creation of CAR/CoS
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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
Related References
B.7.4.5 Parameter Description: QoS Management_Shaping Management of Egress Queues
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l An EMS6 board has been added to the Slot Layout.
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 The NE user must have the authority of Operation Level or higher.
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 4 Set Scheduling Mode and Weight for the port queue.
----End
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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
Related References
B.7.3.1 Parameter Description: Ethernet Service OAM_Creation of MDs
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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 3 Click New and choose Create MA from the drop-down list.
----End
Related References
B.7.3.2 Parameter Description: Ethernet Service OAM_Creation of MAs
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
l The Ethernet services must be created and activated.
l The MD and MA must be created.
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
Related References
B.7.3.3 Parameter Description: Ethernet Service OAM_Creation of MPs
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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 The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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
Related References
B.7.3.4 Parameter Description: Ethernet Service OAM_Enabling LB
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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.
NOTE
To enable an LT test, you can also right-click an MEP and then choose Start LT from the shortcut menu.
----End
Related References
B.7.3.5 Parameter Description: Ethernet Service OAM_Enabling LT
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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 The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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 The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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 The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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
Related References
B.7.3.6 Parameter Description: Ethernet Port OAM_OAM Parameter
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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 3 Select the corresponding port and set Link Event Notification to Enabled.
----End
Related References
B.7.3.8 Parameter Description: Ethernet Port OAM_Remote OAM Parameter
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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:
l The OAM auto-discovery operation is successful.
l Remote Alarm Support for Link Event is set to Enabled and the monitoring time and
error frame thresholds have been configured at the local end.
If Remote Alarm Support for Link Event is also set to Enabled at the opposite end, the
opposite end notifies the local end after detecting a link event, and then the local end generates
the corresponding alarm.
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 3 Select the port and set the parameters in the OAM Error Frame Monitor tab page.
----End
Related References
B.7.3.7 Parameter Description: Ethernet Port OAM_OAM Error Frame Monitoring
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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 3 Choose Enable Remote Loopback from the OAM drop-down menu.
----End
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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 2 Click Query.
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
Related References
B.7.2.14 Parameter Description: LPT Management_Creation of Point-to-Point Service LPT
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The EFP8/EMS6 board must be added in the Slot Layout.
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.
----End
Related References
B.7.2.15 Parameter Description: LPT Management_Creation of Point-to-Multipoint Service
LPT
Prerequisites
The NE user must have the authority of Operation Level or higher.
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
The NE user must have the authority of Operation Level or higher.
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
The NE user must have the authority of Operation Level or higher.
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
The NE user must have the authority of Operation Level or higher.
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.
----End
Prerequisites
The NE user must have the authority of Operation Level or higher.
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
Prerequisites
The NE user must have the authority of Operation Level or higher.
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 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.
----End
Related References
B.9.1.1 Parameter Description: Basic Configurations of MPLS Tunnels
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The port attributes are set correctly.
l The LSR ID of each NE is set correctly.
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.
Click View Peer NE to view the status and tunnel information of the opposite NE.
----End
Related References
B.9.1.3 Parameter Description: Unicast Tunnel Management_Creation of Unidirectional
Tunnels
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The port attributes have been correctly configured.
l The LSR ID of each NE has been correctly configured.
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 Bidirectional Tunnel from the drop-down list.
The New Unicast Bidirectional Tunnel dialog box is displayed.
----End
Related References
B.9.1.4 Parameter Description: Unicast Tunnel Management_Creation of Bidirectional Tunnels
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l MPLS tunnels are configured correctly.
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 4 View the information about all MPLS tunnels configured for the NE in the main interface.
----End
Related References
B.9.1.2 Parameter Description: Unicast Tunnel Management_Static Tunnel
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The MPLS tunnel has been created.
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 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.
----End
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l An MPLS tunnel is configured correctly and is no longer used to transmit services.
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 6 Click Query and find that the selected MPLS tunnel does not exist.
----End
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l MPLS tunnels are created and enabled.
l Node Type is set to Ingress or Egress for tunnels.
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 Select the required MPLS tunnel and set MPLS OAM parameters.
----End
Related References
B.9.1.5 Parameter Description: Unicast Tunnel Management_OAM Parameters
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l MPLS tunnels are created and enabled.
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.
----End
Related References
B.9.1.6 Parameter Description: Unicast Tunnel Management_FDI
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The MPLS OAM function has been enabled and related parameters have been configured.
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.
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 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 The NE user must have the authority of Operation Level or higher.
l The MPLS OAM detection function has been enabled.
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 Select the required tunnel and click OAM Operation at lower right of the main interface.
Step 5 Check the tunnel status according to the LSP Status parameter value in the main interface.
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
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The MPLS OAM detection function has been enabled.
l The tunnel is not configured in any protection group.
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 Select the required tunnel and click OAM Operation at lower right of the main interface.
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
The NE user must have the authority of Operation Level 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 3 Select the required tunnel, click OAM Operation in the lower right corner, and choose Ping
Test from the drop-down list.
NOTE
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.
NOTE
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
Related References
B.9.1.7 Parameter Description: Unicast Tunnel Management_LSP Ping
Prerequisites
The NE user must have the authority of Operation Level 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 3 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.
NOTE
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
Related References
B.9.1.8 Parameter Description: Unicast Tunnel Management_LSP Traceroute
Prerequisites
l The NE user must have the authority of Operation Level 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.
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.
NOTE
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
Related References
B.9.1.15 Parameter Description: Tunnel Protection Group_Creation
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The MPLS APS protection group has been created.
l The MPLS APS protocol has been enabled.
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 Click Query. Check basic information about the protection group.
----End
Related References
B.9.1.14 Parameter Description: MPLS APS Protection Management
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The MPLS APS protection group has been created.
l The MPLS APS protocol has been enabled.
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. Check whether switching is performed
successfully.
----End
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The MPLS APS protection group has been created.
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.
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 The NE user must have the authority of Operation Level or higher.
l PW-carried services have been configured.
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 5 In the main interface, check the basic information and running status of each PW.
----End
Related References
B.9.1.9 Parameter Description: PW Management_PW Management
Prerequisites
The NE user must have the authority of Operation Level or higher.
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 8 Click the Advanced Attributes tab and set advanced attributes.
----End
Related References
B.9.1.10 Parameter Description: PW Management_MS-PW Creation
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l PW-carried services have been configured.
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.
----End
Related References
B.9.1.11 Parameter Description: PW Management_PW OAM
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l A PW has been created and enabled.
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 3 Select the required PW and click OAM Operation > PW Ping Test.
NOTE
Alternatively, you can select a PW, right-click the PW, and select PW Ping Test from the drop-down list.
The Ping Test dialog box is displayed.
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
Related References
B.9.1.12 Parameter Description: PW Management_PW Ping
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l A PW has been created and enabled.
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 3 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.
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
Related References
B.9.1.13 Parameter Description: PW Management_PW Traceroute
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l MPLS APS protection is not configured for the service.
l The tunnel carrying the working and protection PWs has been created.
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.
CES services, ATM services, and E-Line services carried by PWs support PW APS. 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 Protect Group tab.
Step 5 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
Related References
B.9.1.16 Parameter Description: PW APS Protection Group_Creation
Prerequisites
l The NE user must have the authority of Operation Level 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.
Background Information
CES services, ATM services, and E-Line services carried by PWs support PW APS slave
protection pairs. 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 Protect Group tab.
Step 5 Click the General 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
Related References
B.9.1.17 Parameter Description: Slave Protection Pair of a PW APS Protection Group_Creation
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The PW APS protection group has been created.
l The PW APS protocol has been enabled.
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. 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. Check the
status of the protection group.
----End
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The PW APS protection group has been created.
l The PW APS protocol has been enabled.
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 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 5 Click Function and choose Query Switching Status from the drop-down list. Check whether
switching is performed successfully.
----End
Prerequisites
l The NE user must have the authority of Operation Level or higher.
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 The NE user must have the authority of Operation Level 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.
Background Information
l Generally, UNI-NNI CES services are configured on the OptiX RTN 950. 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.9.5.1 Creating a PW APS Protection Group
and A.9.5.2 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
Step 4 Optional: Click Port Attributes tab and set the port attributes.
NOTE
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.
Step 5 Click the PW tab and set the basic attributes of the PW.
NOTE
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 6 Click Advanced Attributes and set parameters for the advanced attributes.
----End
Related References
B.9.2.2 Parameter Description: CES Service Management_Creation
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l CES services have been created.
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. In the main interface, check basic service
information.
Step 3 Click PW General Attributes to query information about the PW that carry the service.
----End
Related References
B.9.2.1 Parameter Description: CES Service Management
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l CES services have been created.
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. 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 Protect Group to check whether a protection group is configured and to check information
about the protection group if configured.
----End
Related References
B.9.2.1 Parameter Description: CES Service Management
Prerequisites
l The NE user must have the authority of Operation Level 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.
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 4 Click Query to check whether the CES service is successfully deleted.
----End
Prerequisites
l The NE user must have the authority of Operation Level 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.6.5 Setting Serial Port Parameters.
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.
l Frame Mode at the local end takes the same value as the opposite end.
----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.
Related References
B.9.3.2 Parameter Description: ATM IMA Management_Bound Path Configuration
Prerequisites
The NE user must have the authority of Operation Level or higher.
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 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 Min.Active Transmission Links and Minimum Number of Active Receiving Links
must be the same because the OptiX RTN 950 supports Symmetrical Mode and Symmetrical
Operation only. The parameters Min.Active Transmission 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
Related References
B.9.3.1 Parameter Description: ATM IMA Management_IMA Group Management
Prerequisites
The NE user must have the authority of Operation Level or higher.
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.
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.
----End
Related References
B.9.3.5 Parameter Description: ATM IMA Management_ATM Interface Management
Prerequisites
The NE user must have the authority of Operation Level or higher.
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.
Step 3 Click Query.
Step 4 Query the running status of an IMA group.
----End
Related References
B.9.3.3 Parameter Description: ATM IMA Management_IMA Group Status
Prerequisites
The NE user must have the authority of Operation Level or higher.
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 Query the running status of the member links of an IMA group.
----End
Related References
B.9.3.4 Parameter Description: ATM IMA Management_IMA Link Status
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l Generally, UNIs-NNI ATM services are configured on the OptiX RTN 950. 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.
Background Information
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.9.5.1 Creating a PW APS Protection Group and A.
9.5.2 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 3 Configure the basic information about the ATM PWE3 service according to the network plan.
Step 5 Click the PW tab, and click New to configure the attributes of PWs.
1. Click the General Attributes tab and set the basic attributes of PWs.
3. Click the Advanced Attributes tab to configure the advanced attributes of PWs.
4. Click OK.
Step 6 Click the CoS Mapping tab and click Add to configure the CoS mapping of PWs.
----End
Related References
B.9.3.11 Parameter Description: ATM Service Management_Creation
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l ATM PWE3 services are already created and their parameters need to be modified
according to the planning information.
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 3 Select the required ATM service and modify the parameters of the ATM service.
----End
Related References
B.9.3.10 Parameter Description: ATM Service Management
Prerequisites
The NE user must have the authority of Operation Level or higher.
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 3 Select the required ATM service and query the parameters of the ATM service.
----End
Related References
B.9.3.10 Parameter Description: ATM Service Management
Prerequisites
The NE user must have the authority of Operation Level or higher.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM
Service Management from the Function Tree.
----End
Prerequisites
The NE user must have the authority of Operation Level or higher.
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.
NOTE
l Eight PHB service classes are available: BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The OptiX RTN
950 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.
NOTE
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
Related References
B.9.3.7 Parameter Description: Configuration of ATM Service Class Mapping Table_Creation
Prerequisites
The NE user must have the authority of Operation Level or higher.
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 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
950 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.
NOTE
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
Related References
B.9.3.6 Parameter Description: Configuration of ATM Service Class Mapping Table
Prerequisites
The NE user must have the authority of Operation Level or higher.
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 3 Configure the parameters of the ATM policy according to the planning information.
----End
Related References
B.9.3.9 Parameter Description: ATM Policy Management_Creation
Prerequisites
The NE user must have the authority of Operation Level or higher.
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 3 Select the required ATM policy and modify its parameters according to the planning information.
----End
Related References
B.9.3.8 Parameter Description: ATM Policy Management
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l ATM services have been configured.
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.
----End
Related References
B.9.3.12 Parameter Description: ATM OAM Management_Segment and End Attributes
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l ATM services have been configured.
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 2 Click the CC Activation Status tab.
Step 3 Configure the parameters of the CC test according to the planning information.
----End
Related References
B.9.3.13 Parameter Description: ATM OMA Management_CC Activation Status
Prerequisites
The NE user must have the authority of Operation Level or higher.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM
OAM Management from the Function Tree.
----End
Related References
B.9.3.15 Parameter Description: ATM OAM Management_LLID
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l ATM services have been configured.
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.
----End
Related References
B.9.3.14 Parameter Description: ATM OAM Management_Remote End Loopback Status
Prerequisites
The NE user must have the authority of Operation Level or higher.
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
Related References
B.10.1.1 Parameter Description: Clock Source Priority Table
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The priority list of the clock source must be configured.
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
Related References
B.10.1.3 Parameter Description: Clock Subnet Setting_Clock Subnet
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The priority level of a clock source must be set.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
Physical Clock > Clock Subnet Configuration.
NOTE
Step 7 Set the clock quality for which the quality level is zero.
NOTE
----End
Related References
B.10.1.4 Parameter Description: Clock Subnet Setting_Clock Quality
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The priority level of a clock source must be set.
l The standard SSM or extended SSM protocol is enabled.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
Physical Clock > 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
Related References
B.10.1.5 Parameter Description: Clock Subset Setting_SSM Output Control
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The priority level of a clock source must be set.
l The extended SSM protocol must be enabled.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
Physical Clock > 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
Related References
B.10.1.6 Parameter Description: Clock Subset Setting_Clock ID Enabling Status
Prerequisites
The NE user must have the authority of Operation Level or higher.
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
Related References
B.10.1.10 Parameter Description: Output Phase-Locked Source of the External Clock Source
Prerequisites
The NE user must have the authority of Operation Level or higher.
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
Related References
B.10.1.2 Parameter Description: Priority Table for the PLL Clock Source of the External Clock
Port
Prerequisites
The NE user must have the authority of Operation Level or higher.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
Physical Clock > Clock Source Switching.
----End
Related References
B.10.1.9 Parameter Description: Clock Source Switching_Clock Source Switching Conditions
Prerequisites
The NE user must have the authority of Operation Level or higher.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
Physical Clock > Clock Source Switching.
----End
Related References
B.10.1.7 Parameter Description: Clock Source Switching_Clock Source Restoration Parameters
Prerequisites
The NE user must have the authority of Operation Level or higher.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
Physical Clock > Clock Synchronization Status.
----End
Related References
B.10.1.11 Parameter Description: Clock Synchronization Status
Prerequisites
l The NE user must have the authority of System Level or higher.
l CES services are configured.
Precautions
NOTICE
l An ACR clock domain can bind only the CES services from the E1 ports 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.
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 an CES service for primary clock extraction.
----End
Related References
B.10.2.1 Parameter Description: ACR Clock Source
Prerequisites
l The NE user must have the authority of System Level or higher.
l CES services are configured.
Precautions
NOTICE
l E1 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 An ACR clock domain can only be applied to the E1 ports on a local board.
l The E1 ports corresponding to the primary clock for an ACR clock domain must be added
to the ACR clock domain.
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.
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 4 In Clock Domain Board, select the board where the ACR clock domain resides.
3. Click .
----End
Related References
B.10.2.3 Parameter Description: Clock Domain_Creation
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The corresponding board must be added in the Slot Layout.
Procedure
Step 1 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
Related References
B.8.1 Parameter Description: RMON Performance_Statistics Group
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The corresponding boards must be added in the Slot Layout.
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose
Performance > RMON Performance from the Function Tree.
Step 3 Select the boards that need to report RMON performance threshold-crossing alarms.
Threshold Detect specifies the mode for report RMON alarms. If Threshold Detect is set to Not
Supported. threshold check is not supported for RMON performance events.
----End
Related References
B.8.4 Parameter Description: RMON Performance_RMON Setting
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The corresponding boards must be added in the Slot Layout.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Performance > RMON History
Control Group.
----End
Related References
B.8.3 Parameter Description: RMON Performance_History Control Group
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The corresponding boards must be added in the Slot Layout.
l The objects and performance events to be monitored must be set.
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose
Performance > RMON Performance from the Function Tree.
----End
Related References
B.8.4 Parameter Description: RMON Performance_RMON Setting
Prerequisites
The NE user must have the authority of Operation Level or higher.
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
Related References
B.11.1 Parameter Description: Orderwire_General
B.11.2 Parameter Description: Orderwire_Advanced
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The board involved in the synchronous data service must be configured.
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
Related References
B.11.3 Parameter Description: Orderwire_F1 Data Port
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The board involved in the asynchronous data service must be configured.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Orderwire
from the Function Tree.
----End
Related References
B.11.4 Parameter Description: Orderwire_Broadcast Data Port
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The IF1 board must be added on the Slot Layout.
l The DCC channels corresponding to external clocks must be disabled.
Background Information
The wayside E1 service can be supported by the IF1 board in the 7,STM-1,28MHz,128QAM
mode and can be supported by the ISU2/ISX2 board in the SDH IF service type.
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
Related References
B.5.5.1 Parameter Description: IF Interface_IF Attribute
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The AUX board must be added on the Slot Layout.
Context
The external alarms of the OptiX RTN 950 are also considered as housekeeping alarms. The
external alarm port of the OptiX RTN 950 is a relay port. This port can be either in the "on" state
or in the "off" state.
The OptiX RTN 950 provides two alarm output ports and four alarm input ports. The alarm input
ports report the RELAY_ALARM alarm (the alarm parameter indicates the port number of the
input alarm) after the external alarm is triggered. To ensure that the external alarm port works
normally, the external alarm cables must be correctly connected.
Procedure
Step 1 Select the 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.
3. Click Apply.
----End
Related References
B.11.5 Parameter Description: Environment Monitoring Interface
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The outdoor cabinet monitoring port on the OptiX RTN 950 has been connected to the
COM_IN port on the outdoor cabinet. In addition, monitoring signal communication is
normal.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and then choose
Configuration > Auxiliary Interface from the Function Tree.
Step 2 Double-click Interface Mode. Select MON from the drop-down list.
NOTE
For the CSH/CST board, Interface Mode can be configured only for port 2.
----End
Related References
B.10.3 Parameter Description: Auxiliary Ports
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l Interface Mode has been configured correctly under Auxiliary Interface.
Context
NOTE
The OptiX RTN 950 supports four types of outdoor cabinet, namely, APM30 AC, APM30 DC, OMB AC, and
OMB DC cabinets. When being installed in the OMB AC or OMB DC cabinet, the OptiX RTN 950 can work
as only a repeater. When using service cables such as E1 cables and Ethernet cables, install the OptiX RTN
950 in the APM30 AC or APM30 DC cabinet.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and then choose
Configuration > NE Attribute from the Function Tree.
NOTE
Ensure that the configured cabinet type is the same as the type of the actually used outdoor cabinet.
----End
A.12.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 The NE user must have the authority of Operation Level or higher.
l The TCU logical board has been added to the Slot Layout.
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 Environment Monitor Interface drop-down list.
Step 3 Optional: Click Query to view the temperature and fan information.
NOTE
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.12.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 The NE user must have the authority of Operation Level or higher.
l The PMU logical board has been added to the Slot Layout.
Context
NOTE
This operation is supported only by APM30 AC and OBM AC cabinets. The OBM AC cabinets do not
support setting and queries of parameters about the battery group.
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 Environment Monitor Interface 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 PMU Electrical Source System Attribute from the
Environment Monitor Interface 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
A.12.6.5 Querying the Ambient Temperature and Humidity of the Outdoor Cabinet
The power monitoring unit (PMU) monitors the ambient temperature and humidity of the
outdoor cabinet.
Prerequisites
l The NE user must have the authority of Operation Level or higher.
l The PMU logical board has been added to the Slot Layout.
Context
NOTE
This operation is supported only by APM30 AC and OBM AC cabinets.
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.12.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 The NE user must have the authority of Operation Level or higher.
l The PMU logical board has been added to the Slot Layout.
Context
NOTE
This operation is supported only by APM30 AC and OBM AC cabinets.
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 PMU Alarm Threshold from the Environment Monitor Interface
drop-down list.
Step 3 Select Operation Object, and set Upper Threshold and Lower Threshold for temperature and
humidity alarms.
It is recommended that the parameters take their default values, unless otherwise specified.
----End
Prerequisites
l The NE must be configured with E1 services, and the E1 services must be transmitted
through the DDF.
l The communication between the NMS and the NE must be normal.
Precautions
NOTICE
l When a PRBS test is performed, the services carried on the tested path are interrupted.
l The PRBS test can be performed only in a unidirectional manner and on one path at a time.
l CES services do not support a PRBS test.
Procedure
Step 1 On the NMS, perform an inloop for the corresponding E1 port at the remote site.
1. Select the PDH interface board in the Object Tree.
2. In the Function Tree, choose Configuration > PDH Interface.
3. Select By Function and select Tributary Loopback from the drop-down menu.
4. In Tributary Loopback, select Inloop.
5. Click Apply.
The Confirm dialog box is displayed.
6. Click OK.
Step 2 At the central site, on the NMS, select the PDH interface board in the Object Tree.
Step 4 Select the first E1 port, and then set the following PRBS-related parameters:
l Direction: Cross
l Duration: a value from 120 to 180
l Measured in Time: seconds
Step 7 When the Progress column is 100%, click Query to check the test result.
The curve diagram should be green.
----End
Prerequisites
The NE must be configured with E1 services, and the E1 services must be transmitted through
the DDF.
For a test of CES services in CESoPSN mode, a BER tester supporting Nx64 Kbit/s timeslot setting is
necessary.
Procedure
Step 1 On the DDF at the central site, connect the BER tester to the first E1 port of the IDU.
The BER tester indicates the AIS alarm.
1
2
RX TX
3
. 4
..
.
BER tester
Step 2 On the NMS, perform an inloop for the corresponding E1 port at the remote site.
1. Select the PDH interface board in the Object Tree.
2. In the Function Tree, choose Configuration > PDH Interface.
3. Select By Function and select Tributary Loopback from the drop-down menu.
4. In Tributary Loopback, select Inloop.
5. Click Apply.
The Confirm dialog box is displayed.
6. Click OK.
Step 3 Test the bit errors for two minutes.
There should be no bit errors.
NOTE
For a test of CES services, it is necessary to configure 64 Kbit/s timeslots on a BER tester to align with the
timeslots carrying CES services.
----End
Prerequisites
Ethernet services must be configured.
NOTE
l It is recommended that you test low-priority Ethernet services in good weather conditions when the AM
function works in the highest-efficiency modulation mode.
l The tested Ethernet services can be Native Ethernet services, EoS/EoPDH services, or Ethernet services
carried by PWs.
NE 2 PORT 2
VLAN ID=100
NE 1
PORT 1
NE 3
PORT 3
Microwave network
VLAN ID=200
The VLAN ID of the Ethernet service from NE2 to NE1 is 100, and the VLAN ID of the Ethernet
service from NE3 to NE1 is 200.
NOTE
If the Ethernet ports are on the EMS6/EFP8 boards, you can still perform the following steps to test the
Ethernet services by eliminating the need to set up the remote maintenance end point. In addition, the
operations on the NMS are different. For details, see A.8.9.1 Creating MDs, A.8.9.2 Creating MAs, A.
8.9.3 Creating MPs, and A.8.9.5 Performing an LB Test.
Procedure
Step 1 Configure the maintenance domains of NE1, NE2, and NE3.
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Service OAM from the Function Tree.
2. Choose New > New Maintenance Domain.
The New Maintenance Domain dialog box is displayed.
3. Configure the parameters of the new maintenance domains.
Parameter Value
Maintenance 4 4 4
Domain Level
NOTE
The maintenance domain names and the maintenance domain levels of the NEs must be the same.
4. Click OK.
Step 2 Configure the maintenance associations of NE1, NE2, and NE3.
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Service OAM from the Function Tree.
2. Select the maintenance domain in which a maintenance association needs to be created.
Choose New > New Maintenance Association.
The New Maintenance Association dialog box is displayed.
3. Configure the parameters of the new maintenance associations.
Parameter Value
NOTE
Click in Relevant Service, and select associated services in the New Maintenance
Association dialog box.
4. Click OK.
Parameter Value
5. Click OK.
Step 4 Configure the remote MEPs for the maintenance associations of NE1, NE2, and NE3.
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Service OAM 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.
Then, the Add Maintenance Association Remote Maintenance Point dialog box is
displayed.
5. Set the parameters of the new remote MEPs.
Parameter Value
NOTE
Set the Remote Maintenance Point ID of NE1 to the MP ID of NE2 and NE3, and set the Remote
Maintenance Point ID of NE2 and NE3 to the MP ID of NE1.
6. Click OK.
Step 5 Test the availability of the Ethernet services from NE1 to NE2 and NE3.
1. Select an NE from the Object Tree in the NE Explorer of the NE1, and then choose
Configuration > Ethernet OAM Management > Ethernet Service OAM.
2. Select the MD, MA, and MEP that correspond to Port 1, click OAM.
3. Select Start LB.
The LB Test window is displayed.
4. Select MP ID, and set the parameters in Test Node.
Parameter Value
Parameter Value
7. Repeat Step 5.4 to Step 5.6 to test the Ethernet services from NE1 to NE3.
Parameter Value
Parameter Value
----End
Prerequisites
l End-to-end ATM services must be configured.
l The NE user must have the authority of Operation Level or higher.
Background Information
When an LB test is performed on the ATM service, the segment and end attribute is set to specify
the types of transmitted ATM OAM cells.
l When Segment End Attribute is set to Segment point, segment LB cells are transmitted.
l When Segment End Attribute is set to Endpoint, end-to-end LB cells are transmitted.
The services of the boards on the NE1 and NE2 are configured as follows:
Attribute NE A NE B
Attribute NE A NE B
VPI 1 101
VCI 51 501
NNI PW ID 1 1
Service source - -
Bound port - -
Figure A-4 Connection diagram for testing the connectivity of the ATM service
UNI NNI NNI UNI
VPI VCI VPI VCI VPI VCI VPI VCI
1 51 101 501 101 501 101 501
NodeB NE A NE B RNC
Procedure
Step 1 Set the segment and end attributes of the ATM services on the NE A and NE B.
1. In the NE Explorer, select an NE and then choose Configuration > ATM OAM
Management from the Function Tree.
2. Click the Segment and End Attribute tab, and choose the ATM service to be tested.
3. As for NE A and NE B, set Segment and End Attribute to Segment point.
4. As for NE A and NE B, set Connection Direction to Sink.
5. Click Apply.
If the default LLID is unique on a network, the default LLID can also be used.
3. Click Apply.
----End
Prerequisites
l The antennas have been aligned.
l The radio links must be the Integrated IP radio links for which the AM function is enabled.
l The E1 service must be configured.
l The weather is favorable.
Precautions
The following test procedure uses the E1 services between NEs as an example.
Procedure
Step 1 Connect the BER tester to an E1 port on the local NE.
NOTE
Test the E1 services with the highest priority, which are not discarded in the lowest-order modulation mode.
Step 2 On the remote NE, perform an inloop at the E1 port by using the NMS.
1. Select the PDH interface board in the Object Tree.
2. In the Function Tree, choose Configuration > PDH Interface.
3. Select By Function and select Tributary Loopback from the drop-down menu.
4. In Tributary Loopback, select Inloop.
5. Click Apply.
The Confirm dialog box is displayed.
6. Click OK.
Step 6 Configure the Hybrid/AM attribute to the planned values on the local NE.
1. Select the IF board from the NE Explorer, and then choose Configuration > IF
Interface from the Function Tree.
2. Click the IF Attributes tab.
3. On the local NE, set the AM attribute to Enable, and set Modulation Mode of the
Guarantee AM Capacity and Modulation Mode of the Full AM Capacity to the planned
values.
4. Click Apply.
NOTE
When adverse weather prevails, the current modulation mode may be lower than the value of
Modulation Mode of the Full AM Capacity.
----End
Prerequisites
l The antennas have been aligned.
l The radio links must be the Integrated IP radio links for which the AM function is enabled.
l The weather is favorable.
Procedure
Step 1 Configure the Hybrid/AM attribute on the local NE.
1. Select the IF board from the NE Explorer, and then choose Configuration > IF
Interface from the Function Tree.
2. Click the IF Attributes tab.
3. On the local NE, set the AM attribute to Disable, and set Manually Specified Modulation
Mode to the same value as Modulation Mode of the Guarantee AM Capacity.
4. Click Apply.
Step 2 Query the 15-minute performance value of the IF board on the local NE.
1. Select the desired IF board from the Object Tree in NE Explorer.
2. In the Function Tree, choose Performance > Current Performance.
3. In Monitored Object Filter Criteria, select All.
4. Set Monitor Period to 15-Minute.
5. In Count, select FEC Performance. In Display Options, select Display Zero Data and
Consecutive Severely Errored Seconds Second.
6. Click Query.
In performance events, the value of FEC_UNCOR_BLOCK_CNT should be 0. If the
value is not 0, choose Reset on the performance register to clear the existing performance
values.
Step 5 Configure the Hybrid/AM attribute to the planned values on the local NE.
1. Select the IF board from the NE Explorer, and then choose Configuration > IF
Interface from the Function Tree.
2. Click the IF Attributes tab.
3. On the local NE, set the AM attribute to Enable, and set Modulation Mode of the
Guarantee AM Capacity and Modulation Mode of the Full AM Capacity to the planned
values.
4. Click Apply.
Step 6 Repeat Step 2. Wait for a period, and query the 15-minute performance value of the IF board
on the local NE.
In performance events, the value of FEC_UNCOR_BLOCK_CNT should be 0.
NOTE
When adverse weather prevails, the current modulation mode may be lower than the value of
Modulation Mode of the Full AM Capacity.
----End
Prerequisites
l The antennas have been aligned.
l The equipment is configured with IF 1+1 protection.
l E1 services are configured.
NE A NE B
As shown in Figure A-5, the following procedures use the E1 services between NE A and NE
B that are configured with 1+1 HSB protection as an example.
NOTE
l If Working Mode of the IF 1+1 protection is set to HSB, TX Status should be set to Mute for the ODU
on the main channel of NE A, and Enable Reverse Switching should be set to Enable. The switching occurs
at NE A.
l If Working Mode of the IF 1+1 protection is set to SD, TX Status should be set to Mute for the ODU on
the main channel of NE A, and Enable Reverse Switching should be set to Enable. The switching occurs
at NE A.
l If Working Mode of the IF 1+1 protection is set to FD, TX Status should be set to Mute for the ODU on
the main channel of NE B. The switching occurs at NE A.
Precautions
NOTE
If no BER tester is available on site, you can compare the values of Active Board of Device or Active Board
of Channel in Protection Group before and after the protection switching.
Procedure
Step 1 Check whether a BER tester is available at the central site.
If... Then...
A BER tester is available on site Perform Step 2 through Step 11.
No BER tester is available on site Perform Step 6 through Step 10.
Step 2 On NE A at the central site, connect one E1 port to the BER tester.
Step 3 On NE B at the remote site, perform a software inloop at the E1 port by using the NMS.
1. Select the PDH interface board in the Object Tree.
2. In the Function Tree, choose Configuration > PDH Interface.
3. Select By Function and select Tributary Loopback from the drop-down menu.
4. In Tributary Loopback, select Inloop.
5. Click Apply.
The Confirm dialog box is displayed.
6. Click OK.
Step 5 Set Enable Reverse Switching in the 1+1 HSB protection group for NE A.
1. Select the desired NE from the Object Tree in the NE Explorer of NE A, and choose
Configuration > Link Configuration from the Function Tree.
2. Click the IF 1+1 Protection tab.
3. Select the corresponding protection group in Protection Group, and set Enable Reverse
Switching to Enable.
4. Click Apply.
Step 6 Before the switching, query the status of the protection group that is configured on NE A.
1. Select the NE from the Object Tree in the NE Explorer of NE A, and choose
Configuration > Link Configuration from the Function Tree.
2. Click the IF 1+1 Protection tab.
3. Select the corresponding protection group in Protection Group, and click Query.
4. In Protection Group, the value of Active Board of Device should be the main IF board
3-ISU2.
4. Click Apply.
If... Then...
A BER tester is available on site Check the test result on the BER tester. It
should show that the services are restored after
transient interruption.
No BER tester is available on site, and the Refer to A.13.1 Testing E1 Services Using
E1 services are transmitted on the radio PRBS to test availability of the E1 services.
link
No BER tester is available on site, and the Refer to A.13.3 Testing Ethernet Services to
Ethernet services are transmitted on the test availability of the Ethernet services.
radio link
Step 9 After the switching, query the status of the protection group that is configured on NE A.
1. Select the NE from the Object Tree in the NE Explorer of NE A, and choose
Configuration > Link Configuration from the Function Tree.
2. Click the IF 1+1 Protection tab.
3. Select the corresponding protection group in Protection Group, and click Query.
4. In Protection Group, the value of Active Board of Device should be the standby IF board
5-ISU2.
3. Select the corresponding protection group in Protection Group, and set Enable Reverse
Switching to Disable.
4. Click Apply.
----End
Prerequisites
l The antennas have been aligned.
l The equipment must be configured with the N+1 protection.
NE A NE B
As shown in Figure A-6, the following procedures consider the E1 services between NE A and
NE B that are configured with the N+1 (N=2) configuration as an example.
Precautions
NOTE
If no BER tester is available on site, you can compare the values of Switching Status in Slot Mapping
Relation before and after the protection switching.
Procedure
Step 1 Check whether a BER tester is available at the central site.
If... Then...
A BER tester is available on site Perform Step 2 to Step 10.
No BER tester is available on site Perform Step 5 to Step 9.
Step 2 At the central site NE A, connect one E1 port to the BER tester.
Step 3 At the remote site NE B, perform a software inloop at the E1 port by using the NMS.
1. Select the PDH interface board in the Object Tree.
2. In the Function Tree, choose Configuration > PDH Interface.
3. Select By Function and select Tributary Loopback from the drop-down menu.
4. In Tributary Loopback, select Inloop.
5. Click Apply.
The Confirm dialog box is displayed.
6. Click OK.
Step 5 Before the switching, query the status of the protection group that is configured on NE B.
1. Select the NE from the Object Tree in the NE Explorer of NE B, and then choose
Configuration > Link Configuration from the Function Tree.
2. Click the N+1 Protection tab.
3. Select the ID of the protection group to be queried, and then click Query.
4. In Slot Mapping Relation, Switching Status of the working units 3-ISU2-1 and 5-
ISU2-1 and the protection unit 4-ISU2-1 should be Normal.
NOTE
If a fault arises, you must rectify the fault and then proceed with the N+1 protection testing.
If... Then...
A BER tester is available on site Check the test result on the BER tester. It
should show that the services are restored after
a transient interruption.
No BER tester is available on site, and the See A.13.1 Testing E1 Services Using
E1 services are transmitted on the radio PRBS to test availability of the E1 services.
link.
No BER tester is available on site, and the See A.13.3 Testing Ethernet Services to test
Ethernet services are transmitted on the availability of the Ethernet service.
radio link.
Step 8 After the switching, query the status of the protection group that is configured on NE B.
1. Select the NE from the Object Tree in the NE Explorer of NE B, and then choose
Configuration > Link Configuration from the Function Tree.
2. Click the N+1 Protection tab.
3. Select the ID of the protection group to be queried, and then click Query.
4. In Slot Mapping Relation, the Switching Status of the working unit 3-ISU2-1 for the
service that is configured with the N+1 protection should be SF.
----End
Prerequisites
l The antennas have been aligned.
l The equipment is configured with the SNCP.
NE A
Working
East West SNC
Protecting SNC
East
West
NE D
NE B
West
East
West East
NE C
Precautions
NOTE
If no BER tester is available on site, you can compare the values of Current Channel in Working Cross-
Connections before an d after the protection switching.
Procedure
Step 1 Check whether a BER tester is available at the central site.
If... Then...
A BER tester is available on site Perform Step 2 through Step 10.
No BER tester is available on site Perform Step 5 through Step 9.
Step 2 At the central site NE A, connect one E1 port to the BER tester.
Step 3 At the remote site NE C, perform a software inloop at the E1 port by using the NMS.
1. Select the PDH interface board in the Object Tree.
2. In the Function Tree, choose Configuration > PDH Interface.
3. Select By Function and select Tributary Loopback from the drop-down menu.
4. In Tributary Loopback, select Inloop.
5. Click Apply.
The Confirm dialog box is displayed.
6. Click OK.
Step 5 Before the switching, query the status of the protection group that is configured on NE C.
1. Select the NE from the Object Tree in the NE Explorer of NE C, and choose
Configuration > SNCP Service Control from the Function Tree.
2. In Working Coross-Connections, select an SNCP service that is already created, then
click Function, and finally select Query Switching Status.
3. The current SNCP status of the equipment is displayed in Working Coross-
Connections and Protection Coross-Connections.
In Current Status, Normal should be displayed. In Current Channel, Working Path
should be displayed.
If... Then...
A BER tester is available on site Check the test result on the BER tester. It
should show that the services are restored after
a transient interruption.
No BER tester is available on site, and the See A.13.1 Testing E1 Services Using
E1 services are transmitted on the radio PRBS to test availability of the E1 services.
link.
Step 8 After the switching, query the status of the protection group that is configured on NE C.
1. Select the NE from the Object Tree in the NE Explorer of NE C, and choose
Configuration > SNCP Service Control from the Function Tree.
2. Click Function, and then select Query Switching Status.
3. The current SNCP status of the equipment is displayed in Working Coross-
Connections and Protection Coross-Connections.
In Current Status, the service switching mode is displayed. In Current Channel,
Protection Path should be displayed.
3. Select By Function and select Tributary Loopback from the drop-down menu.
4. In Tributary Loopback, select Non-Loopback.
5. Click Apply.
The Confirm dialog box is displayed.
6. Click OK.
----End
Prerequisites
l The equipment is configured with ERPS.
l The network cable for carrying the working and protection Ethernet services of ERPS is
properly connected.
East West
NE B
Protection channel East
West
NE A NE D
East
West
Working channel
NE C
West
East
Procedure
Step 1 Before the switching, query the status of the protection group that is configured on NE D.
1. Select the NE from the Object Tree in the NE Explorer of NE D, and choose
Configuration > Ethernet Protection > ERPS Management from the Function Tree.
2. Select the ERPS protection group to be queried, and click Query.
3. The value of State Machine Status should be Idle.
Step 2 Refer to A.13.3 Testing Ethernet Services to test availability of the Ethernet services.
The LossRate in the Detection Result should be 0.
4. Click Apply.
Step 4 After the switching, query the status of the protection group that is configured on NE D.
1. Select the NE from the Object Tree in the NE Explorer of NE D, and choose
Configuration > Ethernet Protection > ERPS Management from the Function Tree.
2. Select the ERPS protection group to be queried, and click Query.
3. The value of State Machine Status should be Protection.
Step 5 Refer to A.13.3 Testing Ethernet Services to test availability of the Ethernet services.
The LossRate in the Detection Result should be 0.
----End
Prerequisites
l The MPLS tunnel protection group must be created properly.
l The NE user must have the authority of Operation Level or higher.
Background Information
1:1 protection
In normal situations, services are transmitted in the working tunnel. That is, services are
transmitted and received in a different tunnel respectively. When the working tunnel is faulty,
the equipment at the transmit end transmits services through the protection tunnel, and the
equipment at the receive end receive services through the protection tunnel after a negotiation
through the APS protocol. Therefore, service switching is realized.
Figure A-9 Connection diagram for testing the MPLS APS protection
Working Tunnel
NE A NE B
Protection Tunnel
Procedure
Step 1 Query the switching status of the current MPLS tunnel 1:1 protection group on NE A and NE
B.
1. In the NE Explorer, select NE A and then choose Configuration > APS Protection
Management from the Function Tree.
2. Click the Tunnel APS Management tab, right-click the tested protection group, and then
choose Query Switching Status from the shortcut menu, to check the MPLS protection
group configured on the NE.
3. Choose the protection group for switching, and check its switching status. In normal
situations, the switching status should be Normal.
Step 2 Switch the services to the protection tunnel manually and forcedly.
1. In the NE Explorer, select NE A and then choose Configuration > APS Protection
Management from the Function Tree.
2. Click the Tunnel APS Management tab and choose the protection group for switching.
3. Right-click the tested protection group, and then choose Forced Switching from the
shortcut menu.
NOTE
l Forced switching: With the highest priority, the operation is performed no matter whether the
current status of the protection tunnel is normal.
l Manual switching: The operation is performed only when the status of the protection tunnel is
normal.
Step 3 Query the switching status of the MPLS 1:1 protection groups on NE A and NE B after the
switching.
1. In the NE Explorer, select NE A and then choose Configuration > APS Protection
Management from the Function Tree.
2. Click the Tunnel APS Management tab and choose the protection group for switching.
3. Right-click the tested protection group and then choose Query Switching Status from the
shortcut menu, to check Switching Status of the tunnel protection group.
In normal situations, the switching status should be Forced Switching.
4. Query Active Tunnel of the tunnel protection group.
In normal situation, Working should be Standby, and Protection should be Active.
NOTE
l If Forced Switching is performed at the previous step, the state of the protection group should be
Forced Switching.
l If Manual Switching to Protection is performed at the previous step, the state of the protection group
should be Manual (Working to Protection) Switching.
----End
Prerequisites
l The equipment must be configured with linear MSP.
l The working and protection optical fibers of the linear MSP are connected properly.
NE A Working channel NE B
Protection channel
Precautions
NOTE
If no BER tester is available on site, you can compare the values of West Switching Status in Slot Mapping
Relation before and after the protection switching.
Procedure
Step 1 Check whether a BER tester is available at the central site.
If... Then...
A BER tester is available on site Perform Step 2 to Step 10.
No BER tester is available on site Perform Step 5 to Step 9.
Step 2 At the central site NE A, connect one E1 port to the BER tester.
Step 3 At the remote site NE B, perform a software inloop at the corresponding E1 port by using the
NMS.
1. Select the PDH interface board in the Object Tree.
2. In the Function Tree, choose Configuration > PDH Interface.
3. Select By Function and select Tributary Loopback from the drop-down menu.
Step 4 Test the BER by using the BER tester. The BER tester should show that no bit errors occur.
If bit errors occur, see the Maintenance Guide for handling the bit errors.
Step 5 Before the switching, query the status of the protection group that is configured on NE A.
1. Select the NE from the Object Tree in the NE Explorer of NE A, and then choose
Configuration > Linear MS from the Function Tree.
2. In Slot Mapping Relation, select Working Unit.
3. Click Query, and then select Query Switching Status.
In Slot Mapping Relation, the value of West Switching Status should be Idle.
NOTE
In the case of the working and protection units of the services that are configured with the linear MSP, the
values of West Switching Status should be Idle. If a fault arises, you must rectify the fault and proceed
with the linear MSP switching testing.
If... Then...
The BER tester is available on site Check the test result on the BER tester. It
should show that the services are restored after
a transient interruption.
No BER tester is available on site, and the See A.13.1 Testing E1 Services Using
E1 services are transmitted on the optical PRBS to test availability of the E1 services.
fiber link.
Step 8 After the switching, query the status of the protection group that is configured on NE A.
1. Select the NE from the Object Tree in the NE Explorer of NE A, and then choose
Configuration > Linear MS from the Function Tree.
2. In Slot Mapping Relation, select Working Unit.
3. Click Query, and then select Query Switching Status.
In Slot Mapping Relation, the value of West Switching Status should be Switch upon
signal failure.
NOTE
In the case of the 1+1 linear MSP, Revertive Mode can be set to Revertive or Non-Revertive. In the case
of the 1:N linear MSP, Revertive Mode is always set to Revertive.
l After the automatic switching occurs on the equipment, the services are restored. If Revertive
Mode is set to Revertive for the linear MSP, the change in values of West Switching Status and
Protected Unit can be queried after the WTR time expires.
l After the automatic switching occurs on the equipment, the services are restored. If Revertive
Mode is set to Non-Revertive for the linear MSP, stop and then start the MSP protocol to restore the
value of West Switching Status to Idle.
----End
A.13.6.7 Switching the System Control Unit and the Cross-Connect Unit
When the OptiX RTN 950 is configured with two system control, cross-connect, and timing
boards, you can manually switch the system control unit and the cross-connect unit as required.
Prerequisites
The NE user must have the authority of Operation Level or higher.
Procedure
Step 1 Select the desired NE from the NE Explorer.
Step 2 Choose Configuration > Board 1+1 Protection from the Function Tree.
If... Then...
Active Board is set to Working Board Click Working/Protection Switching.
Active Board is set to Protection Board Click Restore Working/Protection.
----End
B Parameters Description
B.6 Parameters for Ethernet Services and Ethernet Features on the Packet Plane
This section describes the parameters for the Ethernet services and Ethernet features on the
packet plane, including service parameters, protocol parameters, OAM parameters, Ethernet port
parameters, and QoS parameters.
B.7 Parameters for Ethernet Services and Ethernet Features on the EoS/EoPDH Plane
This section describes the parameters for the Ethernet services and Ethernet features on the EoS/
EoPDH plane, including service parameters, protocol parameters, OAM parameters, Ethernet
port parameters, and QoS parameters.
Navigation Path
In NE List, click NE Search and choose Advanced Search from the drop-down menu.
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
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 the NEs.
SSL Gateway
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)
Related Tasks
A.2.1.2 Creating NEs by Using the Manual Method
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 User
name and Deselected Name and Password to log in to all the
password to login selected NEs.
Use the user name Selected Deselected When this parameter is selected, enter User
and password that Deselected Name and Password that were used for the
was used last time latest login to log in to the NE.
Related Tasks
A.2.1.3 Logging In to an NE
Navigation Path
1. In the NE Explorer, select the NE from the Object Tree and choose Configuration > NE
Attribute from the Function Tree.
2. Click Modify NE ID.
Related Tasks
A.2.1.6 Changing the NE ID
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.
Related Tasks
A.2.1.8 Synchronizing the NE Time
Navigation Path
1. In the NE Explorer, select the NE from the Object Tree and then choose Configuration >
NE Time Localization Management from the Function Tree.
2. Set the correct time zone and daylight saving time of the NE depending on the location of
the NE.
Related Tasks
A.2.1.9 Localizing the NE Time
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. In the NE Explorer, select the NE and then choose Configuration > Automatic Disabling
of NE Function from the Function Tree.
2. Click the Automatic Disabling of NE Function tab.
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.
Related Tasks
A.2.4.1 Setting NE Communication Parameters
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 PDH It is recommended that you use the default
D4-D12 radio whose value, except for the following cases:
transmission l If the IP DCN or OSI over DCC solution
D1-D12 capacity is less than is adopted, Channel for the SDH line
D1-D1 16xE1) ports is set to a value that is the same as
D1-D3 (for other the value 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.
Protocol Type HWECC HWECC It is recommended that you use the default
TCP/IP value, except for the following cases:
Related Tasks
A.2.4.2 Configuring DCCs
A.2.4.14 Configuring Interface IP Addresses of an ABR
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.
Related Tasks
A.2.4.3 Configuring DCC Transparent Transmission
Navigation Path
Click an NE in the NE Explorer. Choose Communication > ECC Management from the
Function Tree.
ECC Extended Auto mode Auto mode It is recommended that you use the default
Mode Specified mode value.
Related Tasks
A.2.4.8 Configuring Extended ECC Communication
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Communication > NE ECC
Link Management from the Function Tree.
Related Tasks
A.2.4.21 Querying ECC Routes
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 Test or Trace Route from the drop-down menu.
Traceroute Parameters
Parameter Value Range Default Value Description
Related Tasks
A.2.4.24 Verifying Connectivity of an ECC Network
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.
Related Tasks
A.2.4.22 Querying IP Routes
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.
Related Tasks
A.2.4.9 Creating Static IP Routes
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
Related Tasks
A.2.4.25 Verifying Connectivity of an IP DCN Network
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
DCC Hello Timer 1 to 255 10 l DCC Hello Timer(s) specifies the Hello
(s) packet timer for the DCC channel or
inband DCN.
l The Hello packets are used for detecting
the neighbor router on the network that
is connected to the router. By
periodically transmitting the hello
packets, you can determine whether the
interface on the neighbor router is still in
the active status.
l DCC Hello Timer(s) determines the
interval for the hello packet timer to
transmit the hello packets.
l In the case of two interconnected NEs,
DCC Hello Timer(s) must be set to the
same value.
l Unless otherwise specified, it is
recommended that this parameter take its
default value.
LAN Hello Timer 1 to 255 10 l DCC Hello Timer(s) specifies the hello
(s) packet timer at the Ethernet network
management port or NE cascading port.
l The hello packets are used for detecting
the neighbor router on the network that
is connected to the router. By
periodically transmitting the hello
packets, you can determine whether the
interface on the neighbor router is still in
the active status.
l LAN Hello Timer(s) determines the
interval for the hello packet timer of the
NE to transmit the hello packets.
l In the case of two interconnected NEs,
LAN Hello Timer(s) must be set to the
same value.
l Unless otherwise specified, it is
recommended that this parameter take its
default value.
Related Tasks
A.2.4.10 Setting OSPF Protocol Parameters
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.
Related Tasks
A.2.4.16 Enabling the Proxy ARP
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
Related Tasks
A.2.4.12 Configuring the Network Information of an ABR
A.2.4.15 Configuring the OSPF Authentication Type
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.
Related Tasks
A.2.4.11 Creating an OSPF Area
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.
Related Tasks
A.2.4.13 Creating a Manual Route Aggregation Group
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. Select the NE from the Object Tree in the NE Explorer. Choose Communication > OSI
Management from the Function Tree.
2. Click the Network Layer Parameters tab.
Related Tasks
A.2.4.17 Configuring the CLNS Role
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Communication > OSI
Management from the Function Tree.
2. Click the Routing Table tab.
Related Tasks
A.2.4.23 Querying OSI Routes
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Communication > OSI
Management from the Function Tree.
2. Click the OSI Tunnel tab.
LAPD Parameters
Parameter Value Range Default Value Description
Related Tasks
A.2.4.18 Configuring the OSI Tunnel
Navigation Path
1. In the NE Explorer, select the desired NE from the Object Tree and choose
Communication > OSI Management from the Function Tree.
2. Click the Port Parameters tab.
Related Tasks
A.2.4.19 Configuring OSI Port Parameters
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.
Tunnel Bandwidth - - The OptiX RTN 950 does not support this
(Kbit/s) parameter.
Related Tasks
A.2.4.4 Configuring the VLAN ID and Bandwidth Used by an Inband DCN
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.
Related Tasks
A.2.4.6 Setting Parameters of Inband DCN
A.2.4.14 Configuring Interface IP Addresses of an ABR
Navigation Path
l In the NE Explorer, select the NE from the Object Tree and then choose
Communication > DCN Management from the Function Tree.
Parameters
Parameter Value Range Default Value Description
Enabled Status Disabled Disabled l Specifies the enabling status of the port.
Enabled 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.
Related Tasks
A.2.4.7 Configuring Access Control
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 PHB service class of inband
EF is VLAN) DCN packets.
Related Tasks
A.2.4.5 Configuring the Priority of Inband DCN Packets
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.
Config Status Auto Auto When the OptiX RTN 950 uses the L2 DCN
Disabled solution, the RSTP protocol can be used to
prevent L2 forwarding loops. It is
recommended that the RSTP protocol uses
its default enable/disable mode Auto for the
OptiX RTN 950 NE level. That is, the RSTP
protocol is automatically enabled/disabled
depending on the enable/disable status of
the L2 DCN function over IF ports.
Related Tasks
A.2.4.20 Enabling/Disabling the RSTP Protocol When the L2 DCN Solution Is Used
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.
Navigation Path
Select the required NE from the Object Tree in the NE Explorer. Choose Security > NE User
Management from the Function Tree.
Related Tasks
A.2.6.2 Changing the Password of an NE User
Navigation Path
1. Select the required NE from the Object Tree in the NE Explorer. Choose Security > NE
User Management from the Function Tree.
2. Click Create.
Related Tasks
A.2.6.1 Creating an NE User
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Security > LCT Access
Control from the Function Tree.
LCT Access Access Allowed Access Allowed l No NMS user logs in to the NE. In this
Control Switch Disable Access case, when the LCT requests an LCT
user to log in to the NE, the NE does not
check the status of LCT Access Control
Switch, and directly allows the LCT user
to log in to the NE.
l An NMS user first logs in to the NE. In
this case, when the LCT requests an LCT
user to log in to the NE, the NE
determines whether to allow the LCT
user to log in to the NE through the LCT
according to the status of LCT Access
Control Switch.
l An LCT user first logs in to the NE. In
this case, when the NMS requests an
NMS user to log in to the NE, the NMS
user can directly log in to the NE. After
the NMS user successfully logs in to the
NE, the online LCT user is not affected.
l When both the LCT user and NMS user
log in to the NE, the online LCT user is
not affected after LCT Access Control
Switch is set to Disable Access.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link
Configuration from the Function Tree.
2. Click the XPIC tab.
3. Click New.
Parameters
Parameter Value Range Default Value Description
Related Tasks
A.3.2 Creating an XPIC Workgroup
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link
Configuration from the Function Tree.
2. Click the XPIC tab.
Related Tasks
A.3.3 Setting the AM Attributes of the XPIC Workgroup
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link
Configuration from the Function Tree.
2. Click the N+1 Protection tab.
3. 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.
l It is recommended that you use the
default value.
Select Mapping Working Unit Working Unit l This parameter specifies the mapping
Direction Protection Unit direction of N+1 protection.
l This parameter is set according to the
planning information.
Related Tasks
A.3.6 Creating an N+1 Protection Group
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link
Configuration from the Function Tree.
2. Click the N+1 Protection tab.
Related Tasks
A.3.8 Querying the IF N+1 Protection Status
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link
Configuration from the Function Tree.
2. Click the IF 1+1 Protection tab.
3. Click New.
Parameters
Parameter Value Range Default Value Description
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. 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 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.
Related Tasks
A.3.1 Creating an IF 1+1 Protection Group
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link
Configuration from the Function Tree.
2. Click the IF 1+1 Protection tab.
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.
Related Tasks
A.3.7 Querying the IF 1+1 Protection Status
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.
2. Click New.
Related Tasks
A.3.12 Creating a PLA Group
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 Parameters
Parameter Value Range Default Value Description
Related Tasks
A.3.13 Querying the Status of a PLA Group
Navigation Path
1. In the NE Explorer, select the NE and then choose Configuration > Link
Configuration from the Function Tree.
2. Click the IF/ODU Configuration tab.
Equipment Information
Parameter Value Range Default Value Description
Related Tasks
A.3.4 Configuring the IF/ODU Information of a Radio Link
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.
l This parameter is set
according to the planning
information.
Select Mapping West Working Unit West Working Unit This parameter specifies the mapping
Direction West Protection direction of the linear MSP.
Unit
Related Tasks
A.4.1 Configuring Linear MSP
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear MS
from the Function Tree.
Related Tasks
A.4.2 Querying the Status of the Linear MSP
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Cross-
Connection Configuration from the Function Tree.
2. Click Scheme to change the VC-12 timeslot numbering policy used by the cross-
connection.
3. Click New.
Parameters
Parameter Value Range Default Value Description
Related Tasks
A.5.1 Creating the Cross-Connections of Point-to-Point Services
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Cross-
Connection Configuration from the Function Tree.
2. Click Scheme to change the VC-12 timeslot numbering policy used by the cross-
connection.
3. Click Create SNCP.
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 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.
Related Tasks
A.5.2 Creating Cross-Connections of SNCP Services
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Cross-
Connection 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 from the shortcut menu.
3. Select the unidirectional service. Right-click the selected service and choose Convert to
SNCP 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 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.
Related Tasks
A.5.7 Converting a Normal Service into an SNCP Service
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Cross-
Connection Configuration from the Function Tree.
Cross-Connection Parameters
Parameter Value Range Default Value Description
Related Tasks
A.5.9 Querying TDM Services
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SNCP Service
Control from the Function Tree.
Related Tasks
A.5.5 Configuring the Automatic Switching of SNCP Services
A.5.11 Querying the Protection Status of SNCP Services
Navigation Path
In the NE Explorer, select the IF board from the Object Tree and choose Alarm > Triggered
Alarm Insertion from the Function Tree.
Related Tasks
A.5.4 Inserting E1_AIS upon a TU_AIS Condition
A.5.4 Inserting E1_AIS upon a TU_AIS Condition
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.
2. Click the Basic Attributes tab.
Related Tasks
A.6.4.1 Setting Basic Attributes of Smart E1 Ports
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.
2. Click the Advanced Attributes tab.
Related Tasks
A.6.4.2 Setting Advanced Attributes of Smart E1 Ports
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.
Related Tasks
A.6.6.1 Setting the Basic Attributes of Ethernet Ports
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.
Related Tasks
A.6.6.2 Configuring the Traffic Control of Ethernet Ports
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.
The parameter Layer 2 Attributes is meaningful only when Port Mode is set to Layer 2.
Ingress UNI Tagged frame The port receives the The port discards The port receives
frame. the frame. the frame.
Untagged frame The port discards the The ports add the The ports add the
frame. VLAN tag, to which VLAN tag, to which
Default VLAN ID Default VLAN ID
and VLAN and VLAN
Priority Priority
correspond, to the correspond, to the
frame and receive frame and receive
the frame. the frame.
Egress UNI 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.
Related Tasks
A.6.6.3 Setting the Layer 2 Attributes of Ethernet Ports
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.
Related Tasks
A.6.6.4 Setting Layer 3 Attributes of Ethernet Ports
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.
Related Tasks
A.6.6.5 Setting the Advanced Attributes of Ethernet Ports
Navigation Path
1. In the NE Explorer, select the required NE from the Object Tree and choose
Configuration > Interface Management > Serial Port from the Function Tree.
2. Click the Basic Attributes tab.
Related Tasks
A.6.5.2 Setting Basic Attributes of Serial Ports
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.
Related Tasks
A.6.5.1 Creating Serial Ports
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
Related Tasks
A.6.7.1 Setting the Basic Attributes of IF_ETH Ports
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.
The parameter Layer 2 Attributes is meaningful only when Port Mode is set to Layer 2.
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-3.
Ingress Port Tagged frame The port receives the The port discards The port receives
frame. the frame. the frame.
Untagged frame The port discards the The port receives The port receives
frame. the frame after the the frame after the
VLAN tag that VLAN tag that
corresponds to corresponds to
"Default VLAN ID" "Default VLAN ID"
and "VLAN 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.
Related Tasks
A.6.7.2 Setting the Layer 2 Attributes of IF_ETH Ports
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.
Related Tasks
A.6.7.3 Setting Layer 3 Attributes of IF_ETH Ports
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 Advanced Attributes tab.
Related Tasks
A.6.7.4 Setting the Advanced Attributes of IF_ETH Ports
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
NOTE
Related Tasks
A.6.8.1 Setting IF Attributes
A.6.8.4 Querying the AM Status
A.6.8.6 Modifying the Hybrid/AM Attributes
A.12.4 Configuring the Wayside E1 Service
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
ATPC Lower - -70.0 receive 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.
l You can set the ATPC upper threshold
only when ATPC Automatic
Threshold(dBm) is set to Disabled.
Related Tasks
A.6.8.2 Configuring ATPC Attributes
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
Related Tasks
A.6.8.3 Setting Advanced AM Attributes
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
Related Tasks
A.6.8.5 Querying ATPC Adjustment Records
Navigation Path
Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > PRBS Test from the Function Tree.
Parameters
Parameter Value Range Default Value Description
Navigation Path
l Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU
Interface from the Function Tree.
l Click the Radio Frequency Attributes tab.
Parameters
Parameter Value Range Default Value Description
Related Tasks
A.6.9.1 Setting ODU Transmit Frequency Attributes
Navigation Path
l Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU
Interface from the Function Tree.
l Click the Power Attributes tab.
Parameters
Parameter Value Range Default Value Description
Related Tasks
A.6.9.3 Setting ODU Power Attributes
Navigation Path
l Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > ODU Interface from the Function Tree.
l Click the Equipment Information tab.
Parameters
Parameter Value Range Default Value Description
Related Tasks
A.6.9.2 Querying ODU Information
Navigation Path
l Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU
Interface from the Function Tree.
l Click the Advanced Attributes tab.
Parameters
Parameter Value Range Default Value Description
Related Tasks
A.6.9.4 Setting ODU Advanced Attributes
Navigation Path
1. Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > SDH Interface from the Function Tree.
2. Select By Board/Port(Path), and select Port or VC4 Path 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 Path is selected from the list box.
Related Tasks
A.6.1 Setting the Parameters of SDH Ports
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 Path 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 the
CRC-4 Multiframe OptiX RTN 950, 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 the OptiX
RTN 950 is used, it is recommended that
E1 Frame Format take its default value
Unframe. If E1 Frame Format is
Unframe, the OptiX RTN 950
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.
Related Tasks
A.6.2 Setting the Parameters of PDH Ports
Navigation Path
Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > PRBS Test from the Function Tree.
Parameters
Parameter Value Range Default Value Description
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.
Related Tasks
A.6.3.1 Configuring RSOHs
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.
Related Tasks
A.6.3.2 Configuring VC-4 POHs
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.
Related Tasks
A.6.3.3 Configuring VC-12 POHs
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.
2. Click the Basic Attributes tab.
3. Choose New.
Port Type EoA Virtual EoA Virtual This parameter displays or specifies the port
Interface Interface type of an Ethernet virtual interface.
VLAN Sub Interface The OptiX RTN 950 allows Port Type to be
set to VLAN Sub Interface only.
Specify IP Address Manually Unspecified This parameter specifies whether to set the
Unspecified IP address for a port.
l Unspecified: indicates that the IP
address will not be specified for a port.
l Manually: indicates that the IP address
will be specified for a port. If the
specified IP address is a valid value, it
will become the IP address of this port.
Layer 3 Attributes
Parameter Value Range Default Value Description
Related Tasks
A.6.10 Creating VLAN Sub-Interfaces
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 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.
Related Tasks
A.7.3.2 Configuring UNI-UNI E-Line Services
A.7.3.3 Configuring NNI-NNI E-Line Services (Carried by QinQ Links)
A.7.3.4 Configuring UNI-NNI E-Line Services (Carried by QinQ Links)
A.7.3.5 Configuring UNI-NNI E-Line Services (Carried by PWs)
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.
Related Tasks
A.7.3.7 Creating a VLAN Forwarding Table for an E-Line Service
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
Related Tasks
A.7.3.9 Configuring IEEE 802.1d Bridge-Based E-LAN Services
A.7.3.10 Configuring IEEE 802.1q Bridge-Based E-LAN Services
A.7.3.11 Configuring IEEE 802.1ad Bridge-Based E-LAN Services
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
Related Tasks
A.7.4.1 Creating a Static MAC Address Entry
A.7.4.2 Creating a Blacklist Entry of MAC Addresses
A.7.4.3 Configuring the Aging Parameters of a MAC Address Table
A.7.4.4 Querying or Deleting a Dynamic MAC Address
A.7.5 Setting the Mode for Processing an Unknown Frame of the E-LAN Service
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.
Related Tasks
A.7.3.1 Configuring the QinQ Link
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 Create.
UNI Parameters
Parameter Value Range Default Value Description
Control Word Not in use Not in use For ETH PWE3 services,
this parameter has a fixed
value of Not in use.
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
Related Tasks
A.7.3.6 Creating E-AGGR Services
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
Related Tasks
A.7.1.1 Creating Ethernet Ring Protection Instances
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
Current Node
Related Tasks
A.7.1.2 Setting the Parameters of Ethernet Ring Protocol
A.7.1.3 Querying the Status of the Ethernet Ring Protocol
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.
Related Tasks
A.7.6.1 Creating the MSTP Port Group
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. On the main interface, select the port group to be configured.
4. Click Config. The Config Port Group dialog box is displayed.
Related Tasks
A.7.6.7 Modifying the Configuration Data of the MSTP Port Group
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
Related Tasks
A.7.6.2 Setting the Bridge Parameters of the MSTP
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
Related Tasks
A.7.6.3 Setting the Parameters of the CIST
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
Related Tasks
A.7.6.4 Querying the CIST Running Information
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.
Related Tasks
A.7.2.1 Creating a LAG
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.
Related Tasks
A.7.2.2 Setting LAG Parameters
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.
Related Tasks
A.7.10.1 Configuring Point-to-Point LPT Traversing an L2 Network
A.7.10.2 Configuring Point-to-Point LPT Traversing a PSN or QinQ 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-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.
Related Tasks
A.7.10.1 Configuring Point-to-Point LPT Traversing an L2 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.
Related Tasks
A.7.10.3 Configuring Point-to-Multipoint LPT
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.
Related Tasks
A.7.10.3 Configuring Point-to-Multipoint LPT
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Service OAM from the Function Tree.
2. Click the Maintenance Association tab.
3. Choose New > New Maintenance Domain.
Related Tasks
A.7.8.1 Creating an MD
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Service OAM 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.
Related Tasks
A.7.8.2 Creating an MA
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Service OAM 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.
Related Tasks
A.7.8.3 Creating MEPs
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Service OAM from the Function Tree.
Related Tasks
A.7.8.4 Creating Remote MEPs in an MA
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Service OAM 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.
Related Tasks
A.7.8.5 Creating MIPs
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Service OAM 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.
Related Tasks
A.7.8.7 Performing an LB Test
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Service OAM 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.
Related Tasks
A.7.8.8 Performing an LT Test
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 Loopback tab.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Port OAM from the Function Tree.
2. Click the OAM Parameter tab.
Related Tasks
A.7.9.1 Enabling the OAM Auto-Discovery Function
A.7.9.2 Enabling the Remote Alarm Support for Link Event
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Port OAM 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 Window step of 100 monitoring error frames.
(ms)
Error Frame 1488 to 892800000, 892800000 This parameter specifies the window of
Period Window in step of 1 monitoring the error frame period.
(frame)
Error Frame 10 to 900, in step of 60 This parameter specifies the time window of
Second Window(s) 1 monitoring the error frame second.
Related Tasks
A.7.9.3 Modifying the OAM Error Frame Monitoring Threshold
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 DiffServ domain exists on the OptiX RTN 950 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.
Related Tasks
A.7.7.2 Modifying the Mapping Relationships for the DS Domain
A.7.7.10 Querying the DS Domain of a Port
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.
Related Tasks
A.7.7.1 Creating a DS 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. 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 950, 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.
Related Tasks
A.7.7.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types
Grooming Police After SP CS7, CS6, EF, BE: SP l The strict priority (SP)
Reloading WRR AF4, AF3, AF2, AF1: scheduling algorithm
WRR 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 950
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.
Related Tasks
A.7.7.5 Modifying the Port Policy
A.7.7.7 Setting the Port That Uses the Port Policy
A.7.7.9 Querying the Port Policy
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 (SP)
Reloading WRR AF4, AF3, AF2, AF1: scheduling algorithm
WRR 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 950
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.
Related Tasks
A.7.7.4 Creating a Port Policy
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
Related Tasks
A.7.7.6 Creating Traffic
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.
Related Tasks
A.7.7.8 Configuring Port Shaping
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.
Related Tasks
A.8.3.1 Creating Ethernet Private Line Services
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.
Operation Type l Add S-VLAN Strip S-VLAN l When used for private line services,
l Transparently QinQ can process VLAN tags in
transmit C- different manners as required.
VLAN l When Service Direction is set to
l Transparently Unidirectional, you can set Operation
transmit S- Type to Strip S-VLAN.
VLAN l Set this parameter according to actual
l Transparently situations.
transmit S-
VLAN and C-
VLAN
l Translate S-
VLAN
l Translate S-
VLAN and
transparently
transmit C-
VLAN
l Strip S-VLAN
S-VLAN Priority AUTO AUTO Specifies the S-VLAN priority. The bigger
Priority 0 to Priority the value, the higher the priority.
7
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.
Related Tasks
A.8.3.5 Creating QinQ-Based EVPL Services
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-17 Parameters on the main interface (Display QinQ Shared Service is not selected)
Table B-18 Parameters on the main interface (Display QinQ Shared Service is selected)
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, all
Mode Filter Enable Filter Enable the VLANs share one MAC address
(supported by the (IEEE 802.1q table. When the bridge uses the IVL
IEEE 802.1q bridge and the mode, each VLAN has an MAC address
bridge and IEEE IEEE 802.1ad table.
802.1ad bridge, bridge) l When the filtering function is enabled at
unsupported by l SVL/Ingress the ingress port, the ingress port checks
the IEEE 802.1d Filter Disable the VLAN tags of all incoming packets.
bridge) (IEEE 802.1d If the VLAN ID contained in the VLAN
l SVL/Ingress bridge) tag of a packet is not included in the
Filter Disable VLAN filtering table, the packet is
(supported by the discarded. When the filtering function is
IEEE 802.1d disabled at the ingress port, the ingress
bridge and IEEE port does not check any VLAN tag of the
802.1ad bridge, incoming packets.
unsupported by
the IEEE 802.1q
bridge)
Hybrid
10M Full-Duplex
100M Half-Duplex
100M Full-Duplex
GE port: 1000M
Full-Duplex
Service Direction Bidirectional Bidirectional l Specifies the direction of the bound path.
Uplink l Set this parameter to Bidirectional
Downlink unless otherwise specified.
Related Tasks
A.8.3.2 Creating Ethernet LAN Services
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.
802.1ad
Bridge Switch l IVL/Ingress l IVL/Ingress l When the bridge uses the SVL mode, all
Mode Filter Enable Filter Enable (the the VLANs share one MAC address
(supported by the 802.1q bridge table. When the bridge uses the IVL
802.1q bridge and the 802.1ad mode, all the VLANs correspond to their
and 802.1ad bridge) respective MAC address tables.
bridge, l SVL/Ingress l If the ingress filter is enabled, the VLAN
unsupported by Filter Disable tag is checked at the ingress port. If the
the 802.1d (the 802.1d VLAN ID does not equal the VLAN ID
bridge) bridge) of the port defined in the VLAN filtering
l SVL/Ingress table, the packet is discarded. If the
Filter Disable ingress filter is disabled, the preceding
(supported by the described check is not conducted.
802.1d bridge
and 802.1ad
bridge,
unsupported by
the 802.1q
bridge)
10M Full-Duplex
100M Half-Duplex
100M Full-Duplex
GE port: 1000M
Full-Duplex
Operation Type Add S-VLAN base Add S-VLAN base For the meaning of each operation type, see
for port for port 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
Service Direction Bidirectional Bidirectional l Specifies the direction of the bound path.
Uplink l Set this parameter to Bidirectional
Downlink unless otherwise specified.
Related Tasks
A.8.3.6 Creating IEEE 802.1ad Bridge-Based EVPLAN Services
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.
Related Tasks
A.8.4.1 Creating a Static MAC Address Entry
A.8.4.2 Creating a Blacklist Entry of a MAC Address
A.8.4.4 Querying or Deleting a Dynamic MAC Address
A.8.4.5 Querying the Actual Capacity of a MAC Address Table
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.
Related Tasks
A.8.3.4 Creating the VLAN Filtering Table
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 the
l 1 to 12 Day 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.
Related Tasks
A.8.4.3 Setting the Aging Time of a MAC Address Table Entry
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
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 Protocol Enabled tab.
Related Tasks
A.8.6.1 Configuring the Type and Enabled Status of the Spanning Tree Protocol
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.
Related Tasks
A.8.6.2 Setting the Parameters of Spanning Tree Protocol
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.
Priority 0-240 128 l The most significant eight bits of the port
ID indicate the port priority.
l The smaller the value of this parameter,
the higher the priority.
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.
Related Tasks
A.8.6.2 Setting the Parameters of Spanning Tree Protocol
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.
Related Tasks
A.8.6.3 Querying the Running Information About the Spanning Tree Protocol
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.
Edge Port Status - - Displays the enabled status of the edge port.
Related Tasks
A.8.6.3 Querying the Running Information About the Spanning Tree Protocol
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.
Point-to-point Adaptive Adaptive connection l This parameter is valid only when the
Attribute connection RSTP is used.
Link connection l If this parameter is set to Adaptive
Shared media connection, the bridge determines the
actual point-to-point attribute of the port
according to the actual working mode of
the port. If the port works in full-duplex
mode, the actual point-to-point attribute
of the port is True. If the port works in
half-duplex mode, the actual point-to-
point attribute of the port is False.
l If you set this parameter to Link
connection, the actual point-to-point
attribute of the port is True.
l If you set this parameter to Shared
media, the actual point-to-point attribute
of the port is False.
l Only the port whose actual point to point
attribute is True can transmit the fast
transition request and response
messages.
l It is recommended that this parameter
takes the default value.
Related Tasks
A.8.6.2 Setting the Parameters of Spanning Tree Protocol
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.
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.
Related Tasks
A.8.7.1 Configuring the IGMP Snooping Protocol
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.
Related Tasks
A.8.7.2 Configuring Static Multicast Entries
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.
Related Tasks
A.8.7.3 Modifying the Aging Time of a Multicast Table Entry
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 Load
MAC Sharing Mode Sharing is Sharing.
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.
Related Tasks
A.8.2.1 Creating a LAG
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.
Port Priority 0-65535 32768 l This parameter is valid only when LAG
Type of a LAG is set to Static.
l This parameter indicates the priorities of
the ports in a LAG as defined in the
LACP protocol. The smaller the value,
the higher the priority.
System Priority 0-65535 32768 l This parameter is valid only when LAG
Type of a LAG is set to Static.
l This parameter indicates the priority of a
LAG. The smaller the value, the higher
the priority.
l When the local LAG and the opposite
LAG negotiate through LACP packets,
one can obtain the system priority of the
other. The LAG with the higher system
priority is considered as the comparison
result. Then, the aggregation
information is consistent at both ends. If
the local LAG and the opposite LAG
have the same system priority, the MAC
addresses are compared. The LAG with
a lower MAC address is considered as
the comparison result. Then, the
aggregation information is consistent at
both ends.
Related Tasks
A.8.2.2 Setting Parameters for LAGs
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.
Related Tasks
A.8.11.1 Configuring LPT for Point-to-Point Services
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 the
Ethernet 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 the
Ethernet selected port is a VCTRUNK.
GFP-CSF l The default value is recommended.
Related Tasks
A.8.11.2 Configuring LPT for Point-to-Multipoint Services
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 level.
Consumer Low(5)
Provider High(4)
Provider Low(3)
Operator High(2)
Operator Middle(1)
Operator Low(0)
Related Tasks
A.8.9.1 Creating MDs
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.
Related Tasks
A.8.9.2 Creating MAs
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.
MEP ID Standard MP: 00-00-0000 Uniquely identifies an MP. From the highest
00-00-0000 to FF- to the lowest, the first byte indicates the
FF-1FFF network number, the second byte indicates
Common MP: the number of the node in the local network,
00-00-0000 to FF- and the third and forth bytes indicate the ID
FF-FF00 of the MP on the network node. The MP ID
must be unique in the entire network.
Level Consumer High(7) Provider High(4) Specifies the level of a common MP. The
Consumer Middle greater the value, the higher the level.
(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 value,
1000 to 60000, in the CC test will become less capable in
step of 100 detecting service interruptions. The
default value is recommended.
l This parameter can be set only for an
MEP.
Related Tasks
A.8.9.3 Creating MPs
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.
Related Tasks
A.8.9.5 Performing an LB Test
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.
Related Tasks
A.8.9.6 Performing an LT Test
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.
Related Tasks
A.8.10.1 Enabling the OAM Auto-Discovery Function
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 Window step of 100 Window (ms), if the number of error frames
(ms) 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 Frame
Period Window in step of 1 FE port: 148800 Period Window (frames), if the number of
(frames) 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, this
Second Window(s) 1 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.
Related Tasks
A.8.10.3 Modifying the OAM Error Frame Monitoring Threshold
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.
Related Tasks
A.8.10.2 Enabling the Link Event Notification
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 this
Port+SVLAN Flow flow type is the line service or Layer 2
Port+CVLAN switching service that uses this port as
+SVLAN Flow 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.
NOTE
An EMS6 board does not support Port+VLAN
+Priority Flow.
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 Layer
PORT7, 2 switching service, set this parameter to
VCTRUNK1 to a mounted port of the bridge.
VCTRUNK8
Related Tasks
A.8.8.1 Creating a Flow
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 packet
Size (kbyte) EMS6: 0 to 16384 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 packets
EMS6 (GE ports): 0 whose rate exceeds the CIR can pass the
to 1024000, in steps restriction of the CAR and are marked
of 64 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.
Related Tasks
A.8.8.2 Creating the CAR
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.
CoS Type simple simple l If the CoS type of a flow is set to simple,
VLAN Priority all the packets in this flow are directly
scheduled to a specified egress queue.
IPTOS
l If the CoS type of a flow is set to VLAN
DSCP priority, the packets in this flow are
scheduled to specified egress queues
according to the user priorities specified
in the VLAN tags of these packets.
l If the CoS type of a flow is set to DSCP,
the packets in this flow are scheduled to
specified egress queues according to
differentiated services code point
(DSCP) in the IPv6 tags of these packets.
l If the CoS type of a flow is set to IP TOS,
the packets in this flow are scheduled to
specified egress queues according to the
TOS values carried in the IPv4 packets.
This CoS type is applicable to IPv4
packets.
Related Tasks
A.8.8.3 Creating the CoS
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.
Related Tasks
A.8.8.4 Binding the CAR/CoS
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 rate
EMS6 (FE ports): 0 restriction is directly discarded. When
to 102400, in steps the rate of packets is more than the CIR
of 64 but not more than the PIR, the packets
that exceed the restriction of the CIR
EMS6 (GE ports): 0 enter the buffer of the CIR. When the
to 1024000, in steps buffer overflows, the packets are marked
of 64 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 priority
Queue 3: WRR of 0-6) are the WRR queues and their
Queue 4: WRR 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 packets
Queue 8: SP
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 priority
Queue 3: 4 of 0-6) are the WRR queues and their
Queue 4: 8 weights are 1:2:4:8:16:32:64.
Queue 5: 16
Queue 6: 32
Queue 7: 64
Queue 8: -
Related Tasks
A.8.8.5 Configuring Traffic Shaping for Egress Queues
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 than
Length EMS6: 1518 to 9600 the maximum length of all the data
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-66.
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-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.
Ingress port Tagged frame Receives the frame. Discards the frame. Receives the frame.
Untagged frame Discards the frame. The port receives the The port receives the
frame after adding to frame after adding to
the frame the VLAN the frame the VLAN
tag that contains tag that contains
Default VLAN ID Default VLAN ID
and VLAN and VLAN
Priority. Priority.
Egress port Tagged frame Transmits the frame. The port strips the l If the VLAN ID
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.
Related Tasks
A.8.5.1 Configuring External Ethernet Ports
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.
TAG Tag Aware Tag Aware l With different tag attributes, the port
Access processes frames in different modes. For
details, see Table B-72.
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.
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 Bit Big endian Big endian l When you set this parameter to Big
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 LCAS
from 0, 2000 to performs switching after a delay of time
10000, in the to prevent the situation where an NE
increments of 100 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 The port receives the
frame after adding to frame after adding to
the frame the VLAN the frame the VLAN
tag that contains tag that contains
Default VLAN ID Default VLAN ID
and VLAN and VLAN
Priority. Priority.
Egress port Tagged frame Transmits the frame. The port strips the l If the VLAN ID
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.
Related Tasks
A.8.5.2 Configuring VCTRUNKs on an Ethernet Board
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.
QinQ Type Area 81 00 8100 Specifies the type field of QinQ frames. Set
(Hexadecimal) 88 A8 this parameter according to the type field of
the accessed QinQ frames.
91 00
0600 to FFFF
Related Tasks
A.8.5.3 Modifying the Type Field of QinQ Frames
Navigation Path
1. Select the corresponding board from the Object Tree in the NE Explorer. Choose
Performance > RMON Performance from the Function Tree.
2. Click the Statistics Group tab.
Parameters
Parameter Value Range Default Value Description
Related Tasks
A.11.1 Browsing the Performance Data in the Statistics Group of a Port
Navigation Path
1. Select the corresponding board from the Object Tree in the NE Explorer. Choose
Performance > RMON Performance from the Function Tree.
2. Click the History Group tab.
Parameters
Parameter Value Range Default Value Description
Period End Time - - This parameter specifies the start time and
from/to end time of the monitoring period.
Custom Period 1
Custom Period 2
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Performance > RMON History
Control Group.
Parameters
Parameter Value Range Default Value Description
Period Length(s) 300 to 43200 900(Custom Period l This parameter indicates or specifies the
(Custom Period 1) 1) monitoring period in Custom Period 1
300 to 86400 86400(Custom and Custom Period 2.
(Custom Period 2) Period 2) l The value must be an integer multiple of
30.
Related Tasks
A.11.3 Configuring a Historical Control Group
Navigation Path
l Select the corresponding board from the Object Tree in the NE Explorer. Choose
Performance > RMON Performance from the Function Tree.
l Click the RMON Setting tab.
Event Parameters
Parameter Value Range Default Value Description
Threshold Detect Report All Report All l This parameter indicates or specifies the
Do Not Detect threshold detection method.
Report Only the l If the number of detected events reaches
Upper Threshold the preset threshold, the events are
reported to the NMS. Otherwise, the
Report Only the events are not reported to the NMS.
Lower Threshold
l If an event does not support this
parameter, Not Supported is displayed.
Related Tasks
A.11.2 Configuring an Alarm Group for a Port
A.11.4 Browsing the Performance Data in the Historical Group of a Port
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.
Related Tasks
A.9.2.1 Setting Basic MPLS Attributes
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.
Related Tasks
A.9.2.4 Querying MPLS Tunnel Information
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 Unidirectional Tunnel from the drop-down list.
The New Unicast Unidirectional Tunnel dialog box is displayed.
4. Select New Reverse Tunnel.
Node Type Ingress Ingress Specifies the node type of a forward tunnel.
Egress
Transit
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.6.6.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.6.6.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.6.7.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.6.7.3 Setting Layer 3 Attributes of
IF_ETH Ports.
EXP 0-7 None l Specifies the value of the EXP field in the
None packets transmitted through MPLS
tunnels.
l This parameter is available only if Node
Type is Ingress.
l If this parameter is set to a value from 0
to 7, the EXP field takes its fixed value.
l If this parameter takes its default value
None, the EXP field is set based on the
DiffServ mappings.
Related Tasks
A.9.2.2 Creating a Unidirectional MPLS Tunnel
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.
Transit
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.6.6.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.6.6.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.6.7.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.6.7.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.