Professional Documents
Culture Documents
V100R002C00
Issue 07
Date 2011-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 the 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
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention Description
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
Convention 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.
Compared with the sixth release, the updated contents are as follows:
Section Description
Compared with the fifth release, the updated contents are as follows:
Section Description
Compared with the fourth release, the updated contents are as follows:
Section Description
Compared with the third release, the updated contents are as follows:
Section Description
4.1.4 TDM Timeslot Planning Schemes Added meanings of the timeslot allocation
diagram and timeslot planning principles.
8 Adding and Modifying Configuration Added common tasks for supplementing and
Data adjusting initial configuration data.
Section Description
Section Description
Contents
2 Configuring NEs............................................................................................................................4
2.1 Basic Concepts...................................................................................................................................................5
2.1.1 DCN...........................................................................................................................................................5
2.1.2 GNE and Non-GNE...................................................................................................................................7
2.1.3 ID and IP Address of an NE......................................................................................................................7
2.1.4 Physical Boards and Logical Boards.........................................................................................................8
2.2 Configuration Procedure.....................................................................................................................................9
2.3 Configuration Example (Chain Network)........................................................................................................12
2.3.1 Networking Diagram...............................................................................................................................12
2.3.2 Board Configuration................................................................................................................................12
2.3.3 Service Planning......................................................................................................................................14
2.3.4 Configuration Process..............................................................................................................................14
2.4 Configuration Example (Ring Network)..........................................................................................................17
2.4.1 Networking Diagram...............................................................................................................................17
2.4.2 Board Configuration................................................................................................................................17
2.4.3 Service Planning......................................................................................................................................19
2.4.4 Configuration Process..............................................................................................................................19
3.4 Configuration Example (Radio Links on the TDM Radio Ring Network)......................................................42
3.4.1 Networking Diagram...............................................................................................................................42
3.4.2 Service Planning......................................................................................................................................44
3.4.3 Configuration Process..............................................................................................................................47
3.5 Configuration Example (Radio Links on the Hybrid Radio Chain Network)..................................................49
3.5.1 Networking Diagram...............................................................................................................................49
3.5.2 Service Planning......................................................................................................................................52
3.5.3 Configuration Process..............................................................................................................................55
3.6 Configuration Example (Radio Links on the Hybrid Radio Ring Network)....................................................59
3.6.1 Networking Diagram...............................................................................................................................59
3.6.2 Service Planning......................................................................................................................................61
3.6.3 Configuration Process..............................................................................................................................64
A Task Collection.........................................................................................................................414
A.1 Managing NEs...............................................................................................................................................416
A.1.1 Creating NEs by Using the Search Method..........................................................................................416
A.1.2 Creating NEs by Using the Manual Method.........................................................................................417
B Parameters Description............................................................................................................570
B.1 Parameters for NE Management....................................................................................................................571
B.1.1 Parameter Description: NE Searching..................................................................................................571
B.1.2 Parameter Description: NE Creation....................................................................................................572
B.1.3 Parameter Description: Login to an NE................................................................................................574
B.1.4 Parameter Description: NE Attribute_Changing NE IDs.....................................................................574
B.1.5 Parameter Description: NE Time Synchronization...............................................................................575
B.1.6 Parameter Description: Localization Management of the NE Time.....................................................580
B.1.7 Parameter Description: License Management......................................................................................581
B.1.8 Parameter Description: Automatic Disabling of the Functions of NEs................................................581
B.2 Parameters for Communications Management..............................................................................................582
B.2.1 Parameter Description: NE Communication Parameter Setting...........................................................582
B.2.2 Parameter Description: DCC Management_DCC Rate Configuration.................................................583
B.2.3 Parameter Description: DCC Management_DCC Transparent Transmission Management................585
B.2.4 Parameter Description: ECC Management_Ethernet Port Extended ECC...........................................586
B.2.5 Parameter Description: NE ECC Link Management............................................................................588
B.2.6 Parameter Description: IP Protocol Stack Management_IP Route Management.................................589
B.2.7 Parameter Description: IP Protocol Stack Management_IP Route Management Creation..................591
B.2.8 Parameter Description: IP Protocol Stack Management_OSPF Parameter Settings............................591
B.2.9 Parameter Description: IP Protocol Stack_Proxy ARP........................................................................594
B.2.10 Parameter Description: OSI Management_Network Layer Parameter...............................................595
B.2.11 Parameter Description: OSI Management_Routing Table.................................................................596
B.2.12 Parameter Description: OSI Management_OSI Tunnel......................................................................597
B.2.13 Parameter Description: DCN Management_Bandwidth Management...............................................601
B.2.14 Parameter Description: DCN Management_Port Setting...................................................................602
B.2.15 Parameter Description: DCN Management_Protocol Setting............................................................603
B.2.16 Parameter Description: Access Control..............................................................................................604
B.3 Network Security Parameters........................................................................................................................605
C Glossary......................................................................................................................................868
C.1 0-9..................................................................................................................................................................869
C.2 A-E.................................................................................................................................................................869
C.3 F-J..................................................................................................................................................................878
C.4 K-O................................................................................................................................................................883
C.5 P-T..................................................................................................................................................................889
C.6 U-Z.................................................................................................................................................................898
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 910 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.
Initial Configuration
Initial configuration of a radio network refers to configuring the network-wide service data by
using the Web LCT for the first time after the NE commissioning is complete. Table 1-1
describes the configuration procedure.
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 1-2.
8.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.
8.2 Common Task Collection (Radio This common task collection lists
Links) configuration operations associated with
radio links, including changing the working
mode of a TDM radio link and changing the
number of E1s on a Hybrid radio link.
8.3 Common Task Collection (TDM This common task collection lists
Services) configuration operations associated with
TDM services, including deleting TDM
services and upgrading a normal service to an
SNCP service.
8.4 Common Task Collection (Ethernet This common task collection lists
Services) configuration operations associated with
Ethernet services, including configuring or
modifying Ethernet interface parameters and
deleting Ethernet services.
2 Configuring NEs
You can manage a transport network by using the Web LCT only after configuring NEs on the
network.
2.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 910 supports several DCN solutions,
including HWECC, IP over DCC, and inband DCN. HWECC is the commonest DCN solution.
HWECC is the default DCN solution provided by the OptiX RTN 910. In the case of HWECC,
the network management (NM) message is encapsulated in the proprietary HWECC protocol
stack. Hence, the HWECC solution is easy to configure. As a proprietary protocol stack,
however, HWECC can be used only when there is one isolated OptiX RTN 910 NE or when the
OptiX RTN 910 NE networks with other OptiX equipment that supports HWECC.
Figure 2-1 shows how the NM message is transmitted when HWECC is used. The NM message
encapsulated in the HWECC protocol stack can be transmitted on the DCC channels over the
optical fiber or microwave, and can also be transmitted over the Ethernet between the Ethernet
NM ports or between the NE cascade ports. If there are no fiber connections or radio links
between two NEs, ensure that the Ethernet connection is set up between the corresponding
Ethernet NM ports or NE cascade ports on the NEs. Otherwise, the communication between the
two NEs fails. The Ethernet connection between the corresponding Ethernet NM ports or NE
cascade ports functions as the extended channel for transmitting the HWECC protocol stack and
is hence considered as the extended ECC. The extended ECC function is enabled by default.
Message
HWECC
DCC
NMS
Message Message
HWECC HWECC
DCC DCC
OptiX radio
OptiX optical transmission equipment
transmission equipment
In addition, the inband DCN is enabled by default. In the inband DCN solution, the NM
management message occupies part of the Ethernet service bandwidth and is transmitted over
Hybrid radio link or through FE/GE ports. The inband DCN solution applies to the scenarios
where the OptiX RTN 910 networks OptiX packet switching equipment, as shown in Figure
2-2.
OptiX Msg
IP stack
NMS
Hybrid MW
OptiX Msg
IP stack
ETH OptiX Msg
IP stack
Inband DCN OptiX Msg
IP stack
FE/GE
In the inband DCN solution, the NM management message occupies part of the Ethernet service
bandwidth. Hence, the DCN function of the ports that are not connected to the OptiX packet
switching equipment must be disabled.
GNE
Generally, the GNE is connected to the NMS through a LAN/WAN. The application layer of
the NMS can directly communicate with the application layer of the GNE. One set of NMS
needs to be connected to one or more GNEs.
Disable the extended ECC function of the GNEs, to prevent oversized DCN that is caused due
to the ECC communication between the GNEs.
Non-GNE
A non-GNE communicates with the GNE through the DCN channels between NEs. It is
recommended that fewer than 50 GNEs are affiliated to a GNE.
ID of an NE
At the application layer of each DCN solution, the OptiX NE uses the NE ID as the address of
the NE. Hence, the ID of each NE on the DCN must be unique and complies with the uniform
DCN planning.
The NE ID has 24 bits. The highest eight bits represent the subnet ID (or the extended ID) and
the lowest 16 bits represent the basic ID. For example, if the ID of an NE is 0x090001, the subnet
ID of the NE is 9 and the basic ID is 1.
IP Address of an NE
An NE uses the IP address as its unique identifier during the TCP/IP communication.
In the HWECC solution, the IP addresses of the NEs on the DCN are used in the following
scenarios:
l The GNE communicates with the Web LCT over TCP/IP based on the IP address. The IP
address must comply with the uniform planning of the external DCN.
l Different NEs communicate with each other over extended ECC channels based on the IP
addresses. The IP addresses of the NEs must be within the same network segment. By
default, the IP address of an NE is within the 129.9.0.0 network segment.
In the DCN solutions (for example, inband DCN) where the NM message is transmitted over
TCP/IP, the IP address of an NE is used as the NE address at the network layer. Hence, the IP
of each NE on the DCN must be unique and complies with the uniform planning of the DCN.
By default, that is, if the IP address of an NE is not changed manually, the IP address and ID of
the NE interlock each other. That is, when the NE ID is changed, the IP address is automatically
modified to 0x81000000 + ID. For example, when the NE ID is changed to 0x090001, the IP
address is automatically changed to 129.9.0.1. After the IP address is changed manually, the
interlocking relation between the ID and IP address fails.
Table 2-1 Mapping relations between the physical boards and logical boards
Physical Board Logical Board
7 A.3.3 Configuring the Required in the case of the GNE. Set the parameters
Extended ECC as follows:
l Set ECC Extended Mode to Specified Mode.
l Adopt the default values for the other parameters.
NOTE
This operation is performed to disable the automatic
extended ECC function of the GNE.
9 A.3.11 Configuring the Required in the case of the Hybrid radio network. Set
Enable Status of the the parameters as follows:
Inband DCN Function l In the case of the Ethernet ports and microwave
on Ports ports that interconnect with the packet switching
equipment, set Enabled Status to Enabled.
l In the case of the other ports, set Enabled
Status to Disabled.
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 need not perform the corresponding operations in the initial configuration
process.
l The preceding configuration procedure is applicable to the scenarios wherein HWECC is used as the DCN
solution. When a DCN solution other than HWECC is used, the DCN-related operations described in the
preceding configuration procedure may be inapplicable.
BTS2
NE4
BTS3
NE3 NE2 NE1 BSC
BTS1
NE6 NE5
BTS5 BTS4
The board configuration information provided in this configuration example also applies to the configuration
examples of radio links, TDM services, and Ethernet services.
E1 STM-1 E1
BTS3
BTS1 STM-1
BSC
BTS5 BTS4
NOTE
"NE cascade" indicates that an Ethernet cable is used to connect two NEs through the Ethernet NM ports or NE
cascading ports.
l The Web LCT is connected to NE1 through the LAN. Hence, NE1 is the GNE and the other
NEs are non-GNEs, which access the Web LCT through NE1.
l The chain network comprises only OptiX RTN 910. Hence, HWECC is preferred as the
DCN solution. In the HWECC solution, NE2 and NE3 communicate with each other
through the extended ECC that is enabled by default, because no fiber connections are set
up between NE2 and NE3. The other NEs communicate with each other through the DCC
channels over microwave.
l NE1 is the GNE. Hence, the extended ECC function of NE1 needs to be disabled.
l On this chain network, the OptiX RTN 910 does not interconnect with OptiX packet
switching equipment. Hence, the inband DCN function needs to be disabled for all the
Hybrid microwave ports and FE ports in the case of the Hybrid radio network.
l Figure 2-6 shows the ID and IP address that are allocated to each NE according to the
uniform DCN planning information.
9-4 10.0.0.100/16
129.9.0.4
0.0.0.0
NE4 9-3 9-2 9-1
129.9.0.3 129.9.0.2 10.0.0.1
0.0.0.0 0.0.0.0 0.0.0.0
NE3 NE2
9-5
9-6 129.9.0.5
129.9.0.6 0.0.0.0
0.0.0.0
NE5 Extended ID-Basic ID
NE6 IP address
Gatew ay
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.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 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, NE1 to NE6 should be added in the NE list.
Parameter Value
Password password
Paramete Value
r
NE1 NE2 NE3 NE4 NE5 NE6
New ID 1 2 3 4 5 6
Step 4 See A.3.1 Setting NE Communication Parameters and set the NE communication parameters.
Parameter Value
NE1
IP 10.0.0.1
Extended ID 9
NOTE
The IP addresses of all the NEs, except NE1, are in the interlocking relations with the NE IDs. Hence, you need
not change the values of the NE communication parameters manually.
Step 5 See A.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 6 See A.3.3 Configuring the Extended ECC and configure the extended ECC.
Parameter Value
NE1
NOTE
This operation is performed to disable the automatic extended ECC function of NE1.
Step 7 In the case of the Hybrid radio network, see A.3.11 Configuring the Enable Status of the
Inband DCN Function on Ports and disable the inband DCN function of the port.
Parameter Value
Step 8 See A.1.7 Synchronizing the NE Time and synchronize the NE time.
Parameter Value
Synchronous Mode NM
Synchronization Period(days) 1
----End
Figure 2-7 shows a backhaul radio subnet for a mobile base station.
NMS
NE1
BSC
BTS1
BTS2
NE3
BTS3
NOTE
The board configuration information provided in this configuration example also applies to the configuration
examples of radio links, TDM services, and Ethernet services.
Figure 2-8 Board configuration of NEs on the TDM radio ring network
BSC NE1
E1 IF1 IF1
CSTA
E1
NE2 NE4
BTS2 IF1 IF1
IF1 IF1 CSTA E1
CSTA
BTS4
E1
BTS3
NE3
IF1 IF1
CSTA
E1
BTS3
Figure 2-9 Board configuration of NEs on the Hybrid radio ring network
BSC NE1
E1+GE IFU2 IFU2
CSHA
E1+FE
NE2 NE4
BTS2 IFU2 IFU2
IFU2 IFU2 CSHA E1+FE
CSHA
BTS4
E1+FE
BTS3
NE3
IFU2 IFU2
CSHA
E1+FE
BTS3
l The OptiX RTN 910 is connected to NE1 through the LAN. Hence, NE1 is the GNE and
the other NEs are non-GNEs, which access the OptiX RTN 910 through NE1.
l The ring network comprises only OptiX RTN 910. Hence, HWECC is preferred as the DCN
solution. In the HWECC solution, the NEs communicate with each other through the DCC
channels over microwave.
l NE1 is the GNE. Hence, the extended ECC function of NE1 should be disabled.
l On this ring network, the OptiX RTN 910 does not interconnect with OptiX packet
switching equipment. Hence, the inband DCN function needs to be disabled for all the
Hybrid microwave ports and FE ports in the case of the Hybrid radio network.
l Figure 2-10 shows the ID and IP address that are allocated to each NE according to the
uniform DCN planning information.
10.0.0.100/16
9-1
10.0.0.1
0.0.0.0
NE1 9-4
9-2
129.9.0.2 129.9.0.4
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.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, NE1 to NE4 should be added in the NE list.
Parameter Value
Password password
Parameter Value
New ID 1 2 3 4
New Extended 9 (default value) 9 (default value) 9 (default value) 9 (default value)
ID
Step 4 See A.3.1 Setting NE Communication Parameters and set the NE communication parameters.
Parameter Value
NE1
IP 10.0.0.1
Extended ID 9
NOTE
The IP addresses of all the NEs, except NE1, are in the interlocking relations with the NE IDs. Hence, you need
not change the values of the NE communication parameters manually.
Step 5 See A.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 6 See A.3.3 Configuring the Extended ECC and configure the extended ECC.
Parameter Value
NE1
NOTE
This operation is performed to disable the automatic extended ECC function of NE1.
Step 7 In the case of the Hybrid radio network, see A.3.11 Configuring the Enable Status of the
Inband DCN Function on Ports and disable the inband DCN function of the port.
Parameter Value
Step 8 See A.1.7 Synchronizing the NE Time and synchronize the NE time.
Parameter Value
Synchronous Mode NM
Synchronization Period(days) 1
----End
Before configuring services on a radio link, you need to configure the radio link.
Figure 3-1 AM
256QAM
128QAM
32QAM
QPSK
32QAM
256QAM 128QAM
16QAM 64QAM
Channel
16QAM
capability
64QAM
E1 services
Ethernet
services
The AM technology adopted by the OptiX RTN 910 has the following features:
l The AM technology can use the QPSK, 16QAM, 32QAM, 64QAM, 128QAM, and
256QAM modulation mode.
l The lowest modulation mode (also called "reference mode") and the highest modulation
mode (also called "nominal mode") actually used by the AM can be configured.
l When the modulation modes of AM are switched, the transmit frequency, receive
frequency, and channel spacing do not change.
l When the modulation modes of AM are switched, the step-by-step switching mode is
adopted.
l AM switching is a hitless switch. When the AM scheme is downshifted, high-priority
services will not be affected due to the mode switching when the low-priority services are
discarded. The switching rate meets the requirement of the 100dB/s fast channel fading.
Therefore, the capacity in CCDP transmission mode is double 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 thus 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 degradation. To cancel the interference, the
XPIC technology is adopted. In the XPIC technology, the signals in the horizontal and vertical
directions are received and then processed. In this manner, the original signals are recovered.
The characteristics of the XPIC function supported by the OptiX RTN 910 are as follows:
l The XPD tolerance is increased, and the notch performance is improved.
l The XPIC function is realized completely through hardware.
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 the case of XPIC
configuration is double the radio link capacity in the case of 1+0 configuration.
The OptiX RTN 910 supports only the XPIC configuration for the Hybrid radio link.
Required
End End
Optional
1 A.6.1 Required when the radio links are configured with 1+1
Creating an protection.
IF 1+1 Parameters are set according to the network planning
Protection information.
Groupa
3 A.6.8 Required when the radio links are configured with N+1
Creating an protection.
N+1 The N+1 protection groups of the equipment at both ends must
Protection have the same attributes.
Group
Parameters are set according to the network planning
information.
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 In the case of radio links configured with 1+1 HSB/SD, you need to configure the IF and ODU information
on the main radio link only. In the case of 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 In the case of TDM radio links configured with N+1 protection, you need to configure the IF and ODU
information on each link. Work Mode must be configured as 7, STM-1, 28MHz, 128QAM.
Table 3-2 Configuration procedure of Hybrid radio links (the XPIC is used)
1 A.6.2 Required.
Creating an Parameters are set according to the network planning
XPIC information.
Protection
Group
2 A.6.3 Required.
Setting the Parameters are set according to the network planning
Hybrid/AM information. The parameters in both polarization directions
Attributes should take the same values.
of the XPIC
Hybrid
Radio Link
4 A.6.5 Required.
Setting IF When the XPIC function is enabled on the IFX2 board, set
Attributes XPIC Enabled to Enabled (default value).
NOTE
l The preceding parameters need to set to the same values, separately for the radio links in the vertical and
horizontal polarization directions.
l During the site commissioning, you can configure the two XPIC links as two separate non-XPIC link
according to Table 3-3.
l The MW_CFG_MISMATCH alarm is reported, if the E1 count, AM enabled status, 1588 timeslot enabled
status, modulation mode, or IF bandwidth is set inconsistently for both ends of a Hybrid radio link.
Table 3-3 Configuration procedure of Hybrid radio links (the XPIC is not used)
Step Operation Description
1 A.6.1 Required when the radio links are configured with 1+1
Creating an protection.
IF 1+1 Parameters are set according to the network planning
Protection information.
Groupa
3 A.6.8 Required when the radio links are configured with N+1
Creating an protection.
N+1 The N+1 protection groups of the equipment at both ends must
Protection have the same attributes.
Group
Parameters are set according to the network planning
information.
4 A.6.5 Required when the XPIC function is not enabled on the IFX2
Setting IF board. In this case, set XPIC Enabled to Disabled.
Attributes NOTE
To configure 1+1 protection radio links, you need to configure the
information about the main IF board only.
NOTE
l a: Generally, during the site commissioning, the previous steps are completed. After the site commissioning,
however, you need to reset Enable AM and ATPC Enable Status.
l In the case of radio links configured with 1+1 HSB/SD, you need to configure the IF and ODU information
on the main radio link only. In the case of 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 Hybrid 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 IF bandwidth is set inconsistently for both ends of a Hybrid radio link.
Number of 16 8 8 14 8
E1 services
l To improve transmission reliability of important services, the radio links between NE1 and
NE2 are configured as a 1+1 HSB protection group.
l The ATPC function is enabled to reduce inter-site interference.
Between NE1 and NE2 3-IF1 (main IF board) Configure the ports as a 1+1
HSB protection group.
4-IF1 (standby IF board)
Between NE2 and NE1 3-IF1 (main IF board) Configure the ports as a 1+1
HSB protection group.
4-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 (NE1) -44 (NE3) -43 (NE3) -48 (NE5)
(dBm) -42 (NE2) -44 (NE4) -43 (NE5) -48 (NE6)
Upper threshold -32 (NE1) -34 (NE3) -33 (NE3) -38 (NE5)
of ATPC -32 (NE2) -34 (NE4) -33 (NE5) -38 (NE6)
adjustment
(dBm)
Lower threshold -52 (NE1) -54 (NE3) -53 (NE3) -58 (NE5)
of ATPC -52 (NE2) -54 (NE4) -53 (NE5) -58 (NE6)
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 3-13.
Main IF board 3-IF1 (NE1) 3-IF1 (NE3) 4-IF1 (NE3) 3-IF1 (NE5)
3-IF1 (NE2) 3-IF1 (NE4) 4-IF1 (NE5) 3-IF1 (NE6)
Reverse Disabled - - -
switching
enabling
l It is recommended that you configure the IF board in slot 3 as the main IF board when
configuring a 1+1 HSB/FD/SD protection group.
l If there are no special requirements, the other parameters of the 1+1 HSB/FD/SD all take
default values.
Procedure
Step 1 See A.6.1 Creating an IF 1+1 Protection Group and create the IF 1+1 protection groups for
NE1 and NE2.
l The values for the relevant parameters of NE1 are provided as follows.
Parameter Value
NE1
Parameter Value
NE1
l The values for the relevant parameters of NE2 are provided as follows.
Parameter Value
NE2
Step 2 See A.6.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 NE1 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 NE2 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 NE3 are provided as follows.
Parameter Value
TX Power(dBm) 10 10
l The values for the relevant parameters of NE4 are provided as follows.
Parameter Value
Link ID 102
TX Frequency(MHz) 14952
TX Power(dBm) 10
TX Status unmute
l The values for the relevant parameters of NE5 are provided as follows.
Parameter Value
TX Power(dBm) 15 10
l The values for the relevant parameters of NE6 are provided as follows.
Parameter Value
Link ID 104
TX Frequency(MHz) 14510
TX Power(dBm) 15
TX Status unmute
----End
Based on 2.4 Configuration Example (Ring Network), configure the TDM radio links
according to the network planning information (as shown in Figure 3-6):
Number of E1 4 4 4 4
services
BSC
101 104
14930M 14958M
14510M 14538M
16E1,14M,16QAM NE1 16E1,14M,16QAM
1+0 1+0
V-polarzation V-polarization
Tx high Tx high
Tx low Tx low
BTS1
Tx low Tx low
NE2 NE4 BTS4
Tx high Tx high
BTS2 102 103
14958M 14930M
14538M 14510M
16E1,14M,16QAM 4E1 16E1,14M,16QAM
1+0 1+0
H-polarization NE3 H-polarzation
BTS3
Link ID
Tx high station Tx Freq.
Tx low station Tx Freq.
Radio work mode
RF configuarion
Polarization
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 (NE1) -44 (NE3) -43 (NE3) -47 (NE1)
(dBm) -46 (NE2) -44 (NE2) -43 (NE4) -47 (NE4)
Upper threshold -36 (NE1) -34 (NE3) -33 (NE3) -37 (NE1)
of ATPC -36 (NE2) -34 (NE2) -33 (NE4) -37 (NE4)
adjustment
(dBm)
Lower threshold -56 (NE1) -54 (NE3) -53 (NE3) -57 (NE1)
of ATPC -56 (NE2) -54 (NE2) -53 (NE4) -57 (NE4)
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 (NE1) 4-IF1 (NE2) 4-IF1 (NE3) 4-IF1 (NE4)
3-IF1 (NE2) 3-IF1 (NE3) 3-IF1 (NE4) 3-IF1 (NE1)
Standby IF - - - -
board
Revertive mode - - - -
WTR time(s) - - - -
Reverse - - - -
switching Disabled
enabling
Procedure
Step 1 See A.6.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 NE1 are provided as follows.
Parameter Value
TX Power(dBm) 8 9
l The values for the relevant parameters of NE2 are provided as follows.
Parameter Value
TX Power(dBm) 9 10
l The values for the relevant parameters of NE3 are provided as follows.
Parameter Value
TX Power(dBm) 10 10
Parameter Value
l The values for the relevant parameters of NE4 are provided as follows.
Parameter Value
TX Power(dBm) 10 8
----End
Based on 2.3 Configuration Example (Chain Network), configure the Hybrid radio links
according to the following network planning information (as shown in Figure 3-7):
l Each Hybrid radio link transmits E1 services and Ethernet services. The AM function is
enabled on each link.
l The service capacity accessed by each BTS is provided in Table 3-22.
Number of 4 2 4 4 4
E1 services
Capacity of 45 15 20 25 15
Ethernet
services
(Mbit/s)
l To improve transmission reliability of important services, the radio links between NE1 and
NE2 are configured as a 1+1 HSB protection group.
Between NE1 and NE2 3-IFU2 (main IF board) Configure the ports as a 1+1
HSB protection group.
4-IFU2 (standby IF board)
Between NE2 and NE1 3-IFU2 (main IF board) Configure the ports as a 1+1
HSB protection group.
4-IFU2 (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 E1 18 6 8 4
services
Capacity of 120 35 40 15
Ethernet
services (Mbit/
s)
NOTE
The Hybrid radio capacity and the AM function require the proper license file.
Receive power -46 (NE1) -44 (NE3) -43 (NE3) -48 (NE5)
(dBm) -46 (NE2) -44 (NE4) -43 (NE5) -48 (NE6)
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-IFU2 (NE1) 3-IFU2 (NE3) 4-IFU2 (NE3) 3-IFU2 (NE5)
3-IFU2 (NE2) 3-IFU2 (NE4) 4-IFU2 (NE5) 3-IFU2 (NE6)
Reverse Disabled - - -
switching
enabling
l It is recommended that you configure the IF board in slot 3 as the main IF board when
configuring a 1+1 HSB/FD/SD protection group.
l If there are no special requirements, it is recommended that you plan the other parameters
of the 1+1 HSB/FD/SD to be the default values.
Procedure
Step 1 See A.6.1 Creating an IF 1+1 Protection Group and create the IF 1+1 protection groups for
NE1 and NE2.
l The values for the relevant parameters of NE1 are provided as follows.
Parameter Value
NE1
l The values for the relevant parameters of NE2 are provided as follows.
Parameter Value
NE2
Step 2 See A.6.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 NE1 are provided as follows.
Parameter Value
Enable AM Enabled
Parameter Value
Link ID 101
TX Frequency(MHz) 14930
TX Power(dBm) 16.5
TX Status unmute
l The values for the relevant parameters of NE2 are provided as follows.
Parameter Value
Enable AM Enabled
Link ID 101
TX Frequency(MHz) 14510
TX Power(dBm) 16.5
TX Status unmute
l The values for the relevant parameters of NE3 are provided as follows.
Parameter Value
Specified Max E1 6 8
Capacity
TX Power(dBm) 16.5 16
l The values for the relevant parameters of NE4 are provided as follows.
Parameter Value
Enable AM Enabled
Link ID 102
TX Frequency(MHz) 14952
TX Power(dBm) 16.5
Parameter Value
TX Status unmute
l The values for the relevant parameters of NE5 are provided as follows.
Parameter Value
Specified Max E1 4 8
Capacity
TX Power(dBm) 20 16
l The values for the relevant parameters of NE6 are provided as follows.
Parameter Value
Channel Space 7M
Enable AM Enabled
Parameter Value
Link ID 104
TX Frequency(MHz) 14510
TX Power(dBm) 20
TX Status unmute
----End
Based on 2.4 Configuration Example (Ring Network), configure the Hybrid radio links
according to the network planning information (as shown in Figure 3-8):
l Each Hybrid radio link transmits E1 services and Ethernet services. The AM function is
enabled on each link.
l The service capacity accessed by each BTS is provided in Table 3-33.
Number of E1 4 4 4 4
services
Capacity of 10 10 10 10
Ethernet
services (Mbit/
s)
BSC
101 104
14930M 14958M
14510M 14538M
14M NE1 14M
1+0 1+0
V-polarzation V-polarization
Tx high Tx high
Tx low Tx low
BTS1
Tx low Tx low
NE2 NE4 BTS4
Tx high Tx high
BTS2 102 103
14958M 14930M
14538M 14510M
14M 4E1 14M
1+0 1+0
H-polarization NE3 H-polarzation
BTS3
Link ID
Tx high station Tx Freq.
Tx low station Tx Freq.
Channel spacing
RF configuarion
Polarization
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 E1 16 16 16 16
services
Capacity of 40 40 40 40
Ethernet
services (Mbit/
s)
NOTE
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 (NE1) -44 (NE3) -43 (NE3) -45 (NE1)
(dBm) -42 (NE2) -44 (NE2) -43 (NE4) -45 (NE4)
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-IFU2 (NE1) 4-IFU2 (NE2) 4-IFU2 (NE3) 4-IFU2 (NE4)
3-IFU2 (NE2) 3-IFU2 (NE3) 3-IFU2 (NE4) 3-IFU2 (NE1)
Standby IF - - - -
board
Revertive mode - - - -
WTR time(s) - - - -
Reverse - - - -
switching
enabling
Procedure
Step 1 See A.6.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 NE1 are provided as follows.
Parameter Value
Parameter Value
Specified Max E1 16 16
Capacity
TX Power(dBm) 15 16.5
l The values for the relevant parameters of NE2 are provided as follows.
Parameter Value
Specified Max E1 16 16
Capacity
Parameter Value
l The values for the relevant parameters of NE3 are provided as follows.
Parameter Value
Specified Max E1 16 16
Capacity
TX Power(dBm) 16.5 16
l The values for the relevant parameters of NE4 are provided as follows.
Parameter Value
Parameter Value
Specified Max E1 16 16
Capacity
TX Power(dBm) 15 16
----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 910, 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
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 910, 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 4-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 910 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 switching.
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. If the radio capacity is E3, only the first VC-3 timeslot in VC4-1 on the IF board is
available and corresponds to the E3 timeslot that is transmitted over microwave.
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 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 4-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.
The principles for obtaining the timeslot cross-connection configurations from the SNCP service
timeslot allocation diagram are as follows:
l The vertical line under the NE name is considered as the reference.
l If a straight line representing a pass-through service crosses the vertical line, it indicates
that cross-connections are configured between the boards on both sides of the vertical line.
The corresponding cross-connected timeslots are marked over the straight line.
l If there is a straight line with one dot on one side of the vertical line, it indicates that SNCP
cross-connections are configured between the board on this side of the vertical line and the
board under the straight line with one dot. The corresponding cross-connected timeslots
are marked over the straight line with one dot.
For details, see 4.4 Configuration Example (TDM Services on a TDM Radio Ring
Network) and 4.6 Configuration Example (TDM Services on a Hybrid Radio Ring
Network).
Required
Start
Optional
Configuring linear MSP
Setting parameters
of SDH port
End
3 A.8.3 Configuring the Optional when the TDM service is an SNCP service.
Automatic Switching
of SNCP Services
7 A.8.10 Testing the E1 The test results should show that each E1 service
Service Through contains no bit errors.
PRBS
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, you also need to configure
the extra services on the protection channel if required.
Based on 3.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 4-8):
l To ensure reliable transmission of the services between NE1 and the BSC, linear MSP is
configured for the optical transmission line.
l Services are transferred between NE2 and NE3 through STM-1 optical ports.
Figure 4-8 Networking diagram (TDM services on a TDM radio chain network)
8xE1
BTS2
STM-1 STM-1
8xE1 NE4
BTS3
16xE1
NE3 NE2 NE1 BSC
14xE1 BTS1
8xE1
NE6 NE5
BTS5 BTS4
Between NE1 and the BSC 8-SL1D-1 (working port) Configure the ports as a 1+1
linear MSP group.
8-SL1D-2 (protection unit)
Between NE1 and NE2 3-IF1 (main IF board) Configure the ports as a 1+1
HSB protection group.
4-IF1 (standby IF board)
Between NE2 and BTS1 9-SP3S (1-16) Configure the ports to access
services from BTS1.
Between NE2 and NE1 3-IF1 (main IF board) Configure the ports as a 1+1
HSB protection group.
4-IF1 (standby IF board)
Between NE4 and BTS2 9-SP3S (1-16) Configure the ports to access
services from BTS2 and
Between NE4 and BTS3 BTS3.
Between NE5 and BTS4 9-SP3S (1-14) Configure the ports to access
services from BTS4.
Between NE6 and BTS5 9-SP3S (1-8) Configure the ports to access
services from BTS5.
Figure 4-9 Timeslot allocation diagram (TDM services on the TDM radio chain network)
Links-1: NE1 - NE2 - NE3 -NE6
Station BS
NE1 NE2 NE3 NE5 NE6
C
Timeslot 8-SL1D-1 3-IF1 3-IF1 8-SL1D-1 8-SL1D-1 4-IF1 4-IF1 3-IF1 3-IF1
VC12: 1-8
VC12: 9-22 9-SP3S:1-8
Links-2: NE3-NE4
Station NE3 NE4
Timeslot 8-SL1D-1 3-IF1 3-IF1
VC12: 23-38 VC12: 1-16
VC4-1
9-SP3S:1-16
Pass through
Add/Drop
Foward
As shown in Figure 4-9, the information about the timeslots that the TDM services occupy on
each NE is as follows:
l E1 services on NE6:
– The E1 services are added to or dropped from the first to eighth ports on the SP3S board
in slot 9 of NE6.
– 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 8 of NE1 and the IF1 board in slot 3 of NE6.
l E1 services on NE5:
– The E1 services are added to or dropped from the first to fourteenth ports on the SP3S
board in slot 9 of NE5.
– 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 8 of NE1 and the IF1 board in slot 3 of
NE5.
l E1 services on NE4:
– The E1 services are added to or dropped from the first to sixteenth ports on the SP3S
board in slot 9 of NE4.
– 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 8 of NE1 and the SL1D board
in slot 8 of NE3.
– The E1 services occupy the first to sixteenth VC-12 timeslots on the link between the
IF1 board in slot 3 of NE3 and the IF1 board in slot 3 of NE4.
l E1 services on NE2:
– The E1 services are added to or dropped from the first to sixteenth ports on the SP3S
board in slot 9 of NE2.
– 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 8 of NE1 and the IF1 board in
slot 3 of NE2.
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 NE1
and BSC. Table 4-8 provides the related planning information.
Parameter NE1
Parameter NE1
NOTE
Unless otherwise specified, SD enable, Protocol Type, SD/SF PRI Switching Tag, and Switching Mode
Indication take the default values.
Procedure
Step 1 See A.7.1 Configuring Linear MSP and configure 1+1 linear MSP.
Parameter Value
NE1
SD enable Enabled
Step 2 See A.8.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 NE1 are provided as follows.
Parameter Value
NE1
Level VC-12
Direction Bidirectional
Parameter Value
NE1
Source 8-SL1D
Source Port 1
Sink 3-IF1
Sink Port 1
l The values for the related parameters of NE2 are provided as follows.
Parameter Value
NE2
Source Port 1 1
Sink Port 1 -
l The values for the related parameters of NE3 are provided as follows.
Parameter Value
NE3
Parameter Value
NE3
Source Port 1 1
Sink Port 1 1
l The values for the related parameters of NE4 are provided as follows.
Parameter Value
NE4
Level VC-12
Direction Bidirectional
Source 3-IF1
Source Port 1
Sink 9-SP3S
Sink Port -
Sink VC4 -
l The values for the related parameters of NE5 are provided as follows.
Parameter Value
NE5
Parameter Value
NE5
Source Port 1 1
Sink Port 1 -
l The values for the related parameters of NE6 are provided as follows.
Parameter Value
NE6
Level VC-12
Direction Bidirectional
Source 3-IF1
Source Port 1
Sink 9-SP3S
Sink Port -
Sink VC4 -
Step 3 See A.8.10 Testing the E1 Service Through 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 3.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 BSC, SNCP is configured to provide
protection for TDM services on the ring network. See Figure 4-10.
Figure 4-10 Networking diagram (TDM services on a TDM radio ring network)
16xE1
NE1
BSC
4xE1
BTS1 4xE1
BTS2
4xE1
NE3
BTS3
Between NE1 and the BSC 9-SP3S (1-16) Configure this port to access
services from the BSC.
Between NE2 and BTS1 9-SP3S (1-8) Configure the ports to access
services from BTS1 and
Between NE2 and BTS2 BTS2.
Configure this port to be the
SNCP service sink.
Between NE3 and BTS3 9-SP3S (1-4) Configure the ports to access
services from BTS3.
Between NE4 and BTS4 9-SP3S (1-4) Configure the ports to access
services from BTS4.
Figure 4-11 Timeslot allocation diagram (TDM service on the TDM radio ring network)
Station NE1 NE2 NE3 NE4 NE1
Timeslot 4-IF1 3-IF1 4-IF1 3-IF1 4-IF1 3-IF1 4-IF1 3-IF1
VC12: 1-8 VC12: 1-8
9-SP3S:1-8 9-SP3S:1-8 9-SP3S:1-8 9-SP3S:1-8
VC12: 9-12 VC12: 9-12
VC4-1 9-SP3S:9-12 9-SP3S:1-4 9-SP3S:1-4 9-SP3S:9-12
VC12: 13-16 VC12: 13-16
9-SP3S:13-16 9-SP3S:1-4 9-SP3S:1-4 9-SP3S:13-16
As shown in Figure 4-11, the information about the timeslots that the TDM services occupy on
each NE is as follows:
l E1 services on NE2:
– The E1 services are added to or dropped from the first to eighth ports on the SP3S board
in slot 9 of NE2.
– The E1 services are added to or dropped from the first to eighth ports on the SP3S board
in slot 9 of NE1.
– The E1 services occupy the first to eighth VC-12 timeslots on the ring.
l E1 services on NE3:
– The E1 services are added to or dropped from the first to fourth ports on the SP3S board
in slot 9 of NE3.
– The E1 services are added to or dropped from the ninth to twelfth ports on the SP3S
board in slot 9 of NE1.
– The E1 services occupy the ninth to twelfth VC-12 timeslots on the ring.
l E1 services on NE4:
– The E1 services are added to or dropped from the first to fourth ports on the SP3S board
in slot 9 of NE4.
– The E1 services are added to or dropped from the thirteenth to sixteenth ports on the
SP3S board in slot 9 of NE1.
– The E1 services occupy the thirteenth to sixteenth VC-12 timeslots on the ring.
SNCP
Table 4-13 provides the information about SNCP.
Parameter NE1
NOTE
Unless otherwise specified, WTR Time, Hold-Off Time, and Switching Condition take the default values.
Procedure
Step 1 See A.8.2 Creating Cross-Connections of SNCP Services and configure the SNCP service
cross-connections.
l The values for the related parameters of NE1 are provided as follows.
Parameter Value
NE1
Hold-off Time(100ms) 0 0
Source Port 1 1
Parameter Value
NE1
Sink Port - -
Sink VC4 - -
l The values for the related parameters of NE2 are provided as follows.
Parameter Value
NE2
Direction Bidirectional
Level VC-12
Hold-off Time(100ms) 0
Source Port 1
Sink 9-SP3S
Sink Port -
Sink VC4 -
l The values for the related parameters of NE3 are provided as follows.
Parameter Value
NE3
Direction Bidirectional
Level VC-12
Parameter Value
NE3
Hold-off Time(100ms) 0
Source Port 1
Sink 9-SP3S
Sink Port -
Sink VC4 -
l The values for the related parameters of NE4 are provided as follows.
Parameter Value
NE4
Direction Bidirectional
Level VC-12
Hold-off Time(100ms) 0
Source Port 1
Sink 9-SP3S
Sink Port -
Parameter Value
NE4
Sink VC4 -
Step 2 See A.8.1 Creating the Cross-Connections of Point-to-Point Services and configure the
service cross-connections on NE2, NE3, and NE4.
l The values for the related parameters of NE2 are provided as follows.
Parameter Value
NE2
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 NE3 are provided as follows.
Parameter Value
NE3
Level VC-12
Direction Bidirectional
Source 3-IF1
Source Port 1
Sink 4-IF1
Sink Port 1
Parameter Value
NE3
l The values for the related parameters of NE4 are provided as follows.
Parameter Value
NE4
Level VC-12
Direction Bidirectional
Source 3-IF1-1
Source Port 1
Sink 4-IF1
Sink Port 1
Step 3 See A.8.10 Testing the E1 Service Through 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 3.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 4-12):
l To ensure reliable transmission of the services between NE1 and the BSC, linear MSP is
configured for the optical transmission line.
l Services are transferred between NE2 and NE3 through E1 channels.
Figure 4-12 Networking diagram (TDM services on a Hybrid radio chain network)
2E1
BTS2
E1 STM-1
4E1 NE4
BTS3
4E1
NE3 NE2 NE1 BSC
4E1 BTS1
4E1
NE6 NE5
BTS5 BTS4
Between NE1 and the BSC 8-SL1D-1 (working port) Configure the ports as a 1+1
linear MSP group.
8-SL1D-2 (protection port)
Between NE1 and NE2 3-IFU2 (main IF board) Configure the ports as a 1+1
HSB protection group.
4-IFU2 (standby IF board)
Between NE2 and BTS1 9-SP3D (15-18) Configure the ports to access
services from BTS1.
Between NE2 and NE1 3-IFU2 (main IF board) Configure the ports as a 1+1
HSB protection group.
4-IFU2 (standby IF board)
Between NE4 and BTS2 9-SP3S (1-6) Configure the ports to access
services from BTS2 and
Between NE4 and BTS3 BTS3.
Between NE5 and BTS4 9-SP3S (1-4) Configure the ports to access
services from BTS4.
Between NE6 and BTS5 9-SP3S (1-4) Configure the ports to access
services from BTS5.
Figure 4-13 Timeslot allocation diagram (Hybrid services on the Hybrid chain radio network)
Links-1: NE1 - NE2 - NE3 -NE5
Station
BSC NE1 NE2 NE3 NE5 NE6
Timeslot 8-SL1D 3-IFU2 3-IFU2 9-SP3D 9-SP3S 4-IFU2 4-IFU2 3-IFU2 3-IFU2
VC12: 1-4
VC12: 5-8 9-SP3S:1-4
VC12: 9-14 9-SP3S:1-4
VC4-1
VC12: 15-18
9-SP3D:15-18
Links-2: NE3-NE4
Station NE3 NE4
Timeslot 9-SP3S 3-IFU2 3-IFU2
VC12: 9-14 VC12: 1-6
VC4-1
9-SP3S:1-6
Pass through
Add/Drop
Fow ard
As shown in Figure 4-13, the information about the timeslots that the TDM services occupy on
each NE is as follows:
l E1 services of NE6:
– The E1 services are added to or dropped from the first to fourth ports on the SP3S board
in slot 9 of NE6.
– The E1 services occupy the first to fourth VC-12 timeslots on the link between the first
optical port on the SL1D board in slot 8 of NE1 and the IFU2 board in slot 3 of NE6.
l E1 services on NE5:
– The E1 services are added to or dropped from the first to fourth ports on the SP3S board
in slot 9 of NE5.
– The E1 services occupy the fifth to eighth VC-12 timeslots on the link between the first
optical port on the SL1D board in slot 8 of NE1 and the IFU2 board in slot 4 of NE5.
l E1 services on NE4:
– The E1 services are added to or dropped from the first to sixth ports on the SP3S board
in slot 9 of NE4.
– The E1 services occupy the ninth to fourteenth VC-12 timeslots on the link between the
first optical port on the SL1D board in slot 8 of NE1 and the SP3S board in slot 9 of
NE3.
– The E1 services occupy the first to sixth VC-12 timeslots on the link between the IFU2
board in slot 3 of NE3 and the IFU2 board in slot 3 of NE4.
l E1 services on NE2:
– The E1 services are added to or dropped from the fifteenth to eighteenth ports on the
SP3S board in slot 9 of NE2.
– The E1 services occupy the fifteenth to eighteenth VC-12 timeslots on the link between
the first optical port on the SL1D board in slot 8 of NE1 to the IFU2 board in slot 3 of
NE2.
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 NE1
and BSC. Table 4-20 provides the related planning information.
Parameter NE1
NOTE
Unless otherwise specified, SD enable, Protocol Type, SD/SF PRI Switching Tag, and Switching Mode
Indication take the default values.
Procedure
Step 1 See A.7.1 Configuring Linear MSP and configure the linear MSP.
Parameter Value
NE1
SD enable Enabled
Step 2 See A.8.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 NE1 are provided as follows.
Parameter Value
NE1
Level VC-12
Direction Bidirectional
Source 8-SL1D
Source Port 1
Sink 3-IFU2
Sink Port 1
l The values for the relevant parameters of NE2 are provided as follows.
Parameter Value
NE2
Level VC-12
Direction Bidirectional
Source 3-IFU2
Source Port 1
Sink 9-SP3D
Sink Port -
Sink VC4 -
l The values for the relevant parameters of NE3 are provided as follows.
Parameter Value
NE3
Source Port - -
Source VC4 - -
Sink Port 1 1
l The values for the relevant parameters of NE4 are provided as follows.
Parameter Value
NE4
Level VC-12
Direction Bidirectional
Source 3-IFU2
Source Port 1
Sink 9-SP3S
Sink Port -
Sink VC4 -
l The values for the relevant parameters of NE5 are provided as follows.
Parameter Value
NE5
Source Port 1 1
Sink Port 1 -
l The values for the relevant parameters of NE6 are provided as follows.
Parameter Value
NE6
Level VC-12
Direction Bidirectional
Source 3-IFU2-
Source Port 1
Sink 9-SP3S
Sink Port -
Sink VC4 -
Step 3 See A.8.10 Testing the E1 Service Through 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
Figure 4-14 Networking diagram (TDM services on a Hybrid radio ring network)
16xE1
NE1
BSC
4xE1
BTS1 4xE1
BTS2
4xE1
NE3
BTS3
Between NE1 and the BSC 9-SP3S (1-16) Configure this port to access
services from the BSC.
Between NE2 and BTS1 9-SP3S (1-8) Configure the ports to access
services from BTS1 and
Between NE2 and BTS2 BTS2.
Between NE3 and BTS3 9-SP3S (1-4) Configure the ports to access
services from BTS3.
Between NE4 and BTS4 9-SP3S (1-4) Configure the ports to access
services from BTS4.
Figure 4-15 Timeslot allocation diagram (TDM services on the Hybrid radio ring network)
Station NE1 NE2 NE3 NE4 NE1
Timeslot 4-IFU2 3-IFU2 4-IFU2 3-IFU2 4-IFU2 3-IFU2 4-IFU2 3-IFU2
VC12: 1-8 VC12: 1-8
9-SP3S:1-8 9-SP3S:1-8 9-SP3S:1-8 9-SP3S:1-8
VC12: 9-12 VC12: 9-12
VC4-1 9-SP3S:9-12 9-SP3S:1-4 9-SP3S:1-4 9-SP3S:9-12
VC12: 13-16 VC12: 13-16
9-SP3S:13-16 9-SP3S:1-4 9-SP3S:1-4 9-SP3S:13-16
As shown in Figure 4-15, the information about the timeslots that the TDM services occupy on
each NE is as follows:
l E1 services on NE2:
– The E1 services are added to or dropped from the first to eighth ports on the SP3S board
in slot 9 of NE2.
– The E1 services are added to or dropped from the first to eighth ports on the SP3S board
in slot 9 of NE1.
– The E1 services occupy the first to eighth VC-12 timeslots on the ring.
l E1 services on NE3:
– The E1 services are added to or dropped from the first to fourth ports on the SP3S board
in slot 9 of NE3.
– The E1 services are added to or dropped from the ninth to twelfth ports on the SP3S
board in slot 9 of NE1.
– The E1 services occupy the ninth to twelfth VC-12 timeslots on the ring.
l E1 services on NE4:
– The E1 services are added to or dropped from the first to fourth ports on the SP3S board
in slot 9 of NE4.
– The E1 services are added to or dropped from the thirteenth to sixteenth ports on the
SP3S board in slot 9 of NE1.
– The E1 services occupy the thirteenth to sixteenth VC-12 timeslots on the ring.
SNCP
Table 4-25 provides the information about SNCP.
Parameter NE1
NOTE
Unless otherwise specified, WTR Time, Hold-Off Time, and Switching Condition take the default values.
Procedure
Step 1 See A.8.2 Creating Cross-Connections of SNCP Services and configure the SNCP service
cross-connections.
l The values for the relevant parameters of NE1 are provided as follows.
Parameter Value
NE1
Hold-off Time(100ms) 0 0
Source Port 1 1
Sink Port - -
Sink VC4 - -
l The values for the relevant parameters of NE2 are provided as follows.
Parameter Value
NE2
Direction Bidirectional
Level VC-12
Hold-off Time(100ms) 0
Parameter Value
NE2
Source Port 1
Sink 9-SP3S
Sink Port -
Sink VC4 -
l The values for the relevant parameters of NE3 are provided as follows.
Parameter Value
NE3
Direction Bidirectional
Level VC-12
Hold-off Time(100ms) 0
Source Port 1
Sink 9-SP3S
Sink Port -
Sink VC4 -
l The values for the relevant parameters of NE4 are provided as follows.
Parameter Value
NE4
Direction Bidirectional
Level VC-12
Hold-off Time(100ms) 0
Source Port 1
Sink 9-SP3S
Sink Port -
Sink VC4 -
Step 2 See A.8.1 Creating the Cross-Connections of Point-to-Point Services and configure the
service cross-connections on NE2, NE3, and NE4.
l The values for the relevant parameters of NE2 are provided as follows.
Parameter Value
NE2
Level VC-12
Direction Bidirectional
Source 3-IFU2
Source Port 1
Sink 4-IFU2
Sink Port 1
Parameter Value
NE2
l The values for the relevant parameters of NE3 are provided as follows.
Parameter Value
NE3
Level VC-12
Direction Bidirectional
Source 3-IFU2
Source Port 1
Sink 4-IFU2
Sink Port 1
l The values for the relevant parameters of NE4 are provided as follows.
Parameter Value
NE4
Level VC-12
Direction Bidirectional
Source 3-IFU2
Source Port 1
Sink 4-IFU2
Sink Port 1
Step 3 See A.8.10 Testing the E1 Service Through 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
Ethernet services are classified into E-Line services and E-LAN services.
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 For the EM6F, PORT1 and PORT2 represent GE1 and GE2 respectively; PORT3 to PORT6
represent FE1 to FE4 respectively.
l For the EM6T, PORT1 and PORT2 represent GE1 and GE2 respectively; PORT3 to PORT6
represent FE1 to FE4 respectively.
l For the EM4T (logical board), PORT3 and PORT4 represent GE1 and GE2 respectively;
PORT1 and PORT2 represent FE1 and FE2 correspond to respectively.
l For the EM4F (logical board), PORT3 and PORT4 represent GE1 and GE2 respectively;
PORT1 and PORT2 represent FE1 and FE2 respectively.
5.1.3 Auto-Negotiation
The auto-negotiation function allows the network equipment to send information of its supported
working mode to the opposite end on the network and to receive the corresponding information
that the opposite end may transfer.
Table 5-1 Auto-negotiation rules of FE electrical ports (when the local FE electrical port adopts
the auto-negotiation mode)
Working Mode of the Opposite FE Auto-Negotiation Result
Electrical Port
NOTE
As provided in Table 5-1, when the working mode of the opposite FE electrical port is 10M full-duplex or 100M
full-duplex, the auto-negotiation result cannot realize the matching between the working modes of the FE
electrical ports at both ends. As a result, certain packets are lost. Hence, when the working mode of the opposite
FE electrical port is 10M full-duplex or 100M full-duplex, you need to 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 the flow control function through the auto-negotiation function.
Table 5-2 Auto-negotiation rules of GE electrical ports (when the local GE electrical port adopts
the auto-negotiation mode)
NOTE
As provided in Table 5-2, when the working mode of the opposite GE electrical port is 10M full-duplex or
100M full-duplex, the auto-negotiation result cannot realize the matching between the working modes of the
GE electrical ports at both ends. As a result, certain packets are lost. Hence, when the working mode of the
opposite GE electrical port is 10M full-duplex or 100M full-duplex, you need to 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 the flow control function through the auto-negotiation function.
The half-duplex Ethernet port applies the back-pressure mechanism to control the flow. The full-
duplex Ethernet port applies PAUSE frames to control the flow. Currently, the half-duplex
Ethernet function is not widely applied. Hence, the flow control function realized by Ethernet
service boards is used for the full-duplex Ethernet ports.
The flow control function realized by Ethernet service boards is classified into two types: auto-
negotiation flow control and non-auto-negotiation flow control.
The OptiX RTN 910 supports only two auto-negotiation flow control modes, namely, disabled mode and
symmetric PAUSE mode.
The OptiX RTN 910 supports only two non-auto-negotiation flow control modes, namely, disabled mode and
symmetric mode.
distinguishing; instead, Ethernet services are transparently transmitted between two service
access points.
Service Model
Table 5-3 describes the point-to-point transparently transmitted E-Line service model.
Typical Application
Figure 5-1 shows the typical application scenarios of the point-to-point transparently transmitted
E-Line service model.
Ethernet service 1 and Ethernet service 2 gain access to NE1 through port 1 and port 2
respectively, regardless of whether the two Ethernet services do not carry any VLAN ID or carry
unknown VLAN IDs. 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.
Models of Services
Table 5-4 shows the models of VLAN-based E-Line services.
Typical Applications
Figure 5-2 shows the typical application of service model 1.
Service 1 and Service 2 carry unknown VLAN IDs, and the two Ethernet services 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 Service 1 and 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 Service 1 and Service 2 to NE2.
NE2 processes Service 1 and Service 2 in the same manner as NE1.
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 5-3 shows the typical application of service model 2. Service 1 and Service 2 carry
different VLAN IDs. Therefore, after the two Ethernet services are accessed to NE1 through
Port 1 and Port 2 respectively, they can 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.
NE2 processes Service 1 and Service 2 in the same manner as NE1.
Model of Service
Table 5-5 shows the models of QinQ-based E-Line services.
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
Ethernet frames, and
then transmits the
Ethernet frames to
the sink port where
the QinQ link is
configured.
Model 4 QinQ link (source) NNI-NNI QinQ (source) The source port
QinQ link (sink) QinQ (sink) transmits the
Ethernet frames that
carry the S-VLAN
tag to the sink port
where the sink QinQ
link is configured.
The S-VLAN tag
carried in the
Ethernet frames
corresponds to the
source QinQ link. If
the source and sink
QinQ links
correspond to
different S-VLAN
tags, the S-VLAN
tags carried in the
Ethernet frames are
exchanged.
NOTE
Typical Applications
Figure 5-4 shows the typical application of service model 1.
Service 1 and Service 2 include tagged frames and untagged frames. Service 1 is accessed to
NE1 through Port 1, and Service 2 is accessed to NE1 through Port 2. Port 1 adds the
corresponding S-VLAN tag to Service 1, and Port 2 adds the corresponding S-VLAN tag to
Service 2. Then, Service 1 and Service 2 are transmitted to Port 3. Port 3 transmits Service 1
and Service 2 to NE2.
NE2 processes Service 1 and Service 2 in the same manner 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
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
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 a same S-VLAN tag. Service 1 is accessed to NE1 through Port
1, and Service 2 is accessed 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 S-VLAN tags
carried in Service 1 and Service 2 are different. 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
Model of Service
Table 5-6 shows the model of E-LAN services based on the IEEE 802.1d bridge.
Table 5-6 Model of E-LAN services based on the IEEE 802.1d bridge
Typical Application
Figure 5-8 shows the typical application of the model of service. The transmission network
needs to carry the A services accessed from NE2 and NE3. The two A services are converged
at the convergence node NE1. The services need not be isolated. Therefore, an IEEE 802.1d
bridge is used at NE1 to groom services.
Figure 5-8 Model of E-LAN services based on the IEEE 802.1d bridge
NE 2
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
Model of Service
Table 5-7 shows the models of E-LAN services based on the IEEE 802.1q bridge.
Table 5-7 Model of E-LAN services based on the IEEE 802.1q bridge
Typical Applications
Figure 5-9 shows the typical application of the model of E-LAN services based on the IEEE
802.1q bridge. The transport network needs to carry G and H services accessed from NE2 and
NE3. Both types of services converge on NE1. G and H services adopt different VLAN planning.
Therefore, the IEEE 802.1q bridge is used on NEs and sub-switching domains are divided based
on VLANs, differentiating and separating the two types of services.
Figure 5-9 Model of E-LAN services based on the IEEE 802.1q bridge
NE 2
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 5.1.5.2 VLAN-based E-Line Services on NE2 and NE3 for accessing services.
Model of Service
Table 5-8 shows the models of E-LAN services based on the IEEE 802.1ad bridge.
Table 5-8 Models of E-LAN services based on the IEEE 802.1ad bridge
Type of Tag Attribute Encapsulation Type of Learning Sub-
Services Mode of Port Logical Port Mode Switching
Domain
NOTE
a: When the encapsulation mode of port is 802.1q, the tag attribute must be Tag Aware.
Typical Applications
Figure 5-10 shows the typical application of the model of service. The transmission network
needs to carry G and H services accessed from NE2 and NE3. The two types of services are
converged on NE1. Since G and H services have a same C-VLAN tag, you need to add different
S-VLAN tags to G and H services for service isolation.
Figure 5-10 Model of E-LAN services based on the IEEE 802.1ad bridge
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 5.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
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
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.
Figure 5-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 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 ports can forward
packets to each other. If a split horizon group is created at NE1 and the east and west ports are
configured as members of the split horizon group, the east and west 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. Therefore, if ERPS is already enabled for a ring network,
a split horizon group is not needed as it may affect normal operation of ERPS.
l On the OptiX RTN 910, only the configuration of a split horizon group based on physical ports is supported.
Therefore, if a physical port is mapped into several logical ports and one of these logical ports is a member
of a split horizon group, the other logical ports 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 realized.
The Ethernet ring network shown in Figure 5-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.
Link 1
Link 2
Ethernet Link 3 Ethernet
packet packet
Link aggregation
group
MSTP
The OptiX RTN 910 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 the case of a network loop. This protocol adopts certain
algorithms to reconstruct a loop network into a loop-free tree network and thus prevents Ethernet
frames from increasing and cycling in an endless manner on the loop network.
In the case of the OptiX RTN 910, the MSTP is used to prevent a network loop on the access
side.
See Figure 5-18. When the user equipment accesses the OptiX RTN 910 through two different
trails, you can configure the ports on the OptiX RTN 910 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. Hence, if a service access link becomes faulty, the MSTP enables a re-configuration to
generate the spanning tree topology, thus providing protection for the user network that is
configured with multiple access points.
Root Root
Port group
CIST
Blocked Port
5.1.11 QoS
The quality of service (QoS) refers to the ability of a communication network to ensure the
expected service quality in the aspects of the bandwidth, delay, delay jitter, and packet loss ratio,
and thus to ensure that the request and response from the user or the request and response from
the application meet the requirements of an expected service class. The OptiX RTN 910 supports
the following QoS functions, namely, differentiated service (DiffServ), flow classification,
CAR, traffic shaping, and queue scheduling.
DiffServ
DiffServ (DS) is an end-to-end QoS control model and performs the QoS processing function
as follows:
1. The DS edge node checks the QoS information carried by the packets that enter the DS
domain. Then, the DS edge node aggregates the packets that are at the same QoS levels
into the same behavior aggregates (BAs) and maps the BAs into corresponding per-hop
behavior (PHB) service class.
2. The DS edge node controls the traffic of the BAs according to the PHB service class, and
forwards the BAs to the DS interior node.
3. The DS internal node controls the traffic of the BAs according to the PHB service class,
and forwards the BAs to the DS edge node of the next hop.
The OptiX RTN 910 supports eight PHB service class, namely, BE, AF1, AF2, AF3, AF4, EF,
CS6, and CS7. Packets can be mapped into the corresponding PHB level according to the C-
VLAN priority, S-VLAN priority, or DSCP value.
NOTE
l The AF1 is classified into three sub service classes, namely, AF11, AF12, and AF13, only one of which is
valid. It is the same case with the AF2, AF3, and AF4.
l In the case of a point-to-point transparently transmitted E-Line service, the OptiX RTN 910 supports only
mapping the PHB service classes according to the DSCP values in the Ethernet frames.
Flow Classification
The OptiX RTN 910 supports two flow classification methods, namely, simple flow
classification and complex flow classification. In the case of the simple flow classification,
different services on specified ports are mapped into different PHB service classes according to
the C-VLAN priority, S-VLAN priority, or DSCP value. In the case of the complex flow
classification, specified services mapped into different PHB service classes according to the C-
VLAN/S-VLAN ID, C-VLAN/S-VLAN priority, or DSCP value.
The OptiX RTN 910 supports the following complex flow types:
The flow can be further classified according to the combination of C-VLAN ID+CVLAN priority
or S-VLAN ID+S-VLAN priority.
In the case of complex flows, the following QoS processing operations can be performed:
l Passes or discards the flow according the access control list (ACL).
l Maps the flow into a new PHB service class.
l In the ingress direction, restrict the rate of the flow by using the CAR.
l In the egress direction, perform the flow shaping.
CAR
The CAR is a type of traffic policing technology. When the CAR is used, the rate of the traffic
after flow classification is assessed in a certain period (including in the long term and in the short
term); the packet rate of which does not exceed the specified value is set to a high priority and
the packet rate of which exceeds the specified value is discarded or downgraded. In this manner,
the CAR restricts the traffic into the transmission network.
The OptiX RTN 910 supports the CAR processing for a complex flow in the ingress direction.
The CAR processing operations are as follows:
l When the rate of packets is lower than or equal to the preset committed information rate
(CIR), these packets are marked green and pass the policing of the CAR. These packets are
always forwarded first in the case of network congestion.
l When the rate of packets exceeds the preset peak information rate (PIR), these packets at
a rate higher than the PIR are marked red and directly discarded.
l When the rate of packets is higher than the CIR but is lower than the PIR, the packets at a
rate higher than the CIR can pass the restriction but are marked yellow. Yellow packets
can be set to "discard", "pass", or "remark". If packets are set to "remark", these packets
are mapped to another specified queue with a certain priority (that is, the priority of these
packets is changed) and then forwarded.
l When the rate of packets that pass the restriction of the CAR is lower than or equal to the
CIR in a certain period, certain packets can burst and these packets are always forwarded
first in the case of network congestion. The maximum traffic of the burst packets is
determined by the committed burst size (CBS).
l When the rate of packets that pass the restriction of the CAR is higher than the CIR but is
lower than or equal to the PIR, certain packets can burst and these packets are marked
yellow. The maximum traffic of the burst packets is determined by the peak burst size
(PBS).
Figure 5-19 shows the traffic change after the CAR processing. The packets that are marked
red are directly discarded, and the packets that are marked yellow and green pass the policing
of the CAR. In addition, the packets that are marked yellow are processed according to the preset
value.
PBS
PIR
CBS
CIR
PBS
PIR PIR
CBS
CIR CAR CIR
Traffic Shaping
When the traffic shaping function is used, the traffic and burst size of an outgoing connection
of a network can be restricted. In this manner, the packet can be transmitted at an even rate.
The OptiX RTN 910 supports the shaping of a complex flow, the PHB service class, or the port
in the egress direction.
Queue Scheduling
In the case of the OptiX RTN 910, each Ethernet port has eight egress queues, which correspond
to eight PHB service classes. The OptiX RTN 910 supports three queue scheduling methods,
namely, strict-priority (SP), weighted round robin (WRR), and SP+WRR.
l SP Scheduling Algorithm
Figure 5-20 shows the SP scheduling algorithm. During the SP queue scheduling, packets
are transmitted in a descending order of priority. When a queue with a higher priority is
empty, the packets in the queue with a lower priority can be transmitted. In this manner,
packets of key services are placed into the queues with higher priorities and packets of non-
key services (such as email services) are placed into queues with lower priorities. Hence,
the packets of key services can be always transmitted first, and the packets of non-key
services are transmitted when the data of key services is not processed.
When the SP queue scheduling algorithm is used, all the resources are used to ensure the
QoS of the services of the highest priority. If there are packets in the queues with higher
priorities when congestion occurs, the packets in the queues with lower priorities cannot
be transmitted all the time.
Queue 1 Lowest
Queue 1 10
In the case of the OptiX RTN 910, the SP+WRR scheduling algorithm is the default queue
scheduling mode for each Ethernet port. The queue priority levels are CS7, CS6, EF, AF4, AF3,
AF2, AF1, and BE in the descending order or priority. AF1 to AF4 are WRR queues. Except
for the default settings, the WRR queues and SP queues cannot be interleaved if you set the SP
+WRR scheduling algorithm manually.
Figure 5-23 Configuration flow chart (point-to-point transparently transmitted E-Line services)
Required Start
Optional
Configuring LAGs
Configuring E-Line
services
Configuring QoS
End
A.10.2.1 Required if LAG protection is configured for FE/GE ports or for the Hybrid
Creating a radio that works in N+0/XPIC mode. Set the parameters as follows:
LAG l Set LAG Type to the same value as the opposite equipment. Generally,
set LAG Type to Static for the equipment at both ends.
l The Hybrid/AM attributes must be set to the same value for the IF ports
in a LAG.
l In the case of FE/GE ports, set Load Sharing to the same value as the
opposite equipment. If the LAG is configured only 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
increase the bandwidth, it is recommended that you set Load
Sharing to Sharing for the equipment at both ends.
l Set Load Sharing to Sharing at both ends, if Hybrid radio works in N
+0/XPIC mode and uses LAG protection.
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 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 Set Main Board, Main Port, and Selected Slave Ports according to
the planning information. 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.
Table 5-11 Procedures for configuring point-to-point transparently transmitted E-Line services
Operation Description
Operation Description
A.10.6.4 Optional.
Setting the
Advanced
Attributes
of Ethernet
Ports
A.10.10.1 Required.
Creating a DS Set the parameters according to the network planning information.
Domain
NOTE
Point-to-point transparently transmitted services support mapping the PHB service
classes based on the DSCP type only. The default DS, however, maps the PHB
service classes according to the CLAN priorities. Therefore, you need to configure
a new DS.
A.10.10.4 Required when you need to apply QoS policies other than DS and port
Creating a Port shaping for a specific port.
Policy Set the parameters according to the network planning information.
A.10.10.6 Required if you need to perform the ACL, CoS, CAR or shaping operation
Creating the for a specific flow over the port.
Traffic Set the related parameters according to the network plan.
Operation Description
A.10.10.8 Required if you need to limit the egress bandwidth that an Ethernet service
Configuring occupies.
Port Shaping Set the parameters according to the network planning information.
A.10.11.1 Required in the case of the NEs where the two Ethernet ports involved in
Creating an the service test are located. Set the parameters as follows:
MD l Set Maintenance Domain Name and Maintenance Domain Level to
the same values for the two NEs.
l In the test of an Ethernet service between two edge nodes on the
transport network, it is recommended that Maintenance Domain
Level takes the default value 4. In the test of an Ethernet service
between two internal NEs on the transport network, set Maintenance
Domain Level to a value smaller than 4. In the test of 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.10.11.2 Required in the case of the NEs where the two Ethernet ports involved in
Creating an the service 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 two
NEs.
l Set Relevant Service to the same service for the two NEs.
l It is recommended that you set CC Test Transmit Period to 1s.
Operation Description
A.10.11.3 Required in the case of the NEs where the two Ethernet ports involved in
Creating an the service test are located. Set the parameters as follows:
MEP Point 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 The MP ID is used to identify the MEP during the LB test. Therefore,
set CC Status to Active.
A.10.11.4 Required in the case of the NE where the Ethernet ports involved in the
Creating OAM 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
Optional
Configuring LAGs
Configuring E-Line
services
Configuring QoS
End
A.10.2.1 Required if LAG protection is configured for FE/GE ports or for the Hybrid
Creating a radio that works in N+0/XPIC mode. Set the parameters as follows:
LAG l Set LAG Type to the same value as the opposite equipment. Generally,
set LAG Type to Static for the equipment at both ends.
l The Hybrid/AM attributes must be set to the same value for the IF ports
in a LAG.
l In the case of FE/GE ports, set Load Sharing to the same value as the
opposite equipment. If the LAG is configured only 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
increase the bandwidth, it is recommended that you set Load
Sharing to Sharing for the equipment at both ends.
l Set Load Sharing to Sharing at both ends, if Hybrid radio works in N
+0/XPIC mode and uses LAG protection.
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 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 Set Main Board, Main Port, and Selected Slave Ports according to
the planning information. 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.
A.10.3.3 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 Item
NOTE
The corresponding VLAN forwarding table items need to be configured for the
source port and sink port.
Operation Description
A.10.6.4 Optional.
Setting the
Advanced
Attributes
of Ethernet
Ports
A.10.7.3 Optional.
Setting the
Advanced
Attributes
of the
IF_ETH
Port
A.10.10.1 Required.
Creating a DS Set the parameters according to the network planning information.
Domain
NOTE
Point-to-point transparently transmitted services support mapping the PHB service
classes based on the DSCP type only. The default DS, however, maps the PHB
service classes according to the CLAN priorities. Therefore, you need to configure
a new DS.
A.10.10.4 Required when you need to apply QoS policies other than DS and port
Creating a Port shaping for a specific port.
Policy Set the parameters according to the network planning information.
A.10.10.6 Required if you need to perform the ACL, CoS, CAR or shaping operation
Creating the for a specific flow over the port.
Traffic Set the related parameters according to the network plan.
A.10.10.8 Required if you need to limit the egress bandwidth that an Ethernet service
Configuring occupies.
Port Shaping Set the parameters according to the network planning information.
A.10.11.1 Required in the case of the NEs where the two Ethernet ports involved in
Creating an the service test are located. Set the parameters as follows:
MD l Set Maintenance Domain Name and Maintenance Domain Level to
the same values for the two NEs.
l In the test of an Ethernet service between two edge nodes on the
transport network, it is recommended that Maintenance Domain
Level takes the default value 4. In the test of an Ethernet service
between two internal NEs on the transport network, set Maintenance
Domain Level to a value smaller than 4. In the test of 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.10.11.2 Required in the case of the NEs where the two Ethernet ports involved in
Creating an the service 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 two
NEs.
l Set Relevant Service to the same service for the two NEs.
l It is recommended that you set CC Test Transmit Period to 1s.
A.10.11.3 Required in the case of the NEs where the two Ethernet ports involved in
Creating an the service test are located. Set the parameters as follows:
MEP Point 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 The MP ID is used to identify the MEP during the LB test. Therefore,
set CC Status to Active.
Operation Description
A.10.11.4 Required in the case of the NE where the Ethernet ports involved in the
Creating OAM 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
Optional
Configuring LAGs
Configuring E-Line
services
Configuring QoS
End
A.10.2.1 Required if LAG protection is configured for FE/GE ports or for the Hybrid
Creating a radio that works in N+0/XPIC mode. Set the parameters as follows:
LAG l Set LAG Type to the same value as the opposite equipment. Generally,
set LAG Type to Static for the equipment at both ends.
l The Hybrid/AM attributes must be set to the same value for the IF ports
in a LAG.
l In the case of FE/GE ports, set Load Sharing to the same value as the
opposite equipment. If the LAG is configured only 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
increase the bandwidth, it is recommended that you set Load
Sharing to Sharing for the equipment at both ends.
l Set Load Sharing to Sharing at both ends, if Hybrid radio works in N
+0/XPIC mode and uses LAG protection.
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 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 Set Main Board, Main Port, and Selected Slave Ports according to
the planning information. 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.10.6.3 Required.
Setting the In the case of an NNI that is connected to the external
Layer 2 equipment, set QinQ Type Domain according to the T-PID
Attributes of the S-VLAN that is supported by the external equipment.
of Ethernet In the case of NNIs within the network, QinQ Type
Ports Domain takes the default value.
A.10.6.4 Optional.
Setting the
Advanced
Attributes
of Ethernet
Ports
A.10.7.2 Optional.
Setting the In the case of an NNI that is connected to the external
Layer 2 equipment, set QinQ Type Domain according to the T-PID
Attributes of the S-VLAN that is supported by the external equipment.
of the In the case of NNIs within the network, QinQ Type
IF_ETH Domain takes the default value.
Port
A.10.7.3 Optional.
Setting the
Advanced
Attributes
of the
IF_ETH
Port
A.10.10.1 Required.
Creating a DS Set the parameters according to the network planning information.
Domain
NOTE
Point-to-point transparently transmitted services support mapping the PHB service
classes based on the DSCP type only. The default DS, however, maps the PHB
service classes according to the CLAN priorities. Therefore, you need to configure
a new DS.
A.10.10.4 Required when you need to apply QoS policies other than DS and port
Creating a Port shaping for a specific port.
Policy Set the parameters according to the network planning information.
A.10.10.6 Required if you need to perform the ACL, CoS, CAR or shaping operation
Creating the for a specific flow over the port.
Traffic Set the related parameters according to the network plan.
A.10.10.8 Required if you need to limit the egress bandwidth that an Ethernet service
Configuring occupies.
Port Shaping Set the parameters according to the network planning information.
A.10.11.1 Required in the case of the NEs where the two Ethernet ports involved in
Creating an the service test are located. Set the parameters as follows:
MD l Set Maintenance Domain Name and Maintenance Domain Level to
the same values for the two NEs.
l In the test of an Ethernet service between two edge nodes on the
transport network, it is recommended that Maintenance Domain
Level takes the default value 4. In the test of an Ethernet service
between two internal NEs on the transport network, set Maintenance
Domain Level to a value smaller than 4. In the test of 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.10.11.2 Required in the case of the NEs where the two Ethernet ports involved in
Creating an the service 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 two
NEs.
l Set Relevant Service to the same service for the two NEs.
l It is recommended that you set CC Test Transmit Period to 1s.
A.10.11.3 Required in the case of the NEs where the two Ethernet ports involved in
Creating an the service test are located. Set the parameters as follows:
MEP Point 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 The MP ID is used to identify the MEP during the LB test. Therefore,
set CC Status to Active.
A.10.11.4 Required in the case of the NE where the Ethernet ports involved in the
Creating OAM 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
Optional
Configuring LAGs
Configuring QoS
End
A.10.2.1 Required if LAG protection is configured for FE/GE ports or for the Hybrid
Creating a radio that works in N+0/XPIC mode. Set the parameters as follows:
LAG l Set LAG Type to the same value as the opposite equipment. Generally,
set LAG Type to Static for the equipment at both ends.
l The Hybrid/AM attributes must be set to the same value for the IF ports
in a LAG.
l In the case of FE/GE ports, set Load Sharing to the same value as the
opposite equipment. If the LAG is configured only 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
increase the bandwidth, it is recommended that you set Load
Sharing to Sharing for the equipment at both ends.
l Set Load Sharing to Sharing at both ends, if Hybrid radio works in N
+0/XPIC mode and uses LAG protection.
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 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 Set Main Board, Main Port, and Selected Slave Ports according to
the planning information. 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.
A.10.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.10.1.2 Required if the values of the default parameters of the ERPS timers need
Setting the to be changed.
Parameters of Set Hold-Off Time(ms), Guard Time(ms), WTR Time(min), and
Ethernet Ring Packet Transmit Interval(s) according to the actual requirements. Set
Protocol these parameters to the same values for all the NEs on the network.
Operation Description
A.10.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.10.6.4 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 Enabling Broadcast Packet Suppression and
of Ethernet Broadcast Packet Suppression Threshold according to the
Ports actual requirements.
A.10.7.3 Optional.
Setting the Set Enabling Broadcast Packet Suppression and
Advanced Broadcast Packet Suppression Threshold according to the
Attributes actual requirements.
of the
IF_ETH
Port
Operation Description
A.10.10.1 Required.
Creating a DS Set the parameters according to the network planning information.
Domain
NOTE
Point-to-point transparently transmitted services support mapping the PHB service
classes based on the DSCP type only. The default DS, however, maps the PHB
service classes according to the CLAN priorities. Therefore, you need to configure
a new DS.
A.10.10.4 Required when you need to apply QoS policies other than DS and port
Creating a Port shaping for a specific port.
Policy Set the parameters according to the network planning information.
A.10.10.6 Required if you need to perform the ACL, CoS, CAR or shaping operation
Creating the for a specific flow over the port.
Traffic Set the related parameters according to the network plan.
Operation Description
A.10.10.8 Required if you need to limit the egress bandwidth that an Ethernet service
Configuring occupies.
Port Shaping Set the parameters according to the network planning information.
A.10.11.1 Required in the case of the NEs where the two Ethernet ports involved in
Creating an the service test are located. Set the parameters as follows:
MD l Set Maintenance Domain Name and Maintenance Domain Level to
the same values for the two NEs.
l In the test of an Ethernet service between two edge nodes on the
transport network, it is recommended that Maintenance Domain
Level takes the default value 4. In the test of an Ethernet service
between two internal NEs on the transport network, set Maintenance
Domain Level to a value smaller than 4. In the test of 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.10.11.2 Required in the case of the NEs where the two Ethernet ports involved in
Creating an the service 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 two
NEs.
l Set Relevant Service to the same service for the two NEs.
l It is recommended that you set CC Test Transmit Period to 1s.
A.10.11.3 Required in the case of the NEs where the two Ethernet ports involved in
Creating an the service test are located. Set the parameters as follows:
MEP Point 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 The MP ID is used to identify the MEP during the LB test. Therefore,
set CC Status to Active.
Operation Description
A.10.11.4 Required in the case of the NE where the Ethernet ports involved in the
Creating OAM 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
Optional
Configuring LAGs
Configuring QoS
End
The detailed information about the procedures in the flow chart is provided as follows.
A.10.2.1 Required if LAG protection is configured for FE/GE ports or for the Hybrid
Creating a radio that works in N+0/XPIC mode. Set the parameters as follows:
LAG l Set LAG Type to the same value as the opposite equipment. Generally,
set LAG Type to Static for the equipment at both ends.
l The Hybrid/AM attributes must be set to the same value for the IF ports
in a LAG.
l In the case of FE/GE ports, set Load Sharing to the same value as the
opposite equipment. If the LAG is configured only 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
increase the bandwidth, it is recommended that you set Load
Sharing to Sharing for the equipment at both ends.
l Set Load Sharing to Sharing at both ends, if Hybrid radio works in N
+0/XPIC mode and uses LAG protection.
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 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 Set Main Board, Main Port, and Selected Slave Ports according to
the planning information. 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.
A.10.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.10.1.2 Required if the values of the default parameters of the ERPS timers need
Setting the to be changed.
Parameters of Set Hold-Off Time(ms), Guard Time(ms), WTR Time(min), and
Ethernet Ring Packet Transmit Interval(s) according to the actual requirements. Set
Protocol these parameters to the same values for all the NEs on the network.
Operation Description
A.10.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
A.10.6.2 Required when the flow control function is enabled on the external
Configuring equipment to which the Ethernet port is connected. Set the parameters as
the Traffic 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
Enable Symmetric Flow Control.
l When the external equipment uses the auto-negotiation flow control
function, set Auto-Negotiation Flow Control Mode to Enable
Symmetric Flow Control.
Operation Description
A.10.6.4 Required when you need to enable the port self-loop test and automatic
Setting the loopback shutdown functions or to enable the broadcast packet suppression
Advanced function.
Attributes of Set Enabling Broadcast Packet Suppression and Broadcast Packet
Ethernet Ports Suppression Threshold according to the requirements.
Operation Description
A.10.10.1 Required.
Creating a DS Set the parameters according to the network planning information.
Domain
NOTE
Point-to-point transparently transmitted services support mapping the PHB service
classes based on the DSCP type only. The default DS, however, maps the PHB
service classes according to the CLAN priorities. Therefore, you need to configure
a new DS.
A.10.10.4 Required when you need to apply QoS policies other than DS and port
Creating a Port shaping for a specific port.
Policy Set the parameters according to the network planning information.
A.10.10.6 Required if you need to perform the ACL, CoS, CAR or shaping operation
Creating the for a specific flow over the port.
Traffic Set the related parameters according to the network plan.
A.10.10.8 Required if you need to limit the egress bandwidth that an Ethernet service
Configuring occupies.
Port Shaping Set the parameters according to the network planning information.
A.10.11.1 Required in the case of the NEs where the two Ethernet ports involved in
Creating an the service test are located. Set the parameters as follows:
MD l Set Maintenance Domain Name and Maintenance Domain Level to
the same values for the two NEs.
l In the test of an Ethernet service between two edge nodes on the
transport network, it is recommended that Maintenance Domain
Level takes the default value 4. In the test of an Ethernet service
between two internal NEs on the transport network, set Maintenance
Domain Level to a value smaller than 4. In the test of 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.10.11.2 Required in the case of the NEs where the two Ethernet ports involved in
Creating an the service 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 two
NEs.
l Set Relevant Service to the same service for the two NEs.
l It is recommended that you set CC Test Transmit Period to 1s.
A.10.11.3 Required in the case of the NEs where the two Ethernet ports involved in
Creating an the service test are located. Set the parameters as follows:
MEP Point 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 The MP ID is used to identify the MEP during the LB test. Therefore,
set CC Status to Active.
Operation Description
A.10.11.4 Required in the case of the NE where the Ethernet ports involved in the
Creating OAM 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
Optional
Configuring LAGs
Configuring QoS
End
The detailed information about the procedures in the flow chart is provided as follows.
A.10.2.1 Required if LAG protection is configured for FE/GE ports or for the Hybrid
Creating a radio that works in N+0/XPIC mode. Set the parameters as follows:
LAG l Set LAG Type to the same value as the opposite equipment. Generally,
set LAG Type to Static for the equipment at both ends.
l The Hybrid/AM attributes must be set to the same value for the IF ports
in a LAG.
l In the case of FE/GE ports, set Load Sharing to the same value as the
opposite equipment. If the LAG is configured only 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
increase the bandwidth, it is recommended that you set Load
Sharing to Sharing for the equipment at both ends.
l Set Load Sharing to Sharing at both ends, if Hybrid radio works in N
+0/XPIC mode and uses LAG protection.
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 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 Set Main Board, Main Port, and Selected Slave Ports according to
the planning information. 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.
A.10.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.10.1.2 Required if the values of the default parameters of the ERPS timers need
Setting the to be changed.
Parameters of Set Hold-Off Time(ms), Guard Time(ms), WTR Time(min), and
Ethernet Ring Packet Transmit Interval(s) according to the actual requirements. Set
Protocol these parameters to the same values for all the NEs on the network.
Operation Description
A.10.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.10.6.2 Required when the flow control function is enabled on the external
Configuring equipment to which the Ethernet port is connected. Set the parameters as
the Traffic 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
Enable Symmetric Flow Control.
l When the external equipment uses the auto-negotiation flow control
function, set Auto-Negotiation Flow Control Mode to Enable
Symmetric Flow Control.
Operation Description
A.10.6.3 Optional.
Setting the l In the case of a UNI, if Encapsulation Type is set to 802.1Q, set
Layer 2 TAG to Tag Aware (default value).
Attributes of
Ethernet Ports l In the case of an NNI that is connected to the external equipment, set
QinQ Type Domain according to the T-PID of the S-VLAN that is
supported by the external equipment.
A.10.6.4 Required when you need to enable the port self-loop test and automatic
Setting the loopback shutdown functions or to enable the broadcast packet suppression
Advanced function.
Attributes of Set Enabling Broadcast Packet Suppression and Broadcast Packet
Ethernet Ports Suppression Threshold according to the requirements.
A.10.10.1 Required.
Creating a DS Set the parameters according to the network planning information.
Domain
NOTE
Point-to-point transparently transmitted services support mapping the PHB service
classes based on the DSCP type only. The default DS, however, maps the PHB
service classes according to the CLAN priorities. Therefore, you need to configure
a new DS.
A.10.10.4 Required when you need to apply QoS policies other than DS and port
Creating a Port shaping for a specific port.
Policy Set the parameters according to the network planning information.
A.10.10.6 Required if you need to perform the ACL, CoS, CAR or shaping operation
Creating the for a specific flow over the port.
Traffic Set the related parameters according to the network plan.
A.10.10.8 Required if you need to limit the egress bandwidth that an Ethernet service
Configuring occupies.
Port Shaping Set the parameters according to the network planning information.
A.10.11.1 Required in the case of the NEs where the two Ethernet ports involved in
Creating an the service test are located. Set the parameters as follows:
MD l Set Maintenance Domain Name and Maintenance Domain Level to
the same values for the two NEs.
l In the test of an Ethernet service between two edge nodes on the
transport network, it is recommended that Maintenance Domain
Level takes the default value 4. In the test of an Ethernet service
between two internal NEs on the transport network, set Maintenance
Domain Level to a value smaller than 4. In the test of 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.10.11.2 Required in the case of the NEs where the two Ethernet ports involved in
Creating an the service 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 two
NEs.
l Set Relevant Service to the same service for the two NEs.
l It is recommended that you set CC Test Transmit Period to 1s.
A.10.11.3 Required in the case of the NEs where the two Ethernet ports involved in
Creating an the service test are located. Set the parameters as follows:
MEP Point 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 The MP ID is used to identify the MEP during the LB test. Therefore,
set CC Status to Active.
Operation Description
A.10.11.4 Required in the case of the NE where the Ethernet ports involved in the
Creating OAM 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
Backhaul network
The connections of Ethernet links shown in Figure 5-29 are described as follows.
Between NE1 and the BTS 7-EM4T-1 Configure this port to access
services from the BTS.
Ethernet Port
Table 5-44 provides the information about the Ethernet port involved in the service.
Parameter 7-EM4T-1
NOTE
l In this example, the GE port on the BTS works in the auto-negotiation mode. Hence, the FE 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.
l Generally, the flow control function is enabled only when the NE or the peer equipment is inadequate for
QoS processing. The flow control planning on the NE must match the flowing control planning on the peer
equipment.
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 5-47. Each Ethernet port involved in the service uses the same DS configuration.
CS7 56 -
CS6 48 -
AF4 32 -
AF1 8 -
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.
Table 5-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
In this example, no CAR or shaping processing needs to be performed on the services transmitted
from the BTS.
Procedure
Step 1 See A.10.3.2 Configuring the E-Line Service and configure the E-Line services.
Parameter Value
Service ID 1
Direction UNI-UNI
Source 7-EM4T-1
Sink 3-IFU2-1
----End
Procedure
Step 1 See A.10.6.1 Setting the General Attributes of Ethernet Ports and set the general attributes
of the Ethernet port.
Parameter Value
7-EM4T-1
----End
Procedure
Step 1 See A.10.10.1 Creating a DS Domain and create a DS domain.
The values for the relevant parameters that need to be set in the main interface are provided as
follows.
Parameter Value
Mapping Relation ID 2
The values for the relevant parameters that need to be set in the Ingress Mapping Relation tab
page are provided as follows.
0 BE
8 AF11
16 AF21
24 AF31
32 AF41
40 EF
48 CS6
56 CS7
The values for the relevant parameters that need to be set in the Egress Mapping Relation tab
page are provided as follows.
BE 0
AF11 8
AF21 16
AF31 24
AF41 32
EF 40
CS6 48
CS7 56
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.
The values for the relevant parameters that need to be set in the Application Port tab page are
provided as follows.
Parameter Value
Step 2 See A.10.10.4 Creating a Port Policy to create the port policy.
Parameter Value
Policy ID 1
Step 3 See A.10.10.7 Setting the Port That Uses the Port Policy and set the ports that use the port
policy.
Parameter Value
Port_Comm
Port 7-EM4F-3
3-IFU2-1
----End
Context
NOTE
This section describes how to configure the point-to-point transparently transmitted Ethernet service on NE1
and how to configure the ETH OAM data on NE2 for testing the Ethernet service.
Procedure
Step 1 See A.10.11.1 Creating an MD and create an MD.
The values for the related parameters are provided as follows.
Parameter Value
NE1 NE2
Maintenance Domain 3 3
Level
Parameter Value
NE1 NE2
NOTE
a: BSCtoBTS_Tline is the name of the point-to-point Ethernet service that is transparently transmitted from NE2
to NE1. The service ID is 1.
Step 3 See A.10.11.3 Creating an MEP Point and create MEP points.
Parameter Value
NE1 NE2
VLAN - -
MP ID 101 102
Parameter Value
NE1 NE2
Step 5 See perform an LB test to test the Ethernet service configurations and test the E-Line service.
Use MP 101 as the source maintenance point and MP 102 as the sink maintenance point to
perform the LB test.
----End
Based on 3.5 Configuration Example (Radio Links on the Hybrid Radio Chain Network),
configure Ethernet services according to the following requirements:
To meet the preceding requirements, VLAN-based E-Line services are configured for service
transmission on each NE; in addition, corresponding LAG protection and QoS processing are
configured.
FE
GE GE
FE NE4
BTS3
20 Mbit/s FE
VLAN 120-129
NE3 NE2 NE1 BSC
120 Mbit/s
VLAN 100-149
FE BTS1
FE 45 Mbti/s
NE6 NE5 VLAN 100-109
BTS4
BTS5 25 Mbit/s
15 Mbit/s VLAN 130-139
VLAN 140-149
The connections of Ethernet links shown in Figure 5-30 are described as follows.
Between NE1 and 7-EM4F-3 Main port of a LAG Configure these ports
the BSC into a load non-
7-EM4F-4 Slave port of a LAG sharing LAG,
therefore improving
link reliability.
Ethernet Ports
Table 5-55 to Table 5-60 provide the information about each Ethernet port involved in the
service.
NOTE
l In this example, the FE ports on all the BTSs work in the auto-negotiation mode. Hence, the FE 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.
l Generally, the flow control function is enabled only when the NE or the peer equipment is inadequate for
QoS processing. The flow control planning on the NE must match the flowing control planning on the peer
equipment.
l In this example, all the services carry VLAN tags. Therefore, the tag attributes of all the ports are tag-aware.
Parameter 3-IFU2-1
To improve the reliability of service transmission, NE1 and the BSC are interconnected through
the LAG formed by two GE links. Table 5-67 provides the planning information.
Parameter NE1
NOTE
In this example, the bandwidth of the Ethernet service to be transmitted is 120 Mbit/s, much smaller than the
bandwidth of a GE port. Therefore, you need not configure the link aggregation group to the load sharing mode
to increase the bandwidth.
Table 5-68 to Table 5-73 provide the detailed service planning information.
Parameter NE1
NE2 to BSC
Service ID 1
Parameter NE1
NE2 to BSC
Direction UNI-UNI
Parameter NE2
Service ID 1 2
Parameter NE3
Service ID 1 2
Parameter NE3
Parameter NE4
Service ID 1 2
Parameter NE5
Service ID 1 2
Parameter NE5
Parameter NE6
BTS5 to NE5
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 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 5-74. Each Ethernet port involved in the service uses the same DS
configuration.
CS7 7 -
CS6 6 -
AF4 4 -
AF1 1 -
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.
Table 5-75 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
In this example, the CAR processing needs to be performed on the DS edge node in the uplink
direction (from the BTS to the BSC) of the non-real-time R99 service on each BTS (that is, the
service with VLAN priority 2). Table 5-76 lists the CAR parameters.
Parameter Value
NOTE
The CBS/PBS is in direct proportion to the CIR/PIR. That is, the larger the value of the CBS/PBS, the more the
burst packets are permitted. In this example, the values of the CBS and the PBS are set according to the bytes
that are transmitted at CIR and PIR during a 100 ms period.
Procedure
Step 1 See A.10.2.1 Creating a LAG and create the LAG for NE1.
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 Settings tab page are
provided as follows.
Parameter Value
----End
Procedure
Step 1 See A.10.3.2 Configuring the E-Line Service and configure the E-Line services.
l The values for the related parameters of NE1 are provided as follows.
Parameter Value
NE2 to BTS
Service ID 1
Direction UNI-UNI
Source 3-IFU2-1
Parameter Value
NE2 to BTS
Sink 7-EM4F-3
l The values for the related parameters of NE2 are provided as follows.
Parameter Value
Service ID 1 2
l The values for the related parameters of NE3 are provided as follows.
Parameter Value
Service ID 1 2
l The values for the related parameters of NE4 are provided as follows.
Parameter Value
Service ID 1 2
Parameter Value
l The values for the related parameters of NE5 are provided as follows.
Parameter Value
Service ID 1 2
l The values for the related parameters of NE6 are provided as follows.
Parameter Value
BTS5 to NE5
Service ID 1
Direction UNI-UNI
Parameter Value
BTS5 to NE5
Source 7-EM4T-1
Sink 3-IFU2-1
----End
Procedure
Step 1 See A.10.6.1 Setting the General Attributes of Ethernet Ports and set the general attributes
of Ethernet ports.
l The values for the related parameters of NE1 are provided as follows.
Parameter Value
7-EM4F-3 7-EM4F-4
l The values for the related parameters of NE2 are provided as follows.
Parameter Value
7-EM4T-1 7-EM4T-3
l The values for the related parameters of NE3 are provided as follows.
Parameter Value
7-EM4T-3
l The values for the related parameters of NE4 are provided as follows.
Parameter Value
7-EM4T-1 7-EM4T-2
l The values for the related parameters of NE5 are provided as follows.
Parameter Value
7-EM4T-1
l The values for the related parameters of NE6 are provided as follows.
Parameter Value
7-EM4T-1
----End
Procedure
Step 1 See A.10.10.1 Creating a DS Domain and create a 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 2
The values for the related parameters that need to be set in the Ingress Mapping Relation tab
page are provided as follows.
0 BE
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.
BE 0
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.
The values for the related parameters that need to be set in the Application Port tab page are
provided as follows.
Paramete Value
r
NE1 NE2 NE3 NE4 NE5 NE6
NOTE
The mapping relation defined in the default DS domain is the same as the mapping relation defined in the DS
domain that is created in this step. Therefore, you can skip this step.
Step 2 See A.10.10.4 Creating a Port Policy and create the port policy.
l The values for the related parameters of NE2, NE4, NE5, and NE6 are provided as follows.
Parameter Value
Policy ID 1 2
Grooming Police After SP (CS7, CS6, and EF) SP (CS7, CS6, and EF)
Reloading WRR (AF4 to AF1) WRR (AF4 to AF1)
SP (BE) SP (BE)
Bandwidth Limit Disabled (for all PHB Disabled (for all PHB
service classes) service classes)
l The values for the related parameters of NE1 and NE3 are provided as follows.
Parameter Value
Policy ID 1
Step 3 See A.10.10.6 Creating the Traffic and create the traffic on NE2, NE4, NE5, and NE6.
The values for the related parameters that need to be set in the main interface are provided as
follows.
Parameter Value
Traffic Classification ID 1
The values for the related parameters that need to be set in the INGRESS tab page are provided
as follows.
Parameter Value
Match Value 2
Wildcard 0
CoS -
CIR(kbit/s) 4096
PIR(kbit/s) 8192
CBS(byte) 51200
PBS(byte) 102400
The values for the related parameters that need to be set in the EGRESS tab page are provided
as follows.
Parameter Value
Step 4 See A.10.10.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 NE1 are provided as follows.
Parameter Value
Port 3-IFU2-1
7-EM4F-3
l The values for the related parameters of NE2 are provided as follows.
Parameter Value
l The values for the related parameters of NE3 are provided as follows.
Parameter Value
Port 3-IFU2-1
4-IFU2-1
7-EM4T-3
l The values for the related parameters of NE4 are provided as follows.
Parameter Value
l The values for the related parameters of NE5 are provided as follows.
Parameter Value
l The values for the related parameters of NE6 are provided as follows.
Parameter Value
----End
Procedure
Step 1 See A.10.11.1 Creating an MD and configure the MD for NE1, NE2, NE4, NE5, and NE6.
The values for the related parameters are provided as follows.
Parameter Value
Maintenanc 4 4 4 4 4
e Domain
Level
Step 2 See A.10.11.2 Creating an MA and create the maintenance association (MA) for NE1, NE2,
NE4, NE5, and NE6.
l The values for the relevant parameters of NE1 are provided as follows.
Parameter Value
Relevant 1- 1- 1- 1- 1-
Service NE2toBSC_ NE2toBSC_ NE2toBSC_ NE2toBSC_ NE2toBSC_
Vline Vline Vline Vline Vline
Parameter Value
CC Test 1s 1s 1s 1s 1s
Transmit
Period
l The values for the relevant parameters of NE2 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE4 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE5 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE6 are provided as follows.
Parameter Value
Step 3 See A.10.11.3 Creating an MEP Point and create the MEP for NE1, NE2, NE4, NE5, and NE6.
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
Board 7-EM4T
Port 7-EM4T-1
VLAN 100
MP ID 201
Direction Ingress
CC Status Active
l The values for the related parameters of NE4 are provided as follows.
Parameter Value
Parameter Value
MP ID 401 402
l The values for the related parameters of NE5 are provided as follows.
Parameter Value
Board 7-EM4T
Port 7-EM4T-1
VLAN 130
MP ID 501
Direction Ingress
CC Status Active
l The values for the related parameters of NE6 are provided as follows.
Parameter Value
Board 7-EM4T
Port 7-EM4T-1
VLAN 140
MP ID 601
Direction Ingress
CC Status Active
Step 4 See A.10.11.4 Creating Remote MEPs in an MA and create the remote MEP points for NE1,
NE2, NE4, NE5, and NE6.
The values for the related parameters of NE1 are provided as follows.
Parameter Value
The values for the related parameters of NE2 are provided as follows.
Parameter Value
The values for the related parameters of NE4 are provided as follows.
Parameter Value
The values for the related parameters of NE5 are provided as follows.
Parameter Value
The values for the related parameters of NE6 are provided as follows.
Parameter Value
Step 5 See perform an LB test to test the Ethernet service configurations and test the E-Line services
on NE1.
l Perform the LB test by considering the MEP whose MP ID is 101 as the source MEP and
the MEP whose MP ID is 201 as the sink MEP.
l Perform the LB test by considering the MEP whose MP ID is 102 as the source MEP and
the MEP whose MP ID is 401 as the sink MEP.
l Perform the LB test by considering the MEP whose MP ID is 103 as the source MEP and
the MEP whose MP ID is 402 as the sink MEP.
l Perform the LB test by considering the MEP whose MP ID is 104 as the source MEP and
the MEP whose MP ID is 501 as the sink MEP.
l Perform the LB test by considering the MEP whose MP ID is 105 as the source MEP and
the MEP whose MP ID is 601 as the sink MEP.
There should be no packets lost during the LB tests.
----End
Based on 3.5 Configuration Example (Radio Links on the Hybrid Radio Chain Network),
configure Ethernet services according to the following actual requirements:
To meet the preceding requirements, QinQ-based E-Line services are configured for service
transmission on each NE; in addition, corresponding LAG protection and QoS processing are
configured.
FE
GE GE
FE NE4
BTS3
20 Mbit/s FE
S-VLAN 120
NE3 NE2 NE1
BSC
120 Mbit/s
FE BTS1 S-VLAN 100, 110,120,130,140
FE 45 Mbit/s
NE6 NE5 S-VLAN 100
BTS4
BTS5 25 Mbit/s
15 Mbit/s S-VLAN 130
S-VLAN 140
NOTE
The connections of Ethernet links shown in Figure 5-31 are described as follows.
Between NE1 and 7-EM4F-3 Main port of a LAG Configure these ports
the BSC into a load non-
7-EM4F-4 Slave port of a LAG sharing LAG,
therefore improving
link reliability.
Ethernet Port
Table 5-83 to Table 5-88 provide the information about each Ethernet port involved in the
service.
Parameter 7-EM4T-3
Parameter 7-EM4T-1
Parameter 7-EM4T-1
NOTE
l If the Ethernet services on each BTS do not contain any untagged frames, you can set Encapsulation
Type to 802.1Q and set Tag to Tag Aware for the FE port that accesses the Ethernet services on each BTS.
l In this example, the FE ports on all the BTSs work in the auto-negotiation mode. Hence, the FE 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.
l Generally, the flow control function is enabled only when the NE or the peer equipment is inadequate for
QoS processing. The flow control planning on the NE must match the flowing control planning on the peer
equipment.
l In this example, the S-VLAN T-PID that the BSC can identify is 0x8100. Hence, you need to set QinQ
Type Domain to 0x8100 for the two GE ports connecting to the BSC. The other NNI ports connect to internal
equipment. Hence, you need to set QinQ Type Domain to 0x88a8 for the other NNI ports.
Parameter 3-IFU2-1
Tag 0x88a8
Parameter 3-IFU2-1
Tag 0x88a8
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.
To improve the reliability of service transmission, NE1 and the BSC are interconnected through
the LAG formed by two GE links. Table 5-95 provides the planning information.
Parameter NE1
NOTE
In this example, the bandwidth of the Ethernet service to be transmitted is 120 Mbit/s, much smaller than the
bandwidth of a GE port. Therefore, you need not configure the link aggregation group to the load sharing mode
to increase the bandwidth.
Table 5-96 to Table 5-101 provide the detailed service planning information.
Parameter NE1
Service ID 1 2 3 4 5
Parameter NE1
Source Port - - - - -
Source C- - - - - -
VLANs
Service ID 1 2 3 4 5
Source C- Blank - - - -
VLANs
Parameter NE2
Parameter NE3
Service ID 1 2 3 4
Source Port - - - -
Source C- - - - -
VLANs
Parameter NE4
Service ID 1 2
Parameter NE4
Service ID 1 2
BTS5 to NE5
Service ID 1
Parameter NE6
BTS5 to NE5
Direction UNI-NNI
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 5-102. Each Ethernet port involved in the service uses the same DS
configuration.
CS7 7 -
CS6 6 -
AF4 4 -
AF1 1 -
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.
Table 5-103 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
In this example, the CAR processing needs to be performed on the DS edge node in the uplink
direction (from the BTS to the BSC) of the non-real-time R99 service on each BTS (that is, the
service with VLAN priority 2). Table 5-104 lists the CAR parameters.
Parameter Value
In this example, the shaping processing needs to be performed in the uplink direction (from the
BTS to the BSC) of the real-time OM and HSDPA services on each BTS. Table 5-105 lists the
shaping parameters.
Parameter Value
NOTE
The CBS/PBS is in direct proportion to the CIR/PIR. That is, the larger the value of the CBS/PBS, the more the
burst packets are permitted. In this example, the values of the CBS and the PBS are set according to the bytes
that are transmitted at CIR and PIR during a 100 ms period.
Procedure
Step 1 See A.10.2.1 Creating a LAG and create the LAG for NE1.
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 Settings tab page are
provided as follows.
Parameter Value
----End
Procedure
Step 1 See A.10.3.2 Configuring the E-Line Service and configure the E-Line services.
l The values for the related parameters of NE1 are provided as follows.
Para Value
mete
r BTS1 to BTS2 to BTS3 to BTS4 to BTS5 to
BSC BSC BSC BSC BSC
Servi 1 2 3 4 5
ce ID
Sour QinQ Link-6 QinQ Link-7 QinQ Link-8 QinQ Link-9 QinQ Link-10
ce
Sink QinQ Link-1 QinQ Link-2 QinQ Link-3 QinQ Link-4 QinQ Link-5
Port 3- 7- 3- 7- 3- 7- 3- 7- 3- 7-
IFU2 EM4 IFU2 EM4 IFU2 EM4 IFU2 EM4 IFU2 EM4
-1 F-3 -1 F-3 -1 F-3 -1 F-3 -1 F-3
Enca QinQ QinQ QinQ QinQ QinQ QinQ QinQ QinQ QinQ QinQ
psula
tion
Type
Tag Tag Tag Tag Tag Tag Tag Tag Tag Tag Tag
Awar Awar Awar Awar Awar Awar Awar Awar Awar Awar
e e e e e e e e e e
l The values for the related parameters of NE2 are provided as follows.
Para Value
mete
r BTS1 to NE1 BTS2 to NE1 BTS3 to NE1 BTS4 to NE1 BTS5 to NE1
Servi 1 2 3 4 5
ce ID
Sour 7-EM4T-1 QinQ Link-6 QinQ Link-7 QinQ Link-8 QinQ Link-9
ce
Sour Blank - - - -
ce
VLA
N
(e.g.
1,3-5
)
Sink QinQ Link-1 QinQ Link-2 QinQ Link-3 QinQ Link-4 QinQ Link-5
Port 7- 3- 7- 3- 7- 3- 7- 3- 7- 3-
EM4 IFU2 EM4 IFU2 EM4 IFU2 EM4 IFU2 EM4 IFU2
T-1 -1 T-3 -1 T-3 -1 T-3 -1 T-3 -1
Para Value
mete
r BTS1 to NE1 BTS2 to NE1 BTS3 to NE1 BTS4 to NE1 BTS5 to NE1
Enca Null QinQ QinQ QinQ QinQ QinQ QinQ QinQ QinQ QinQ
psula
tion
Type
Tag Tag Tag Tag Tag Tag Tag Tag Tag Tag Tag
Awar Awar Awar Awar Awar Awar Awar Awar Awar Awar
e e e e e e e e e e
l The values for the related parameters of NE3 are provided as follows.
Param Value
eter
BTS2 to NE1 BTS3 to NE1 BTS4 to NE1 BTS5 to NE1
Servic 1 2 3 4
e ID
Port 3- 7- 3- 7- 3- 7- 3- 7-
IFU2-1 EM4F- IFU2-1 EM4F- IFU2-1 EM4F- IFU2-1 EM4F-
3 3 3 3
Param Value
eter
BTS2 to NE1 BTS3 to NE1 BTS4 to NE1 BTS5 to NE1
l The values for the related parameters of NE4 are provided as follows.
Parameter Value
Service ID 1 2
l The values for the related parameters of NE5 are provided as follows.
Parameter Value
Service ID 1 2
Parameter Value
Port - 3-IFU2-1
S-Vlan ID - 140
l The values for the related parameters of NE6 are provided as follows.
Parameter Value
BTS5 to NE5
Service ID 1
Direction UNI-NNI
Source 7-EM4T-1
Port 3-IFU2-1
S-Vlan ID 140
Parameter Value
BTS5 to NE5
----End
Procedure
Step 1 See A.10.6.1 Setting the General Attributes of Ethernet Ports and set the general attributes
of Ethernet ports.
l The values for the related parameters of NE1 are provided as follows.
Parameter Value
7-EM4F-3 7-EM4F-4
l The values for the related parameters of NE2 are provided as follows.
Parameter Value
7-EM4T-1 7-EM4T-3
l The values for the related parameters of NE3 are provided as follows.
Parameter Value
7-EM4T-3
l The values for the related parameters of NE4 are provided as follows.
Parameter Value
7-EM4T-1 7-EM4T-2
l The values for the related parameters of NE5 are provided as follows.
Parameter Value
7-EM4T-1
l The values for the related parameters of NE6 are provided as follows.
Parameter Value
7-EM4T-1
Step 2 See A.10.6.3 Setting the Layer 2 Attributes of Ethernet Ports and set Layer 2 attributes of
Ethernet ports for NE1.
Parameter Value
7-EM4F-3 7-EM4F-4
----End
Procedure
Step 1 See A.10.10.1 Creating a DS Domain and create a 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 2
The values for the related parameters that need to be set in the Ingress Mapping Relation tab
page are provided as follows.
0 0 BE
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.
BE 0 0
AF11 1 1
AF21 2 2
AF31 3 3
AF41 4 4
EF 5 5
CS6 6 6
CS7 7 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.
The values for the related parameters that need to be set in the Application Port tab page are
provided as follows.
Paramete Value
r
NE1 NE2 NE3 NE4 NE5 NE6
Step 2 See A.10.10.3 Changing the Ports That Use the DS Domain and change the ports that use the
DS domain.
l The values for the related parameters of NE1 are provided as follows.
3-IFU2-1 SVLAN
7-EM4F-3 SVLAN
SVLAN
l The values for the related parameters of NE2 are provided as follows.
7-EM4T-1 CVLAN
7-EM4T-3 SVLAN
3-IFU2-1 SVLAN
l The values for the related parameters of NE3 are provided as follows.
3-IFU2-1 SVLAN
4-IFU2-1 SVLAN
7-EM4T-3 SVLAN
l The values for the related parameters of NE4 are provided as follows.
7-EM4T-1 CVLAN
7-EM4T-2 CVLAN
3-IFU2-1 SVLAN
l The values for the related parameters of NE5 are provided as follows.
3-IFU2-1 SVLAN
4-IFU2-1 SVLAN
7-EM4T-1 cvlan
l The values for the related parameters of NE6 are provided as follows.
3-IFU2-1 SVLAN
7-EM4T-1 CVLAN
Step 3 See A.10.10.4 Creating a Port Policy and create the port policy.
l The values for the related parameters of NE1 and NE3 are provided as follows.
Parameter Value
Policy ID 1
l The values for the related parameters of NE2 and NE5 are provided as follows.
Parameter Value
Policy ID 1 2 3
Grooming Police SP (CS7, CS6, and SP (CS7, CS6, and SP (CS7, CS6, and
After Reloading EF) EF) EF)
WRR (AF4 to AF1) WRR (AF4 to AF1) WRR (AF4 to AF1)
SP (BE) SP (BE) SP (BE)
Bandwidth Limit Disabled (for all Disabled (for all Disabled (for all
PHB service PHB service PHB service
classes) classes) classes)
l The values for the related parameters of NE4 and NE6 are provided as follows.
Parameter Value
Policy ID 1 2
Grooming Police After SP (CS7, CS6, and EF) SP (CS7, CS6, and EF)
Reloading WRR (AF4 to AF1) WRR (AF4 to AF1)
SP (BE) SP (BE)
Bandwidth Limit Disabled (for all PHB Disabled (for all PHB
service classes) service classes)
Step 4 See A.10.10.6 Creating the Traffic and create the traffic for NE2, NE4, NE5, and NE6.
l Parameters of NE2
The values for the related parameters that need to be set in the main interface are provided
as follows.
Parameter Value
Traffic Classification ID 1 1
The values for the related parameters that need to be set in the INGRESS tab page are
provided as follows.
Parameter Value
CoS - -
CIR(kbit/s) 4096 -
PIR(kbit/s) 8192 -
Parameter Value
CBS(byte) 51200 -
PBS(byte) 102400 -
The values for the related parameters that need to be set in the EGRESS tab page are provided
as follows.
Parameter Value
CIR(kbit/s) - 2048
PIR(kbit/s) - 4096
CBS(byte) - 25600
PBS(byte) - 51200
l Parameters of NE4
The values for the related parameters that need to be set in the main interface are provided
as follows.
Parameter Value
Traffic 1 1 2
Classification ID
The values for the related parameters that need to be set in the INGRESS tab page are
provided as follows.
Parameter Value
CoS - - -
CIR(kbit/s) 4096 - -
PIR(kbit/s) 8192 - -
CBS(byte) 51200 - -
PBS(byte) 102400 - -
Handling Discard - -
Mode (red)
Remark
(yellow)
Pass (green)
Relabeled - (red) - -
CoS EF (yellow)
- (green)
The values for the related parameters that need to be set in the EGRESS tab page are provided
as follows.
Parameter Value
Parameter Value
l Parameters of NE5
The values for the related parameters that need to be set in the main interface are provided
as follows.
Parameter Value
Traffic Classification ID 1 1
The values for the related parameters that need to be set in the INGRESS tab page are
provided as follows.
Parameter Value
CoS - -
CIR(kbit/s) 4096 -
PIR(kbit/s) 8192 -
CBS(byte) 51200 -
PBS(byte) 102400 -
Parameter Value
The values for the related parameters that need to be set in the EGRESS tab page are provided
as follows.
Parameter Value
CIR(kbit/s) - 2048
PIR(kbit/s) - 4096
CBS(byte) - 25600
PBS(byte) - 51200
l Parameters of NE6:
The values for the related parameters that need to be set in the main interface are provided
as follows.
Parameter Value
Traffic Classification ID 1 1
The values for the related parameters that need to be set in the INGRESS tab page are
provided as follows.
Parameter Value
Parameter Value
CoS - -
CIR(kbit/s) 4096 -
PIR(kbit/s) 8192 -
CBS(byte) 51200 -
PBS(byte) 102400 -
The values for the related parameters that need to be set in the EGRESS tab page are provided
as follows.
Parameter Value
CIR(kbit/s) - 2048
PIR(kbit/s) - 4096
CBS(byte) - 25600
PBS(byte) - 51200
Step 5 See A.10.10.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 NE1 are provided as follows.
Parameter Value
Port 3-IFU2-1
7-EM4F-3
l The values for the related parameters of NE2 are provided as follows.
Parameter Value
l The values for the related parameters of NE3 are provided as follows.
Parameter Value
Port 3-IFU2-1
4-IFU2-1
7-EM4T-3
l The values for the related parameters of NE4 are provided as follows.
Parameter Value
l The values for the related parameters of NE5 are provided as follows.
Parameter Value
l The values for the related parameters of NE6 are provided as follows.
Parameter Value
----End
Procedure
Step 1 See A.10.11.1 Creating an MD and configure the MD for NE1, NE2, NE4, NE5, and NE6.
Parameter Value
Maintenanc 4 4 4 4 4
e Domain
Level
Step 2 See A.10.11.2 Creating an MA and create the MA for NE1, NE2, NE4, NE5, and NE6.
l The values for the relevant parameters of NE1 are provided as follows.
Parameter Value
Relevant 1- 2- 3- 4- 5-
Service BTS1_Qlin BTS2_Qlin BTS3_Qlin BTS4_Qlin BTS5_Qlin
e e e e e
CC Test 1s 1s 1s 1s 1s
Transmit
Period
l The values for the relevant parameters of NE2 are provided as follows.
Parameter Value
Parameter Value
l The values for the relevant parameters of NE4 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE5 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE6 are provided as follows.
Parameter Value
Step 3 See A.10.11.3 Creating an MEP Point and create the MEP for NE1, NE2, NE4, NE5, and NE6.
l The values for the related parameters of NE1 are provided as follows.
Parameter Value
Parameter Value
l The values for the related parameters of NE2 are provided as follows.
Parameter Value
Board 7-EM4T
Port 7-EM4T-1
VLAN -
MP ID 201
Direction Ingress
CC Status Active
l The values for the related parameters of NE4 are provided as follows.
Parameter Value
VLAN - -
MP ID 401 402
Parameter Value
l The values for the related parameters of NE5 are provided as follows.
Parameter Value
Board 7-EM4T
Port 7-EM4T-1
VLAN -
MP ID 501
Direction Ingress
CC Status Active
l The values for the related parameters of NE6 are provided as follows.
Parameter Value
Board 7-EM4T
Port 7-EM4T-1
VLAN -
MP ID 601
Direction Ingress
CC Status Active
Step 4 See A.10.11.4 Creating Remote MEPs in an MA and create the remote MEP points for NE1,
NE2, NE4, NE5, and NE6.
The values for the related parameters of NE1 are provided as follows.
Parameter Value
Parameter Value
The values for the related parameters of NE2 are provided as follows.
Parameter Value
The values for the related parameters of NE4 are provided as follows.
Parameter Value
The values for the related parameters of NE5 are provided as follows.
Parameter Value
The values for the related parameters of NE6 are provided as follows.
Parameter Value
Step 5 See perform an LB test to test the Ethernet service configurations and test the E-Line services
on NE1.
l Perform the LB test by considering the MEP whose MP ID is 101 as the source MEP and
the MEP whose MP ID is 201 as the sink MEP.
l Perform the LB test by considering the MEP whose MP ID is 102 as the source MEP and
the MEP whose MP ID is 401 as the sink MEP.
l Perform the LB test by considering the MEP whose MP ID is 103 as the source MEP and
the MEP whose MP ID is 402 as the sink MEP.
l Perform the LB test by considering the MEP whose MP ID is 104 as the source MEP and
the MEP whose MP ID is 501 as the sink MEP.
l Perform the LB test by considering the MEP whose MP ID is 105 as the source MEP and
the MEP whose MP ID is 601 as the sink MEP.
There should be no packets lost during the LB tests.
----End
FE
FE
FE
ERPS
FE
NE3
802.1d bridge BTS3
10 Mbit/s
The connections of Ethernet links shown in Figure 5-32 are described as follows.
Between NE1 and 7-EM4T-3 Main port of a LAG Configure these ports
the BSC into a load non-
7-EM4T-4 Slave port of a LAG sharing LAG,
therefore improving
link reliability.
Between NE1 and 4-IFU2-1 East port of an ERPS Configure this port to
NE2 ring node transmit Ethernet
services on Hybrid
radio.
Between NE2 and 4-IFU2-1 East port of an ERPS Configure this port to
NE3 ring node transmit Ethernet
services on Hybrid
radio.
Between NE4 and 4-IFU2-1 East port of an ERPS Configure this port to
NE1 ring node transmit Ethernet
services on Hybrid
radio.
Ethernet Port
Table 5-110 to Table 5-113 provide the information about each Ethernet port involved in the
service.
Broadcast Packet - -
Suppression Threshold
Broadcast Packet - -
Suppression Threshold
NOTE
l In this example, the FE/GE port on the BTS/BSC works in the auto-negotiation mode. Hence, 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.
l Generally, the flow control function is enabled only when the NE or the peer equipment is inadequate for
QoS processing. The flow control planning on the NE must match the flowing control planning on the peer
equipment.
l In this example, the broadcast packet suppression functions need not be enabled.
LAG
To improve the reliability of service transmission, NE1 and the BSC are interconnected through
the LAG formed by two GE links. Table 5-118 provides the planning information.
Parameter NE1
NOTE
In this example, the bandwidth of the Ethernet service to be transmitted is 40 Mbit/s, much smaller than the
bandwidth of a GE port. Therefore, you need not configure the link aggregation group to the load sharing mode
to increase the bandwidth.
ERPS Instance
Table 5-119 provides the information about ERPS.
ERPS ID 1 1 1 1
RPLOwner No No Yes No
Ring Node Flag
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 NE1. Hence, the NE that is farthest from NE1 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. Considering that the inband DCN
uses VLAN 4094, 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 use the default
values.
Service ID 1 1 1 1
NOTE
In this example, ERPS is adopted to prevent network loop. Therefore, the split horizon group cannot be used.
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 5-121. Each Ethernet port involved in the service uses the same DS
configuration.
CS7 7 -
CS6 6 -
AF4 4 -
AF1 1 -
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.
Table 5-122 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.10.2.1 Creating a LAG and create the LAG on NE1.
The values for the related parameters that need to be set in the main interface are provided as
follows.
The values for the related parameters that need to be set in Port Settings are provided as follows.
Step 2 See A.10.1.1 Creating Ethernet Ring Protection Instances and create the ERPS instance.
The values for the related parameters are provided as follows.
ERPS ID 1 1 1 1
RPLOwner No No Yes No
Ring Node Flag
----End
Procedure
Step 1 See A.10.3.4 Configuring the E-LAN Service and configure the E-LAN services.
l Parameters of NE1
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 are provided
as follows.
Port
7-EM4T-3
3-IFU2-1
4-IFU2-1
l Parameters of NE2
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
Self-Learning Enabled
MAC Address
The values for the related parameters that need to be set in the Get UNI Port are provided
as follows.
Port
7-EM4T-1
7-EM4T-2
3-IFU2-1
4-IFU2-1
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 are provided
as follows.
Port
7-EM4T-1
3-IFU2-1
4-IFU2-1
----End
Procedure
Step 1 See A.10.6.1 Setting the General Attributes of Ethernet Ports and set the basic attributes of
Ethernet ports.
l The values for the related parameters of NE1 are provided as follows.
Parameter Value Range
7-EM4T-3 7-EM4T-4
l The values for the related parameters of NE2 are provided as follows.
Parameter Value Range
7-EM4T-1 7-EM4T-2
l The values for the related parameters of NE3 and NE4 are provided as follows.
Parameter Value Range
7-EM4T-1
----End
Procedure
Step 1 See A.10.10.1 Creating a DS Domain and create a DS domain.
The values for the related parameters that need to be set in the main interface are provided as
follows.
Mapping Relation ID 2
The values for the related parameters that need to be set in the Ingress Mapping Relation tab
page are provided as follows.
0 BE
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.
BE 0
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.
The values for the related parameters that need to be set in the Apply Port tab page are provided
as follows.
Step 2 See A.10.10.4 Creating a Port Policy and create the port policy.
The values for the related parameters of each NE are provided as follows.
Policy ID 1
Step 3 See A.10.10.7 Setting the Port That Uses the Port Policy and set the port that uses the port
policy.
l The values for the related parameters of NE1 are provided as follows.
Parameter Value Range
Port 7-EM4T-3
3-IFU2-1
4-IFU2-1
l The values for the related parameters of NE2 are provided as follows.
Parameter Value Range
Port 7-EM4T-1
7-EM4T-2
3-IFU2-1
4-IFU2-1
l The values for the related parameters of NE3 and NE4 are provided as follows.
Parameter Value Range
Port 7-EM4T-1
3-IFU2-1
4-IFU2-1
----End
Procedure
Step 1 See A.10.11.1 Creating an MD and create the MDs.
The values for the related parameters are provided as follows.
Maintenance 4 4 4 4
Domain Level
CC Test 1s 1s 1s 1s
Transmit
Period
Step 3 See A.10.11.3 Creating an MEP Point and create the MEP points.
VLAN - - - - -
Step 4 See A.10.11.4 Creating Remote MEPs in an MA and create the remote MEP points for NE1
to NE4.
The values for the related parameters of NE1 are provided as follows.
Parameter Value
The values for the related parameters of NE2 are provided as follows.
Parameter Value
The values for the related parameters of NE3 are provided as follows.
Parameter Value
The values for the related parameters of NE4 are provided as follows.
Parameter Value
Step 5 See perform an LB test to test the Ethernet service configurations and test the E-LAN
services.
l Perform the LB test by considering the MEP whose MP ID is 101 as the source MEP and
the MEP whose MP ID is 201 as the sink MEP.
l Perform the LB test by considering the MEP whose MP ID is 101 as the source MEP and
the MEP whose MP ID is 202 as the sink MEP.
l Perform the LB test by considering the MEP whose MP ID is 101 as the source MEP and
the MEP whose MP ID is 301 as the sink MEP.
l Perform the LB test by considering the MEP whose MP ID is 101 as the source MEP and
the MEP whose MP ID is 401 as the sink MEP.
There should be no packets lost during the LB tests.
----End
Based on 3.5 Configuration Example (Radio Links on the Hybrid Radio Chain Network),
configure Ethernet services according to the following requirements:
To meet the preceding requirements, IEEE 802.1q bridge-based E-LAN services are configured
for service transmission on each NE; in addition, corresponding LAG protection and QoS
processing are configured.
FE
Domain 1
VLAN 110-119
FE NE4
BTS3
20 Mbit/s GE GE
VLAN 110-119
FE
NE3 NE2 NE1 BSC
120 Mbit/s
Domain 2 VLAN 110-129
BTS1
VLAN 120-129 45 Mbti/s
VLAN 110-119
FE
FE
NE6 NE5
BTS4
BTS5 25 Mbit/s
15 Mbit/s VLAN 120-129
VLAN 120-129
The connections of Ethernet links shown in Figure 5-33 are described as follows.
Between NE1 and 7-EM4F-3 Main port of a LAG Configure these ports
the BSC into a load non-
7-EM4F-4 Slave port of a LAG sharing LAG,
therefore improving
link reliability.
Broadcast packet - -
suppression threshold
Broadcast packet - -
suppression threshold
Broadcast packet - -
suppression threshold
NOTE
l In this example, the FE/GE port on the BTS/BSC works in auto-negotiation mode. Therefore, the FE/GE
port on each NE that transmits/receives services must work in auto-negotiation mode. For example, if the
peer Ethernet port changes to another working mode, the local Ethernet port also needs to change to the
same working mode accordingly. Plan the Ethernet ports within a network to work in auto-negotiation mode.
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 In this example, all the services carry VLAN tags. Therefore, the TAG attributes of all the ports are Tag
Aware.
l Generally, the flow control function is enabled only when the NE or the peer equipment is inadequate for
QoS processing. The flow control planning on the NE must match the flow control planning on the peer
equipment.
l In this example, no broadcast packet suppression function is enabled.
Parameter 3-IFU2-1
Parameter 3-IFU2-1
Parameter 3-IFU2-1
To improve the reliability of service transmission, NE1 and the BSC are interconnected through
the LAG formed by two GE links. Table 5-141 provides the planning information.
Parameter NE1
NOTE
In this example, the bandwidth of the Ethernet service to be transmitted is 120 Mbit/s, much smaller than the
bandwidth of a GE port. Therefore, you need not configure the link aggregation group to the load sharing mode
to increase the bandwidth.
Service ID 1 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 5-143. Each Ethernet port involved in the service uses the same DS
configuration.
CS7 7 -
CS6 6 -
AF4 4 -
AF1 1 -
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.
CS7 SP
CS6 SP
EF SP
BE SP
In this example, the CAR processing needs to be performed on the DS edge node in the uplink
direction (from the BTS to the BSC) of the non-real-time R99 service on each BTS (that is, the
service with VLAN priority 2). Table 5-145 lists the CAR parameters.
Parameter Value
NOTE
The CBS/PBS is in direct proportion to the CIR/PIR. That is, the larger the value of the CBS/PBS, the more the
burst packets are permitted. In this example, the values of the CBS and the PBS are set according to the bytes
that are transmitted at CIR and PIR during a 100 ms period.
Procedure
Step 1 See A.10.2.1 Creating a LAG and create the LAG for NE1.
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 Settings tab page are
provided as follows.
Parameter Value
----End
Procedure
Step 1 See A.10.3.4 Configuring the E-LAN Service and configure the E-LAN services.
l Parameters of NE1
The values for the relevant parameters that need to be set in the main interface are provided
as follows.
Parameter Value
Service ID 1
The values for the relevant parameters that need to be set in the Get UNI Port tab page are
provided as follows.
7-EM4F-3 110-129
3-IFU2-1 110-129
l Parameters of NE2
The values for the relevant 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 relevant parameters that need to be set in the Get UNI Port tab page are
provided as follows.
7-EM4T-3 110-129
7-EM4T-1 110-119
3-IFU2-1 110-129
l Parameters of NE3
The values for the relevant 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 relevant parameters that need to be set in the Get UNI Port tab page are
provided as follows.
7-EM4T-3 110-129
3-IFU2-1 110-119
4-IFU2-1 120-129
l Parameters of NE4
The values for the relevant 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 relevant parameters that need to be set in the Get UNI Port tab page are
provided as follows.
Port VLAN (e.g.1,3-5)
7-EM4T-1 110-119
7-EM4T-2 110-119
3-IFU2-1 110-119
l Parameters of NE5
The values for the relevant 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 relevant parameters that need to be set in the Get UNI Port tab page are
provided as follows.
7-EM4T-1 120-129
3-IFU2-1 120-129
4-IFU2-1 120-129
l Parameters of NE6
The values for the relevant parameters that need to be set in the main interface are provided
as follows.
Parameter Value
Service ID 1
Parameter Value
The values for the relevant parameters that need to be set in the Get UNI Port tab page are
provided as follows.
Port VLAN (e.g.1,3-5)
7-EM4T-1 120-129
3-IFU2-1 120-129
----End
Procedure
Step 1 See A.10.6.1 Setting the General Attributes of Ethernet Ports and set the general attributes
of Ethernet ports.
l The values for the related parameters of NE1 are provided as follows.
Parameter Value
7-EM4F-3 7-EM4F-4
l The values for the related parameters of NE2 are provided as follows.
Parameter Value
7-EM4T-1 7-EM4T-3
l The values for the related parameters of NE3 are provided as follows.
Parameter Value
7-EM4T-3
l The values for the related parameters of NE4 are provided as follows.
Parameter Value
7-EM4T-1 7-EM4T-2
l The values for the related parameters of NE5 are provided as follows.
Parameter Value
7-EM4T-1
l The values for the related parameters of NE6 are provided as follows.
Parameter Value
7-EM4T-1
----End
Procedure
Step 1 See A.10.10.1 Creating a DS Domain and create a 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 2
The values for the related parameters that need to be set in the Ingress Mapping Relation tab
page are provided as follows.
0 BE
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.
BE 0
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.
The values for the related parameters that need to be set in the Application Port tab page are
provided as follows.
Paramete Value
r
NE1 NE2 NE3 NE4 NE5 NE6
NOTE
The mapping relation defined in the default DS domain is the same as the mapping relation defined in the DS
domain that is created in this step. Therefore, you can skip this step.
Step 2 See A.10.10.4 Creating a Port Policy and create the port policy.
l The values for the related parameters of NE2, NE4, NE5, and NE6 are provided as follows.
Parameter Value
Policy ID 1 2
Grooming Police After SP (CS7, CS6, and EF) SP (CS7, CS6, and EF)
Reloading WRR (AF4 to AF1) WRR (AF4 to AF1)
SP (BE) SP (BE)
Bandwidth Limit Disabled (for all PHB Disabled (for all PHB
service classes) service classes)
l The values for the related parameters of NE1 and NE3 are provided as follows.
Parameter Value
Policy ID 1
Step 3 See A.10.10.6 Creating the Traffic and create the traffic on NE2, NE4, NE5, and NE6.
The values for the related parameters that need to be set in the main interface are provided as
follows.
Parameter Value
Traffic Classification ID 1
The values for the related parameters that need to be set in the INGRESS tab page are provided
as follows.
Parameter Value
Match Value 2
Wildcard 0
CoS -
CIR(kbit/s) 4096
PIR(kbit/s) 8192
CBS(byte) 51200
PBS(byte) 102400
The values for the related parameters that need to be set in the EGRESS tab page are provided
as follows.
Parameter Value
Step 4 See A.10.10.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 NE1 are provided as follows.
Parameter Value
Port 3-IFU2-1
7-EM4F-3
l The values for the related parameters of NE2 are provided as follows.
Parameter Value
l The values for the related parameters of NE3 are provided as follows.
Parameter Value
Port 3-IFU2-1
4-IFU2-1
7-EM4T-3
l The values for the related parameters of NE4 are provided as follows.
Parameter Value
l The values for the related parameters of NE5 are provided as follows.
Parameter Value
l The values for the related parameters of NE6 are provided as follows.
Parameter Value
----End
Procedure
Step 1 See A.10.11.1 Creating an MD and create the MDs for NE1, NE2, NE4, NE5, and NE6.
Parameter Value
Maintenanc 4 4 4 4 4
e Domain
Level
Step 2 See A.10.11.2 Creating an MA and create the maintenance associations (MAs) for NE1, NE2,
NE4, NE5, and NE6.
l The values for the relevant parameters of NE1 are provided as follows.
Parameter Value
CC Test 1s 1s 1s 1s 1s
Transmit
Period
l The values for the relevant parameters of NE2 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE4 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE5 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE6 are provided as follows.
Parameter Value
Step 3 See A.10.11.3 Creating an MEP Point and create the MEP for NE1, NE2, NE4, NE5, and NE6.
l The values for the relevant parameters of NE1 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE2 are provided as follows.
Parameter Value
Board 7-EM4T
Port 7-EM4T-1
VLAN 110
MP ID 201
Direction Ingress
CC Status Active
l The values for the relevant parameters of NE4 are provided as follows.
Parameter Value
Parameter Value
MP ID 401 402
l The values for the relevant parameters of NE5 are provided as follows.
Parameter Value
Board 7-EM4T
Port 7-EM4T-1
VLAN 120
MP ID 501
Direction Ingress
CC Status Active
l The values for the relevant parameters of NE6 are provided as follows.
Parameter Value
Board 7-EM4T
Port 7-EM4T-1
VLAN 120
MP ID 601
Direction Ingress
CC Status Active
Step 4 See A.10.11.4 Creating Remote MEPs in an MA and create the remote MEP points for NE1,
NE2, NE4, NE5, and NE6.
The values for the relevant parameters of NE1 are provided as follows.
Parameter Value
The values for the relevant parameters of NE2 are provided as follows.
Parameter Value
The values for the relevant parameters of NE4 are provided as follows.
Parameter Value
The values for the relevant parameters of NE5 are provided as follows.
Parameter Value
The values for the relevant parameters of NE6 are provided as follows.
Parameter Value
Step 5 See perform an LB test to test the Ethernet service configurations and test the E-LAN
services on NE1.
l Perform the LB test by considering the MEP whose MP ID is 101 as the source MEP and
the MEP whose MP ID is 201 as the sink MEP.
l Perform the LB test by considering the MEP whose MP ID is 102 as the source MEP and
the MEP whose MP ID is 401 as the sink MEP.
l Perform the LB test by considering the MEP whose MP ID is 103 as the source MEP and
the MEP whose MP ID is 402 as the sink MEP.
l Perform the LB test by considering the MEP whose MP ID is 104 as the source MEP and
the MEP whose MP ID is 501 as the sink MEP.
l Perform the LB test by considering the MEP whose MP ID is 105 as the source MEP and
the MEP whose MP ID is 601 as the sink MEP.
There should be no packets lost during the LB tests.
----End
Based on 3.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.1ad bridge-based E-LAN services are configured
to implement transmission of the BTS services; in addition, ERPS is configured to protect
services on the ring network. See Figure 5-34.
BTS4
FE 10 Mbit/s
S-VLAN 130
FE
FE
ERPS
NE2 NE4
802.1ad bridge
802.1ad bridge
FE
NE3
802.1ad bridge BTS3
10 Mbit/s
S-VLAN 120
The connections of Ethernet links shown in Figure 5-34 are described as follows.
Between NE1 and 7-EM4T-3 Main port of a LAG Configure these ports
the BSC into a load non-
7-EM4T-4 Slave port of a LAG sharing LAG,
therefore improving
link reliability.
Between NE1 and 4-IFU2-1 East port of an ERPS Configure this port to
NE2 ring node transmit Ethernet
services on Hybrid
radio.
Between NE2 and 4-IFU2-1 East port of an ERPS Configure this port to
NE3 ring node transmit Ethernet
services on Hybrid
radio.
Between NE4 and 4-IFU2-1 East port of an ERPS Configure this port to
NE1 ring node transmit Ethernet
services on Hybrid
radio.
Ethernet Port
Table 5-150 to Table 5-153 provide the information about each Ethernet port involved in the
service.
Broadcast Packet - -
Suppression Threshold
Broadcast Packet - -
Suppression Threshold
Parameter 7-EM4T-1
NOTE
l If the Ethernet services on each BTS do not contain any untagged frames, you can set Encapsulation
Type to 802.1Q and set Tag to Tag Aware for the FE port that accesses the Ethernet services on each BTS.
l In this example, the FE/GE port on the BTS/BSC works in the auto-negotiation mode. Hence, 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.
l Generally, the flow control function is enabled only when the NE or the peer equipment is inadequate for
QoS processing. The flow control planning on the NE must match the flowing control planning on the peer
equipment.
l In this example, the broadcast packet suppression functions need not be enabled.
l In this example, the S-VLAN T-PID that the BSC can identify is 0x8100. Hence, you need to set QinQ
Type Domain to 0x8100 for the two GE ports connecting to the BSC.
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.
LAG
To improve the reliability of service transmission, NE1 and the BSC are interconnected through
the LAG formed by two GE links. Table 5-158 provides the planning information.
NOTE
In this example, the bandwidth of the Ethernet service to be transmitted is 40 Mbit/s, much smaller than the
bandwidth of a GE port. Therefore, you need not configure the link aggregation group to the load sharing mode
to increase the bandwidth.
ERPS Instance
Table 5-159 provides the information about ERPS.
ERPS ID 1 1 1 1
RPLOwner No No Yes No
Ring Node Flag
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 NE1. Hence, the NE that is farthest from NE1 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. Considering that the inband DCN
uses VLAN 4094, 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 use the default
values.
Service ID 1 1 1 1
Mounted NNI 3-IFU2-1 (S- 3-IFU2-1 (S- 3-IFU2-1 (S- 3-IFU2-1 (S-
Port VLAN ID: VLAN ID: VLAN ID: VLAN ID:
100,110,120,13 100,110,120,13 100,110,120,13 100,110,120,13
0) 0) 0) 0)
4-IFU2-1 (S- 4-IFU2-1 (S- 4-IFU2-1 (S- 4-IFU2-1 (S-
VLAN ID: VLAN ID: VLAN ID: VLAN ID:
100,110,120,13 100,110,120,13 100,110,120,13 100,110,120,13
0) 0) 0) 0)
7-EM4T-3 (S-
VLAN ID:
100,110,120,13
0)
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 5-161. Each Ethernet port involved in the service uses the same DS
configuration.
CS7 7 -
CS6 6 -
AF4 4 -
AF1 1 -
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.
Table 5-162 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
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 5-163. Each Ethernet port involved in the service uses the same DS
configuration.
CS7 7 -
CS6 6 -
AF4 4 -
AF1 1 -
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.
Procedure
Step 1 See A.10.2.1 Creating a LAG and create the LAG on NE1.
The values for the related parameters that need to be set in the main interface are provided as
follows.
The values for the related parameters that need to be set in Port Settings are provided as follows.
Step 2 See A.10.1.1 Creating Ethernet Ring Protection Instances and create the ERPS instance.
ERPS ID 1 1 1 1
RPLOwner No No Yes No
Ring Node Flag
----End
Procedure
Step 1 See A.10.3.4 Configuring the E-LAN Service and configure the E-LAN services.
l Parameters of NE1
The values for the relevant 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 relevant parameters that need to be set in the Get NNI Port are provided
as follows.
Port Port Type C-VLAN S-VLAN
l Parameters of NE2
The values for the relevant 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 relevant parameters that need to be set in the Get UNI Port are provided
as follows.
The values for the relevant parameters that need to be set in the Get NNI Port are provided
as follows.
Port Port Type C-VLAN S-VLAN
l Parameters of NE3
The values for the relevant 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 relevant parameters that need to be set in the Get UNI Port are provided
as follows.
Port Port Type C-VLAN S-VLAN
The values for the relevant parameters that need to be set in the Get NNI Port are provided
as follows.
Port Port Type C-VLAN S-VLAN
l Parameters of NE4
The values for the relevant 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 relevant parameters that need to be set in the Get UNI Port are provided
as follows.
Port Port Type C-VLAN S-VLAN
The values for the relevant parameters that need to be set in the Get NNI Port are provided
as follows.
----End
Procedure
Step 1 See A.10.6.1 Setting the General Attributes of Ethernet Ports and set the basic attributes of
Ethernet ports.
l The values for the related parameters of NE1 are provided as follows.
Parameter Value
7-EM4T-3 7-EM4T-4
l The values for the related parameters of NE2 are provided as follows.
Parameter Value
7-EM4T-1 7-EM4T-2
l The values for the related parameters of NE3 and NE4 are provided as follows.
Parameter Value
7-EM4T-1
Step 2 See A.10.6.3 Setting the Layer 2 Attributes of Ethernet Ports and set the Layer 2 attributes
of Ethernet ports for NE1.
Parameter Value
7-EM4T-3 7-EM4T-4
----End
Procedure
Step 1 See A.10.10.1 Creating a DS Domain and create a 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 2
The values for the related parameters that need to be set in the Ingress Mapping Relation tab
page are provided as follows.
0 0 BE
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.
BE 0 0
AF11 1 1
AF21 2 2
AF31 3 3
AF41 4 4
EF 5 5
CS6 6 6
CS7 7 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.
The values for the related parameters that need to be set in the Application Port tab page are
provided as follows.
Parameter Value
Step 2 See A.10.10.3 Changing the Ports That Use the DS Domain and change the ports that use the
DS domain.
l The values for the related parameters of NE1 are provided as follows.
3-IFU2-1 SVLAN
4-IFU2-1 SVLAN
7-EM4T-3 SVLAN
l The values for the related parameters of NE2 are provided as follows.
7-EM4T-1 CVLAN
7-EM4T-2 CVLAN
3-IFU2-1 SVLAN
4-IFU2-1 SVLAN
l The values for the related parameters of NE3 and NE4 are provided as follows.
Selected Port Packet Type
7-EM4T-1 CVLAN
3-IFU2-1 SVLAN
4-IFU2-1 SVLAN
Step 3 See A.10.10.4 Creating a Port Policy and create the port policy.
l Parameters of NE1
The values for the related parameters of NE1 are provided as follows.
Parameter Value
Policy ID 1
Policy ID 1 2
Grooming Police After SP (CS7, CS6, and EF) SP (CS7, CS6, and EF)
Reloading WRR (AF4 to AF1) WRR (AF4 to AF1)
SP (BE) SP (BE)
Parameter Value
Bandwidth Limit Disabled (for all PHB Disabled (for all PHB
service classes) service classes)
Step 4 See A.10.10.6 Creating the Traffic and create the traffic for NE2, NE3, and NE4.
The values for the related parameters that need to be set in the main interface are provided as
follows.
Parameter Value
Traffic Classification ID 1
The values for the related parameters that need to be set in the INGRESS tab page are provided
as follows.
Parameter Value
Match Value 2
Wildcard 0
CoS -
CIR(kbit/s) 4096
PIR(kbit/s) 8192
CBS(byte) 51200
PBS(byte) 102400
Parameter Value
The values for the related parameters that need to be set in the EGRESS tab page are provided
as follows.
Parameter Value
Step 5 See A.10.10.7 Setting the Port That Uses the Port Policy and set the port that uses the port
policy.
l The values for the related parameters of NE1 are provided as follows.
Parameter Value
Port 3-IFU2-1
4-IFU2-1
7-EM4F-3
l The values for the related parameters of NE2 are provided as follows.
Parameter Value
l The values for the related parameters of NE3 and NE4 are provided as follows.
Parameter Value
----End
Procedure
Step 1 See A.10.11.1 Creating an MD and create the MDs.
Maintenance 4 4 4 4
Domain Level
Parameter Value
CC Test 1s 1s 1s 1s
Transmit
Period
Step 3 See A.10.11.3 Creating an MEP Point and create the MEP points.
l The values for the relevant parameters of NE1 are provided as follows,
Parameter Value
Parameter Value
l The values for the relevant parameters of NE2 are provided as follows.
Parameter Value
VLAN - -
MP ID 201 202
l The values for the relevant parameters of NE3 are provided as follows.
Parameter Value
Board 7-EM4T
Port 7-EM4T-1
VLAN -
MP ID 301
Direction Ingress
Parameter Value
CC Status Active
l The values for the relevant parameters of NE4 are provided as follows.
Parameter Value
Board 7-EM4T
Port 7-EM4T-1
VLAN -
MP ID 401
Direction Ingress
CC Status Active
Step 4 See A.10.11.4 Creating Remote MEPs in an MA and create the remote MEP points for NE1
to NE4.
The values for the related parameters of NE1 are provided as follows.
Parameter Value
The values for the related parameters of NE2 are provided as follows.
Parameter Value
Parameter Value
The values for the related parameters of NE3 are provided as follows.
Parameter Value
The values for the related parameters of NE4 are provided as follows.
Parameter Value
Step 5 See perform an LB test to test the Ethernet service configurations and test the E-LAN
services.
l Perform the LB test by considering the MEP whose MP ID is 101 as the source MEP and
the MEP whose MP ID is 201 as the sink MEP.
l Perform the LB test by considering the MEP whose MP ID is 102 as the source MEP and
the MEP whose MP ID is 202 as the sink MEP.
l Perform the LB test by considering the MEP whose MP ID is 103 as the source MEP and
the MEP whose MP ID is 301 as the sink MEP.
l Perform the LB test by considering the MEP whose MP ID is 104 as the source MEP and
the MEP whose MP ID is 401 as the sink MEP.
There should be no packets lost during the LB tests.
----End
FE
GE GE
BTS3 FE
NE4
20 Mbit/s FE
NE3 NE2 NE1 BSC
120 Mbit/s
FE BTS1
FE 45 Mbit/s
NE6 NE5
BTS4
BTS5 25 Mbit/s
15 Mbit/s
Point-to-point transparently
transmitted E-Line service
The connections of Ethernet links shown in Figure 5-35 are described as follows.
Between NE1 and 7-EM4F-3 Main port of a LAG Configure these ports
the BSC into a load non-
7-EM4F-4 Slave port of a LAG sharing LAG,
therefore improving
link reliability.
Broadcast packet - -
suppression threshold
Broadcast packet - -
suppression threshold
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 port on the BTS/BSC works in auto-negotiation mode. Therefore, the FE/GE
port on each NE that transmits/receives services must work in auto-negotiation mode. For example, if the
peer Ethernet port changes to another working mode, the local Ethernet port also needs to change to the
same working mode accordingly. Plan the Ethernet ports within a network to work in auto-negotiation mode.
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 NE or the peer equipment is inadequate for
QoS processing. The flow control planning on the NE must match the flow control planning on the peer
equipment.
l In this example, no broadcast packet suppression function is enabled.
NOTE
In this example, the bandwidth of the Ethernet service to be transmitted is 120 Mbit/s, much smaller than the
bandwidth of a GE port. Therefore, you need not configure the link aggregation group to the load sharing mode
to increase the bandwidth.
Table 5-183 Information about point-to-point transparently transmitted E-Line services (NE1)
Parameter NE1
Service ID 1
Table 5-184 Information about point-to-point transparently transmitted E-Line services (NE6)
Parameter NE6
Service ID 1
Service ID 1
Table 5-186 Information about IEEE 802.1d bridge-based E-LAN services (NE3)
Parameter NE3
Service ID 1
Table 5-187 Information about IEEE 802.1d bridge-based E-LAN services (NE4)
Parameter NE4
Service ID 1
Parameter NE4
Table 5-188 Information about IEEE 802.1d bridge-based E-LAN services (NE5)
Parameter NE5
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 5-189. Each Ethernet port involved in the service uses the same DS
configuration.
CS7 56 -
CS6 48 -
AF4 32 -
AF1 8 -
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.
Table 5-190 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
In this example, traffic shaping also needs to be performed on the DS edge node in the uplink
direction (from the BTS to the BSC) of the OM and HSDPA real-time services on each BTS
(that is, the service with the DSCP value being 24). Table 5-192 lists the shaping parameters.
NOTE
The CBS/PBS is proportional to the CIR/PIR. That is, the larger the value of the CBS/PBS, the more the burst
packets are permitted. In this example, the values of the CBS and the PBS are set according to the bytes that are
transmitted at CIR and PIR during a 100 ms period.
Procedure
Step 1 See A.10.2.1 Creating a LAG and create the LAG for NE1.
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 Settings tab page are
provided as follows.
Parameter Value
----End
Procedure
Step 1 See A.10.3.2 Configuring the E-Line Service and configure the E-Line services on NE1 and
NE6.
l The values for the relevant parameters of NE1 are provided as follows.
Parameter Value
Service ID 1
Direction UNI-UNI
Source 3-IFU2-1
Sink 7-EM4F-3
l The values for the relevant parameters of NE6 are provided as follows.
Parameter Value
Service ID 1
Direction UNI-UNI
Source 7-EM4T-1
Sink 3-IFU2-1
Step 2 See A.10.3.4 Configuring the E-LAN Service and configure the E-LAN services on NE2 to
NE5.
The values for the relevant parameters of NE2 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 relevant parameters that need to be set in the Get UNI Port tab page are
provided as follows.
Port
7-EM4T-3
7-EM4T-1
3-IFU2-1
The values for the relevant parameters that need to be set in the Split Horizon Group tab page
are provided as follows.
1 7-EM4T-3, 7-EM4T-1
The values for the relevant parameters of NE3 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 relevant parameters that need to be set in the Get UNI Port tab page are
provided as follows.
Port
7-EM4T-3
3-IFU2-1
4-IFU2-1
The values for the relevant parameters that need to be set in the Split Horizon Group tab page
are provided as follows.
1 3-IFU2-1, 4-IFU2-1
The values for the relevant parameters of NE4 that need to be set in the main interface are
provided as follows.
Parameter Value
Service ID 1
Parameter Value
Self-Learning Enabled
MAC Address
The values for the relevant parameters that need to be set in the Get UNI Port tab page are
provided as follows.
Port
7-EM4T-1
7-EM4T-2
3-IFU2-1
The values for the relevant parameters that need to be set in the Split Horizon Group tab page
are provided as follows.
1 7-EM4T-1, 7-EM4T-2
The values for the relevant parameters of NE5 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 relevant parameters that need to be set in the Get UNI Port tab page are
provided as follows.
Port
7-EM4T-1
3-IFU2-1
4-IFU2-1
The values for the relevant parameters that need to be set in the Split Horizon Group tab page
are provided as follows.
1 3-IFU2-1, 7-EM4T-1
----End
Procedure
Step 1 See A.10.6.1 Setting the General Attributes of Ethernet Ports and set the general attributes
of Ethernet ports.
l The values for the relevant parameters of NE1 are provided as follows.
Parameter Value
7-EM4F-3 7-EM4F-4
l The values for the relevant parameters of NE2 are provided as follows.
Parameter Value
7-EM4T-1 7-EM4T-3
l The values for the relevant parameters of NE3 are provided as follows.
Parameter Value
7-EM4T-3
l The values for the relevant parameters of NE4 are provided as follows.
Parameter Value
7-EM4T-1 7-EM4T-2
l The values for the relevant parameters of NE5 are provided as follows.
Parameter Value
7-EM4T-1
l The values for the relevant parameters of NE6 are provided as follows.
Parameter Value
7-EM4T-1
----End
Procedure
Step 1 See A.10.10.1 Creating a DS Domain and create a DS domain.
The values for the relevant parameters that need to be set in the main interface are provided as
follows.
Parameter Value
Mapping Relation ID 2
The values for the relevant parameters that need to be set in the Ingress Mapping Relation tab
page are provided as follows.
0 BE
8 AF11
16 AF21
24 AF31
32 AF41
40 EF
48 CS6
56 CS7
The values for the relevant parameters that need to be set in the Egress Mapping Relation tab
page are provided as follows.
BE 0
AF11 8
AF21 16
AF31 24
AF41 32
EF 40
CS6 48
CS7 56
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.
The values for the relevant parameters that need to be set in the Apply Port tab page are provided
as follows.
Paramete Value
r
NE1 NE2 NE3 NE4 NE5 NE6
Step 2 See A.10.10.4 Creating a Port Policy and create the port policy.
l The values for the relevant parameters of NE1 and NE3 are provided as follows.
Parameter Value
Policy ID 1
l The values for the relevant parameters of NE2 and NE5 are provided as follows.
Parameter Value
Policy ID 1 2 3
Grooming Police SP (CS7, CS6, and SP (CS7, CS6, and SP (CS7, CS6, and
After Reloading EF) EF) EF)
WRR (AF4 to AF1) WRR (AF4 to AF1) WRR (AF4 to AF1)
SP (BE) SP (BE) SP (BE)
Parameter Value
Bandwidth Limit Disabled (for all Disabled (for all Disabled (for all
PHB service PHB service PHB service
classes) classes) classes)
l The values for the relevant parameters of NE4 and NE6 are provided as follows.
Parameter Value
Policy ID 1 2
Grooming Police After SP (CS7, CS6, and EF) SP (CS7, CS6, and EF)
Reloading WRR (AF4 to AF1) WRR (AF4 to AF1)
SP (BE) SP (BE)
Bandwidth Limit Disabled (for all PHB Disabled (for all PHB
service classes) service classes)
Step 3 See A.10.10.6 Creating the Traffic and create the traffic on NE2, NE4, NE5, and NE6.
l Parameters of NE2
The values for the relevant parameters that need to be set in the main interface are provided
as follows.
Parameter Value
Traffic Classification ID 1 1
The values for the relevant parameters that need to be set in the INGRESS tab page are
provided as follows.
Parameter Value
Match Value 16 24
Wildcard 0 0
CoS - -
CIR(kbit/s) 4096 -
PIR(kbit/s) 8192 -
CBS(byte) 51200 -
PBS(byte) 102400 -
The values for the relevant parameters that need to be set in the EGRESS tab page are
provided as follows.
Parameter Value
CIR(kbit/s) - 2048
PIR(kbit/s) - 4096
CBS(byte) - 25600
PBS(byte) - 51200
l Parameters of NE4
The values for the relevant parameters that need to be set in the main interface are provided
as follows.
Parameter Value
Traffic 1 1 2
Classification ID
The values for the relevant parameters that need to be set in the INGRESS tab page are
provided as follows.
Parameter Value
Match Value 16 24 24
Wildcard 0 0 0
CoS - - -
CIR(kbit/s) 4096 - -
PIR(kbit/s) 8192 - -
CBS(byte) 51200 - -
PBS(byte) 102400 - -
The values for the relevant parameters that need to be set in the EGRESS tab page are
provided as follows.
Parameter Value
l Parameters of NE5
The values for the relevant parameters that need to be set in the main interface are provided
as follows.
Parameter Value
Traffic Classification ID 1 1
The values for the relevant parameters that need to be set in the INGRESS tab page are
provided as follows.
Parameter Value
Match Value 16 24
Wildcard 0 0
CoS - -
CIR(kbit/s) 4096 -
PIR(kbit/s) 8192 -
CBS(byte) 51200 -
Parameter Value
PBS(byte) 102400 -
The values for the relevant parameters that need to be set in the EGRESS tab page are
provided as follows.
Parameter Value
CIR(kbit/s) - 2048
PIR(kbit/s) - 4096
CBS(byte) - 25600
PBS(byte) - 51200
l Parameters of NE6
The values for the relevant parameters that need to be set in the main interface are provided
as follows.
Parameter Value
Traffic Classification ID 1 1
The values for the relevant parameters that need to be set in the INGRESS tab page are
provided as follows.
Parameter Value
Match Value 16 24
Wildcard 0 0
CoS - -
CIR(kbit/s) 4096 -
PIR(kbit/s) 8192 -
CBS(byte) 51200 -
PBS(byte) 102400 -
The values for the relevant parameters that need to be set in the EGRESS tab page are
provided as follows.
Parameter Value
CIR(kbit/s) - 2048
PIR(kbit/s) - 4096
CBS(byte) - 25600
PBS(byte) - 51200
Step 4 See A.10.10.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 NE1 are provided as follows.
Parameter Value
Port 3-IFU2-1
7-EM4F-3
l The values for the related parameters of NE2 are provided as follows.
Parameter Value
l The values for the related parameters of NE3 are provided as follows.
Parameter Value
Port 3-IFU2-1
4-IFU2-1
7-EM4T-3
l The values for the related parameters of NE4 are provided as follows.
Parameter Value
l The values for the related parameters of NE5 are provided as follows.
Parameter Value
l The values for the related parameters of NE6 are provided as follows.
Parameter Value
----End
Procedure
Step 1 See A.10.11.1 Creating an MD and configure the MD for NE1, NE2, NE4, NE5, and NE6.
The values for the related parameters are provided as follows.
Parameter Value
Maintenanc 4 4 4 4 4
e Domain
Level
Step 2 See A.10.11.2 Creating an MA and configure the MDs for NE1, NE2, NE4, NE5, and NE6.
l The values for the relevant parameters of NE1 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE2 are provided as follows.
Parameter Value
Parameter Value
l The values for the relevant parameters of NE4 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE5 are provided as follows.
Parameter Value
l The values for the relevant parameters of NE6 are provided as follows.
Parameter Value
Step 3 See A.10.11.3 Creating an MEP Point and create the MAs for NE1, NE2, NE4, NE5, and NE6.
l The values for the relevant parameters of NE1 are provided as follows.
Parameter Value
Board 7-EM4F
Port 7-EM4F-3
VLAN -
Parameter Value
MP ID 101
Direction Ingress
CC Status Active
l The values for the relevant parameters of NE2 are provided as follows.
Parameter Value
Board 7-EM4T
Port 7-EM4T-1
VLAN -
MP ID 201
Direction Ingress
CC Status Active
l The values for the relevant parameters of NE4 are provided as follows.
Parameter Value
VLAN - -
MP ID 401 402
l The values for the relevant parameters of NE5 are provided as follows.
Parameter Value
Parameter Value
Board 7-EM4T
Port 7-EM4T-1
VLAN -
MP ID 501
Direction Ingress
CC Status Active
l The values for the relevant parameters of NE6 are provided as follows.
Parameter Value
Board 7-EM4T
Port 7-EM4T-1
VLAN -
MP ID 601
Direction Ingress
CC Status Active
Step 4 See A.10.11.4 Creating Remote MEPs in an MA and create the MEP for NE1, NE2, NE4,
NE5, and NE6.
The values for the relevant parameters of NE1 are provided as follows.
Parameter Value
The values for the relevant parameters of NE2 are provided as follows.
Parameter Value
The values for the relevant parameters of NE4 are provided as follows.
Parameter Value
The values for the relevant parameters of NE5 are provided as follows.
Parameter Value
The values for the relevant parameters of NE6 are provided as follows.
Parameter Value
Step 5 See perform an LB test to test the Ethernet service configurations and test the Ethernet
services on NE1.
l Perform the LB test by considering the MEP whose MP ID is 101 as the source MEP and
the MEP whose MP ID is 201 as the sink MEP.
l Perform the LB test by considering the MEP whose MP ID is 101 as the source MEP and
the MEP whose MP ID is 401 as the sink MEP.
l Perform the LB test by considering the MEP whose MP ID is 101 as the source MEP and
the MEP whose MP ID is 402 as the sink MEP.
l Perform the LB test by considering the MEP whose MP ID is 101 as the source MEP and
the MEP whose MP ID is 501 as the sink MEP.
l Perform the LB test by considering the MEP whose MP ID is 101 as the source MEP and
the MEP whose MP ID is 601 as the sink MEP.
There should be no packets lost during the LB tests.
----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.
As shown in Figure 6-1, the radio links between NE1 and NE2 adopt the 1+1 protection. NE2
needs to trace the clock on the radio links to keep synchronous 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.
Thus, if the 1+1 IF protection switching occurs on the radio links, the clock can be switched at
the same time.
1+1 protection
configuration
SSM Protection
The SSM protection uses the SSM protocol specified in ITU-T G.781 to realize the clock
protection. According to the SSM protocol, the SDH NE transmits the SSM protocol through
bits 5-8 of the S1 byte, realizes the automatic protection switching of clock sources, and prevents
the timing loop. The OptiX RTN 910 supports the SSM protection on the SDH optical
transmission lines and STM-1 radio links. After the SSM protection is enabled on an NE, the
automatic protection switching of clock sources conforms to the following rules:
l According to the clock source priority list, the NE selects the clock source of the best quality
as the synchronization source.
l If multiple clock sources have the best quality, the NE selects the one of the highest priority
as the synchronization source.
l By using the S1 byte, the NE broadcasts the information of the synchronization source
quality to the downstream NEs, and also notifies the upstream NE that the clock source
from the NE cannot be used for synchronization.
Figure 6-2 is an STM-1 radio ring where the SSM protection is enabled.
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 unusable.
3. NE3 detects that the clock sources from NE2 and NE4 have the same quality and selects
the clock source of a higher priority (the clock source from NE2) as the synchronization
source. In addition, NE3 transmits the information of the synchronization source quality to
NE4 and notifies NE2 that the clock source from NE3 is unusable.
4. NE4 detects that the clock sources from NE1 and NE3 have the same quality and selects
the clock source of a higher priority (the clock source from NE3) as the synchronization
source. In addition, NE4 transmits the information of the synchronization source quality to
NE1 and notifies NE3 that the clock source from NE4 is unusable.
5. According to the clock quality in west and east directions and the configured clock source
priorities, NE2, NE3, and NE4 determine that the synchronization source requires no
modifications. Thus, the clock source selection is finished.
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 the information
of the synchronization source quality to NE1 and NE3.
2. NE3 selects NE2 as the clock source and informs NE4 of the clock quality.
3. After detecting that the quality of the clock from NE1 is higher than the quality of the clock
from NE3, NE4 transmits the clock quality information to NE3 and informs NE1 that the
clock from NE4 is unavailable.
4. After detecting 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, transmits
the information of the synchronization source quality to NE2, and notifies NE4 that the
clock source from NE3 is unusable.
5. After detecting 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,
transmits the information of the synchronization source quality to NE1, and notifies NE3
that the clock source from NE2 is unusable.
6. According to the clock quality in west and east directions and the configured clock source
priorities, NE2, NE3, and NE4 determine that the synchronization source requires no
modifications. Thus, the clock source selection is finished.
NOTE
The SSM protection does not provide a complete solution to the timing loop. Thus, when you configure clock
sources, the clocks cannot form a loop as on NE1 in this example.
E W
W E
West/East/
West/East/
Internal
Internal
NE2 W NE4
E
W E
l According to the clock source priority list, the NE selects the clock source of the best quality
as the synchronization source.
l If the clock ID of a certain clock source indicates that the clock source is from the NE itself,
the clock source is not processed.
l If multiple clock sources have the best quality, the NE selects the one of the highest priority
as the synchronization source.
l By using the S1 byte, the NE broadcasts the information of the synchronization source
quality to the downstream NEs, and also notifies the upstream NE that the clock source
from the NE cannot be used for synchronization.
The clock ID takes a value from 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 clock
source 0 as the current clock source.
The following principles need to be followed when allocating clock ID:
l When the extended SSM is used, the clock ID of an external clock source cannot be
automatically extracted and needs to be allocated.
l At all the nodes that access external clock sources, the internal clock sources should have
a clock ID.
l At all the intersection nodes of a ring/chain and a ring, the internal clock sources should
have a clock ID.
l At all the intersection nodes of a ring/chain and a ring, the line clock sources that are
accessed into the ring should have a clock ID.
l The clock sources other than the preceding four types should have a default clock ID of 0.
l Clock IDs are used for timing reference only. They do not indicate any priority difference.
Thus, the clock source has the same priority regardless of whether the clock ID is 1 or 15.
Figure 6-3 is an STM-1 radio ring where the extended SSM protection is enabled.
On the ring, the following clock sources require a clock ID:
l External clock source 1
l External clock source 2
l Internal clock source on NE1
l Internal clock source on NE3
E W
W E
West/East/ West/East/
Internal
Internal
NE2 E W NE4
W E
West/
East/
NE3 Extenal/
Master clock Internal
Slave BITS
NOTE
l The extended SSM protection provides a complete solution to the timing loop. Thus, when you configure
clock sources, the clocks can form a loop.
l The extended SSM protection is advantageous in the complex networking of clock protection, for example,
the dual external clocks. Hence, the extended SSM protection is used in only a few cases.
l The master (source) node accesses one clock source (which can be an external clock, a line
clock, or an Ethernet clock). On this node, the accessed clock source should be configured.
l In the case of the other nodes, the clock sources for their upper level radio links should be
configured.
l If the upper level radio link is configured with 1+1 protection, a node should be configured
with two radio clock sources, and the clock source for the main radio link should have a
higher priority than the clock source for the standby radio link.
l If a node has multiple upper level radio links (for example, the upper level radio links are
configured with XPIC or N+1 protection), each radio link should be configured with one
radio clock source on this node. In addition, these radio clock sources should be configured
with different priorities according to the actual condition.
l The SSM or extended SSM protection need not be configured.
Figure 6-4 shows the clock synchronization policy for a chain network.
l The master node (NE1) accesses one external clock source. In this case, the clock source
priorities for NE1 in a descending order are as follows: external clock source > internal
clock source.
l The radio link between NE1 and NE2 comprises the IF1 board in slot 3 on NE2, and thus
the clock source priorities for NE2 in a descending order are as follows: 3-IF1-1 > internal
clock source.
l The radio link between NE3 and NE2 comprises the IF1 board in slot 3 on NE3, and thus
the clock source priorities for NE3 in a descending order are as follows: 3-IF-1 > internal
clock source.
l The SSM or extended SSM protection need not be configured.
clock
Figure 6-5 Clock synchronization policy for a ring network (on which only the SDH signal is
transmitted)
BITS
NE2 NE1
NE6
West/East/ West/East/
Internal E Internal
W Extenal/ W E
E Internal W
W E
West/East/ E W
W E West/East/
Internal
Internal
NE3 NE5
NE4
West/East/
Master clock Internal
Figure 6-6 shows the clock synchronization policy for a ring on which not only the SDH signal
is transmitted.
l The ring uses the Hybrid radio for transmission. Thus, divide the ring into the following
chains at the master node (NE1): NE1-NE2-NE3 and NE1-NE4.
l In the case of the master node (NE1), the port 1 on the EM6T board in slot 2 accesses the
Ethernet link, which functions as a clock source. Hence, the clock source priorities for NE1
in a descending order are as follows: 2-EMT6-1 > internal clock source.
l NE2 traces the clock of the master node, and thus the clock source priorities for NE2 in a
descending order are as follows: west clock source > internal clock source.
l NE3 traces the clock of NE2, and thus the clock source priorities for NE3 in a descending
order are as follows: west clock source > internal clock source.
l NE4 traces the clock of the master node (NE1), and thus the clock source priorities for NE4
in a descending order are as follows: east clock source > internal clock source.
l The SSM or extended SSM protection need not be configured.
Figure 6-6 Clock synchronization policy for a ring network (on which not only the SDH signal
is transmitted)
BSC NE1
2-EM6T-1/
Internal
E W
W E
West/ East/
Internal Internal
NE2 W NE4
E
W E
West/
Internal
NE3
Clock
l The upper level NE accesses a clock source (which can be an external clock source, a line
clock source, or an Ethernet clock source).
l If the service of a lower-level NE is aggregated to the upper level NE through the optical
transmission line or Ethernet, the lower-level NE should trace the upper level line clock or
Ethernet clock.
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/system control, cross-connect, and timing 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 anomalies such as pointer justifications. In this case, the
lower-level NE should trace the external clock source output by the upper level NE.
l The SSM or extended SSM protection need not be configured.
Figure 6-7 shows the clock synchronization policy for a tributary port aggregation network.
l The master node (NE1) accesses one external clock source. In this case, the clock source
priorities for NE1 in a descending order are as follows: external clock source > internal
clock source.
l The IF1 boards in slots 3 and 4 on NE2 form a 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. Hence, the clock source priorities for NE2 in a descending
order are as follows: 3-IF1-1 > 4-IF1-1 > internal clock source.
l The service of NE3 is aggregate to NE2 through ports 1 to 4 on the SP3S board in slot 9.
Hence, the clock source priorities for NE3 in a descending order are as follows: 9-SP3S-1
> internal clock source.
l NE4 is connected to many hops of downstream radio links. In this case, if it traces the
tributary clock source, pointer justifications occur on the downstream nodes. Hence, NE4
traces the external clock source output by NE2.
l The SSM protection or extended SSM protection need not be configured.
Figure 6-7 Clock synchronization policy for a port aggregation network (aggregation only
through the tributary port)
NE3
NE1 NE2
9-SP3S-1/
Internal
External/ 3-IF1-1/ NE4
Internal 4-IF1-1/
Internal
External/
Clock Internal
l The number of NEs on a long clock chain should not be more than 20. A number smaller
than 10 is recommended. If a large number of NEs exist on a long clock chain, add one
more clock source for signal compensation in the middle of the chain.
l It is recommended that the SDH optical port should be used at a convergence node to
converge the TDM service. In this manner, the clock signal can be transmitted over the
SDH signal rather than over the PDH signal, which ensures the quality of the clock signal.
If the BTS can access the transmission network through an SDH optical port or Ethernet port,
use the SDH optical port or Ethernet port to provide the timing reference signal for the BTS.
If the BTS can access the transmission network only through the E1 signal, the external clock
port is preferred to transmit the timing reference signal to the BTS.
If the BTS can access the transmission network only through the E1 signal and the external clock
port cannot be used, use the E1 port to transmit the timing reference signal to the BTS. If the
output clock does not meet the requirement of the BTS, the NE that is connected to the BTS can
use the tributary retiming function.
If the BTS can be accessed to the transmission network through Ethernet only and does not
support the synchronous Ethernet function, you can provide the timing reference signal to the
BTS through the external clock port.
Tributary Retiming
When being transmitted by the OptiX RTN 910, 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 realizes the 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 6-8 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 910 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, which causes a delay of 125 us or more. Use
this function 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
5 A.9.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.
6 A.14 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.
7 A.9.9 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 Working Mode to Free-Run Mode for
this NE; set NE Clock Working 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
Working Mode to Tracing Mode for all the
NEs.
Based on 3.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 6-10):
l The radio transmission network is directly synchronized with the clock of the BSC.
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 NE1 and the BSC 8-SL1D-1 (working port of a The ports are used to
linear MSP group) synchronizing NE1 with the
clock of the BSC.
8-SL1D-2 (protection port of
a linear MSP group)
Between NE2 and NE1 3-IF1 (main IF board of a 1+1 The ports are used to
HSB protection group) synchronizing NE2 with the
clock of the BSC.
4-IF1 (standby IF board of a
1+1 HSB protection group)
STM-1 STM-1
NE4
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.9.1 Configuring the Clock Sources and configure the clock sources.
Paramete Value
r
NE1 NE2 NE3 NE4 NE5 NE6
Step 2 See A.9.9 Querying the Clock Synchronization Status and query the clock synchronization
status of the NEs.
NE Clock Working Mode of all the NEs should be Tracing Mode.
----End
Based on 3.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 6-12):
l The radio transmission network is directly synchronized with the clock of the BSC.
l Clock synchronization signals are transmitted to the BTSs over E1 signals.
E1
NE1
BSC
E1
BTS1 E1
BTS2
E1
NE3
BTS3
Between NE2 and BTS1 9-SP3S The ports are used for
enabling the re-timing
Between NE2 and BTS2 9-SP3S function so that the BTS can
be more precisely
synchronized with the clock
of the BSC.
Between NE3 and BTS3 9-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 BSC.
Between NE4 and BTS4 9-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 BSC.
BSC
NE2 NE4
3-IF1-1/ 4-IF1-1/
Internal Internal
NE3
Clock
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.9.1 Configuring the Clock Sources and configure the clock sources.
Parameter Value
Step 2 See A.14 Setting the Parameters of PDH Ports and set the PDH port parameters.
Parameter Value
Step 3 See A.9.9 Querying the Clock Synchronization Status and query the clock synchronization
status of the NEs.
NE Clock Working Mode of all the NEs should be Tracing Mode.
----End
Based on 3.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 6-14):
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 7-EM4F-3 (main port of a The ports are used to
LAG) synchronizing NE1 with the
clock of the BSC.
7-EM4F-4 (slave port of a
LAG)
Between NE2 and NE1 3-IFU2 (main IF board of a 1 The ports are used to
+1 HSB protection group) synchronizing NE2 with the
clock of the BSC.
4-IFU2 (standby IF board of
a 1+1 HSB protection group)
Figure 6-15 Networking diagram (clock for a Hybrid radio chain network)
3-IFU2-1/
Internal
GE
NE4 GE
Clock
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.9.1 Configuring the Clock Sources and configure the clock sources.
The values for the related parameters are provided as follows.
Paramete Value
r
NE1 NE2 NE3 NE4 NE5 NE6
Step 2 See A.9.9 Querying the Clock Synchronization Status and query the clock synchronization
status of the NEs.
NE Clock Working Mode of all the NEs should be Tracing Mode.
----End
Based on 3.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 6-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.
GE
NE1
BSC
FE
BTS1 FE
BTS2
FE
NE3
BTS3
Between NE1 and the BSC 7-EM4T-3 (main port of a The ports are used to
LAG) synchronizing NE1 with the
clock of the BSC.
7-EM4T-4 (slave port of a
LAG)
BSC
NE2 NE4
3-IFU2-1/ 4-IFU2-1/
Internal Internal
Clock NE3
3-IFU2-1/
Internal
NOTE
Separately configure the Ethernet clock source for each link in the LAG.
Clock Protection
In this example, a Hybrid 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.
Procedure
Step 1 See A.9.1 Configuring the Clock Sources and configure the clock sources.
The values for the related parameters are provided as follows.
Parameter Value
Step 2 See A.9.9 Querying the Clock Synchronization Status and query the clock synchronization
status of the NEs.
NE Clock Working Mode of all the NEs should be Tracing Mode.
----End
The OptiX RTN 910 provides multiple auxiliary ports and functions. These functions require
certain data configuration.
Orderwire
The OptiX RTN 910 supports one orderwire phone so that the operation or maintenance
engineers at different workstations can perform voice communication through microwave or
SDH overhead bytes.
When using the orderwire phone, take the following precautions:
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 SCC, cross-connect and clock board.
For definitions of the pins on the ports, see the OptiX RTN 910 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 SCC, cross-connect and
clock board. For definitions of the pins on the ports, see the OptiX RTN 910 IDU Hardware
Description.
Wayside E1 Services
The OptiX RTN 910 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.
External Alarms
External alarms are also called Boolean alarms or relay alarms. The OptiX RTN 910 provides
3-input 1-output external alarms.
Figure 7-1 shows the port circuits of the input external alarms. When the external relay is
switched off, the port circuit generates a high-level signal. When the external relay is switched
on, the port circuit generates a low-level signal. The board generates the corresponding alarm
based on the level that is generated by the port circuit. Input external alarms are mainly used for
accessing the relay alarms generated by the environmental alarm generator.
The port circuits for the output external alarms function the same as the external system shown
in Figure 7-1. When the external alarm output conditions specified for the NE are met, the NE
drives the relay to turn on or off the switch according to the conditions that result the alarm.
Otherwise, the NE drives the relay to change the switch to the reverse status that results in the
alarm. Output external alarms are mainly used for indicating the alarm status of the equipment
that is contained by the centralized alarming devices.
The equipment provides the external alarm ports on the SCC, cross-connect and clock board.
For definitions of the pins on the ports, see the OptiX RTN 910 IDU Hardware Description.
1+0
1+1
NE4 E1
1+0
NE3 NE2 NE1
1+0
NE6 NE5
Between NE1 and NE2 3-IFU2 (main IF board) Configure the ports as a 1+1
HSB protection group.
4-IFU2 (standby IF board)
Between NE2 and NE1 3-IFU2 (main IF board) Configure the ports as a 1+1
HSB protection group.
4-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
4-IFU2-1
NE2 3-IFU2-1
4-IFU2-1
F1
NE3 3-IFU2-1
4-IFU2-1
F1
NE4 3-IFU2-1
NE5 3-IFU2-1
4-IFU2-1
NE Orderwire Port
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.16.1 Configuring the Orderwire and configure the orderwire.
Paramete Value
r
NE1 NE2 NE3 NE4 NE5 NE6
Call 5 5 5 5 5 5
Waiting
Time(s)
----End
In the networking diagram shown in Figure 7-4, 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 ETH
equipment NE4 E1 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 7-13.
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.16.2 Configuring the Synchronous Data Service and configure the synchronous data
services.
The values for the related parameters are provided as follows.
Parameter Value
----End
In the networking diagram shown in Figure 7-5, 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 ETH
equipment NE4 E1 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.
l In this example, the TDM service between NE2 and NE3 is forwarded through the E1 line.
Therefore, service spanning is required. The two asynchronous data ports between NE2
and NE3 are interconnected with each other to realize the service spanning function.
l In this example, the SDH equipment is not required to jointly transmit the asynchronous
data service. Hence, the overhead byte is set to SERIAL1.
l According to the service path, you can obtain the asynchronous data service information
provided in Table 7-19.
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.16.3 Configuring the Asynchronous Data Service and configure the asynchronous data
services.
The values for the related parameters are provided as follows.
Parameter Value
----End
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.16.4 Configuring the Wayside E1 Service and configure the wayside E1 service.
The values for the related parameters are provided as follows.
Parameter Value
NE1 NE2
----End
Input 1
Smoke sensor
Input 2
NE1
Output 1
Water sensor Input 3
Magnetic door
Centralized
switch sensor
alarming box
NOTE
The OptiX RTN 910 supports the automatic mode and the manual mode. The manual mode is used for
commissioning the output alarms.
Procedure
Step 1 See A.16.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
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.1.1 Creating NEs by l Generally, NEs
to perform centralized Using the Search are created by
management of NEs, Method or A.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.1.7 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.
CAUTION
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 In the case of 1+1 HSB/SD protection, you need to configure only the IF/ODU information of the main
radio link.
l In the case of 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 In the case of XPIC configuration, you need to configure the IF/ODU information of the two radio
links in different polarization directions separately.
l In the case of N+1 protection, you need to configure the IF/ODU information of the N+1 radio links
respectively.
l The MW_CFG_MISMATCH alarm is reported, if the E1 count, AM enabled status, 1588 timeslot
enabled status, modulation mode, or IF bandwidth is set inconsistently for both ends of a Hybrid radio
link.
Changing the You need to change the 1. A.8.4 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.
Configuring The ATPC function A.6.4 Configuring the To enable the ATPC
the ATPC needs to be enabled for IF/ODU Information function, set ATPC
function the radio link or the of a Radio Link Enable Status to
values of ATPC Enabled and change
parameters need to be other ATPC
changed. parameter values
according to the
planning
information.
Changing the You can change the A.6.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.4 Configuring the l Before using the
modulation modulation scheme IF/ODU Information new modulation
scheme of a does not meet the of a Radio Link 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
Guaranteed
Capacity
Modulation and
Full Capacity
Modulation.
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.4 Configuring the l If E1s decrease,
number of E1s of E1s and Ethernet IF/ODU Information you need to
on a Hybrid bandwidth, you need to of a Radio Link release the
radio link change the number of timeslots on the
E1s on the Hybrid IF board and then
radio link. delete cross-
connections
before changing
Specified Max
E1 Capacity. For
example, the
services on a
Hybrid radio link
required five E1
previously and
currently requires
only four E1s. In
this case, you
need to release the
fifth timeslot on
the IF board and
then change
Specified Max
E1 Capacity to 4.
l Ensure that the
parameter values
are the same at
both ends of the
Hybrid radio link.
A Task Collection
This section describes how to configure the parameters of ODU ports, including the transmit
frequency attribute, power attribute, ODU attribute, and advanced attributes.
A.13 Setting the Parameters of SDH Ports
The parameters of SDH ports are used to configure the loopback on the SDH interface board
and the laser status.
A.14 Setting the Parameters of PDH Ports
The parameters of PDH ports are used to configure the tributary loopback, service load
indication, and tributary retiming.
A.15 Configuring Overhead Bytes
Generally, the default overload bytes can meet the requirements of the device. In certain special
application scenarios, however, such as device interconnection, you need to change the overload
bytes according to the requirements of the interconnected device.
A.16 Configuring Auxiliary Ports and Functions
The auxiliary ports and functions supported by the OptiX RTN 910 include the orderwire,
synchronous data service, asynchronous data service, wayside E1 service, and external alarm.
A.17 Testing the Protection Switching
By testing the protection switching, you can check whether the protection switching is normal
over radio links.
A.18 Testing the AM Switching
By testing the AM switching, you can check whether the AM switching is normal over radio
links.
Prerequisite
l The communication between the NMS and the NE must be normal.
l The NE user must have the authority of Operation Level or higher.
Procedure
Step 1 In NE List, click NE Search.
Then, the Search NE dialog box is displayed.
During initial configuration, Domain is 129.9.255.255 by default. After the gateway NE IP address of the
searched NE is changed, you need to change the value of Domain. The default network segment cannot
be modified and deleted.
Step 4 After the Web LCT finds the NEs to be managed, click End Search.
Step 5 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
Related References
B.1.1 Parameter Description: NE Searching
Prerequisite
l The NE user must have the authority of Operation Level or higher.
l The communication between the NMS and the NE to be created must be normal.
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.
Then, the Add NE dialog box is displayed.
----End
Related References
B.1.2 Parameter Description: NE Creation
A.1.3 Logging In to an NE
After an NE is created, you need to log in to the NE before managing the NE.
Prerequisite
l The NE user must have the authority of Operation Level or higher.
l The NEs to be managed must be created in the NE List.
Procedure
Step 1 In the NE List, select the target NE and click NE Login.
TIP
Login Status of the NE in the NE List changes to Logged In. Alarm Status of the NE is changed
from Unknown to the current alarm status of the NE.
Step 3 Click NE Explorer.
The NE Explorer is displayed.
TIP
l Check the legend to learn the specific meanings of different colors and symbols in the slot layout
diagram.
----End
Related References
B.1.3 Parameter Description: Login to an NE
Prerequisite
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 select Add
XXX. XXX is the name of the board to be added.
Step 3 Optional: On the slot to which the board is to be deleted, right-click, and then select Delete.
NOTE
Before deleting the board, delete the data, such as the service, clock, orderwire, and protection, on the
board.
----End
Prerequisite
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.
Step 2 Click Modify NE ID.
The Modify NE ID dialog box is displayed.
Step 3 Specify New ID and New Extended ID.
----End
Related References
B.1.4 Parameter Description: NE Attribute_Changing NE IDs
Prerequisite
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
Prerequisite
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 that is installed with the NMS software.
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.
NOTE
If you only need to synchronize the NE time and need not 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 GNE, set the external NTP server as the standard NTP server.
l If the NE is a non-GNE, set the GNE as the standard NTP server.
----End
Related References
B.1.5 Parameter Description: NE Time Synchronization
Prerequisite
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.6 Parameter Description: Localization Management of the NE Time
Prerequisite
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 Enable 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 Enable and
then selecting To in the Set 15-Minute Monitoring or Set 24-Hour Monitoring area.
4. Click Apply.
----End
Prerequisite
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.2.1 Parameter Description: NE Communication Parameter Setting
Prerequisite
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.
Step 2 Click the DCC Rate Configuration tab.
Step 3 Optional: Change the enable status of the DCC.
1. Double-click the cell in the Enabled/Disabled column to which the DCC corresponds.
Select the required state from the drop-down list.
2. Click Apply.
Step 4 Optional: Change the protocol type of the DCC.
1. Double-click the cell in the Protocol Type column to which the DCC corresponds. Select
the required protocol type from the drop-down list.
2. Click Apply.
NOTE
In this figure, 1-CSHC-1 corresponds to the external clock interface on the CSHC board in slot 1.
3. Click OK.
----End
Related References
B.2.2 Parameter Description: DCC Management_DCC Rate Configuration
Prerequisite
The NE user must have the authority of Operation Level or higher.
Procedure
Step 1 Click an NE in the NE Explorer. Choose Communication > ECC Management from the
Function Tree.
Step 2 Set the ECC Extended Mode.
Step 3 Set other parameters when the ECC extended mode is set to the specified mode.
Step 4 Click Apply. A dialog box is displayed indicating that this operation will reset the
communication between NEs.
Step 5 Click OK.
----End
Related References
B.2.4 Parameter Description: ECC Management_Ethernet Port Extended ECC
Prerequisite
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.2.3 Parameter Description: DCC Management_DCC Transparent Transmission Management
Prerequisite
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.2.7 Parameter Description: IP Protocol Stack Management_IP Route Management Creation
Prerequisite
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 parameters of the OSPF protocol.
----End
Related References
B.2.8 Parameter Description: IP Protocol Stack Management_OSPF Parameter Settings
Prerequisite
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 Proxy ARP tab.
Step 3 Set the enable status of the proxy ARP.
----End
Related References
B.2.9 Parameter Description: IP Protocol Stack_Proxy ARP
Prerequisite
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 Network Layer Parameters tab.
Step 3 Set the CLNS role of the NE.
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.2.10 Parameter Description: OSI Management_Network Layer Parameter
Prerequisite
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 6 Configure the attributes of the OSI tunnel according to the network planning.
----End
Related References
B.2.12 Parameter Description: OSI Management_OSI Tunnel
Prerequisite
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 2 Click the Bandwidth Management tab.
Step 3 Set the VLAN ID and bandwidth used by an inband DCN.
----End
Related References
B.2.13 Parameter Description: DCN Management_Bandwidth Management
Prerequisite
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 2 Click the Port Settings tab.
Step 3 Select FE/GE.
Step 4 Configure the enable status of the inband DCN function on ports.
----End
Related References
B.2.14 Parameter Description: DCN Management_Port Setting
Prerequisite
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 In the NE Explorer, select the required NE from the Object Tree, and then choose
Communication > DCN Management from the Function Tree.
Step 2 Click the Protocol Settings tab.
Step 3 Set the protocol type of the inband DCN.
----End
Related References
B.2.15 Parameter Description: DCN Management_Protocol Setting
Prerequisite
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.2.5 Parameter Description: NE ECC Link Management
Prerequisite
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 planning information.
----End
Related References
B.2.6 Parameter Description: IP Protocol Stack Management_IP Route Management
Prerequisite
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 2 Click the Routing Table tab.
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.2.11 Parameter Description: OSI Management_Routing Table
Prerequisite
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.
----End
Prerequisite
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 Set the status of the network port to Enabled and enable the Ethernet access function of the NE.
NOTE
To disable the Ethernet access function of an NE, set the status of the network port to Disabled.
Step 4 Click OK. Then, close the operation result dialog box that is displayed.
----End
Prerequisite
The NE user must have the authority of Operation Level or higher.
Context
If the LCT cannot access an NE through serial interfaces 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. and then close the displayed prompt dialog box.
Step 4 Optional: Select the baud rate of the serial interface from the Baud Rate drop-down list. Click
Apply, and then close the displayed prompt dialog box.
----End
Prerequisite
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 planning information.
----End
Related References
B.3.2 Parameter Description: NE User Management_Creation
Prerequisite
l The NE user must have the authority of System Level or higher.
l The NE user is created.
l An online user can change the password of a user at a lower level.
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 Set Password of NE User dialog box is displayed.
----End
Prerequisite
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. Then, choose Security > NE
Security Parameters from the Function Tree.
Step 2 Set Warning Screen Switching and Warning Screen Information according to the planning
information.
----End
Prerequisite
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 through the configuration of the IF
1+1 protection group, the original service is not interrupted. The board where the original service
exists, however, needs to be set to the working board.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link
Configuration from the Function Tree.
Step 2 Click the IF 1+1 Protection tab.
Step 3 Click New.
The Create IF 1+1 Protection dialog box is displayed.
Step 4 Configure the parameters of the IF 1+1 protection group.
----End
Related References
B.4.5 Parameter: IF 1+1 Protection_Create
Prerequisite
l The NE user must have the authority of Operation Level or higher.
l The IFX2 boards and the ODUs to which the IFX2 boards are connected must be added on
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.
Step 2 Click the XPIC tab.
Step 3 Click New.
The Create XPIC Protection Group dialog box is displayed.
Step 4 Configure the parameters for the XPIC protection group.
----End
Related References
B.4.1 Parameter Description: Link Configuration_XPIC Workgroup_Creation
Prerequisite
l The NE user must have the authority of Operation Level or higher.
l The XPIC protection group must be created.
Background Information
The IFX2 board (XPIC IF board) supports Hybrid radio. Therefore, the Hybrid/AM attributes
can be set for the IFX2 board.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link
Configuration from the Function Tree.
Step 4 Configure the Hybrid/AM attributes of the XPIC Hybrid radio link.
----End
Related References
B.4.2 Parameter Description: Link Configuration_XPIC
Prerequisite
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 In the case of 1+1 HSB/SD protection, you need to configure only the IF/ODU information
of the main radio link.
l In the case of 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 In the case of XPIC configuration, you need to configure the IF/ODU information of the
two radio links in different polarization directions separately.
l In the case of N+1 protection, you need to configure the IF/ODU information of the N+1
radio links respectively.
l The MW_CFG_MISMATCH alarm is reported, if the E1 count, AM enabled status, 1588
timeslot enabled status, modulation mode, or IF bandwidth is set inconsistently for both
ends of a Hybrid radio link.
Procedure
Step 1 In the NE Explorer, select the NE and then choose Configuration > Link Configuration from
the Function Tree.
----End
Related References
B.4.7 Parameter: Link Configuration_IF/ODU Configuration
Prerequisite
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 board is used for Hybrid.
l The IFX2 board is used for XPIC Hybrid.
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.11.1 Parameter Description: IF Interface_IF Attribute
Prerequisite
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 configuration of ATPC parameters in the IF interface
configuration dialog box of the IF board. You can also configure ATPC parameters in the
following configuration dialog boxes:
– Create an XPIC working group
– IF/ODU configuration
NOTE
In the IF/ODU configuration dialog box, the ATPC adjustment thresholds cannot be changed.
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > IF Interface from the Function Tree.
Step 2 Click the ATPC Attributes tab.
Step 3 Configure the parameters of ATPC attributes.
----End
Related References
B.11.2 Parameter Description: IF Interface_ATPC Attribute
Prerequisite
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.
Background Information
The OptiX RTN 910 supports the Hybrid/AM function and the corresponding IF boards are
IFU2 and IFX2.
Procedure
Step 1 In the NE Explorer, select a Hybrid IF board from the Object Tree and then choose
Configuration > Hybrid/AM Configuration from the Function Tree.
----End
Related References
B.11.3 Parameter Description: Hybrid/AM Configuration
Prerequisite
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 Hybrid radio links, 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 Work Unit from Select Mapping Direction.
2. Select a port to which a working channel corresponds from Select Mapping Way, 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 Select Mapping Way, and
then click .
----End
Related References
B.4.3 Parameter Description: N+1 Protection_Create
Prerequisite
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.
Step 2 Click Query to query the running information of the ATPC function.
----End
Related References
B.11.4 Parameter Description: ATPC Adjustment Records
Prerequisite
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 Analyze from the Function Tree.
Step 2 Specify the start time and end time of a specific time span.
NOTE
The time span starts from the last routine maintenance time to the current time.
Step 4 Click Draw. The history transmit and receive power curve of the ODU in the specified time
span is displayed.
----End
Prerequisite
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 In the NE Explorer, select a Hybrid IF board from the Object Tree and then choose
Configuration > Hybrid/AM Configuration from the Function Tree.
----End
Related References
B.11.3 Parameter Description: Hybrid/AM Configuration
Prerequisite
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, and then close the displayed prompt dialog box. 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 Switch Status from the shortcut menu to
check the protection status of the IF 1+1 protection group.
----End
Related References
B.4.6 Parameter Description: IF 1+1 Protection
Prerequisite
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 Select the protection group whose protection status needs to be queried.
Step 4 Click Query. Check the protection status of the IF N+1 protection group in Slot Mapping
Relation.
----End
Related References
B.4.4 Parameter Description: N+1 Protection
Prerequisite
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 2 Click the IF 1+1 Protection tab.
Step 3 In Protection Group, select the protection group for protection switching.
Step 4 In Slot Mapping Relation, 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 6 Click OK to close the confirmation dialog box that is displayed. Then, click OK to close the
dialog box that is displayed, indicating that the operation is successful.
Step 7 Click Query Switch Status to check whether the switching operation is successful.
----End
Prerequisite
l The NE user must have the authority of Operation 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 2 Click the N+1 Protection tab.
Step 3 In Protection Group, select the protection group for protection switching.
Step 4 In Slot Mapping Relation, 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 6 Click OK to close the confirmation dialog box that is displayed. Then, click OK to close the
dialog box that is displayed, indicating that the operation is successful.
Step 7 Click Query to check whether the switching operation is successful.
----End
Prerequisite
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 2 Click the N+1 Protection tab.
Step 3 In Protection Group, select the protection group whose N+1 protection protocol needs to be
started.
Step 4 Click Start Protocol or Stop Protocol. Then, close the displayed prompt dialog box.
Step 5 Click Query to check the protocol status.
----End
Prerequisite
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.5.1 Parameter Description: Linear MSP_Creation
Prerequisite
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 3 In Protection Group, click the linear MSP group to be queried.
Step 4 Click Query > Query Switching Status In Slot Mapping Relation, query the status of the
linear MSP.
----End
Related References
B.5.2 Parameter Description: Linear MSP
Prerequisite
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 > Linear MS
from the Function Tree.
Step 2 In Protection Group, select the MSP group to be switched. In Slot Mapping Relation, select
the working unit or protection unit, and then right-click.
Step 3 Right-click and select the required switching mode, and then close the dialog box that is
displayed.
----End
Prerequisite
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 to query the Protocol Status.
----End
Prerequisite
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.6.1 Parameter Description: SDH Service Configuration_Creation
Prerequisite
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.6.2 Parameter Description: SDH Service Configuration_SNCP Service Creation
Prerequisite
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 Initiation Condition to which the
working service corresponds.
Step 3 Set the initiation condition for the working service. Click OK.
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.6.5 Parameter Description: SNCP Service Control
Prerequisite
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
Prerequisite
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.
Related References
B.6.3 Parameter Description: SDH Service Configuration_Converting Normal Services Into
SNCP Services
Prerequisite
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 clickTo Normal.
l To convert the cross-connection into a cross-connection between the working source and the service
sink, choose Working.
l To convert the cross-connection into a cross-connection between the protection source and the service
sink, choose Protection.
----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.
Prerequisite
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.6.4 Parameter Description: SDH Service Configuration
Prerequisite
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 4 In the displayed dialog box for confirmation, click OK.
Step 5 The system displays a prompt dialog box, indicating that the operation is successful. Then, close
the displayed prompt dialog box.
Step 6 Choose Function > Query Switch Status to check whether the switching operation is
successful.
----End
Prerequisite
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.
Step 3 Click Function > Query Switch Status, and then close the displayed prompt dialog box.
----End
Related References
B.6.5 Parameter Description: SNCP Service Control
Prerequisite
l The NE equipment 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
CAUTION
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.
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
Prerequisite
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.
By pressing the Ctrl key on the keyboard, you can select multiple clock sources at one time.
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.7.1 Parameter Description: Clock Source Priority Table
Prerequisite
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 > Clock
Subnet Configuration.
Step 3 Start the clock protection protocol and configure its parameters.
----End
Related References
B.7.2 Parameter Description: Clock Subnet Setting_Clock Subnet
Prerequisite
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 > Clock
Subnet Configuration.
NOTE
Step 7 Set the clock quality for which the quality level is zero.
NOTE
----End
Related References
B.7.3 Parameter Description: Clock Subnet Setting_Clock Quality
Prerequisite
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 SSM protocol must be enabled or extended.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Clock
Subnet Configuration.
Step 2 Click the SSM Output Control tab.
Step 3 Set the SSM control status.
----End
Related References
B.7.4 Parameter Description: Clock Subset Setting_SSM Output Control
Prerequisite
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 > Clock
Subnet Configuration.
Step 2 Click the Clock ID Status tab.
Step 3 Set the clock ID control status.
----End
Related References
B.7.5 Parameter Description: Clock Subset Setting_Clock ID Enabling Status
Prerequisite
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 >
Phase-Locked Source Output by External Clock.
----End
Related References
B.7.9 Parameter Description: Output Phase-Locked Source of the External Clock Source
Prerequisite
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 > Clock
Source Switching.
----End
Related References
B.7.8 Parameter Description: Clock Source Switching_Clock Source Switching Conditions
Prerequisite
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 > Clock
Source Switching.
----End
Related References
B.7.6 Parameter Description: Clock Source Switching_Clock Source Restoration Parameters
Prerequisite
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 > Clock
Synchronization Status.
----End
Related References
B.7.10 Parameter Description: Clock Synchronization Status
Prerequisite
l The NE user must have the authority of Operation Level or higher.
l The Ethernet boards or hybrid IF boards must be added to the Slot Layout.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protection > ERPS Management.
----End
Related References
B.9.2.1 Parameter Description: ERPS Management_Creation
Prerequisite
l The NE user must have the authority of Operation Level or higher.
l The protection instance of the ERPS 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.
----End
Related References
B.9.2.2 Parameter Description: ERPS Management
Prerequisite
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.
----End
Related References
B.9.2.2 Parameter Description: ERPS Management
Prerequisite
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.
Step 2 Click the Link Aggregation Group Management tab.
Step 3 Click New.
The system displays the Create Link Aggregation Group dialog box.
Step 4 Set the attributes of the LAG in Attribute Settings.
Hold on the Ctrl key or the Shift key on the keyboard to select multiple ports.
4. Click OK.
----End
Related References
B.9.2.15 Parameter Description: Ethernet Link Aggregation Management_LAG Creation
Prerequisite
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.
Step 2 Click the Link Aggregation Parameters tab.
Step 3 Set the port priority.
----End
Related References
B.9.2.16 Parameter Description: Ethernet Link Aggregation_Link Aggregation
Prerequisite
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.
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 specific information about the LAG from the
shortcut menu.
----End
Prerequisite
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.9.1.6 Parameter Description: QinQ Link_Creation
Prerequisite
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 > Ethernet
Service Management > E-Line Service from the Function Tree.
l The parameters on the interface for configuring an E-Line service vary according to the value of
Direction.
l For the method of creating a QinQ link, see A.10.3.1 Configuring the QinQ Link.
2. Optional: Change the Ethernet port attributes of the source and sink ports.
Step 4 Ensure that the parameters are set correctly and then click Next.
NOTE
To create more than one VLAN switching table, you need to click New more than one time.
Step 6 Ensure that the parameters are set correctly and then click Finish.
NOTE
To check the parameters that are configured in the preceding step, click Previous.
----End
Related References
B.9.1.1 Parameter Description: E-Line Service_Creation
Prerequisite
l The NE user must have the authority of Operation Level or higher.
l The corresponding Ethernet board must be added to Slot Layout.
l The UNI-UNI E-Line service must be created.
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 4 Set the attributes of the new VLAN forwarding table item.
----End
Related References
B.9.1.3 Parameter Description: VLAN Forwarding Table Item_Creation
Prerequisite
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 > Ethernet
Service Management > E-LAN Service from the Function Tree.
Step 2 Click Create.
The Create E-LAN Service dialog box is displayed.
Step 3 Perform Step 1: Configure the source and sink.
1. Set the attributes according to the planning information.
NOTE
2. Click Get UNI Port and configure the UNI port connected to the bridge.
3. Optional: Click Get NNI Port and configure the NNI port connected to the bridge.
NOTE
This step takes effect only when Tag Type is set to S-Awared.
4. Optional: Change the Ethernet port attribute of the port mounted to the bridge.
Step 4 Ensure that the parameters are set correctly and then click Next.
Step 5 Perform Step 2: Set the service parameters.
Step 6 Optional: Select Split Horizon Group.
1. Click Create.
Then, the Create Split Horizon Group dialog box is displayed.
2. Select the port to be added from Available Port List and then click .
NOTE
To select more than one port at a time, press and hold the Ctrl key when selecting the ports.
3. Click OK.
Step 7 Ensure that the parameters are set correctly and then click Finish.
NOTE
To check the parameters that are configured in the preceding step, click Previous.
----End
Related References
B.9.1.4 Parameter Description: E-LAN Service_Creation
Prerequisite
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.
Step 2 Add or delete logical ports connected to a VB.
NOTE
l To add or delete ports connected to the VB on the UNI side, click Get UNI Port.
l To add or delete ports connected to the VB on the NNI side, click Get NNI Port.
1. Optional: Click to add ports to the list of ports connected to the VB.
2. Optional: Click to delete ports from the list of ports connected to the VB.
TIP
To select more than one port at a time, press and hold the Ctrl key when selecting the ports.
3. In Selected Port List, set the attributes of the ports connected to the VB.
4. Click OK.
----End
Prerequisite
l The NE user must have the authority of Operation Level or higher.
l The E-Line service must be configured and the 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 2 Click Query, and then close the dialog box that is displayed.
Step 3 Select the Ethernet-line service that needs to be deleted and then click Delete.
Then, a dialog box is displayed, querying whether you need to perform this operation.
----End
Prerequisite
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.
Step 2 Click Query. Then, close the dialog box that is displayed.
Step 3 Select the E-LAN service to be deleted and click Delete.
Then, a confirmation dialog box is displayed.
Step 4 Click OK.
Step 5 Click Query.
At this time, the E-LAN service is already deleted.
----End
Prerequisite
Ethernet services must be configured.
NOTE
It is recommended that you test low-priority Ethernet services in good weather conditions, where the AM
function works in the highest modulation mode.
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.
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.
l Maintenance Domain Name: MD1 for NE1, NE2, and NE3
l Maintenance Domain Level: 4 for NE1, NE2, and NE3
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.
l Maintenance Association Name: MA1 for NE1, NE2, and NE3
l Relevant Service: services from NE1 to NE2 and NE3
NOTE
Click in Relevant Service, and select relevant services in the New Maintenance
Association dialog box.
4. Click OK.
Step 3 Configure the MEPs of NE1, NE2, and NE3.
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Service from the Function Tree.
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. Then, 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.
l Remote Maintenance Point ID: 102 and 103 for NE1, and 101 for NE2 and NE3
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.
l Source Maintenance Point ID: 101 (maintenance point ID of NE1)
l Destination Maintenance Point ID: 102 (maintenance point ID of NE2)
l Transmitted Packet Count: 20 (recommended)
l Transmitted Packet Length: 64 (64 is a recommended value, and the parameter can
also be set to 128, 256, 512, 1024, and 1280 for testing the Ethernet services of different
packet lengths.)
NOTE
7. Repeat Step 5.4 to Step 5.6 to test the Ethernet services from NE1 to NE3.
l Source Maintenance Point ID: 101 (maintenance point ID of NE1)
l Destination Maintenance Point ID: 103 (maintenance point ID of NE3)
l Transmitted Packet Count: 20 (recommended)
l Transmitted Packet Length: 64 (recommended)
l Transmitted Packet Priority: 7 (recommended)
The LossRate in the Detection Result should be 0.
----End
Prerequisite
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.9.1.5 Parameter Description: E-LAN Service
Prerequisite
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.
----End
Related References
B.9.1.5 Parameter Description: E-LAN Service
Prerequisite
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.9.1.5 Parameter Description: E-LAN Service
Prerequisite
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. Then, click OK
in the dialog box that is displayed for confirmation.
----End
Related References
B.9.1.5 Parameter Description: E-LAN Service
Prerequisite
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.9.1.5 Parameter Description: E-LAN Service
Prerequisite
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 4 Click Apply, and then close the dialog box that is displayed.
----End
Related References
B.9.5.1 Parameter Description: Ethernet Interface_Basic Attributes
Prerequisite
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 Flow Control tab.
Step 3 Configure the traffic control of Ethernet ports.
----End
Related References
B.9.5.2 Parameter Description: Ethernet Interface_Flow Control
Prerequisite
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 Layer 2 Attributes tab.
Step 3 Configure the L2 attributes of Ethernet ports.
----End
Related References
B.9.5.3 Parameter Description: Ethernet Interface_Layer 2 Attributes
Prerequisite
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 4 Click Apply, and then close the dialog box that is displayed.
----End
Related References
B.9.5.4 Parameter Description: Ethernet Interface_Advanced Attributes
Prerequisite
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 > Ethernet Interface from the Function Tree.
----End
Related References
B.11.13 Parameter Description: Microwave Interface_Basic Attributes
Prerequisite
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 > Ethernet Interface from the Function Tree.
----End
Related References
B.11.14 Parameter Description: Microwave Interface_Layer 2 Attributes
Prerequisite
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 > Ethernet Interface from the Function Tree.
----End
Related References
B.11.15 Parameter Description: Microwave Interface_Advanced Attributes
Prerequisite
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.
Step 3 Click Create. The Create Port Group dialog box is displayed.
Then, the Create Port Group dialog box is displayed.
3. Select the member port from Available Port List. Then, click .
TIP
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.9.2.3 Parameter Description: MSTP Configuration_Port Group Creation
Prerequisite
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.9.2.5 Parameter Description: MSTP Configuration_ Bridge Parameters
Prerequisite
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 2 Click the CIST&MSTI Parameters tab.
Step 3 Select the port group from the drop-down list of Port Group.
Step 4 Set the parameters of the port group.
----End
Related References
B.9.2.6 Parameter Description: MSTP Configuration_CIST Parameters
Prerequisite
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.9.2.7 Parameter Description: MSTP Configuration_Running Information About the CIST
A.10.8.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.
Prerequisite
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
Prerequisite
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 2 Click the Port Group Parameters tab.
Step 3 Select Enabled or Disabled from the Enable Protocol drop-down list of the port group for
which the MSTP protocol needs to be enabled or disabled.
----End
Prerequisite
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 2 Click the Port Group Parameters tab.
Option Description
If ... Then ...
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 .
TIP
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.9.2.4 Parameter Description: MSTP Configuration_Port Group Configuration
Prerequisite
l The NE user must have the authority of Operation Level or higher.
l The E-LAN service must be created.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protocol Configuration > IGMP Snooping Configuration from the Function Tree.
----End
Related References
B.9.2.8 Parameter Description: IGMP Snooping Configuration_Protocol Configuration
Prerequisite
l The NE user must have the authority of Operation Level or higher.
l The E-LAN service must be created.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protocol Configuration > IGMP Snooping Configuration from the Function Tree.
----End
Related References
B.9.2.10 Parameter Description: IGMP Snooping Configuration_Route Management
Prerequisite
l The NE user must have the authority of Operation Level or higher.
l The E-LAN service must be created.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protocol Configuration > IGMP Snooping Configuration from the Function Tree.
----End
Related References
B.9.2.12 Parameter Description: IGMP Snooping Configuration_Route Member Port
Management
Prerequisite
l The NE user must have the authority of Operation Level or higher.
l The E-LAN service must be created.
l The NNI port must be configured for the E-LAN service.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protocol Configuration > IGMP Snooping Configuration from the Function Tree.
1. Select the static router port from the drop-down list of Available Port. Click .
TIP
To select more than one port at a time, press and hold the Ctrl key or the Shift key when selecting
the ports.
2. Click OK.
----End
Related References
B.9.2.11 Parameter Description: IGMP Snooping Configuraiton_Static Router Port Creation
Prerequisite
l The NE user must have the authority of Operation Level or higher.
l The E-LAN service must be created.
l The UNI port must be configured for the E-LAN service.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protocol Configuration > IGMP Snooping Configuration from the Function Tree.
Step 2 Click the Route Member Port Management tab.
Step 3 Click New.
Step 4 Set the attributes of members in the static multicast group.
1. Set Service ID and VLAN ID.
2. Select the member ports from the drop-down list of Available Port. Click .
TIP
To select more than one port at a time, press and hold the Ctrl key or Shift key when selecting the
ports.
3. Click OK.
----End
Related References
B.9.2.13 Parameter Description: IGMP Snooping Configuration_Static Multicast Group
Member Creation
Prerequisite
l The NE user must have the authority of Operation Level or higher.
l The E-LAN service must be created.
l The UNI port must be configured for the E-LAN service.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protocol Configuration > IGMP Snooping Configuration from the Function Tree.
Step 2 Click the Protocol Configuration tab.
----End
Related References
B.9.2.9 Parameter Description: IGMP Snooping Configuration_Adding Port to Be Quickly
Deleted
Prerequisite
l The NE user must have the authority of Operation Level or higher.
l The E-LAN service must be created.
l The UNI port must be configured for the E-LAN service.
l Dynamic or static multicast member ports must be configured.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protocol Configuration > IGMP Snooping Configuration from the Function Tree.
Step 2 Click the Packet Statistics tab.
----End
Related References
B.9.2.14 Parameter Description: IGMP Snooping Configuration_Data Statistics
Prerequisite
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 910 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. The default DS domain cannot be modified or deleted. You can only change
Packet Type of a port.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Diffserv Domain Management from the Function Tree.
Step 5 Configure the mapping relations between the priorities of ingress packets and PHB service
classes.
Step 7 Configure the mapping relations between the priorities of egress packets and PHB service
classes.
Step 8 Select Board where the application ports exist from Application Port.
Related References
B.9.4.2 Parameter Description: DiffServ Domain Management_Create
Prerequisite
l The NE user must have the authority of Operation Level or higher.
l The DS domain must be created.
Background Information
The OptiX RTN 910 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. The default DS domain cannot be modified or deleted. You can only change
Packet Type of a port.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Diffserv Domain Management from the Function Tree.
Step 2 Select the created DS domain and change its attributes on the main interface.
----End
Prerequisite
l The NE user must have the authority of Operation Level or higher.
l The DS domain must be created.
Background Information
The OptiX RTN 910 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. The default DS domain cannot be modified or deleted. You can only change
Packet Type of a port.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
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 drop-
down list of Available Port.
3. Click .
You need to change the packet type Select a new packet type from the drop-down list
identified by the port of Packet Type.
TIP
To select more than one port at a time, press and hold the Ctrl key when selecting the ports.
----End
Related References
B.9.4.3 Parameter Description: DiffServ Domain Applied Port_Modification
Prerequisite
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 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Policy Management from the Function Tree.
4. Click OK.
----End
Related References
B.9.4.5 Parameter Description: Port Policy
Prerequisite
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 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,
weight, and queue shaping of the port queues.
Step 4 Click Apply.
----End
Prerequisite
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 from the Function Tree.
Step 2 Click the Traffic Classification Configuration tab.
Step 3 Click New. The Create Traffic Classification dialog box is displayed.
The Create Traffic Classification dialog box is displayed.
Step 4 Configure the attributes of a new traffic.
----End
Related References
B.9.4.6 Parameter Description: Port Policy_Traffic Classification Configuration
Prerequisite
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 from the Function Tree.
3. Click OK.
To select more than one port at a time, press and hold the Ctrl key when selecting the ports.
2. Click OK.
----End
Related References
B.9.4.4 Parameter Description: Policy Management
Prerequisite
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.
----End
Related References
B.9.4.7 Parameter Description: Port Shaping Management_Creation
Prerequisite
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 from the Function Tree.
----End
Related References
B.9.4.4 Parameter Description: Policy Management
Prerequisite
The NE user must have the authority of Operation Level or higher.
Background Information
The OptiX RTN 910 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. The default DS domain cannot be modified or deleted. You can only change
Packet Type of a port.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Diffserv Domain Management from the Function Tree.
Step 2 Click the Ingress Mapping Relation tab.
Step 3 Click Query.
Step 4 Query the attributes of the DS domain and the mapping relation between the priority level of
the packets in the ingress direction and the PHB service class.
Step 5 Click the Egress Mapping Relation tab.
Step 6 Click Query.
Step 7 Query the attributes of the DS domain and the mapping relation between the priority level of
the packets in the egress direction and the PHB service class.
Step 8 Click the Apply Port tab.
Step 9 Click Query.
Step 10 Query the ports that use the DS domain.
----End
Related References
B.9.4.1 Parameter Description: Diffserv Domain Management
A.10.11.1 Creating an MD
A maintenance domain (MD) defines the range and level of the Ethernet OAM. MDs of different
ranges and levels can provide users with differentiated OAM services.
Prerequisite
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.
Step 2 Click the Maintenance Association tab.
Step 3 Choose New > New Maintenance Domain.
----End
Related References
B.9.3.1 Parameter Description: Ethernet Service OAM Management_Maintenance Domain
Creation
A.10.11.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.
Prerequisite
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 Select Service dialog box that
is displayed.
----End
Related References
B.9.3.2 Parameter Description: Ethernet Service OAM Management_Maintenance Association
Creation
Prerequisite
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 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 parameters of the MEP point.
----End
Related References
B.9.3.3 Parameter Description: Ethernet Service OAM Management_MEP Creation
Prerequisite
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 Choose OAM > Manage Remote MEP Point. Then, the Manage Remote MEP Point dialog
box is displayed.
Step 4 Click New.
Then, the Add Maintenance Association Remote Maintenance Point dialog box is displayed.
Step 5 Set the parameters of the new remote MEPs.
----End
Related References
B.9.3.4 Parameter Description: Ethernet Service OAM Management_Remote MEP Creation
Prerequisite
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 MIP Point tab.
Step 3 Select the maintenance domain in which an MIP needs to be created, and then click New.
Then, the New MIP Maintenance Point dialog box is displayed.
Step 4 Set the parameters of the new MIP.
----End
Related References
B.9.3.5 Parameter Description: Ethernet Service OAM Management_MIP Creation
Prerequisite
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 2 Click the Maintenance Association tab.
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
Prerequisite
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 a 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 2 Click the Maintenance Association tab.
Step 3 Select the maintenance domain and maintenance association for the LB test.
Step 4 Choose OAM > Start LB.
Then, the LB Test dialog box is displayed.
Step 5 Select the method for identifying the destination MP and set the parameters involved in the LB
test.
NOTE
Step 6 Click Start Test. Then, the LB test result is displayed in the Detection Result window.
----End
Related References
B.9.3.6 Parameter Description: Ethernet Service OAM Management_LB Enabling
Prerequisite
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.
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 a LT 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 2 Click the Maintenance Association tab.
Step 3 Select the maintenance domain and maintenance association for the LT test.
Step 4 Choose OAM > Start LT.
Then, the LT Test dialog box is displayed.
Step 5 Select the method for identifying the destination MP and set the parameters involved in the LT
test.
NOTE
Step 6 Click Start Test. Then, the LT test result is displayed in the Detection Result window.
----End
Related References
B.9.3.7 Parameter Description: Ethernet Service OAM Management_LT Enabling
Prerequisite
The NE user must have the authority of Operation Level or higher.
Background Information
The OAM auto-discovery is realized through the auto-negotiation between the local equipment
and the opposite equipment. If the negotiation fails, the local equipment reports an alarm. After
the OAM auto-discovery succeeds, the link performance is monitored according to the error
frame threshold. You can set the error frame threshold on the NMS.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Port OAM from the Function Tree.
Step 2 Click the OAM Parameter tab.
Step 3 Select the port, and set OAM Working Mode.
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, the OAM auto-discovery
fails.
l If the OAM modes of the two systems are both passive modes, a fault occurs on the line, or one system
fails to receive the OAM protocol message, an alarm is reported, indicating that the OAM auto-
discovery fails.
----End
Related References
B.9.3.8 Parameter Description: Ethernet Port OAM Management_OAM Parameter
Prerequisite
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.
Background Information
After the OAM auto-discovery operation is successful at both ends, the link fault detection and
performance detection are automatically started.
l To report the detected link fault event to the opposite equipment, you need to set Remote
Alarm Support For Link Event to Enabled for the local equipment.
l To report the detected link fault event to the opposite equipment, you need to set Remote
Alarm Support For Link Event to Enabled and set Error Frame Period Window
(ms) and Error Frame Monitor Threshold (frame) for the local equipment.
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
ETH_EFM_EVENT 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, you can query the
ETH_EFM_REMFAULT alarm, which is reported at the local end, by using the NMS.
According to the alarm, you can determine the fault type.
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.9.3.8 Parameter Description: Ethernet Port OAM Management_OAM Parameter
Prerequisite
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.
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.
----End
Related References
B.9.3.9 Parameter Description: Ethernet Port OAM Management_OAM Error Frame
Monitoring
Prerequisite
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 initiating state and reports the loopback initiating
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. At this time, the alarm is automatically
cleared.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Port OAM from the Function Tree.
Step 2 Click the OAM Parameter tab.
Step 3 Select the port and set Remote Side Loopback Response to Enabled.
----End
Prerequisite
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.
Background Information
After the loopback detection is enabled at an Ethernet port, the ETHOAM_SELF_LOOP alarm
is reported if a loopback occurs at the port.
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
Prerequisite
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 from the Function Tree.
Step 2 Click New.
The Create LPT dialog box is displayed.
----End
Related References
B.9.2.17 Parameter Description: LPT Management_Creation
Prerequisite
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.
NOTE
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
Prerequisite
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.
----End
Related References
B.8.4 Parameter Description: RMON Performance_RMON Setting
Prerequisite
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
Prerequisite
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.
Step 2 Click the History Group tab.
----End
Related References
B.8.4 Parameter Description: RMON Performance_RMON Setting
Prerequisite
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.
Step 2 Click the Radio Frequency Attributes tab.
----End
Related References
B.11.6 Parameter Description: ODU Interface_Radio Frequency Attribute
Prerequisite
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.11.8 Parameter Description: ODU Interface_Equipment Information
Prerequisite
l The NE user must have the authority of Operation Level or higher.
l The related IF board must be added.
l The corresponding board 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.
Step 2 Click the Power Attributes tab.
Step 3 Configure the power attribute parameters of the ODU.
----End
Related References
B.11.7 Parameter Description: ODU Interface_Power Attributes
Prerequisite
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.
Step 2 Click the Advanced Attributes tab.
Step 3 Configure the parameters of the ODU, such as Configure Transmission Status.
----End
Related References
B.11.9 Parameter Description: ODU Interface_Advanced Attributes
Prerequisite
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.
----End
Prerequisite
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. Click Apply.
A dialog box is displayed for confirmation.
2. Click OK.
----End
Related References
B.11.10 Parameter Description: SDH Interfaces
Prerequisite
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.
----End
Related References
B.11.12 Parameter Description: PDH Interfaces
Prerequisite
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.
Step 2 Configure the J0 byte.
1. Double-click the parameter whose value needs to be changed.
The Please input the overhead byte dialog box is displayed.
2. Configure overhead bytes.
3. Click OK.
Step 3 Click Apply.
A dialog box is displayed for confirmation.
Step 4 Click OK.
----End
Related References
B.12.1 Parameter Description: Regenerator Section Overhead
Prerequisite
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.
Step 2 Choose Display in Text Format or Display in Hexadecimal.
Step 3 Optional: Configure the J1 byte.
1. Click the Trace Byte J1 tab.
2. Double-click the parameter whose value needs to be changed.
The Please Input Overhead Byte dialog box is displayed.
3. Configure overhead bytes.
4. Click OK.
5. Click Apply.
A dialog box is displayed for confirmation.
6. Click OK.
3. Click Apply.
A dialog box is displayed for confirmation.
4. Click OK.
----End
Related References
B.12.2 Parameter Description: VC-4 POHs
Prerequisite
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.
4. Click OK.
5. Click Apply.
A dialog box is displayed for confirmation.
6. Click OK.
----End
Related References
B.12.3 Parameter Description: VC-12 POHs
Prerequisite
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.
Step 2 Click the General tab.
Step 3 Configure the orderwire information.
3. Click Apply.
----End
Related References
B.10.1 Parameter Description: Orderwire_General
Prerequisite
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.10.3 Parameter Description: Orderwire_F1 Data Port
Prerequisite
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.10.4 Parameter Description: Orderwire_Broadcast Data Port
Prerequisite
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,
8,E3,28MHz,QPSK, or 9,E3,14MHz,16QAM mode.
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.11.1 Parameter Description: IF Interface_IF Attribute
Prerequisite
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 910 are also considered as housekeeping alarms. The
external alarm port of the OptiX RTN 910 is a relay port. This port can be either in the "on" state
or in the "off" state.
The OptiX RTN 910 provides one alarm output port and three 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 logical 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.10.5 Parameter Description: Environment Monitoring Interface
Prerequisite
l Aligning the antennas is complete.
l The equipment is configured with the IF 1+1 protection.
l The E1 service is configured.
NE A NE B
As shown in Figure A-2, the following procedures consider the E1 service between NE A and
NE B that is configured with the 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 to Step 11.
No BER tester is available on site Perform Step 6 to Step 10.
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.
If... Then...
A BER tester is available on site Check the test result on the BER tester. It
should show that the service is restored after a
transient interruption.
No BER tester is available on site, and the See A.8.10 Testing the E1 Service Through
E1 service is transmitted on the radio link. PRBS to test the availability of the E1 service.
No BER tester is available on site, and the See A.10.3.8 Testing the Ethernet Service to
Ethernet service is transmitted on the radio test the availability of the Ethernet service.
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 then 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 then click Query.
4. In Protection Group, the value of Active Board of Device should be the standby IF board
4-IFU2.
----End
Prerequisite
l Aligning the antennas must be complete.
l The equipment must be configured with the N+1 protection.
NE A NE B
As shown in Figure A-3, the following procedures consider the E1 service between NE A and
NE B that is configured with the N+1 (N=1) protection 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 unit 3-IFU2-1 and the
protection unit 4-IFU2-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 service is restored after a
transient interruption.
No BER tester is available on site, and the See A.8.10 Testing the E1 Service Through
E1 service is transmitted on the radio link. PRBS to test the availability of the E1 service.
No BER tester is available on site, and the See A.10.3.8 Testing the Ethernet Service to
Ethernet service is transmitted on the radio test the availability of the Ethernet service.
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-IFU2-1 for the
service that is configured with the N+1 protection should be SF.
----End
Prerequisite
l Aligning the antennas must be complete.
l The equipment must be configured with the SNCP.
NE A
Working
Protecting SNC SNC
NE D
NE B
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 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 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 4 Test the BER by using the BER tester.
The BER tester should show that no bit errors occur.
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 then choose
Configuration > SNCP Service Control from the Function Tree.
2. In Working Cross-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 Cross-Connections
and Protection Cross-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 service is restored after a
transient interruption.
No BER tester is available on site, and the See A.8.10 Testing the E1 Service Through
E1 service is transmitted on the radio link. PRBS to test the availability of the E1 service.
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 then 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 Cross-Connections
and Protection Cross-Connections.
----End
Prerequisite
l The equipment must be configured with the ERPS.
l The network cable for carrying the working and protection Ethernet services of the ERPS
must be 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 then choose
Configuration > Ethernet Protection > ERPS Management from the Function Tree.
2. Select the ERPS protection group to be queried, and then click Query.
3. The value of Status of State Machine should be Idle.
Step 2 See A.10.3.8 Testing the Ethernet Service to test the availability of the Ethernet service.
The LossRate in the Detection Result should be 0.
Step 3 Set TX Status to mute for the west ODU 23-ODU of NE A.
1. Select the NE from the Object Tree in the NE Explorer of NE A, and then choose
Configuration > Link Configuration from the Function Tree.
2. Click the IF/ODU Configuration tab.
3. Select the required ODU, and set TX Status to mute.
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 then choose
Configuration > Ethernet Protection > ERPS Management from the Function Tree.
2. Select the ERPS protection group to be queried, and then click Query.
3. The value of Status of State Machine should be Protection.
Step 5 See A.10.3.8 Testing the Ethernet Service to test the availability of the Ethernet service.
The LossRate in the Detection Result should be 0.
Step 6 Set TX Status to unmute for the west ODU 23-ODU of NE A.
1. Select the NE from the Object Tree in the NE Explorer of NE A, and then choose
Configuration > Link Configuration from the Function Tree.
2. Click the IF/ODU Configuration tab.
3. Select the required ODU, and set TX Status to Unmute.
4. Click Apply.
----End
Prerequisite
l The equipment must be configured with the linear MSP.
l The working and protection optical fibers of the linear MSP are connected properly.
l BER tester
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.
4. In Tributary Loopback, select Inloop.
5. Click Apply.
The Confirm dialog box is displayed.
6. Click OK.
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 service that is 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 service is restored after a
transient interruption.
No BER tester is available on site, and the See A.8.10 Testing the E1 Service Through
E1 service is transmitted on the optical fiber PRBS to test the availability of the E1 service.
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 service is 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 service is 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
Prerequisite
l Aligning the antennas must be complete.
l The radio links must be Hybrid 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 considers the E1 service 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 > Hybrid/AM
Configuration from the Function Tree.
2. 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.
3. Click Apply.
Step 7 Querying the AM working status on the local NE.
1. Select the IF board from the NE Explorer, and then choose Configuration > Hybrid/AM
Configuration from the Function Tree.
2. Click Query.
Transmit-End Modulation mode should be Modulation Mode of the Full AM
Capacity of a preset value.
NOTE
In the case of unfavorable weather, the current modulation mode may be lower than the value of
Modulation Mode of the Full AM Capacity.
----End
Prerequisite
l Aligning the antennas must be complete.
l The radio links must be Hybrid 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 > Hybrid/AM
Configuration from the Function Tree.
2. 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.
3. Click Apply.
Step 2 Query the 15-minute performance value of the IF board on the local NE.
1. Select the required IF board from the Object Tree in NE Explorer.
2. In the Function Tree, choose Performance > Current Performance.
3. In Monitored Object Filter Condition, select All.
4. Set Monitor Period to 15-Minute.
5. In Count, select Other Errors. In Display Options, select Consecutive Severely Errored
Seconds Second.
6. Click Query.
In performance events, the value of FEC_BEF_COR_ER should be 0.
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 > Hybrid/AM
Configuration from the Function Tree.
2. 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.
3. 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_BEF_COR_ER should be 0.
NOTE
In the case of unfavorable weather, the current modulation mode may be lower than the value of
Modulation Mode of the Full AM Capacity.
----End
B Parameters Description
Navigation Path
In NE List, click NE Search.
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.
Related Tasks
A.1.1 Creating NEs by Using the Search Method
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.
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.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.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.1.5 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.1.7 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.1.8 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.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Communication >
Communication Parameters from the Function Tree.
Related Tasks
A.3.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.
Enabled/Disabled Enabled Enabled (for line It is recommended that you use the default
Disabled ports) value, except for the following cases:
Disabled (for l If the port is connected to the other ECC
external clock subnet, Enabled/Disabled is set to
interfaces) 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 If external clock interfaces are used to
transmit the DCC solution, Enabled/
Disabled is set to Enabled for the
external clock interfaces.
Channel Type 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 over DCC or OSI over DCC
D1-D12 capacity is less than solution is adopted, Channel Type for
D1-D1 16xE1) the SDH line ports is set to a value that
D1-D3 (for other is the same as the value for third-party
cases) network.
l If the DCC transparent transmission
solution is adopted, the value of
Channel Type 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:
OSI l If the IP over DCC solution is adopted,
Protocol Type is set to TCP/IP.
l If the OSI over DCC solution is adopted,
Protocol Type is set to OSI.
Related Tasks
A.3.2 Configuring DCCs
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.3.4 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.3.3 Configuring the Extended ECC
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.3.13 Querying ECC 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.
Related Tasks
A.3.14 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.3.5 Creating Static 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 OSPF Parameter Settings tab.
OSPF Parameters
Parameter Value Range Default Value Description
DCC Hello Timer 1 to 255 1 l DCC Hello Timer(s) specifies the Hello
(s) packet timer at the DCC interface.
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.
LAN Hello Timer 1 to 255 1 l DCC Hello Timer(s) specifies the hello
(s) packet timer at the LAN interfaces.
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.
Related Tasks
A.3.6 Setting Parameters of the OSPF Protocol
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.3.7 Enabling the ARP Proxy
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.3.8 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.3.15 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.3.9 Configuring the OSI Tunnel
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 910 does not support this
(kbps) parameter.
IF Port Bandwidth - - The OptiX RTN 910 does not support this
(kbps) parameter.
Related Tasks
A.3.10 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.3.11 Configuring the Enable Status of the Inband DCN Function on Ports
Navigation Path
1. In the NE Explorer, select the required NE from the Object Tree, and then choose
Communication > DCN Management from the Function Tree.
2. Click the Protocol Settings tab.
Related Tasks
A.3.12 Configuring the Protocol Type of the Inband DCN
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Communication > Access
Control from the Function Tree.
Enable Ethernet Enabled Enabled After The First Network Port is set to
Access Disabled Enabled for Ethernet access, the NE can
access the NMS through the Ethernet port.
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.
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.5.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
ATPC Upper -85.0 to -20.0 -45.0 l The central value between the ATPC
Threshold(dBm) upper threshold and the ATPC lower
threshold is set as the expected receive
ATPC Lower -90.0 to -25.0 -70.0 power.
Threshold(dBm)
l It is recommended that you set ATPC
Upper Threshold(dBm) to the sum of
the planned central value between the
ATPC upper threshold and the ATPC
lower threshold and 10 dB, and ATPC
Lower Threshold(dBm) to the
difference between the planned central
value between the ATPC upper
threshold and the ATPC lower threshold
and 10 dB.
l You can set the ATPC upper threshold
only when ATPC Automatic
Threshold Enable Status is set to
Disabled.
Related Tasks
A.6.2 Creating an XPIC 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 XPIC tab.
ATPC Upper -85.0 to -20.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 -90.0 to -25.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) o the
difference between the planned central
value between the ATPC upper threshold
and the ATPC lower threshold and 10
dB.
l You can set this parameter only when
ATPC Automatic Threshold Enable
Status is set to Disabled.
Related Tasks
A.6.3 Setting the Hybrid/AM Attributes of the XPIC Hybrid Radio Link
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 Work Unit Work 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.6.8 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.6.13 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
Revertive Mode Revertive Mode Revertive Mode l This parameter specifies the revertive
Non-Revertive mode of the IF 1+1 protection.
Mode l When this parameter is set to Revertive
Mode, the NE that is in the switching
state releases the switching and enables
the former working channel to return to
the normal state some time after the
former working channel is restored to
normal.
l When this parameter is set to Non-
Revertive Mode, the NE that is in the
switching state keeps the current state
unchanged unless another switching
occurs even though the former working
channel is restored to normal.
l It is recommended that you set this
parameter to Revertive Mode.
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 You can set WTR Time(s) only when
Revertive Mode is set to Revertive
Mode.
l It is recommended that you use the
default value.
NOTE
Each of the parameters Working Mode, Revertive Mode, WTR Time(s), and Enable Reverse
Switching must be set to the same value at both ends of a radio hop.
Related Tasks
A.6.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.
NOTE
Each of the parameters Working Mode, Enable Reverse Switching, Revertive Mode, and WTR Time
(s) must be set to the same value at both ends of a radio hop.
Related Tasks
A.6.12 Querying the IF 1+1 Protection Status
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.
ATPC Upper -75.0 to -20.0 -45.0 l This parameter specifies the central
Threshold(dBm) value between the ATPC upper
threshold and the ATPC lower threshold
to a value for the expected receive
power.
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
ATPC Lower -35.0 to -90.0 -70.0 lower threshold and 10 dB, and ATPC
Threshold(dBm) 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.
Enable IEEE-1588 Enabled Disabled If the OptiX RTN 910 is interconnected with
Timeslot Disabled the packet radio equipment, this parameter
is set to Enabled. Otherwise, this parameter
is set to Disabled.
NOTE
This parameter is not applicable to the IF1 board.
Power to Be -90.0 to -20.0 -10.0 l This parameter is used to set the expected
Received(dBm) 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 the antenna misalignment
indicating function is enabled, if the
actual receive power of the ODU
exceeds the range of receive power±3
dB, the ODU LED of the IF board
connected to the ODU is on (yellow) for
300 ms and off for 300 ms repeatedly,
indicating that the antenna is not aligned.
l After the antenna alignment, after the
state that the antenna is aligned lasts for
30 minutes, the NE automatically
disables the antenna misalignment
indicating function.
l When this parameter takes the default
value, the antenna misalignment
indicating function is disabled.
l This parameter needs to be according to
the planning.
Equipment Information
Parameter Value Range Default Value Description
Related Tasks
A.6.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 protection
1:N 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.
Revertive Mode Non-Revertive Non-Revertive (1+1 l This parameter specifies the revertive
Revertive Protection) mode of the linear MSP.
Revertive (1:N l When this parameter is set to
Protection) Revertive, the NE that is in the
switching state releases the switching
and enables the former working channel
to return to the normal state some time
after the former working channel is
restored to normal.
l When this parameter is set to Non-
Revertive, the NE that is in the
switching state keeps the current state
unchanged unless another switching
occurs even though the former working
channel is restored to normal.
l It is recommended that you set this
parameter to Revertive.
l If the linear MSP type is set to 1:N
Protection, Revertive Mode can be set
to Revertive only.
WTR Time(s) 300 to 720 600 l This parameter specifies the WTR time.
l When the time after the former working
channel is restored to normal reaches the
preset WTR time, a revertive switching
occurs.
l You can set WTR Time(s) only when
Revertive Mode is set to Revertive.
l It is recommended that you use the
default value.
Protocol Type New Protocol New Protocol l The new protocol is supported at the
Restructure Protocol early stage, and the mainstream protocol
version is used currently.
l The restructure protocol optimizes the
new protocol and provides better
measures to protect the new protocol,
thus ensuring that the new protocol runs
in a better manner.
l The new protocol is more mature, and
the restructure protocol complies with
the standard. It is recommended that you
use the new protocol.
l You must ensure that the interconnected
NEs run the protocols of the same type.
SD/SF PRI High priority High priority (1+1 l When this parameter is set to High
Switching Tag Low priority Protection) priority, "1101" and "1011" are used as
Low priority (1:N an SF/SD switching request.
Protection) l When this parameter is set to Low
priority, "1100" and "1010" are used as
an SF/SD switching request.
Switching Mode Not indicated Not indicated (1+1 l When this parameter is set to
Indication Indicated Protection) Indicated, the MSP protocol uses K2
Indicated (1:N (bit 6 to bit 8) to indicate the switching
Protection) mode (that is, uses code "100" to indicate
the single-ended mode and code "101" to
indicate the dual-ended mode).
l When this parameter is set to Not
indicated, the MSP protocol does not
indicate the switching mode.
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.7.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.7.2 Querying the Status of the Linear MSP
Navigation Path
l Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Cross-
Connection Configuration from the Function Tree.
l Click Scheme to change the VC-12 timeslot numbering policy used by the cross-
connection.
l Click New.
Parameters
Parameter Value Range Default Value Description
Related Tasks
A.8.1 Creating the Cross-Connections of Point-to-Point Services
Navigation Path
l Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Cross-
Connection Configuration from the Function Tree.
l Click Scheme to change the VC-12 timeslot numbering policy used by the cross-
connection.
l 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.8.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.8.5 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.8.7 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.
Group Type - - The OptiX RTN 910 does not support this
parameter.
Related Tasks
A.8.3 Configuring the Automatic Switching of SNCP Services
A.8.9 Querying the Protection Status of SNCP Services
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
Physical Clock > Clock Source Priority.
2. Click the System Clock Source Priority List tab.
Parameters
Parameter Value Range Default Value Description
Related Tasks
A.9.1 Configuring the Clock Sources
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
Clock Subnet Configuration.
2. Click the Clock Subnet tab.
Protection Status Start Extended SSM Stop SSM Protocol l The SSM protocol is a
Protocol scheme used for
Start Standard SSM synchronous
Protocol management on an
SDH network and
Stop SSM Protocol indicates that the SSM
is passed by the lower
four bits of the S1 byte
and can be exchanged
between the nodes.
The SSM protocol
ensures that the
equipment
automatically selects
the clock source of the
highest quality and
highest priority, thus
preventing mutual
clock tracing.
l After the standard
SSM protocol is
started, the NE first
performs the
protection switching
on the clock source
according to the clock
quality level
information provided
by the S1 byte. If the
quality level of the
clock source is the
same, the NE then
performs the
protection switching
according to the clock
priority table. That is,
the NE selects an
unlocked clock source
that is of the highest
quality and highest
priority from all the
current available clock
sources as the clock
source to be
synchronized and
traced by the local
station.
l If the SSM protocol is
stopped, it indicates
Related Tasks
A.9.2 Configuring Clock Subnets
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
Clock Subnet Configuration.
2. Click the Clock Quality tab.
Manual Setting of 0 Do Not Use For Do Not Use For This parameter specifies
Quality Level Synchronization Synchronization the clock quality whose
G.811 Reference Clock level is manually set to
zero.
Between G.811 Reference
Clock and G.812 Transit l Do Not Use For
Clock Synchronization: the
notification
G.812 Transit Clock information in the
Between G.812 Transit reverse direction of the
Clock and G.812 Local selected
Clock synchronization clock
G.812 Local Clock source to avoid direct
mutual locking of
Between G.812 Local
adjacent NEs.
Clock and synchronous
equipment timing source l G.811 Reference
(SETS) Clock: the clock signal
specified in ITU-T G.
SETS Clock
811.
Between synchronous
l Between G.811
equipment timing source
Reference Clock and
(SETS) and quality
G.812 Transit Clock:
unavailable
lower than the quality
level of the clock
signal specified in
ITU-T G.811 but
higher than the quality
level of the transit
exchange clock signal
specified in ITU-T G.
812.
l G.812 Transit Clock:
the transit exchange
clock signal specified
in ITU-T G.812.
l Between G.812
Transit Clock and G.
812 Local Clock:
lower than the quality
level of the transit
exchange clock signal
specified in ITU-T G.
812 but higher than the
quality level of the
local exchange clock
signal specified in
ITU-T G.812.
l G.812 Local Clock:
the local exchange
Related Tasks
A.9.3 Self-Defined Clock Quality
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
Clock Subnet Configuration.
2. Click the SSM Output Control tab.
Parameters
Parameter Value Range Default Value Description
Related Tasks
A.9.4 Configuring the SSM Output Status
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
Clock Subnet Configuration.
2. Click the Clock ID Status tab.
Parameters
Parameter Value Range Default Value Description
Related Tasks
A.9.5 Configuring the Clock ID Output Status
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
Clock Source Switching.
2. Click the Clock Source Reversion Parameter tab.
Parameters
Parameter Value Range Default Value Description
Related Tasks
A.9.8 Modifying the Recovery Parameter of the Clock Source
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
Clock Source Switching.
2. Click the Clock Source Switching tab.
Parameters
Parameter Value Range Default Value Description
Navigation Path
1. In the NE Explorer, select the NE from the Object Tree and choose Configuration >
Clock > Clock Source Switching from the Function Tree.
2. Click the Clock Source Switching Condition tab.
Parameters
Parameter Value Range Default Value Description
Related Tasks
A.9.7 Changing the Conditions for Clock Source Switching
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
Phase-Locked Source Output by External Clock.
Parameters
Parameter Value Range Default Value Description
2M Phase-Locked Shut Down Output Shut Down Output l This parameter is valid
Source Fail Action 2M Output S1 Byte only when 2M Phase-
Unavailable Locked Source Fail
Condition is not set to
Send AIS No Failure
Condition.
l This parameter
specifies the operation
of the 2 Mbit/s phase-
locked loop (PLL)
when the 2 Mbit/s
phase-locked clock
source meets the
failure conditions.
l It is recommended that
you use the default
value.
Related Tasks
A.9.6 Modifying the Parameters of the Clock Output
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Clock
Synchronization Status.
Parameters
Parameter Value Range Default Value Description
Data Output Method in Normal Data Output Normal Data Output l When all the reference
Holdover Mode Mode Mode timing signals are lost,
Keep the Latest Data the slave clock
changes to the
holdover mode. At this
time, the slave clock
works based on the
latest frequency
information stored
before the reference
timing signals are lost.
Then, the frequency of
the oscillator drifts
slowly to ensure that
the offset between the
frequency of the slave
clock and the reference
frequency is very
small. As a result, the
impact caused by the
drift is limited within
the specified
requirement.
l Normal Data Output
Mode: The slave clock
works based on the
latest frequency
information stored
before the reference
timing signals are lost,
and the holdover
duration depends on
the size of the phase-
locked clock register
on the equipment. The
holdover duration can
be up to 24 hours.
l Keep the Latest Data:
The slave clock works
in holdover mode all
the time based on the
latest frequency
information stored
before the reference
timing signals are lost.
Related Tasks
A.9.9 Querying the Clock Synchronization Status
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 an Ethernet 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.
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(300 300 to 43200 900 l This parameter indicates or specifies the
to 43200 seconds, a monitoring period in Custom Period 1.
multiple of 30) l The value must be an integer multiple of
30.
Period Length(300 300 to 86400 86400 l This parameter indicates or specifies the
to 86400 seconds, a monitoring period in Custom Period 2.
multiple of 30) l The value must be an integer multiple of
30.
Related Tasks
A.11.3 Configuring a History 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 an Ethernet Port
A.11.4 Browsing the Performance Data in the History Group of an Ethernet Port
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 (Step 1: Configuring the Source and Sink Ports)
Parameter Value Range Default Value Description
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.10.3.2 Configuring the E-Line Service
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.
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 Create.
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.10.3.3 Creating a VLAN Forwarding Table Item
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 Create.
Parameters on the Main Interface (Step 1: Configuring the Source and Sink Ports)
Parameter Value Range Default Value Description
Related Tasks
A.10.3.4 Configuring the E-LAN Service
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.10.4.1 Creating a Static MAC Address Entry
A.10.4.2 Creating a Blacklist Entry of MAC Addresses
A.10.4.3 Configuring the Aging Parameters of a MAC Address Table
A.10.4.4 Querying or Deleting a Dynamic MAC Address
A.10.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 Create.
Related Tasks
A.10.3.1 Configuring the QinQ Link
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.10.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
Related Tasks
A.10.1.2 Setting the Parameters of Ethernet Ring Protocol
A.10.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. The Create Port Group dialog box is displayed.
Related Tasks
A.10.8.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 Configure Port Group dialog box is displayed.
Related Tasks
A.10.8.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.10.8.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.10.8.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.10.8.4 Querying the CIST Running Information
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protocol Configuration > IGMP Snooping Configuration from the Function Tree.
2. Click the Protocol Configuration tab.
Related Tasks
A.10.9.1 Configuring the IGMP Snooping Protocol
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protocol Configuration > IGMP Snooping Configuration from the Function Tree.
2. Click the Protocol Configuration tab.
3. Click Add.
Related Tasks
A.10.9.6 Adding a Quickly Deleted Port
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protocol Configuration > IGMP Snooping Configuration from the Function Tree.
2. Click the Router Port Management tab.
Related Tasks
A.10.9.2 Querying the Port Information of the Routers
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protocol Configuration > IGMP Snooping Configuration from the Function Tree.
2. Click the Router Management tab.
3.
4. Click New.
Related Tasks
A.10.9.4 Creating Static Router Ports
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protocol Configuration > IGMP Snooping Configuration from the Function Tree.
2. Click the Route Member Port Management tab.
Related Tasks
A.10.9.3 Querying the Information About the Multicast Groups
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protocol Configuration > IGMP Snooping Configuration from the Function Tree.
2. Click the Route Member Port Management tab.
3. Click New.
Related Tasks
A.10.9.5 Creating a Member of a Static Multicast Group
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protocol Configuration > IGMP Snooping Configuration from the Function Tree.
2. Click the Packet Statistics tab.
Related Tasks
A.10.9.7 Calculating IGMP Packets
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.10.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.
Load Sharing Hash Source MAC Source MAC l This parameter is valid
Algorithm Destination MAC only when Load
Sharing of a LAG is
Source and Destination set to Sharing.
MAC
l The load sharing
Source IP computation methods
Destination IP include: MAC address
Source and Destination IP specific allocation
(based on the source
MAC address,
destination MAC
address, and XOR
between source MAC
address and source
MAC address), IP
address specific
allocation (based on
the source IP address,
destination IP address,
and XOR between
source IP address and
source IP address).
Related Tasks
A.10.2.2 Setting Parameters for LAGs
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT
Management from the Function Tree.
2. Click New.
Related Tasks
A.10.13 LPT Configuration
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Port
Mirroring from the Function Tree.
2. Click New. The Port Mirror Management dialog box is displayed.
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.10.11.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.10.11.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 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.10.11.3 Creating an MEP Point
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 OAM > Manage Remote MEP Point. Then, the Manage Remote MEP Point
dialog box is displayed.
4. Click New.
Related Tasks
A.10.11.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.10.11.5 Creating an MIP
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.10.11.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.10.11.8 Performing an LT Test
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.10.12.1 Enabling the OAM Auto-Discovery Function
A.10.12.2 Enabling the Link Event Notification
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.10.12.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 from the Function Tree.
NOTE
If one default DiffServ domain exists on the OptiX RTN 910 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 the domain.
The default DiffServ domain cannot be modified or deleted. You can only change Packet Type of a port.
Related Tasks
A.10.10.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 from the Function Tree.
2. Click New.
NOTE
If one default DS domain exists on the OptiX RTN equipment, Mapping Relation ID is set to 1, Mapping
Relation Name is set to Default Map. If these parameters are not set, all the ports belong to the domain. The
default DS domain cannot be modified and deleted.
Related Tasks
A.10.10.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 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 910, 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 the domain. The port applied
to the default DS domain cannot be modified.
Related Tasks
A.10.10.3 Changing the Ports That Use the DS Domain
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Policy Management from the Function Tree.
Parameters
Parameter Value Range Default Value Description
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 910
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).
Related Tasks
A.10.10.7 Setting the Port That Uses the Port Policy
A.10.10.9 Querying the Port Policy
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Policy Management from the Function Tree.
2. Click the CoS Queue Configuration tab.
3. Click New. The Create Port Policy dialog box is displayed.
Parameters
Parameter Value Range Default Value Description
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 910
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).
Related Tasks
A.10.10.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 from the Function Tree.
2. Click the Traffic Classification Configuration tab.
3. Click New. The Create Traffic Classification dialog box is displayed.
Ingress Parameters
Parameter Value Range Default Value Description
Egress Parameters
Parameter Value Range Default Value Description
Related Tasks
A.10.10.6 Creating the 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.10.10.8 Configuring Port Shaping
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 General Attributes tab.
Related Tasks
A.10.6.1 Setting the General 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.10.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.
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.10.6.3 Setting the Layer 2 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.10.6.4 Setting the Advanced Attributes of Ethernet Ports
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Orderwire from the Function Tree.
2. Click the General tab.
Parameters
Parameter Value Range Default Value Description
Dialling Mode Pulse Dual-Tone This parameter indicates the dialling mode
Dual-Tone Frequency of the orderwire phone.
Frequency
Related Tasks
A.16.1 Configuring the Orderwire
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Orderwire from the Function Tree.
2. Click the Advanced tab.
Related Tasks
A.16.1 Configuring the Orderwire
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Orderwire from the Function Tree.
2. Click the F1 Data Port tab.
Parameters
Parameter Value Range Default Value Description
Related Tasks
A.16.2 Configuring the Synchronous Data Service
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Orderwire from the Function Tree.
2. Click the Broadcast Data Port tab.
Related Tasks
A.16.3 Configuring the Asynchronous Data Service
Navigation Path
Select the AUX logical board from the Object Tree in the NE Explorer. Choose
Configuration > Environment Monitor Configuration > Environment Monitor Interface
from the Function Tree.
Relay Control Auto Control Auto Control l Auto Control: If an alarm is reported, the
Mode Manual Control alarming relay is started up
automatically. Otherwise, the alarming
relay is shut down.
l Manual Control: Relay Status in Major
Alarm(K0) and Relay Status in
Critical Alarm(K1) need to be set.
Relay Status in Disabled Disabled l This parameter indicates that the status
Major Alarm(K0) Enabled of the relay is set manually for major
alarms.
l Enable: The relay is set to the "0N" status
for major alarms.
l Disabled: The relay is set to the "OFF"
status for major alarms.
l This parameter is valid only when Relay
Control Mode is set to Manual
Control.
Relay Status in Disabled Disabled l This parameter indicates that the status
Critical Alarm(K1) Enabled of the relay is set manually for critical
alarms.
l Enable: The relay is set to the enabled
status for critical alarms.
l Disabled: The relay is set to the disabled
status for critical alarms.
l This parameter is valid only when Relay
Control Mode is set to Manual
Control.
3rd Auxiliary Disabled Disabled This parameter specifies whether the third
Alarm Output Enabled auxiliary alarm output is enabled.
Using Status Unused Unused This parameter specifies whether the alarm
Used interface of the input relay is used.
Alarm Mode Relay Turns Off/ Relay Turns Off/ l If this parameter is set to Relay Turns
High Level High Level Off/High Level, an alarm is generated
Relay Turns On/ when the relay is turned off.
Low Level l If this parameter is set to Relay Turns
On/Low Level, an alarm is generated
when the relay is turned on.
l This parameter is valid only when Using
Status is set to Used.
Alarm Severity Critical Alarm Critical Alarm This parameter specifies the severity of the
Major Alarm alarm that is generated at the input relay.
Minor Alarm
Warning Alarm
Related Tasks
A.16.5 Configure External Alarms
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
Enable IEEE-1588 Enabled Disabled If the OptiX RTN 910 is interconnected with
Timeslotc Disabled the packet radio equipment, this parameter
should be set to Enabled. Otherwise, this
parameter should be set to Disabled.
NOTE
l a. The IFU2 and IFX2 boards do not support the 2M wayside service.
l b. The IFU2 and IF1 boards do not support the XPIC function.
l c. The IF1 board does not support the IEEE-1588 timeslot function.
Related Tasks
A.6.5 Setting IF Attributes
A.16.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 -85.0 to -20.0 -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 -90.0 to -25.0 -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.6 Configuring the ATPC Attributes
Navigation Path
l In the NE Explorer, select a Hybrid IF board from the Object Tree and then choose
Configuration > Hybrid/AM Configuration from the Function Tree.
l Click the Hybrid/AM Configuration tab.
Parameters
Parameter Value Range Default Value Description
AM Enable Status Disable Disable l When this parameter is set to Disable, the
Enable radio link uses only the specified
modulation scheme. In this case, you
need to select Manually Specified
Modulation Mode.
l When this parameter is set to Enable, the
radio link uses the corresponding
modulation scheme according to the
channel conditions.
Hence, the Hybrid radio can ensure the
reliable transmission of the E1 services and
provide bandwidth adaptively for the
Ethernet services when the AM function is
enabled.
Related Tasks
A.6.7 Setting the Hybrid/AM Attributes
A.6.11 Querying the AM Status
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.9 Querying the 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.12.1 Setting the Transmit Frequency Attribute of the ODU
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
Power to Be -90.0 to -20.0 -10.0 l This parameter is used to set the expected
Received(dBm) 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 the antenna misalignment
indicating function is enabled, if the
actual receive power of the ODU is 3 dB
lower than the power expected to be
received, the ODU LED of the IF board
connected to the ODU is on (yellow) for
300 ms and off for 300 ms repeatedly,
indicating that the antenna is not aligned.
l After the antenna alignment, after the
state that the antenna is aligned lasts for
30 minutes, the NE automatically
disables the antenna misalignment
indicating function.
l When this parameter takes the default
value, the antenna misalignment
indicating function is disabled.
l This parameter is set according to the
planning information.
Related Tasks
A.12.3 Setting the Power Attributes of the ODU
Navigation Path
l Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > ODU Interface from the Function Tree.
Parameters
Parameter Value Range Default Value Description
Related Tasks
A.12.2 Querying the ODU Attribute
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.12.4 Setting the Advanced Attributes of the ODU
Navigation Path
l Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > SDH Interface from the Function Tree.
l 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.13 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
l Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > PDH Interface from the Function Tree.
l Select By Board/Port(Channel).
l Select Path from the list box.
Parameters
Parameter Value Range Default Value Description
Related Tasks
A.14 Setting the Parameters of PDH 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 General Attributes tab.
Parameters
Parameter Value Range Default Value Description
Related Tasks
A.10.7.1 Setting the General Attributes of the IF_ETH Port
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.
Tag Tag Aware Tag Aware l This parameter specifies the TAG flag of
Access a port. For details about the TAG flags
and associated frame-processing
Hybrid methods, see Table B-2.
l If all the accessed services are frames
that contain the VLAN tag (tagged
frames), set this parameter to "Tag
Aware".
l If all the accessed services are frames
that do not contain the VLAN tag
(untagged frames), set this parameter to
"Access".
l If the accessed services contain tagged
frames and untagged frames, set this
parameter to "Hybrid".
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.10.7.2 Setting the Layer 2 Attributes of the IF_ETH Port
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.
PHY Loopback Non-Loopback Non-Loopback The IF port on the OptiX RTN 910 does not
support the setting of this parameter.
Related Tasks
A.10.7.3 Setting the Advanced Attributes of the IF_ETH Port
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.15.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.15.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.15.3 Configuring VC-12 POHs
C Glossary
C.1 0-9
This section provides the terms starting with numbers.
C.2 A-E
This section provides the terms starting with letters A to E.
C.3 F-J
This section provides the terms starting with letters F to J.
C.4 K-O
This section provides the terms starting with letters K to O.
C.5 P-T
This section provides the terms starting with letters P to T.
C.6 U-Z
This section provides the terms starting with letters U to Z.
C.1 0-9
This section provides the terms starting with numbers.
1U The standard electronics industries association (EIA) rack unit (44 mm/1.75 in.)
C.2 A-E
This section provides the terms starting with letters A to E.
B
backward defect When detecting a defect, the sink node of an LSP uses backward defect indication (BDI)
indication to inform the upstream end of the LSP of a downstream defect along the return path.
bandwidth A range of transmission frequencies that a transmission line or channel can carry in a
network. In fact, it is the difference between the highest and lowest frequencies the
transmission line or channel. The greater the bandwidth, the faster the data transfer rate.
base station controller A logical entity that connects the BTS with the MSC in a GSM network. It interworks
with the BTS through the Abis interface, the MSC through the A interface. It provides
the following functions: radio resource management, base station management, power
control, handover control, and traffic measurement. One BSC controls and manages one
or more BTSs in an actual network.
base transceiver station A Base Transceiver Station terminates the radio interface. It allows transmission of traffic
and signaling across the air interface. The BTS includes the baseband processing, radio
equipment, and the antenna.
basic input/output A firmware stored in the computer mainboard. It contains basic input/output control
system programs, power-on self test (POST) programs, bootstraps, and system setting
information. The BIOS provides hardware setting and control functions for the computer.
BDI See backward defect indication
BE See best effort
BER See bit error rate
best effort A traditional IP packet transport service. In this service, the diagrams are forwarded
following the sequence of the time they reach. All diagrams share the bandwidth of the
network and routers. The amount of resource that a diagram can use depends of the time
it reaches. BE service does not ensure any improvement in delay time, jitter, packet loss
ratio, and high reliability.
binding strap The binding strap is 12.7 mm wide, with one hook side (made of transparent
polypropylene material) and one mat side (made of black nylon material).
BIOS See basic input/output system
BIP See bit interleaved parity
bit error An incompatibility between a bit in a transmitted digital signal and the corresponding
bit in the received digital signal.
bit error rate Ratio of received bits that contain errors. BER is an important index used to measure the
communications quality of a network.
bit interleaved parity A method of error monitoring. With even parity an X-bit code is generated by the
transmitting equipment over a specified portion of the signal in such a manner that the
first bit of the code provides even parity over the first bit of all X-bit sequences in the
covered portion of the signal, the second bit provides even parity over the second bit of
all X-bit sequences within the specified portion, etc. Even parity is generated by setting
the BIP-X bits so that there is an even number of 1s in each monitored partition of the
signal. A monitored partition comprises all bits which are in the same bit position within
the X-bit sequences in the covered portion of the signal. The covered portion includes
the BIP-X.
BPDU See bridge protocol data unit
bridge protocol data The data messages that are exchanged across the switches within an extended LAN that
unit uses a spanning tree protocol (STP) topology. BPDU packets contain information on
ports, addresses, priorities and costs and ensure that the data ends up where it was
intended to go. BPDU messages are exchanged across bridges to detect loops in a
network topology. The loops are then removed by shutting down selected bridges
interfaces and placing redundant switch ports in a backup, or blocked, state.
broadcast A means of delivering information to all members in a network. The broadcast range is
determined by the broadcast address.
BSC See base station controller
BTS See base transceiver station
buffer A storage area used for handling data in transit. Buffers are used in internetworking to
compensate for differences in processing speed between network devices. Bursts of data
can be stored in buffers until they can be handled by slower processing devices. In a
program, buffers are created to hold some amount of data from each of the files that will
be read or written. In a streaming media application, the program uses buffers to store
an advance supply of audio or video data to compensate for momentary delays.
C
cable tie The tape used to bind the cables.
cable tray N/A
cable trough N/A
CAR See committed access rate
CBR See constant bit rate
CBS See committed burst size
CC See connectivity check
CCC See circuit cross connect
CCDP See co-channel dual polarization
CCM See continuity check message
CE See customer edge
central processing unit The computational and control unit of a computer. The CPU is the device that interprets
and executes instructions. The CPU has the ability to fetch, decode, and execute
instructions and to transfer information to and from other resources over the computer's
main data-transfer path, the bus.
CES See circuit emulation service
CF See compact flash
CGMP See Cisco Group Management Protocol
channel A telecommunication path of a specific capacity and/or at a specific speed between two
or more locations in a network. The channel can be established through wire, radio
(microwave), fiber or a combination of the three. The amount of information transmitted
per second in a channel is the information transmission speed, expressed in bits per
second. For example, b/s (100 bit/s), kb/s (103 bit/s), Mb/s (106 bit/s), Gb/s (109 bit/s),
and Tb/s (1012 bit/s).
constant bit rate A kind of service categories defined by the ATM forum. CBR transfers cells based on
the constant bandwidth. It is applicable to service connections that depend on precise
clocking to ensure undistorted transmission.
continuity check CCM is used to detect the link status.
message
corrugated pipe Used to protect optical fibers.
CPU See central processing unit
CRC See cyclic redundancy check
cross polarization A technology used in the case of the Co-Channel Dual Polarization (CCDP) to eliminate
interference the cross-connect interference between two polarization waves in the CCDP.
cancellation
customer edge A part of BGP/MPLS IP VPN model. It provides interfaces for direct connection to the
Service Provider (SP) network. A CE can be a router, switch, or host.
CWDM See coarse wavelength division multiplexing
cyclic redundancy A procedure used in checking for errors in data transmission. CRC error checking uses
check a complex calculation to generate a number based on the data transmitted. The sending
device performs the calculation before transmission and includes it in the packet that it
sends to the receiving device. The receiving device repeats the same calculation after
transmission. If both devices obtain the same result, it is assumed that the transmission
was error free. The procedure is known as a redundancy check because each transmission
includes not only data but extra (redundant) error-checking values.
D
data communication A communication network used in a TMN or between TMNs to support the Data
network Communication Function (DCF).
data communications The data channel that uses the D1-D12 bytes in the overhead of an STM-N signal to
channel transmit information on operation, management, maintenance and provision (OAM&P)
between NEs. The DCC channels that are composed of bytes D1-D3 is referred to as the
192 kbit/s DCC-R channel. The other DCC channel that are composed of bytes D4-D12
is referred to as the 576 kbit/s DCC-M channel.
Datagram A kind of PDU which is used in Connectionless Network Protocol, such as IP datagram,
UDP datagram.
DC See direct current
DC-C See DC-return common (with ground)
DC-C DC-return common (with ground)
DC-C See DC-return common (with ground)
DC-I See DC-return isolate (with ground)
DC-return common A power system, in which the BGND of the DC return conductor is short-circuited with
(with ground) the PGND on the output side of the power supply cabinet and also on the line between
the output of the power supply cabinet and the electric equipment.
DC-return common A power system, in which the BGND of the DC return conductor is short-circuited with
(with ground) the PGND on the output side of the power supply cabinet and also on the line between
the output of the power supply cabinet and the electric equipment.
DC-return isolate (with A power system, in which the BGND of the DC return conductor is short-circuited with
ground) the PGND on the output side of the power supply cabinet and is isolated from the PGND
on the line between the output of the power supply cabinet and the electric equipment.
DCC See data communications channel
DCN See data communication network
DDF See digital distribution frame
DDN See digital data network
DE See discard eligible
differentiated services A service architecture that provides the end-to-end QoS function. It consists of a series
of functional units implemented at the network nodes, including a small group of per-
hop forwarding behaviors, packet classification functions, and traffic conditioning
functions such as metering, marking, shaping and policing.
differentiated services A marker in the header of each IP packet that prompts network routers to apply
code point differentiated grades of service to various packet streams. It is specified by the DiffServ
policy proposed by the IETF (Internet Engineering Task Force). This allows Internet and
other IP-based network service providers to offer different levels of service to customers.
DiffServ See differentiated services
digital data network A high-quality data transport tunnel that combines the digital channel (such as fiber
channel, digital microwave channel, or satellite channel) and the cross multiplex
technology.
digital distribution A type of equipment used between the transmission equipment and the exchange with
frame transmission rate of 2 to 155 Mbit/s to provide the functions such as cables connection,
cable patching, and test of loops that transmitting digital signals.
digital modulation A digital modulation controls the changes in amplitude, phase, and frequency of the
carrier based on the changes in the baseband digital signal. In this manner, the
information can be transmitted by the carrier.
direct current Electrical current whose direction of flow does not reverse. The current may stop or
change amplitude, but it always flows in the same direction.
discard eligible A bit in the frame relay header. It indicates the priority of a packet. If a node supports
the FR QoS, the rate of the accessed FR packets is controlled. When the packet traffic
exceeds the specified traffic, the DE value of the redundant packets is set to 1. In the
case of network congestion, the packets with DE value as 1 are discarded at the node.
Distance Vector An Internet gateway protocol mainly based on the RIP. The protocol implements a typical
Multicast Routing dense mode IP multicast solution. The DVMRP protocol uses IGMP to exchange routing
Protocol datagrams with its neighbors.
DS boundary node A DS node that connects one DS domain to a node either in another DS domain or in a
domain that is not DS-capable.
DS domain In the DifferServ mechanism, the DS domain is a domain consisting of a group of
network nodes that share the same service provisioning policy and same PHB. It provides
point-to-point QoS guarantees for services transmitted over this domain.
DS interior node A DS node located at the center of a DS domain. It is a non-DS boundary node.
DS node A DS-compliant node, which is subdivided into DS boundary node and ID interior node.
DSCP See differentiated services code point
dual-polarized antenna An antenna intended to radiate or receive simultaneously two independent radio waves
orthogonally polarized.
DVMRP See Distance Vector Multicast Routing Protocol
E
E-Aggr See Ethernet aggregation
E-LAN See Ethernet LAN
E-Line See Ethernet line
E-Tree See Ethernet-tree
EBS See excess burst size
ECC See embedded control channel
EF See expedited forwarding
electromagnetic Electromagnetic compatibility is the condition which prevails when telecommunications
compatibility equipment is performing its individually designed function in a common electromagnetic
environment without causing or suffering unacceptable degradation due to unintentional
electromagnetic interference to or from other equipment in the same environment.
electromagnetic Any electromagnetic disturbance that interrupts, obstructs, or otherwise degrades or
interference limits the effective performance of electronics/electrical equipment.
electrostatic discharge The sudden and momentary electric current that flows between two objects at different
electrical potentials caused by direct contact or induced by an electrostatic field.
embedded control A logical channel that uses a data communications channel (DCC) as its physical layer,
channel to enable transmission of operation, administration, and maintenance (OAM)
information between NEs.
EMC See electromagnetic compatibility
EMI See electromagnetic interference
Engineering label A mark on a cable, a subrack, or a cabinet for identification.
EPL See Ethernet private line
EPLAN See Ethernet private LAN service
equalization A method of avoiding selective fading of frequencies. Equalization can compensate for
the changes of amplitude frequency caused by frequency selective fading.
ERPS See Ethernet ring protection switching
ESD See electrostatic discharge
ESD jack Electrostatic discharge jack. A hole in the cabinet or shelf, which connect the shelf or
cabinet to the insertion of ESD wrist strap.
Ethernet A technology complemented in LAN. It adopts Carrier Sense Multiple Access/Collision
Detection. The speed of an Ethernet interface can be 10 Mbit/s, 100 Mbit/s, 1000 Mbit/
s or 10000 Mbit/s. The Ethernet network features high reliability and easy maintaining.
Ethernet A technology complemented in LAN. It adopts Carrier Sense Multiple Access/Collision
Detection. The speed of an Ethernet interface can be 10 Mbit/s, 100 Mbit/s, 1000 Mbit/
s or 10000 Mbit/s. The Ethernet network features high reliability and easy maintaining..
Ethernet aggregation A type of Ethernet service that is based on a multipoint-to-point EVC (Ethernet virtual
connection).
Ethernet LAN A type of Ethernet service that is based on a multipoint-to-multipoint EVC (Ethernet
virtual connection).
Ethernet line A type of Ethernet service that is based on a point-to-point EVC (Ethernet virtual
connection).
Ethernet private LAN An Ethernet service type, which carries Ethernet characteristic information over a
service dedicated bridge, point-to-multipoint connections, provided by SDH, PDH, ATM, or
MPLS server layer networks.
Ethernet private line A type of Ethernet service that is provided with dedicated bandwidth and point-to-point
connections on an SDH, PDH, ATM, or MPLS server layer network.
Ethernet ring protection switching mechanisms for ETH layer Ethernet ring topologies.
protection switching
Ethernet virtual An Ethernet service type, which carries Ethernet characteristic information over a shared
private LAN service bridge, point-to-multipoint connections, provided by SDH, PDH, ATM, or MPLS server
layer networks.
Ethernet virtual An Ethernet service type, which carries Ethernet characteristic information over shared
private line bandwidth, point-to-point connections, provided by SDH, PDH, ATM, or MPLS server
layer networks.
Ethernet-tree An Ethernet service type that is based on a Point-to-multipoint Ethernet Virtual
Connection.
ETS European Telecommunication Standards
ETSI See European Telecommunications Standards Institute
European A standards-setting body in Europe. Also the standards body responsible for GSM.
Telecommunications
Standards Institute
EVPL See Ethernet virtual private line
EVPLAN See Ethernet virtual private LAN service
excess burst size A parameter related to traffic. In the single rate three color marker (srTCM) mode, the
traffic control is achieved by the token buckets C and E. Excess burst size is a parameter
used to define the capacity of token bucket E, that is, the maximum burst IP packet size
when the information is transferred at the committed information rate. This parameter
must be larger than 0. It is recommended that this parameter should be not less than the
maximum length of the IP packet that might be forwarded.
Exercise Switching An operation to check if the protection switching protocol functions normally. The
protection switching is not really performed.
expansion Connecting a storage system to more disk enclosures through connection cables, thus
expanding the capacity of the storage system.
expedited forwarding The highest order QoS in the Diff-Serv network. EF PHB is suitable for services that
demand low packet loss ratio, short delay, and broad bandwidth. In all the cases, EF
traffic can guarantee a transmission rate equal to or faster than the set rate. The DSCP
value of EF PHB is "101110".
C.3 F-J
This section provides the terms starting with letters F to J.
failure If the fault persists long enough to consider the ability of an item with a required function
to be terminated. The item may be considered as having failed; a fault has now been
detected.
fast Ethernet Any network that supports transmission rate of 100Mbits/s. The Fast Ethernet is 10 times
faster than 10BaseT, and inherits frame format, MAC addressing scheme, MTU, and so
on. Fast Ethernet is extended from the IEEE802.3 standard, and it uses the following
three types of transmission media: 100BASE-T4 (4 pairs of phone twisted-pair cables),
100BASE-TX (2 pairs of data twisted-pair cables), and 100BASE-FX (2-core optical
fibers).
fast link pulse The link pulse that is used to encode information during automatic negotiation.
FD See frequency diversity
FDI See forward defect indication
FE See fast Ethernet
FEC See forward error correction
FFD fast failure detection
fiber patch cord A kind of fiber used for connections between the subrack and the ODF, and for
connections between subracks or inside a subrack.
field programmable A type of semi-customized circuit used in the Application Specific Integrated Circuit
gate array (ASIC) field. It is developed on the basis of the programmable components, such as the
PAL, GAL, and EPLD. It not only remedies the defects of customized circuits, but also
overcomes the disadvantage of the original programmable components in terms of the
limited number of gate arrays.
FIFO See First in First out
File Transfer Protocol A member of the TCP/IP suite of protocols, used to copy files between two computers
on the Internet. Both computers must support their respective FTP roles: one must be an
FTP client and the other an FTP server.
First in First out A stack management mechanism. The first saved data is first read and invoked.
Forced switch For normal traffic signals, switches normal traffic signal to the protection section, unless
an equal or higher priority switch command is in effect or SF condition exists on the
protection section, by issuing a forced switch request for that traffic signal.
forward defect Forward defect indication (FDI) is generated and traced forward to the sink node of the
indication LSP by the node that first detects defects. It includes fields to indicate the nature of the
defect and its location. Its primary purpose is to suppress alarms being raised at affected
higher level client LSPs and (in turn) their client layers.
forward error A bit error correction technology that adds the correction information to the payload at
correction the transmit end. Based on the correction information, the bit errors generated during
transmission are corrected at the receive end.
Forwarding plane Also referred to as the data plane. The forwarding plane is connection-oriented, and can
be used in Layer 2 networks such as an ATM network.
FPGA See field programmable gate array
fragment Piece of a larger packet that has been broken down to smaller units.
Fragmentation Process of breaking a packet into smaller units when transmitting over a network medium
that cannot support the original size of the packet.
frame A frame, starting with a header, is a string of bytes with a specified length. Frame length
is represented by the sampling circle or the total number of bytes sampled during a circle.
A header comprises one or a number of bytes with pre-specified values. In other words,
a header is a code segment that reflects the distribution (diagram) of the elements pre-
specified by the sending and receiving parties.
frequency diversity A diversity scheme that enables two or more microwave frequencies with a certain
frequency interval are used to transmit/receive the same signal and selection is then
performed between the two signals to ease the impact of fading.
FTP See File Transfer Protocol
full-duplex A full-duplex, or sometimes double-duplex system, allows communication in both
directions, and, unlike half-duplex, allows this to happen simultaneously. Land-line
telephone networks are full-duplex, since they allow both callers to speak and be heard
at the same time. A good analogy for a full-duplex system would be a two-lane road with
one lane for each direction.
G
gateway network A network element that is used for communication between the NE application layer and
element the NM application layer
GE See gigabit Ethernet
generic framing A framing and encapsulated method which can be applied to any data type. It has been
procedure standardized by ITU-T SG15.
generic traffic shaping A traffic control measure that initiatively adjusts the output speed of the traffic. This is
to adapt the traffic to network resources that can be provided by the downstream router
to avoid packet discarding and congestion.
GFP See generic framing procedure
gigabit Ethernet GE adopts the IEEE 802.3z. GE is compatible with 10 Mbit/s and 100 Mbit/s Ethernet.
It runs at 1000 Mbit/s. Gigabit Ethernet uses a private medium, and it does not support
coaxial cables or other cables. It also supports the channels in the bandwidth mode. If
Gigabit Ethernet is, however, deployed to be the private bandwidth system with a bridge
(switch) or a router as the center, it gives full play to the performance and the bandwidth.
In the network structure, Gigabit Ethernet uses full duplex links that are private, causing
the length of the links to be sufficient for backbone applications in a building and campus.
Global Positioning A global navigation satellite system. It provides reliable positioning, navigation, and
System timing services to worldwide users.
GNE See gateway network element
GPS See Global Positioning System
graphical user interface A visual computer environment that represents programs, files, and options with
graphical images, such as icons, menus, and dialog boxes, on the screen.
GTS See generic traffic shaping
GUI See graphical user interface
guide rail Components to guide, position, and support plug-in boards.
H
HA See high availability
half-duplex A transmitting mode in which a half-duplex system provides for communication in both
directions, but only one direction at a time (not simultaneously). Typically, once a party
begins receiving a signal, it must wait for the transmitter to stop transmitting, before
replying.
HDLC See high level data link control
hierarchical quality of A type of QoS that can control the traffic of users, and perform the scheduling according
service to the priority of user services. HQoS has a perfect traffic statistics function, and the
administrator can monitor the usage of bandwidth of each service. Hence, the bandwidth
can be allocated reasonably through traffic analysis.
high availability Typically, a scheme in which two modules operate in active/standby mode to achieve
high availability. When the active module fails, the standby module automatically takes
over the system functions of the active module.
high level data link The HDLC protocol is a general purpose protocol which operates at the data link layer
control of the OSI reference model. Each piece of data is encapsulated in an HDLC frame by
adding a trailer and a header.
High Speed Downlink A modulating-demodulating algorithm put forward in 3GPP R5 to meet the requirement
Packet Access for asymmetric uplink and downlink transmission of data services. It enables the
maximum downlink data service rate to reach 14.4 Mbit/s without changing the
WCDMA network topology.
higher order path In an SDH network, the higher order path layers provide a server network from the lower
order path layers.
Hold priority The priority of the tunnel with respect to holding resources, ranging from 0 (indicates
the highest priority) to 7. It is used to determine whether the resources occupied by the
tunnel can be preempted by other tunnels.
hop A network connection between two distant nodes. For Internet operation a hop represents
a small step on the route from one main computer to another.
hot standby A mechanism of ensuring device running security. The environment variables and
storage information of each running device are synchronized to the standby device. When
the faults occur on the running device, the standby device can take over the services in
the faulty device in automatic or manual way to ensure the normal running of the entire
system.
HP See higher order path
HQoS See hierarchical quality of service
HSB See hot standby
HSDPA See High Speed Downlink Packet Access
I
ICMP See Internet Control Message Protocol
IDU See indoor unit
IEC See International Electrotechnical Commission
IEEE See Institute of Electrical and Electronics Engineers
IETF See Internet Engineering Task Force
IF See intermediate frequency
IGMP See Internet Group Management Protocol
IGMP snooping A multicast constraint mechanism running on a layer 2 device. This protocol manages
and controls the multicast group by listening to and analyze the Internet Group
Management Protocol (IGMP) packet between hosts and layer 3 devices. In this manner,
the spread of the multicast data on layer 2 network can be prevented efficiently.
IMA See inverse multiplexing over ATM
indoor unit The indoor unit of the split-structured radio equipment. It implements accessing,
multiplexing/demultiplexing, and IF processing for services.
Inloop A method of looping the signals from the cross-connect unit back to the cross-connect
unit.
Institute of Electrical A society of engineering and electronics professionals based in the United States but
and Electronics boasting membership from numerous other countries. The IEEE focuses on electrical,
Engineers electronics, computer engineering, and science-related matters.
intermediate frequency The transitional frequency between the frequencies of a modulated signal and an RF
signal.
Intermediate System The basic unit in the IS-IS protocol used to transmit routing information and generate
routes.
Intermediate System to A protocol used by network devices (routers) to determine the best way to forward
Intermediate System datagrams or packets through a packet-based network, a process called routing.
routing protocol
internal spanning tree A segment of CIST in a certain MST region. An IST is a special MSTI whose ID is 0.
International The International Electrotechnical Commission (IEC) is an international and non-
Electrotechnical governmental standards organization dealing with electrical and electronic standards.
Commission
International An international association that works to establish global standards for communications
Organization for and information exchange. Primary among its accomplishments is the widely accepted
Standardization ISO/OSI reference model, which defines standards for the interaction of computers
connected by communications networks.
J
Jitter Short waveform variations caused by vibration, voltage fluctuations, and control system
instability.
C.4 K-O
This section provides the terms starting with letters K to O.
L
L2VPN See Layer 2 virtual private network
label switched path A sequence of hops (R0...Rn) in which a packet travels from R0 to Rn through label
switching mechanisms. A label-switched path can be chosen dynamically, based on
normal routing mechanisms, or through configuration.
label switching router Basic element of MPLS network. All LSRs support the MPLS protocol. The LSR is
composed of two parts: control unit and forwarding unit. The former is responsible for
allocating the label, selecting the route, creating the label forwarding table, creating and
removing the label switch path; the latter forwards the labels according to groups
received in the label forwarding table.
LACP See Link Aggregation Control Protocol
LAG See link aggregation group
LAN See local area network
LAN See local area network
LAPS link access protocol-SDH
Laser A component that generates directional optical waves of narrow wavelengths. The laser
light has better coherence than ordinary light. The fiber system takes the semi-conductor
laser as the light source.
layer 2 switch A data forwarding method. In LAN, a network bridge or 802.3 Ethernet switch transmits
and distributes packet data based on the MAC address. Since the MAC address is the
second layer of the OSI model, this data forwarding method is called layer 2 switch.
Layer 2 virtual private A virtual private network achieved by Layer 2 switching technologies in the packet
network switched (IP/MPLS) network.
LB See loopback
LCAS See link capacity adjustment scheme
LCT local craft terminal
line rate The maximum packet forwarding capacity on a cable. The value of line rate equals the
maximum transmission rate capable on a given type of media.
line rate forwarding The line rate equals the maximum transmission rate capable on a given type of media.
Link Aggregation A method of bundling a group of physical interfaces together as a logical interface to
Control Protocol increase bandwidth and reliability. For related protocols and standards, refer to IEEE
802.3ad.
link aggregation group An aggregation that allows one or more links to be aggregated together to form a link
aggregation group so that a MAC client can treat the link aggregation group as if it were
a single link.
link capacity LCAS in the virtual concatenation source and sink adaptation functions provides a
adjustment scheme control mechanism to hitlessly increase or decrease the capacity of a link to meet the
bandwidth needs of the application. It also provides a means of removing member links
that have experienced failure. The LCAS assumes that in cases of capacity initiation,
increases or decreases, the construction or destruction of the end-to-end path is the
responsibility of the Network and Element Management Systems.
Link Protection Protection provided by the bypass tunnel for the link on the working tunnel. The link is
a downstream link adjacent to the PLR. When the PLR fails to provide node protection,
the link protection should be provided.
LMSP linear multiplex section protection
local area network A network formed by the computers and workstations within the coverage of a few square
kilometers or within a single building. It features high speed and low error rate. Ethernet,
FDDI, and Token Ring are three technologies used to implement a LAN. Current LANs
are generally based on switched Ethernet or Wi-Fi technology and running at 1,000 Mbit/
s (that is, 1 Gbit/s).
local area network A network formed by the computers and workstations within the coverage of a few square
kilometers or within a single building. It features high speed and low error rate. Ethernet,
FDDI, and Token Ring are three technologies used to implement a LAN. Current LANs
are generally based on switched Ethernet or Wi-Fi technology and running at 1,000 Mbit/
s (that is, 1 Gbit/s).
Locked switching When the switching condition is satisfied, this function disables the service from being
switched from the working channel to the protection channel. When the service has been
switched, the function enables the service to be restored from the protection channel to
the working channel.
LOF See Loss Of Frame
LOM loss of multiframe
loopback A troubleshooting technique that returns a transmitted signal to its source so that the
signal or message can be analyzed for errors.
LOP See loss of pointer
LOS See Loss Of Signal
Loss Of Frame A condition at the receiver or a maintenance signal transmitted in the PHY overhead
indicating that the receiving equipment has lost frame delineation. This is used to monitor
the performance of the PHY layer.
loss of pointer Loss of Pointer: A condition at the receiver or a maintenance signal transmitted in the
PHY overhead indicating that the receiving equipment has lost the pointer to the start of
cell in the payload. This is used to monitor the performance of the PHY layer.
Loss Of Signal Loss of signal (LOS) indicates that there are no transitions occurring in the received
signal.
LP lower order path
LPT link-state pass through
LSP See label switched path
M
MA See maintenance association
MAC See media access control
MAC See media access control
MADM multiple add/drop multiplexer
main topology A interface that displays the connection relation of NEs on the NMS (screen display).
The default client interface of the NMS, a basic component of the human-machine
interactive interface. The topology clearly shows the structure of the network, the alarms
of different NEs, subnets in the network, the communication status as well as the basic
network operation status. All topology management functions are accessed here.
maintenance That portion of a Service Instance, preferably all of it or as much as possible, the
association connectivity of which is maintained by CFM. It is also a full mesh of Maintenance
Entities.
maintenance A MEP is an actively managed CFM Entity, associated with a specific DSAP of a Service
association end point Instance, which can generate and receive CFM frames and track any responses. It is an
end point of a single Maintenance Association, and terminates a separate Maintenance
Entity for each of the other MEPs in the same Maintenance Association.
maintenance domain The network or the part of the network for which connectivity is managed by CFM. The
devices in an MD are managed by a single ISP.
maintenance point Maintenance Point (MP) is one of either a MEP or a MIP.
management A type of database used for managing the devices in a communications network. It
information base comprises a collection of objects in a (virtual) database used to manage entities (such as
routers and switches) in a network.
manual switch Switches normal traffic signal to the protection section, unless a failure condition exists
on other sections (including the protection section) or an equal or higher priority switch
command is in effect, by issuing a manual switch request for that normal traffic signal.
maximum transmission The largest packet of data that can be transmitted on a network. MTU size varies,
unit depending on the network—576 bytes on X.25 networks, for example, 1500 bytes on
Ethernet, and 17,914 bytes on 16 Mbps Token Ring. Responsibility for determining the
size of the MTU lies with the link layer of the network. When packets are transmitted
across networks, the path MTU, or PMTU, represents the smallest packet size (the one
that all networks can transmit without breaking up the packet) among the networks
involved.
MBS maximum burst size
MCF See message communication function
MD See maintenance domain
MDI See medium dependent interface
Mean Time Between The average time between consecutive failures of a piece of equipment. It is a measure
Failures of the reliability of the system.
Mean Time To Repair The average time that a device will take to recover from a failure.
media access control A protocol at the media access control sublayer. The protocol is at the lower part of the
data link layer in the OSI model and is mainly responsible for controlling and connecting
the physical media at the physical layer. When transmitting data, the MAC protocol
checks whether to be able to transmit data. If the data can be transmitted, certain control
information is added to the data, and then the data and the control information are
transmitted in a specified format to the physical layer. When receiving data, the MAC
protocol checks whether the information is correct and whether the data is transmitted
correctly. If the information is correct and the data is transmitted correctly, the control
information is removed from the data and then the data is transmitted to the LLC layer.
media access control A protocol at the media access control sublayer. The protocol is at the lower part of the
data link layer in the OSI model and is mainly responsible for controlling and connecting
the physical media at the physical layer. When transmitting data, the MAC protocol
checks whether to be able to transmit data. If the data can be transmitted, certain control
information is added to the data, and then the data and the control information are
transmitted in a specified format to the physical layer. When receiving data, the MAC
protocol checks whether the information is correct and whether the data is transmitted
correctly. If the information is correct and the data is transmitted correctly, the control
information is removed from the data and then the data is transmitted to the LLC layer.
medium dependent The electrical and mechanical interface between the equipment and the media
interface transmission.
MEP See maintenance association end point
MEP maintenance end point
message The MCF is composed of a protocol stack that allows exchange of management
communication information with their prs.
function
MIB See management information base
MIP maintenance intermediate point
mounting ear A piece of angle plate with holes in it on a rack. It is used to fix network elements or
components.
MP See maintenance point
MPID maintenance point identification
MPLS See Multiprotocol Label Switching
MPLS L2VPN The MPLS L2VPN provides the Layer 2 VPN service based on an MPLS network. In
this case, on a uniform MPLS network, the carrier is able to provide Layer 2 VPNs of
different media types, such as ATM, FR, VLAN, Ethernet, and PPP.
MPLS OAM The MPLS OAM provides continuity check for a single LSP, and provides a set of fault
detection tools and fault correct mechanisms for MPLS networks. The MPLS OAM and
relevant protection switching components implement the detection function for the CR-
LSP forwarding plane, and perform the protection switching in 50 ms after a fault occurs.
In this way, the impact of a fault can be lowered to the minimum.
MPLS TE See multiprotocol label switching traffic engineering
MPLS TE tunnel In the case of reroute deployment, or when traffic needs to be transported through
multiple trails, multiple LSP tunnels might be used. In traffic engineering, such a group
of LSP tunnels are referred to as TE tunnels. An LSP tunnel of this kind has two
identifiers. One is the Tunnel ID carried by the SENDER object, and is used to uniquely
define the TE tunnel. The other is the LSP ID carried by the SENDER_TEMPLATE or
FILTER_SPEC object.
MS See multiplex section
MSP See multiplex section protection
MSTP See Multiple Spanning Tree Protocol
MTBF See Mean Time Between Failures
MTTR See Mean Time To Repair
MTU See maximum transmission unit
Multicast A process of transmitting packets of data from one source to many destinations. The
destination address of the multicast packet uses Class D address, that is, the IP address
ranges from 224.0.0.0 to 239.255.255.255. Each multicast address represents a multicast
group rather than a host.
Multiple Spanning Multiple spanning tree protocol. The MSTP can be used in a loop network. Using an
Tree Protocol algorithm, the MSTP blocks redundant paths so that the loop network can be trimmed
as a tree network. In this case, the proliferation and endless cycling of packets is avoided
in the loop network. The protocol that introduces the mapping between VLANs and
multiple spanning trees. This solves the problem that data cannot be normally forwarded
in a VLAN because in STP/RSTP, only one spanning tree corresponds to all the VLANs.
multiplex section The trail between and including two multiplex section trail termination functions.
multiplex section A function, which is performed to provide capability for switching a signal between and
protection including two multiplex section termination (MST) functions, from a "working" to a
"protection" channel.
Multiprotocol Label A technology that uses short tags of fixed length to encapsulate packets in different link
Switching layers, and provides connection-oriented switching for the network layer on the basis of
IP routing and control protocols. It improves the cost performance and expandability of
networks, and is beneficial to routing.
multiprotocol label N/A
switching traffic
engineering
N
N+1 protection A radio link protection system composed of N working channels and one protection
channel.
NE See network element
NE Explorer The main operation interface, of the NMS, which is used to manage the
telecommunication equipment. In the NE Explorer, the user can query, manage and
maintain the NE, boards, and ports on a per-NE basis.
network element A network element (NE) contains both the hardware and the software running on it. One
NE is at least equipped with one system control and communication(SCC) board which
manages and monitors the entire network element. The NE software runs on the SCC
board.
Network Management A system in charge of the operation, administration, and maintenance of a network.
System
network service access A network address defined by ISO, through which entities on the network layer can
point access OSI network services.
network to network An internal interface within a network linking two or more elements.
interface
next hop The next router to which a packet is sent from any given router as it traverses a network
on its journey to its final destination.
NLP normal link pulse
NMS See Network Management System
NNI See network to network interface
node A node stands for a managed device in the network. For a device with a single frame,
one node stands for one device. For a device with multiple frames, one node stands for
one frame of the device. Therefore, a node does not always mean a device.
Node Protection A parameter of the FRR protection. It indicates that the bypass tunnel should be able to
protect the downstream node that is involved in the working tunnel and adjacent to the
PLR. The node cannot be a merge point, and the bypass tunnel should also be able to
protect the downstream link that is involved in the working tunnel and adjacent to the
PLR.
non-gateway network A network element whose communication with the NM application layer must be
element transferred by the gateway network element application layer.
non-GNE See non-gateway network element
NSAP See network service access point
NSF not stop forwarding
O
OAM See operation, administration and maintenance
ODF See optical distribution frame
ODU See outdoor unit
OM Operation and maintenance
One-to-One Backup A local repair method in which a backup tunnel is separately created for each protected
tunnel at a PLR.
open shortest path first A link-state, hierarchical interior gateway protocol (IGP) for network routing. Dijkstra's
algorithm is used to calculate the shortest path tree. It uses cost as its routing metric. A
link state database is constructed of the network topology which is identical on all routers
in the area.
Open Systems A framework of ISO standards for communication between different systems made by
Interconnection different vendors, in which the communications process is organized into seven different
categories that are placed in a layered sequence based on their relationship to the user.
Each layer uses the layer immediately below it and provides a service to the layer above.
Layers 7 through 4 deal with end-to-end communication between the message source
and destination, and layers 3 through 1 deal with network functions.
operation, A group of network support functions that monitor and sustain segment operation,
administration and activities that are concerned with, but not limited to, failure detection, notification,
maintenance location, and repairs that are intended to eliminate faults and keep a segment in an
operational state and support activities required to provide the services of a subscriber
access network to users/subscribers.
optic fiber connector A device installed at the end of a fiber, optical source or receive unit. It is used to couple
the optical wave to the fiber when connected to another device of the same type. A
connector can either connect two fiber ends or connect a fiber end and an optical source
(or a detector).+
optical distribution A frame which is used to transfer and spool fibers.
frame
orderwire A channel that provides voice communication between operation engineers or
maintenance engineers of different stations.
OSI See Open Systems Interconnection
OSPF See open shortest path first
outdoor unit The outdoor unit of the split-structured radio equipment. It implements frequency
conversion and amplification for RF signals.
Outloop A method of looping back the input signals received at a port to an output port without
changing the structure of the signals.
Output optical power The ranger of optical energy level of output signals.
C.5 P-T
This section provides the terms starting with letters P to T.
P
packet switched A telecommunication network which works in packet switching mode.
network
Packing case A case which is used for packing the board or subrack.
Path A performance resource object defined in the network management system. The left end
of a path is a device node whose port needs to be specified and the right end of a path is
a certain IP address which can be configured by the user. By defining a path in the
network management system, a user can test the performance of a network path between
a device port and an IP address. The tested performance may be the path delay, packet
loss ratio or other aspects.
PBS See peak burst size
PCB See printed circuit board
PCI bus PCI (Peripheral Component Interconnect) bus. A high performance bus, 32-bit or 64-bit
for interconnecting chips, expansion boards, and processor/memory subsystems.
PDH See plesiochronous digital hierarchy
PDU See protocol data unit
PE See provider edge
peak burst size A parameter used to define the capacity of token bucket P, that is, the maximum burst
IP packet size when the information is transferred at the peak information rate. This
parameter must be larger than 0. It is recommended that this parameter should be not
less than the maximum length of the IP packet that might be forwarded.
peak information rate A traffic parameter, expressed in bit/s, whose value should be not less than the committed
information rate.
penultimate hop Penultimate Hop Popping (PHP) is a function performed by certain routers in an MPLS
popping enabled network. It refers to the process whereby the outermost label of an MPLS tagged
packet is removed by a Label Switched Router (LSR) before the packet is passed to an
adjacent Label Edge Router (LER).
per-hop behavior IETF Diff-Serv workgroup defines forwarding behaviors of network nodes as per-hop
behaviors (PHB), such as, traffic scheduling and policing. A device in the network should
select the proper PHB behaviors, based on the value of DSCP. At present, the IETF
defines four types of PHB. They are class selector (CS), expedited forwarding (EF),
assured forwarding (AF), and best-effort (BE).
PHB See per-hop behavior
PHP See penultimate hop popping
PIR See peak information rate
plesiochronous digital A multiplexing scheme of bit stuffing and byte interleaving. It multiplexes the minimum
hierarchy rate 64 kit/s into the 2 Mbit/s, 34 Mbit/s, 140 Mbit/s, and 565 Mbit/s rates.
Point-to-Point Protocol A protocol on the data link layer, provides point-to-point transmission and encapsulates
data packets on the network layer. It is located in layer 2 of the IP protocol stack.
polarization A kind of electromagnetic wave, the direction of whose electric field vector is fixed or
rotates regularly. Specifically, if the electric field vector of the electromagnetic wave is
perpendicular to the plane of horizon, this electromagnetic wave is called vertically
polarized wave; if the electric field vector of the electromagnetic wave is parallel to the
plane of horizon, this electromagnetic wave is called horizontal polarized wave; if the
tip of the electric field vector, at a fixed point in space, describes a circle, this
electromagnetic wave is called circularly polarized wave.
Power box A direct current power distribution box at the upper part of a cabinet, which supplies
power for the subracks in the cabinet.
PPP See Point-to-Point Protocol
PQ See priority queue
PRBS See pseudo random binary sequence
PRC primary reference clock
printed circuit board A board used to mechanically support and electrically connect electronic components
using conductive pathways, tracks, or traces, etched from copper sheets laminated onto
a non-conductive substrate.
priority queue An abstract data type in computer programming that supports the following three
operations: (1) InsertWithPriority: add an element to the queue with an associated
priority (2) GetNext: remove the element from the queue that has the highest priority,
and return it (also known as "PopElement(Off)", or "GetMinimum") (3) PeekAtNext
(optional): look at the element with highest priority without removing it
protection ground A cable which connects the equipment and the protection grounding bar. Usually, one
cable half of the cable is yellow; while the other half is green.
Protection path A specific path that is part of a protection group and is labeled protection.
protocol data unit It is a data packet at the network layer of the OSI model.
provider edge A device that is located in the backbone network of the MPLS VPN structure. A PE is
responsible for VPN user management, establishment of LSPs between PEs, and
exchange of routing information between sites of the same VPN. During the process, a
PE performs the mapping and forwarding of packets between the private network and
the public channel. A PE can be a UPE, an SPE, or an NPE.
pseudo random binary A sequence that is random in a sense that the value of an element is independent of the
sequence values of any of the other elements, similar to real random sequences.
pseudo wire An emulated connection between two PEs for transmitting frames. The PW is established
and maintained by PEs through signaling protocols. The status information of a PW is
maintained by the two end PEs of a PW.
pseudo wire emulation A type of end-to-end Layer 2 transmitting technology. It emulates the essential attributes
edge-to-edge of a telecommunication service such as ATM, FR or Ethernet in a Packet Switched
Network (PSN). PWE3 also emulates the essential attributes of low speed Time Division
Multiplexed (TDM) circuit and SONET/SDH. The simulation approximates to the real
situation.
PSN See packet switched network
PTN packet transport network
PW See pseudo wire
PWE3 See pseudo wire emulation edge-to-edge
Q
QinQ A layer 2 tunnel protocol based on IEEE 802.1Q encapsulation. It encapsulates the tag
of the user's private virtual local area network (VLAN) into the tag of the public VLAN.
The packet carries two layers of tags to travel through the backbone network of the
carrier. In this manner, the layer 2 virtual private network (VPN) is provided for the user.
QoS See quality of service
QPSK See quadrature phase shift keying
quadrature phase shift A modulation method of data transmission through the conversion or modulation and
keying the phase determination of the reference signals (carrier). It is also called the fourth period
or 4-phase PSK or 4-PSK. QPSK uses four dots in the star diagram. The four dots are
evenly distributed on a circle. On these phases, each QPSK character can perform two-
bit coding and display the codes in Gray code on graph with the minimum BER.
R
radio frequency A type of electric current in the wireless network using AC antennas to create an
electromagnetic field. It is the abbreviation of high-frequency AC electromagnetic wave.
The AC with the frequency lower than 1 kHz is called low-frequency current. The AC
with frequency higher than 10 kHz is called high-frequency current. RF can be classified
into such high-frequency current.
radio network A device in the RNS which is in charge of controlling the use and the integrity of the
controller radio resources.
random early detection A packet loss algorithm used in congestion avoidance. It discards the packet according
to the specified higher limit and lower limit of a queue so that global TCP synchronization
resulted in traditional Tail-Drop can be prevented.
Rapid Spanning Tree An evolution of the Spanning Tree Protocol, providing for faster spanning tree
Protocol convergence after a topology change. The RSTP protocol is backward compatible with
the STP protocol.
RDI See remote defect indication
received signal level The signal level at a receiver input terminal.
Received Signal The received wide band power, including thermal noise and noise generated in the
Strength Indicator receiver, within the bandwidth defined by the receiver pulse shaping filter, for TDD
within a specified timeslot. The reference point for the measurement shall be the antenna
Receiver Sensitivity Receiver sensitivity is defined as the minimum acceptable value of average received
power at point R to achieve a 1 x 10-12 BER (The FEC is open).
RED See random early detection
Reed-Solomon-Code A forward error correction code located before interleaving that enables correction of
errors induced by burst noise. Widely used error correction scheme to fight transmission
errors at the receiver site.
REI See remote error indication
remote defect A signal transmitted at the first opportunity in the outgoing direction when a terminal
indication detects specific defects in the incoming signal.
remote error indication A remote error indication (REI) is sent upstream to signal an error condition. There are
two types of REI alarms: Remote error indication line (REI-L) is sent to the upstream
LTE when errors are detected in the B2 byte. Remote error indication path (REI-P) is
sent to the upstream PTE when errors are detected in the B3 byte.
Request For Comments A document in which a standard, a protocol, or other information pertaining to the
operation of the Internet is published. The RFC is actually issued, under the control of
the IAB, after discussion and serves as the standard. RFCs can be obtained from sources
such as InterNIC.
Resource Reservation The Resource Reservation Protocol (RSVP) is designed for Integrated Service and is
Protocol used to reserve resources on every node along a path. RSVP operates on the transport
layer; however, RSVP does not transport application data. RSVP is a network control
protocol like Internet Control Message Protocol (ICMP).
reverse pressure A traffic control method. In telecommunication, when detecting that the transmit end
transmits a large volume of traffic, the receive end sends signals to ask the transmit end
to slow down the transmission rate.
RF See radio frequency
RFC See Request For Comments
RIP See Routing Information Protocol
RMON remote network monitoring
RMON remote network monitoring
RNC See radio network controller
Root alarm An alarm directly caused by anomaly events or faults in the network. Some lower-level
alarms always accompany a root alarm.
route A route is the path that network traffic takes from its source to its destination. In a TCP/
IP network, each IP packet is routed independently. Routes can change dynamically.
route table A mapping table that stores the relationship between the original address, destination
address, short message (SM) protocol type and account. The SMSC delivers an SM to
the designated account according to the information set in the route table.
Routing Information A simple routing protocol that is part of the TCP/IP protocol suite. It determines a route
Protocol based on the smallest hop count between source and destination. RIP is a distance vector
protocol that routinely broadcasts routing information to its neighboring routers and is
known to waste bandwidth.
routing table A table that stores and updates the locations (addresses) of network devices. Routers
regularly share routing table information to be up to date. A router relies on the
destination address and on the information in the table that gives the possible routes--in
hops or in number of jumps--between itself, intervening routers, and the destination.
Routing tables are updated frequently as new information is available.
RSL See received signal level
RSSI See Received Signal Strength Indicator
RSTP See Rapid Spanning Tree Protocol
RSVP See Resource Reservation Protocol
RTN radio transmission node
S
SD See space diversity
SDH See synchronous digital hierarchy
SEMF See synchronous equipment management function
service level agreement A service contract between a customer and a service provider that specifies the
forwarding service a customer should receive. A customer may be a user organization
(source domain) or another differentiated services domain (upstream domain). A SLA
may include traffic conditioning rules which constitute a traffic conditioning agreement
as a whole or partially.
Service Level A management-documented agreement that defines the relationship between service
Agreement * provider and its customer. It also provides specific, quantifiable information about
measuring and evaluating the delivery of services. The SLA details the specific operating
and support requirements for each service provided. It protects the service provider and
customer and allows the service provider to provide evidence that it has achieved the
documented target measure.
SES See severely errored second
Setup Priority The priority of the tunnel with respect to obtaining resources, ranging from 0 (indicates
the highest priority) to 7. It is used to determine whether the tunnel can preempt the
resources required by other backup tunnels.
severely errored second A one-second period which has a bit error ratio ≥ X 10-3 or at least one defect. Time
interval of one second during which a given digital signal is received with an error ratio
greater than 1 X 10 -3 (Rec. ITU R F. 592 needs correction).
SF See signal fail
SFP See small form-factor pluggable
side trough The trough on the side of the cable rack, which is used to place nuts so as to fix the
cabinet.
signal cable Common signal cables cover the E1 cable, network cable, and other non-subscriber
signal cable.
signal fail A signal that indicates the associated data has failed in the sense that a near-end defect
condition (non-degrade defect) is active.
signal to noise ratio The ratio of the amplitude of the desired signal to the amplitude of noise signals at a
given point in time. SNR is expressed as 10 times the logarithm of the power ratio and
is usually expressed in dB (Decibel).
Simple Network A network management protocol of TCP/IP. It enables remote users to view and modify
Management Protocol the management information of a network element. This protocol ensures the
transmission of management information between any two points. The polling
mechanism is adopted to provide basic function sets. According to SNMP, agents, which
can be hardware as well as software, can monitor the activities of various devices on the
network and report these activities to the network console workstation. Control
information about each device is maintained by a management information block.
simplex Designating or pertaining to a method of operation in which information can be
transmitted in either direction, but not simultaneously, between two points.
SLA See service level agreement
SLA* See Service Level Agreement *
Slicing To divide data into the information units proper for transmission.
small form-factor A specification for a new generation of optical modular transceivers.
pluggable
SNC See subnetwork connection
Synchronization Status A message that carries quality levels of timing signals on a synchronous timing link.
Message Nodes on an SDH network and a synchronization network acquire upstream clock
information through this message. Then the nodes can perform proper operations on their
clocks, such as tracing, switching, or converting to holdoff, and forward the
synchronization information to downstream nodes.
synchronous digital A transmission scheme that follows ITU-T G.707, G.708, and G.709. It defines the
hierarchy transmission features of digital signals such as frame structure, multiplexing mode,
transmission rate level, and interface code. SDH is an important part of ISDN and B-
ISDN. It interleaves the bytes of low-speed signals to multiplex the signals to high-speed
counterparts, and the line coding of scrambling is used only for signals. SDH is suitable
for the fiber communication system with high speed and a large capacity since it uses
synchronous multiplexing and flexible mapping structure.
synchronous The SEMF converts performance data and implementation specific hardware alarms into
equipment object-oriented messages for transmission over DCCs and/or a Q interface.
management function
synchronous transport Synchronous Transfer Mode at 155 Mbit/s.
mode-1
Synchronous An STM is the information structure used to support section layer connections in the
Transport Module SDH. It consists of information payload and Section Overhead (SOH) information fields
organized in a block frame structure which repeats every 125. The information is suitably
conditioned for serial transmission on the selected media at a rate which is synchronized
to the network. A basic STM is defined at 155 520 kbit/s. This is termed STM-1. Higher
capacity STMs are formed at rates equivalent to N times this basic rate. STM capacities
for N = 4, N = 16 and N = 64 are defined; higher values are under consideration.
synchronous transport A STM-N is the information structure used to support section layer connections in SDH.
module of order N See ITU-T Recommendation G. 707 for STM modules of order 1, 4, 16 and 64.
tail drop A type of QoS. When a queue within a network router reaches its maximum length,
packet drops can occur. When a packet drop occurs, connection-based protocols such as
TCP slow down their transmission rates in an attempt to let queued packets be serviced,
thereby letting the queue empty. This is also known as tail drop because packets are
dropped from the input end (tail) of the queue.
Tail drop A congestion management mechanism, in which packets arrive later are discarded when
the queue is full. This policy of discarding packets may result in network-wide
synchronization due to the TCP slow startup mechanism.
TCI tag control information
TCP See Transmission Control Protocol
TDM See time division multiplexing
TE See traffic engineering
TEDB See traffic engineering database
Telecommunication A protocol model defined by ITU-T for managing open systems in a communications
Management Network network. An architecture for management, including planning, provisioning, installation,
maintenance, operation and administration of telecommunications equipment, networks
and services.
two rate three color The trTCM meters an IP packet stream and marks its packets based on two rates, Peak
marker Information Rate (PIR) and Committed Information Rate (CIR), and their associated
burst sizes to be either green, yellow, or red. A packet is marked red if it exceeds the
PIR. Otherwise it is marked either yellow or green depending on whether it exceeds or
doesn't exceed the CIR.
C.6 U-Z
This section provides the terms starting with letters U to Z.
U
U-VLAN A VLAN attribute indicating that the current VLAN is a user VLAN of an M-VLAN.
Multicast services are copied from the M-VLAN to the user VLAN.
UAS unavailable second
UBR See unspecified bit rate
UDP See User Datagram Protocol
underfloor cabling The cables connected cabinets and other devices are routed underfloor.
UNI See user network interface
unicast The process of sending data from a source to a single recipient.
unspecified bit rate No commitment to transmission. No feedback to congestion. This type of service is ideal
for the transmission of IP datagrams. In case of congestion, UBR cells are discarded,
and no feedback or request for slowing down the data rate is delivered to the sender.
upload An operation to report some or all configuration data of an NE to the NMS(Network
Management system). The configuration data then covers the configuration data stored
at the NMS side.
User Datagram A TCP/IP standard protocol that allows an application program on one device to send a
Protocol datagram to an application program on another. User Datagram Protocol (UDP) uses IP
to deliver datagrams. UDP provides application programs with the unreliable
connectionless packet delivery service. Thus, UDP messages can be lost, duplicated,
delayed, or delivered out of order. UDP is used to try to transmit the data packet, that is,
the destination device does not actively confirm whether the correct data packet is
received.
user network interface The interface between user equipment and private or public network equipment (for
example, ATM switches).
V
V-UNI See virtual user-network interface
variable bit rate One of the traffic classes used by ATM (Asynchronous Transfer Mode). Unlike a
permanent CBR (Constant Bit Rate) channel, a VBR data stream varies in bandwidth
and is better suited to non real time transfers than to real-time streams such as voice calls.
VBR See variable bit rate
VC See virtual container
W
wait to restore The number of minutes to wait before services are switched back to the working line.
WAN See wide area network
Web LCT The local maintenance terminal of a transport network, which is located on the NE
management layer of the transport network
weighted fair queuing A fair queue scheduling algorithm based on bandwidth allocation weights. This
scheduling algorithm allocates the total bandwidth of an interface to queues, according
to their weights and schedules the queues cyclically. In this manner, packets of all priority
queues can be scheduled.
weighted random early A packet loss algorithm used for congestion avoidance. It can prevent the global TCP
detection synchronization caused by traditional tail-drop. WRED is favorable for the high-priority
packet when calculating the packet loss ratio.
weighted round Robin N/A
WFQ See weighted fair queuing
wide area network A network composed of computers which are far away from each other which are
physically connected through specific protocols. WAN covers a broad area, such as a
province, a state or even a country.
winding pipe A tool for fiber routing, which acts as the corrugated pipe.
WRED See weighted random early detection
WRR See weighted round Robin
WTR See wait to restore
X
XPIC See cross polarization interference cancellation