Beruflich Dokumente
Kultur Dokumente
V100R012C00
Configuration Guide
Issue 01
Date 2017-09-30
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Related Versions
The following table lists the product versions related to this document.
Intended Audience
This document describes how to configure optical network elements, WDM services, and
Ethernet services.
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Symbol Description
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
Change History
Updates between document issues are cumulative. Therefore, the latest document issue
contains all updates made in previous issues.
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Whole manual 3.1 Configuring the TN11TOM Board (Manually by Station), 3.2
Configuring the TN52TOM Board (by Station), 4 Configuring the
THA/TOA Board (Manually by Station), 5 Configuring the LOA
Board (Manually by Station), 7 Configuring Universal Line
Boards, 8 Configuring WDM Services (by Station Service Package)
and 14 Configuration Tasks: Optimized the operation procedure and
added operation screenshots.
Some bugs are fixed in this version.
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
14.9 Modifying This chapter is deleted. Modifying Port and 14.9.2 Modifying the
the Services Configuration are moved to 14 Configuration Tasks.
Configuration
Data
Update Description
Update Description
14.9 Modifying This chapter is deleted. Modifying Port and 14.9.2 Modifying the
the Services Configuration are moved to 14 Configuration Tasks.
Configuration
Data
Update Description
14.9 Modifying l Conversion Between EVPL Ethernet Services and VLAN SNCP
the Services is modified.
Configuration l Converting an EVPL Ethernet Service to a VLAN SNCP Service is
Data modified.
l Converting a VLAN SNCP Service to an EVPL Ethernet Service is
modified.
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
2 Configuring l The chapter Configuring WDM Services for Tributary Boards and
WDM Services Line Boards (with ODUK SNCP Protection) is deleted.
(Manually by
Station)
Update Description
Update Description
Whole manual Add the chapter 4 Configuring the THA/TOA Board (Manually by
Station).
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
2.3 Configuring 2.3 Configuring WDM Services for OTU Boards Without Cross-
WDM Services Connect Capability, 2.4 Configuring WDM Services for OTU
for OTU Boards Boards with Cross-Connect Capability, 2.5 Configuring WDM
Without Cross- Services for Tributary Boards and Line Boards, and Configuring
Connect WDM Services for Boards with the Layer 2 Switching Function are
Capability added.
2.4 Configuring
WDM Services
for OTU Boards
with Cross-
Connect
Capability
2.5 Configuring
WDM Services
for Tributary
Boards and
Line Boards
Configuring
WDM Services
for Boards with
the Layer 2
Switching
Function
Update Description
Configuring Configuring WDM Services for Tributary Boards and Line Boards
WDM Services (with ODUK SNCP Protection) is added.
for Tributary
Boards and Line
Boards (with
ODUK SNCP
Protection)
Update Description
Contents
6.3 Configuration Example: FC3200 -> ODUflex FC -> ODUC2 -> OTUC2 Services................................................. 285
13.3 Configuring an Ethernet Service on a Packet Network in Single Site Mode .......................................................... 820
13.3.1 Configuration Flow for the E-Line Services......................................................................................................... 821
13.3.1.1 E-Line Services Carried by PWs........................................................................................................................ 821
13.3.1.2 E-Line Services Carried by QinQ Links.............................................................................................................823
13.3.1.3 E-Line Services Carried by Ports....................................................................................................................... 826
13.3.1.4 Configuration Flow for the UNI-UNI E-Line Services......................................................................................829
13.3.2 Configuration Flow for the E-LAN Services........................................................................................................ 831
13.3.2.1 E-LAN Services Carried by PWs ...................................................................................................................... 832
13.3.2.2 E-LAN Services Carried by QinQ Links ...........................................................................................................834
13.3.2.3 E-LAN Services Carried by Ports...................................................................................................................... 837
13.3.3 Configuring an Ethernet Port.................................................................................................................................840
13.3.3.1 Setting the Basic Attributes of Ethernet Ports.................................................................................................... 841
13.3.3.2 Setting the Layer 2 Attributes of Ethernet Ports.................................................................................................842
13.3.3.3 Setting the Layer 3 Attributes of Ethernet Ports.................................................................................................843
13.3.3.4 Setting the Advanced Attributes of Ethernet Ports.............................................................................................844
13.3.3.5 Configuring the Flow Control............................................................................................................................ 845
13.3.4 Configuring the NNIs............................................................................................................................................ 846
13.3.4.1 Configuring the NNIs for Ethernet Services Carried by Ports........................................................................... 846
13.3.4.2 Configuring the NNIs for Ethernet Services Carried by Static MPLS Tunnels................................................. 849
13.3.4.3 Configuring the NNIs for Ethernet Services Carried by QinQ Links................................................................ 849
13.3.5 Configuring an MPLS Tunnel............................................................................................................................... 850
13.3.5.1 Configuring LSR ID........................................................................................................................................... 851
13.3.5.2 Configuring a Unidirectional Static MPLS Tunnel on a Per-NE Basis..............................................................852
13.3.5.3 Configuring a Bidirectional Static MPLS Tunnel on a Per-NE Basis................................................................ 854
13.3.6 Operation Tasks for Configuring E-Line Services................................................................................................ 855
13.3.6.1 Configuring UNI-UNI E-Line Services............................................................................................................. 855
13.3.6.2 Configuring UNI-NNI E-Line Services Carried by Ports.................................................................................. 858
13.3.6.3 Configuring UNI-NNI E-Line Services Carried by PWs on a Per-NE Basis.....................................................861
13.3.6.4 Creating UNI-NNI E-Line Services Carried by QinQ Links............................................................................. 864
13.3.7 Configuring E-LAN Services................................................................................................................................ 866
13.3.7.1 Configuring E-LAN Services Carried by Ports.................................................................................................. 866
13.3.7.2 Creating E-LAN Services Carried by PWs on a Per-NE Basis.......................................................................... 868
13.3.7.3 Configuring E-LAN Services Carried by QinQ Links....................................................................................... 870
13.3.8 Configuring Transit Nodes for Ethernet Services..................................................................................................872
13.3.8.1 Configuring Transit NEs for Ethernet Services Carried by Ports.......................................................................872
13.3.8.2 Configuring Transit NEs for Ethernet Services Carried by PWs....................................................................... 874
13.3.8.3 Configuring Transit NEs for Ethernet Services Carried by QinQ Links............................................................875
13.3.9 Configuring Address Resolution........................................................................................................................... 877
13.3.10 Configuring the NE-Level TPID......................................................................................................................... 878
13.3.11 Creating a QinQ Link.......................................................................................................................................... 878
13.3.12 Managing the Blacklist........................................................................................................................................ 879
13.4 Managing Services................................................................................................................................................... 880
B Glossary.................................................................................................................................... 1080
This manual describes how to configure services on the NMS and other NMS operations
involved in service configuration. This section provides guidelines to use this manual and
obtain reference information.
To... Then...
NOTE
l To configure services with ODUk SNCP protection, see ODUk SNCP Protection in the Feature
Description.
l To configure PID boards, see "PID" in the Feature Description.
Configure NEs and See Configuring NE and Network in the Commissioning Guide.
networks Configure each functional part of a network according to the
network creation process so that services can be created on the
network topology.
Understand detailed See the description of each board in the Hardware Description:
information about l Physical and Logical Ports: Describes physical ports
boards displayed on the NMS and logical ports of each board.
l Configuration of Cross-connection: Describes cross-
connection configurations of each board.
l Parameters Can Be Set or Queried by NMS: Describes
parameters that can be set or queried on the NMS for each
board, default values of the parameters, and parameter
configuration principles.
To... Then...
Configure features See the Feature Description to understand features, such as:
l Optical Line Protection
l Intra-Board 1+1 Protection
l IPA
l Synchronization
l OTN Overheads Technology
l Master-Slave Subrack Management
To understand more features, see Feature at a Glance in the
Feature Description.
Back up NE data See Backing Up the NE Database to the SCC Board, Manually
Backing Up the NE Database to a CF Card, and Backing Up
Device Data to the NMS Server or the NMS Client in the
Commissioning Guide.
When manually configuring WDM services by station, you need to perform various
operations such as configuring board service types and creating cross-connections.
Configuring WDM services in this mode involves multiple NMS GUIs and the configuration
process is complex. However, the mode is applicable to various scenarios and very flexible.
Basic Concept
Inter-board electrical cross-connections are configured between boards to groom ODUk and
GE services inside a subrack. They are configured on the U2000.
Some OTU boards for the OptiX OSN 3800 and OptiX OSN 6800 support inter-board 10GE
and GE cross-connections. For details, see section "Physical and Logical Ports".
Port Type
The source and sink ports must be specified when you configure inter-board cross-
connections. On the U2000, the following ports can be configured as the source or sink ports
of cross-connections:
l ClientLP-n: the logical client-side port of a board in compatible mode, for example,
201(ClientLP1/ClientLP1)-1, where 201(ClientLP1/ClientLP1) indicates the port
number and -1 indicates the channel number.
l ODUkLP-n: the logical ODUk port of a board in compatible mode, for example,
161(ODU0LP1/ODU0LP1)-2, where 161(ODU0LP1/ODU0LP1) indicates the port
number and -2 indicates the channel number.
l RX/TX-n: the logical client-side port of a board in standard mode, for example, RX2/
TX2-2, where RX2/TX2 indicates the port number and -2 indicates the channel number.
l n(INn/OUTn)-OCH:1-ODUk:m-ODUp:q: the ODUk-level logical port of a board in
standard mode, from which you can learn the service mapping path. The service
mapping paths are different in the following ODU timeslot configuration modes: Assign
consecutive and Assign random.
– In the Assign consecutive mode, level-by-level service mapping is performed from
lower rates to higher rates, for example, ODU0->ODU1->ODU2. In this example,
the logical port is represented as 1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:2-ODU0:1,
which means the first ODU0 in the second ODU1 of the first ODU2 on optical port
1.
– In the Assign random mode, cross-level service mapping is performed from a low
rate to a high rate, for example, ODU0->ODU2. In this example, the logical port is
represented as 1(IN1/OUT1)-OCH:1-ODU2:1-ODU0:1, which means the first
ODU0 in the second ODU2 on optical port 1.
Configuration Principles
The source and sink ports of a cross-connection must have the same ODUk service
granularity and line rate (standard mode/speedup mode ), but they do not require the same
board working mode (standard/compatible) or ODUk timeslot configuration mode (assign
random/assign consecutive). The following figure shows ODU0-level cross-connections. In
the figure, each of the boards can work in either standard or compatible mode.
l As for the same ODUk service granularity, tributary boards (standard/compatible) can
interconnect with line boards (standard/compatible), and the cross-connections between
the boards are indicated by 1 2 3 4 in the figure.
l As for the same ODUk service granularity and line rate, line boards (standard/
compatible) can interconnect with each other, and the cross-connection between the
boards is indicated by 5 in the figure.
2(IN2/OUT2)-OCh:1-ODU2:1-ODU0:8
NOTE
l On the U2000, the subrack layout diagram displays different names of the board in different modes
(standard and compatible). For example, the name of the TN52ND2 board in standard mode is
displayed as TN52ND2(STND), and the name of the TN52ND2 board in compatible mode is
displayed as TN52ND2. For the board names in different modes, see 2.1.2 Standard Mode and
Compatible Mode.
l Line Rate is a parameter available only to line boards and can be set using the U2000. For the
parameter setting of boards, see the "Parameters Can Be Set and Queried on the NMS" topic for the
boards.
Applications
l Adding/Dropping of Client-Side Services on the WDM Side
The cross-connect board cross-connects the ODUk services between OTN tributary
boards and line boards/PID boards/universal line boards.
Figure 2-1 illustrates how adding/dropping client-side services is achieved on the WDM
side using the ODU0 cross-connections between the TOA board (standard mode) and the
ND2 board (standard mode).
Figure 2-1 Adding/dropping of client-side services on the WDM side at sites A and C
Adding/dropping Client side WDM side
of client services
on the WDM side OTN tributary ODU0 OTN line
A board board
GE
OTN
Client service ODU0
network -> ODU0 Cross-connect -> OTU2
board
GE
TOA standard mode ND2 standard mode
B C 3(TX1/RX1)-1 1(IN1/OUT1)-OCh:1-ODU2:1-ODU0:1
Local service 4(TX2/RX2)-1 1(IN1/OUT1)-OCh:1-ODU2:1-ODU0:2
Adding/dropping
pass-through on of client services 5(TX3/RX3)-1 1(IN1/OUT1)-OCh:1-ODU2:1-ODU0:3
the WDM side on the WDM side
10(TX8/RX8)-1 1(IN1/OUT1)-OCh:1-ODU2:1-ODU0:8
Signal flow 2(IN2/OUT2)-OCh:1-ODU2:1-ODU0:1
2(IN2/OUT2)-OCh:1-ODU2:1-ODU0:8
Figure 2-2 Local service pass-through on the WDM side at site B (non-PID network)
Adding/dropping WDM side WDM side
of client services
on the WDM side OTN line ODU0 OTN line
A
board board
GE
OTN
OTU2 ODU0
network ->ODU0 ->OTU2
Cross-connect
board
GE
168(ODU0LP8/ODU0LP8)-1
Signal flow 168(ODU0LP8/ODU0LP8)-2
1(IN1/OUT1)-OCh:1-ODU2:1-ODU0:8
2(IN2/OUT2)-OCh:1-ODU2:1-ODU0:1
2(IN2/OUT2)-OCh:1-ODU2:1-ODU0:8
Figure 2-3 Local service pass-through on the WDM side (interconnection of PID
network and non-PID network)
PID network Non-PID network
- WDM side - WDM side
PID board OTN line
Non-PID ODU1 board
network
Tangent NE:
The PID and
OTN/universal OTU2 ODU1
line boards ->ODU1 Cross-connect ->OTU2
reside in the board
same subrack.
figure, ports enclosed in are the source and sink ports of the cross-connection.
1. In the NE Explorer, choose Configuration > WDM Service Management from the
navigation tree.
2. Click the WDM Cross-Connection Configuration tab and click Create. Then the
Create Cross-Connection Service dialog box is displayed.
Figure 2-4 GUI for configuring cross-connections (using the ODU0 cross-connection
between TOA and ND2 boards as an example)
TOA Compatible mode
201(ClientLP1/ClientLP1)-1
202(ClientLP2/ClientLP2)-1
203(ClientLP3/ClientLP3)-1
208(ClientLP8/ClientLP8)-1
1(IN1/OUT1)-OCh:1-ODU2:1-ODU0:8
2(IN2/OUT2)-OCh:1-ODU2:1-ODU0:1
2(IN2/OUT2)-OCh:1-ODU2:1-ODU0:8
NOTE
Direction shown in the figure can be set to Unidirectional or Bidirectional.
l Unidirectional creates unidirectional cross-connections from the source optical port to the sink
optical port. Signals can be transmitted only in one direction at the same time, such as only sending
or receiving signals.
l Bidirectional creates bidirectional cross-connections from the source optical port to the sink optical
port and from the sink optical port to the source optical port. Signals can be transmitted in both
directions at the same time.
Basic Concept
Intra-board electrical cross-connections are used to flexibly groom services inside a board and
they can be configured using the U2000. For example, to converge multiple services into one
ODU1 signal, intra-board cross-connections must be created to groom the services into an
ODU1 signal.
Port Type
The source and sink ports must be specified when you configure intra-board cross-
connections. On the NMS, the following ports can be configured as the source or sink ports of
cross-connections:
l ClientLP-n: the logical client-side port of a board in compatible mode, for example,
201(ClientLP1/ClientLP1)-1, where 201(ClientLP1/ClientLP1) indicates the port
number and -1 indicates the channel number.
l ODUkLP-n: the logical ODUk port of a board in compatible mode, for example,
161(ODU0LP1/ODU0LP1)-2, where 161(ODU0LP1/ODU0LP1) indicates the port
number and -2 indicates the channel number.
l RX/TX-n: the logical client-side port of a board in standard mode, for example, RX2/
TX2-2, where RX2/TX2 indicates the port number and -2 indicates the channel number.
l n(INn/OUTn)-OCH:1-ODUk:m-ODUp:q: the ODUk-level logical port of a board in
standard mode, from which you can learn the service mapping path. For example, 1(IN1/
OUT1)-OCH:1-ODU2:1-ODU1:1 indicates the first ODU1 signal in the first ODU2
signal on optical port 1.
Schematic Diagram
Figure 2-5 illustrates intra-board cross-connections using the TOA board as an example.
Services from client-side ports 3(TX1/RX1)-1 to 5(TX3/RX3)-1 are cross-connected to port
201ClientLP. In this way, the three client-side Any-rate services are converged into one
ODU1 signal. The TOA board can converge a maximum of eight client-side Any-rate services
into one ODU1 signal.
Any ODU1
Multiple Any-rate cross- convergence
connections in a board are Any ODU1
groomed to the multiple Any
channels of one ODU1 port.
Backplane
Client side side
5(TX3/RX3)-1
201(ClientLP1/ClientLP1)-8
6(TX4/RX4)-1 202(ClientLP2/ClientLP2)-1 202(ClientLP2/ClientLP2)-1
7(TX5/RX5)-1
202(ClientLP2/ClientLP2)-8
8(TX6/RX6)-1
Intra-board cross-connections are configured on the U2000 in the same way as inter-board
cross-connections. For details, see 2.1.1.1 Inter-board Electrical Cross-Connections.
55TOX - 55TOX
54TSC - 54TSC
54TSXL - 54TSXL
54TTX - 54TTX
55NO2 - 55NO2
55NS3 - 55NS3
56NS3 - 56NS3
54NS4 - 54NS4
56NS4 - 56NS4
57NS4 - 57NS4
58NS4 - 58NS4
54NS4M - 54NS4M
54HUNQ2 - 54HUNQ2
54HUNS3 - 54HUNS3
55NPO2E - 55NPO2E
The hyphen (-) indicates that the compatible mode is not supported.
l Boards in standard mode cannot connect with those in compatible mode on the WDM
side. They can be interconnect only on the backplane side.
l If electrical-layer ASON services need to traverse boards in standard mode, the version
of the source NE must be V100R006C01 or later.
The following uses the TN53NS2 board as an example to introduces the standard and
compatible modes of a line board.
Standard Mode
Figure 2-6 shows the board model of the TN53NS2 board in standard mode.
IN/OUT-OCh:1-ODU2:1-ODUflex:(1~2)
ODUflex:1
ODU2:1 OCh:1
2XODUflex ODUflex:2
IN/OUT-OCh:1
OCh :1
1 xODU2/
1xODU 2e
IN/OUT-OCh:1-ODU2:1-ODU1:(1~4)
Other tributary/line/PID board
ODU1:1
ODU2:1 OCh : 1
4 xODU1
ODU1:4 IN/OUT
IN/OUT-OCh:1-ODU2:1-ODU1:(1~4)-ODU0:(1~2)
ODU0:1
ODU1:1
ODU0:2
ODU2:1 OCh :1
8 xODU0 ODU 0:1
ODU 1:4
ODU 0:2
IN/OUT-OCh:1-ODU2:1-ODU0:(1~8)
ODU0:1
ODU2:1 OCh :1
8 xODU0
ODU0: 8
Backplane
Compatible Mode
Figure 2-7 shows the board model of the TN53NS2 board in compatible mode.
161
51
(ODU0LP1/ODU0LP1)-1
161 ODU1 (ODU1LP1/ODU1LP1)-1
(ODU0LP1/ODU0LP1)-2
71
(ODU2LP1/ODU2LP1)-1 1
(IN1/OUT1)-1
164
ODU2
(ODU0LP4/ODU0LP4)-1 51
164 ODU1 (ODU1LP1/ODU1LP1)-4
(ODU0LP4/ODU0LP4)-2
Logical ports are internal points used to adapt, terminate, and multiplex internal signals of
the board. They also can be used as sources or sinks of cross-connections.
Path View In the NE panel, select a See Figure 2-8. See Figure 2-9.
board, double-click the board
icon or right-click and
choose Path View from the
shortcut menu.
WDM In the NE Explorer, select the See Figure 2-10. See Figure 2-11.
Interface required board and choose
Configuration > WDM
Interface from the Function
Tree. tab.
Create Cross- In the NE Explorer, select the See Figure 2-12. See Figure 2-13.
Connection required NE and choose
Service Configuration > WDM
Service Management from
the Function Tree.
2.1.3 ODUflex
Starting from V100R006C01, the equipment supports the ODUflex (ODUk with variable
bandwidth) technology, which enables users to flexibly configure the container capacity based
on service sizes, leveraging line bandwidth.
Applicable Boards
Only OptiX OSN 8800 supports ODUflex that is applicable to the following boards:
l Tributary boards: TN53TDX, TN57TDX, TN55TQX, TN57TQX, TN54TOA,
TN57TOA, TEM28TN55TTX, TN56TOX
l Line boards: TN52ND2, TN53ND2, TN52NS2, TN53NS2, TN53NQ2, TN54NS4,
TN56NS4, TN57NS4, TN58NS4, TN54NS4M, TN54HUNS3, TN54HUNQ2, TN56NS3
l Tributary-line integrated board: LOA
NOTE
l The TN11LOA board supports ODUflex only when ODU Timeslot Configuration Mode is set to
Assign random.
l The TN52ND2, TN53ND2, TN53NQ2, TN52NS2, and TN53NS2 boards support ODUflex only
when they work in Standard Mode and ODU Timeslot Configuration Mode is set to Assign
random.
WDM Interface When the board where you want to In the NE Explorer, select the
create services is a line board or the required board and choose
LOA board and the services need to Configuration > WDM
be encapsulated into ODUflex Interface > Advanced
services, set ODU Timeslot Attributes from the Function
Configuration Mode to Assign Tree.
random.
Create Cross- When Level is set to ODUflex, you In the NE Explorer, select the
Connection Service must set Service Type. required NE and choose
Configuration > WDM
Service Management from
the Function Tree. In the
displayed window, click
New.
NOTE
l The value of Occupied ODUTUk Timeslots is in the range of 1 to 8 for the TEM28 board and 3 to
7 for other boards, which indicates that the service rate supported by ODUflex is in the range of 1.25
Gbit/s (1 x 1.25 Gbit/s) to 10 Gbit/s (8 x 1.25 Gbit/s).
l The rule for calculating the value of Occupied ODUTUk Timeslots is as follows: Value = Service
rate mapping the service type configured at a port/Bandwidth of each TS subtimeslot (1.25 Gbit/s).
If the value is not an integer, the value is the quotient plus 1. For example, if an FC400 service is
received, the value of Occupied ODUTUk Timeslots is 4 (4.25 Gbit/s/1.25 Gbit/s = 3.4, 3 + 1 = 4).
Configure the
2 timeslot
configuration mode
3 Configure the
service type
(Optional)
4 Configure ODUflex
Tolerance
Configure cross-
5 connections
Service Requirement
See Figure 2-15. Optical NEs (ONEs) A, B, C, and D form a ring network. All the ONEs
function as OADM stations.
User1 and User2 communicate with each other. One bidirectional 10GE LAN service is
available between station A and station B. At station A, the LDX board accesses one 10GE
LAN service. At station B, the LDX board accesses one 10GE LAN service.
East 12LDX
West
C
User2 East
:OADM
West East
NOTE
Prerequisite
Fibers are connected correctly according to the network structure. (Namely, OCh trails can be
searched out. For details, see Searching for WDM Trails.)
Check parameters of the OTU board and ensure that no error is found.
----End
Verifying Configurations
Check whether service configurations are correct. If the end-to-end services on the client side
are correctly configured, the client trails of 10GE LAN levels can be searched out. For details,
see Searching for WDM Trails.
Service Requirement
On the network shown in Figure 2-16, ONEs A, B, C, and D form a ring network. All the
NEs function as OADM stations. The service requirement is as follows:
User1 and User2 communicate with each other. One unidirectional GE service is available
between station A and station B.
East 12LQMS
:OADM
West East
Figure 2-17 shows the service signal flow between station A and station B.
NOTE
ClientLP is a logical port. Cross-connections between client-side RX/TX ports and ClientLP ports need
to be configured. There are connections between ClientLP ports and WDM-side IN/OUT ports, and
therefore cross-connections do not need to be configured.
Prerequisite
Fibers are connected correctly according to the network structure. (Namely, OCh trails can be
searched out. For details, see 9.6 Searching for WDM Trails.)
Check parameters of the OTU board and ensure that no error is found. .
Background Information
If the capacity of the configured services is greater than the available cross-connection
capacity, the service configuration fails.
After Board Mode is set to LQM Mode, the TN12LQMS board can serve as a tributary and line board and
convert four Any services into one OTU1 service.
Step 2 Set Service Mode of the client-side ports on the TN12LQMS boards at stations A and B to
Client Mode. For details, see Configuring the Service Mode.
NOTE
After Service Mode is set to Client Mode, the TN12LQMS board can access services other than OTN
services.
Step 3 Set Service Type of the client-side ports on the TN12LQMS boards at stations A and B to
GE. For details, see Configuring the Service Type.
The following table lists the values of the parameters for station A.
Field Value
Level GE
NOTE
On the Web LCT, this parameter is Service
Level.
Service Type -
Field Value
Direction Bidirectional
NOTE
For details on how to select a port for electrical cross-connection services, see 2.4.2 Service
Signal Flow.
Step 5 Click Query. Ensure that the query result is consistent with the configuration.
Step 6 Optional: Configure service timeslots of the logical port of the TN12LQMS board at station
A. For details, see 14.5 Configuring Service Timeslots.
The following table lists the values of the parameters for station B.
Field Value
Level GE
NOTE
On the Web LCT, this parameter is Service
Level.
Field Value
Service Type -
Direction Bidirectional
NOTE
For details on how to select a port for electrical cross-connection services, see 2.4.2 Service
Signal Flow.
Step 8 Click Query. Ensure that the query result is consistent with the configuration.
Step 9 Optional: Configure service timeslots of the logical port of the TN12LQMS board at station
B. For details on how to configure service timeslots, see 14.5 Configuring Service
Timeslots.
----End
Verifying Configurations
Check whether service configurations are correct. If the end-to-end services on the client side
are correctly configured, the client trails of GE levels can be searched out. For details, see
Searching for Trails.
Service Requirement
See Figure 2-18. ONEs A, B, C, and D form a ring network. All the ONEs function as
OADM stations.
User1 and User2 communicate with each other. One bidirectional GE service is available
between station A and station B. At station A, the TN12TQM board accesses one GE service
and multiplexes the GE service into one channel of ODU1 electrical signals, that is, one
ODU1 service. Then, the ODU1 service is sent to the TN52NQ2 board and is multiplexed
with other services into one OTU2 service. At station B, the TN12TQM board accesses one
GE service and multiplexes the GE service into one channel of ODU1 electrical signals, that
is, one ODU1 service. Then, the ODU1 service is sent to the TN52NQ2 board and is
multiplexed with other services into one OTU2 service.
West A East
B D
C West
User2 East
West 12TQM
West 52NQ2
:OADM
West East
NOTE
ClientLP and ODU1LP are logical ports. Cross-connections between client-side RX/TX ports and
ClientLP ports need to be configured. ODU1 cross-connections between the ClientLP ports of the TQM
board and the ODU1LP ports of the NQ2 board need to be configured. There are connections between
the ODU1LP ports of the NQ2 board and WDM-side IN/OUT ports, and therefore cross-connections do
not need to be configured.
Prerequisite
Fibers are connected correctly according to the network structure. (Namely, OCh trails can be
searched out. For details, see Searching for WDM Trails.)
Check parameters of the OTU board and ensure that no error is found.
You must be an NM user with "NE operator" authority or higher.
After Service Mode is set to Client Mode, the TN12TQM board can access services other than OTN
services.
Step 2 Set Service Mode of the client-side ports on the TN52NQ2 boards at stations A and B to
ODU1. For details, see Configuring the Service Mode.
NOTE
After Service Mode is set to ODU1, the TN52NQ2 board can access ODU1 services.
Step 3 Set Service Type of the client-side ports on the TN12TQM boards at stations A and B to GE.
For details, see Configuring the Service Type.
Step 4 Configure the internal cross-connections for the wavelengths that are added or dropped from
the TN12TQM board at station A.
1. Configure a GE service from the RX/TX port of the TN12TQM board to the ClientLP
port. For details, see Creating Cross-Connections.
The following table lists the values of the parameters for station A.
Field Value
Level GE
NOTE
On the Web LCT, this parameter is Service
Level.
Service Type -
Direction Bidirectional
NOTE
For details on how to select a port for electrical cross-connection services, see 2.5.2 Service
Signal Flow.
Step 5 Click Query. Ensure that the query result is consistent with the configuration.
Step 6 Configure ODU1 services between the TN52NQ2 board and the TN12TQM board at station
A.
1. Configure an ODU1 service from the ClientLP port of the TN12TQM board to the
ODU1LP port of the TN52NQ2 board. For details, see Creating Cross-Connections.
The following table lists the values of the parameters for station A.
Field Value
Level ODU1
NOTE
On the Web LCT, this parameter is Service
Level.
Service Type -
Direction Bidirectional
NOTE
For details on how to select a port for electrical cross-connection services, see 2.5.2 Service
Signal Flow.
Step 7 Click Query. Ensure that the query result is consistent with the configuration.
Step 8 Optional: Configure service timeslots of the logical port of the TN12TQM board at station A.
For details on how to configure service timeslots, see 14.5 Configuring Service Timeslots.
Step 9 Configure the internal cross-connections for the wavelengths that are added or dropped from
the TN12TQM board at station B.
1. Configure a GE service from the RX/TX port of the TN12TQM board to the ClientLP
port. For details, see Creating Cross-Connections.
The following table lists the values of the parameters for station B.
Field Value
Level GE
NOTE
On the Web LCT, this parameter is Service
Level.
Service Type -
Direction Bidirectional
NOTE
For details on how to select a port for electrical cross-connection services, see 2.5.2 Service Signal
Flow.
Step 10 Click Query. Ensure that the query result is consistent with the configuration.
Step 11 Configure ODU1 cross-connections between the TN52NQ2 board and the TN12TQM board
at station B.
1. Configure an ODU1 service from the ClientLP port of the TN12TQM board to the
ODU1LP port of the TN52NQ2 board. For details, see Creating Cross-Connections.
The following table lists the values of the parameters for station B.
Field Value
Level ODU1
NOTE
On the Web LCT, this parameter is Service
Level.
Service Type -
Direction Bidirectional
NOTE
For details on how to select a port for electrical cross-connection services, see 2.5.2 Service
Signal Flow.
Step 12 Click Query. Ensure that the query result is consistent with the configuration.
Step 13 Optional: Configure service timeslots of the logical port of the TN12TQM board at NE B.
For details, see 14.5 Configuring Service Timeslots.
----End
Verifying Configurations
Check whether service configurations are correct. If the end-to-end services on the client side
are correctly configured, the client trails of GE levels can be searched out. For details, see
Searching for WDM Trails.
Service Requirement
See Figure 2-20. The optical NEs (ONEs) A, B, C, and D form a ring network. All the ONEs
function as OADM stations.
User1 and User2 communicate with each other. One bidirectional 10GE LAN service is
available between station A and station C. At station A, the TN52TDX board accesses one
10GE LAN service and encapsulates the 10GE LAN service into one channel of ODU2
electrical signals, that is, one ODU2 service. The TN52NS2 board accesses the ODU2 service
and then outputs one OTU2 service. Station B transparently transmits the OTU2 service. At
station C, the TN52NS2 board accesses the OTU2 service and converts the OTU2 service into
ODU2 electrical signals, which are groomed to the TN52TDX board and then output as one
10GE LAN service.
East 52NS2
West 52NS2
West A East
B D
East West
C
West East
:OADM
West 52TDX
West 52NS2
:REG
User2
Servive
processing
module
71(ODU2LP/ 71(ODU2LP/
ODU2LP)-1 ODU2LP)-1 1(IN/OUT)-1
B 1(IN/OUT)-1
Servive Servive
processing processing
module module
Servive
processing Cross-
module connection
NOTE
ClientLP and ODU2LP are logical ports. There are cross-connections between client-side RX/TX ports
and ClientLP ports and therefore cross-connections do not need to be configured. ODU2 cross-
connections between the ClientLP ports of the TDX board and the ODU2LP ports of the NS2 board
need to be configured. There are connections between the ODU2LP ports of the NS2 board and WDM-
side IN/OUT ports and therefore cross-connections do not need to be configured.
Prerequisite
You are an NMS user with " NE operator" privilege or higher.
Context
Legend Information
Figure 2-22 shows legend information about U2000 operations.
Background Information
l The port mapping mode of 10GE LAN services can be configured as Bit Transparent
Mapping (11.1 G) or MAC Transparent Mapping (10.7 G). Users can select a proper
mapping mode according to the service transmission requirements.
– Bit Transparent Mapping (11.1 G) meets customer requirement for transparent bit
transport of 10GE LAN signals. In the Bit Transparent Mapping (11.1 G) mode,
transmission of signals are achieved by increasing the OTU frame frequency. This
ensures the encoding gain and correction capability of FEC. In this mode, however,
the bit rate is higher than the standard bit rate of OTU2 signals.
– MAC Transparent Mapping (10.7 G) is specific to transparent transmission of
10GE MAC frames as required by customers. In this port mapping mode, a 10GE
LAN signal is encapsulated in the GFP-F format and then mapped into a standard
OTU frame. This mode supports transparent transmission of only client 10GE MAC
frames. In this mode, the signals are in standard OTU2 frames. In addition, the
FEC/AFEC code pattern is applicable to 10GE LAN services in this mode.
Originally, the FEC/AFEC code pattern is intended for 10G SDH services.
l The port mapping modes of the upstream and downstream board must be the same.
NOTICE
l When 10GE LAN signals are received on the client side of the TDX board and Port
Mapping of the TDX board is set to Transparent Mapping (11.1 G), Line Rate of the
71(ODU2LP/ODU2LP)-1 port on the backplane side of the TN52NS2 board that services
pass through must be set to Speedup Mode.
l When 10GE LAN signals are received on the client side of the TDX board and Port
Mapping of the TDX board is set to MAC Transparent Mapping (10.7 G), Line Rate of
the 71(ODU2LP/ODU2LP)-1 port on the backplane side of the TN52NS2 board that
services pass through must be set to Standard Mode.
l The Service Mode must be set to ODU2 or Automatic.
5
4
NOTE
5
:
– When Port Mapping is set to Bit Transparent Mapping (11.1G), the service cross-connect
granularity is ODU2e.
– When Port Mapping is set to MAC Transparent Mapping (10.7 G) , the service cross-
connect granularity is ODU2.
5. Click Apply. In the dialog box that is displayed, click OK.
6. Click Query. Ensure that the query result is consistent with the configuration.
Step 2 Configure attributes of client-side ports on the TN52NS2 board of station A.
1. In the NE Explorer, select the TN52NS2 board and choose Configuration > WDM
Interface from the Function Tree.
2. Click By Board/Port (Channel), and then choose Channel from the drop-down list.
3. Select the Basic Attributes tab.
4. Select the ODU2LP port. Double-click the Service Mode parameter and then select
ODU2 or Automatic.
Configuration example:
5. On the Advanced Attributes tab, select the ODU2LP port and then double-click the
Line Rate parameter and select Speedup Mode.
Configuration example:
3
4
NOTICE
– When Port Mapping of the ClientLP port on the TDX board is set to Bit
Transparent Mapping (11.1 G), Line Rate of the ODU2LP port on the NS2 board
must be set to Speedup Mode.
– When Port Mapping is set to MAC Transparent Mapping (10.7 G) , Line Rate
must be set to Standard Mode.
Port Mapping and Line Rate of the boards that services pass must be consistent;
otherwise, service interruption occurs.
Step 3 Repeat step 2 to configure attributes of ports on the TN52NS2 board at station B.
Step 4 Repeat steps 1 and 2 to configure attributes of ports on the TN52TDX and TN52NS2 boards
of station C.
Step 5 Configure ODU2 services between the TN52NS2 board and the TN52TDX board at station
A.
1. Configure ODU2 services from the ClientLP port of the TN52TDX board to the
ODU2LP port of the TN52NS2 board. For details, see Creating Cross-Connections.
Field Value
Level ODU2
Service Type -
Direction Bidirectional
Field Value
NOTE
For details on how to select a port for electrical cross-connection services, see 2.6.2 Service
Signal Flow.
Step 6 Click Query. Ensure that the query result is consistent with the configuration.
Step 7 Configure ODU2 services between the TN52NS2 boards at station B.
The following table lists the values of the parameters.
Field Value
Level ODU2
Service Type -
Direction Bidirectional
NOTE
For details on how to select a port for electrical cross-connection services, see 2.6.2 Service Signal
Flow.
Step 8 Click Query. Ensure that the query result is consistent with the configuration.
Step 9 Configure ODU2 services between the TN52NS2 board and the TN52TDX board at station C.
1. Configure ODU2 services from the ClientLP port of the TN52TDX board to the
ODU2LP port of the TN52NS2 board. For details, see Creating Cross-Connections.
Field Value
Level ODU2
Service Type -
Direction Bidirectional
NOTE
For details on how to select a port for electrical cross-connection services, see 2.6.2 Service
Signal Flow.
Step 10 Click Query. Ensure that the query result is consistent with the configuration.
----End
Prerequisites
You are an NMS user with " NE operator" privilege or higher.
Legend Information
Figure 2-23 shows legend information about U2000 operations.
Application Diagram
Figure 2-24 Position of the TQX and NS3 boards in the WDM system
4xODU2/ODU2e 4xODU2/ODU2e
M M
1×ODU3/ODU3e
4×ODU2/ODU2e
4×ODU2/ODU2e
1×ODU3/ODU3e
1×OTU3/OTU3e
1×OTU3/OTU3e
1 1 1 U U IN 1 1 1
OUT
X X
TQX IN / / OUT TQX
D D
M M
4 4 4 U U 4 4 4
X X
NS3 NS3
Cross-Connection Diagram
NOTE
In this configuring process, a TN54NS3 board in compatible mode is used as an example in Figure
2-25.
71(ODU2LP1/ODU2LP1)-1
71(ODU2LP1/ODU2LP1)-2
NS3
Client side
201(ClientLP1/ClientLP1)-1
202(ClientLP2/ClientLP2)-1
TQX
203(ClientLP3/ClientLP3)-1
204(ClientLP4/ClientLP4)-1
Cross connect mode
The client side of the TQX board are cross-connected to the WDM side of the NS3 board
Procedure
Step 1 Configure attributes of client-side ports on the TN52TQX board of station A.
1. In the NE Explorer, select the TN52TQX board that you want to configure, and then
choose Configuration > WDM Interface from the Function Tree.
2. Click By Board/Port (Channel), and select Channel from the drop-down list.
3. Select the Basic Attributes tab.
4. Select the ClientLP port, the service type that needs to be set, and then double-click the
corresponding parameter domain to set the following parameters.
– Service Type: 10GE LAN
– Port Mapping: Bit Transparent Mapping (11.1G)
3
1
5
4
NOTE
5
:When the service type is 10GE LAN, the service mapping path can be Bit Transparent
Mapping (11.1G) or MAC Transparent Mapping (10.7 G) . Users can select the service
mapping path based on the service transmission requirements.
When Port Mapping is set to Bit Transparent Mapping (11.1G), the service cross-connect
granularity is ODU2e. When Port Mapping is set to MAC Transparent Mapping (10.7 G) , the
service cross-connect granularity is ODU2.
5. Click Apply. In the dialog box that is displayed, click OK.
6. Click Query, In the dialog box that is displayed, click Close. Ensure that the query result
is consistent with the configuration.
Step 2 Configure attributes of client-side ports on the TN54NS3 board of station A.
1. In the NE Explorer, select the TN54NS3 board and choose Configuration > WDM
Interface from the Function Tree.
2. Click By Board/Port (Channel) and choose Channel from the drop-down list.
3. Select the Basic Attributes tab.
4. Select the ODU2 port. Double-click the Service Mode parameter and then select ODU2
or Automatic.
5. Select the ODU3 port. Double-click the Service Mode parameter and then select
Automatic or MIX.
6. On the Advanced Attributes tab, select the ODU2 port and ODU3 port and double-click
the Line Rate parameter and set to Speedup Mode.
3
4
NOTICE
– When Port Mapping of the ClientLP port on the TQX board is set to Bit
Transparent Mapping (11.1 G), Line Rate of the corresponding ODU2 port of the
TN54NS3 board must be set to Speedup Mode. Line Rate of the ODU3 port must
be set to Speedup Mode.
– When Port Mapping of the ClientLP port on the TQX board is set to MAC
Transparent Mapping (10.7 G) , Line Rate of the corresponding ODU2 port of the
TN54NS3 board must be set to Standard Mode. Line Rate of the ODU3 port can be
set to Standard Mode or Speedup Mode.
Port Mapping and Line Rate of the boards that services pass must be consistent;
otherwise, service interruption occurs.
3
4
1
----End
2.8 Parameters
Describes the parameters involved in the WDM services configuration.
Service Type For example: FE, STM-1, The Service Type parameter
FICON is used to set the type of the
services at an optical port
when the cross-connections
of any services are
configured, to match the
type of the actual services.
This section describes how to manually configure services carried by the TOM board by
station.
Board mode
As shown in Table 3-1, the TN11TOM boards support the cascading and non-cascading
modes.
Cascading l A maximum of eight multi-rate (< 2.5 Gbit/s) client-side services can
mode be input to the TN11TOM board through the SFP module on the
client side.
l The services are then multiplexed into different timeslots of one or
two ODU0 services or one ODU1 service.
l Each group of ClientLP ports, for example, 201(ClientLP1/
ClientLP1)-1 to 201(ClientLP1/ClientLP1)-8 ports, can access a
maximum of eight client-side services.
Non-cascading l A maximum of eight multi-rate (< 2.5 Gbit/s) client-side services can
mode be input to the TN11TOM board through the SFP module on the
client side.
l The services are then multiplexed into different timeslots of one to
eight ODU0 services or one to four ODU1 services.
l Each group of ClientLP ports, for example, 201(ClientLP1/
ClientLP1)-1 to 201(ClientLP1/ClientLP1)-4 ports, can access a
maximum of four client-side services.
Table 3-2 Mappings between the working modes and the service mapping paths
Board Configuration Port Working Mapping Path
Working Scenario Mode
Mode
a: "Any" in the table indicates the client-side service supported in the corresponding
application scenario.
Application Diagram
Figure 3-1 shows the position of the TN11TOM board in a WDM system where the
TN11TOM board works in cascading ODU1 tributary mode.
Figure 3-1 Position of the TN11TOM board in a WDM system (scenario 1: ODU1 tributary
mode (cascading))
1xODU1 1xOTU2 1xOTU2 1xODU1
RX1 RX1
TOM TOM
FE, GE, FDDI, TX1 M M TX1 FE, GE, FDDI,
STM-1, OC-3, U U
DVB-ASI, STM-1, OC-3,
X X DVB-ASI,
1×ODU1
1×ODU1
STM-16, OC- N N
8×Any
8×Any
/ / STM-16, OC-
48, ESCON, S S
D D 48, ESCON,
STM-4, OC-12, 2 2
RX8 M M RX8 STM-4, OC-12,
FC100, FICON, U U
FC200, FICON FC100, FICON,
X X
Express, OTU1 TX8 TX8 FC200, FICON
Express, OTU1
Cross-Connection Diagram
Figure 3-2 shows the cross-connection diagram of the TN11TOM board.
Figure 3-2 Cross-connection diagram of the TN11TOM board (scenario 1: ODU1 tributary
mode (cascading))
WDM side
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:1
Line board
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:2
in standard
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:3
mode
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:4
51(ODU1LP1/ODU1LP1)-1
Line/PID
51(ODU1LP1/ODU1LP1)-2
board in
51(ODU1LP1/ODU1LP1)-3
compatible
51(ODU1LP1/ODU1LP1)-4
Cross-connect mode
module
Client side
3(TX1/RX1)-1 201(ClientLP1/ClientLP1)-1
4(TX2/RX2)-1 201(ClientLP1/ClientLP1)-2
5(TX3/RX3)-1 201(ClientLP1/ClientLP1)-3 2
6(TX4/RX4)-1 1 201(ClientLP1/ClientLP1)-4 TOM
7(TX5/RX5)-1 201(ClientLP1/ClientLP1)-5
8(TX6/RX6)-1 201(ClientLP1/ClientLP1)-6
9(TX7/RX7)-1 201(ClientLP1/ClientLP1)-7
10(TX8/RX8)-1 201(ClientLP1/ClientLP1)-8
Cross-connect module Cross-connect module
The internal cross-connection of the board, which needs to be configured on the NMS
The client side of the TOM board are cross-connected to the WDM side of other boards,
which needs to be configured on the NMS
NOTE
A cross-connection can be configured between any client-side port and any ClientLP port.
Legend Information
Figure 3-3 shows legend information about U2000 operations.
Procedure
Step 1 Set the Board Mode of the TN11TOM board to Cascading mode.
Operation Example:
Step 2 Optional: When the client service type is ,Service Mode must be set to OTN Mode.
Operation Example:
Step 3 Configure the service type for the ports on the TN11TOM board.
Operation Example:
1
4
2
NOTICE
l Modifying the service type leads to a service interruption.
l When configuring a GE service, make sure that the service encapsulation types specified
for the transmitter and receiver are the same.
Step 4 Configure the cross-connections from the RX/TX ports to the ClientLP ports on the
TN11TOM board.
Operation Example in the client service type for FE, for example ,For other services types,
configuration is the same:
1
NOTE
The service type must be the same as Service Type in the WDM Interface window of the TN11TOM board.
In this configuration, you can set Service Level to GE or ANY. If you set Service Level to ANY, you can set
Service Type to a specific service, such as FE.
Step 5 Configure the cross-connections for the ODU1 services between the TN11TOM and
TN12NS2 boards.
Operation Example:
NOTE
----End
Application Diagram
Figure 3-4 lists two conditions in which the TN11TOM board works in cascading ODU1
tributary-line mode. Perform the configurations for this board according to the network plan.
l Dual-fed and selectively receiving on the WDM side: The TN11TOM board receives a
maximum of six services on the client side. The other two client-side ports work as
WDM-side ports, which selectively receive services.
l Single transmitting and single receiving on the WDM side: The TN11TOM board
receives a maximum of seven services on the client side, and the other client-side port
works as a WDM-side port, which also receives services.
Figure 3-4 Position of the TN11TOM board in a WDM system (scenario 2: ODU1 tributary-
line mode (cascading))
Dual-fed and selectively receiving on the WDM side:
1xOTU1 1xOTU1
RX1 RX1
TOM TOM
TX1 TX7 RX7
FE, GE, FDDI, STM- TX1 FE, GE, FDDI, STM-
1, OC-3, STM-4, OC- MUX/ MUX/ 1, OC-3, STM-4, OC-
RX7 DMUX DMUX TX7
12, STM-16, OC- 12, STM-16, OC-
1×ODU1
1×OTU1
1×ODU1
1×OTU1
6×Any
6×Any
48,ESCON, 48,ESCON,
FC100, FICON, FC100, FICON,
TX8 RX8
FC200, FICON RX6 RX6 FC200, FICON
Express, DVB-ASI, MUX/ MUX/
RX8 DMUX TX8 Express, DVB-ASI,
OTU1 DMUX
TX6 TX6 OTU1
Any Any
1×ODU1
1×OTU1
7×Any
48,ESCON, 48,ESCON,
7×Any
MUX/ MUX/
FC100, FICON, RX8 DMUX DMUX TX8 FC100, FICON,
FC200, FICON FC200, FICON
RX7 RX7
Express, DVB-ASI, Express, DVB-ASI,
OTU1 OTU1
TX7 TX7
Any Any
Cross-Connection Diagram
Figure 3-5 shows the cross-connection diagram of the TN11TOM board.
Figure 3-5 Cross-connection diagram of the TN11TOM board (scenario 2: ODU1 tributary-
line mode (cascading))
Dual-fed and selectively receiving on the WDM side:
Client side WDM side
3(TX1/RX1)-1 201(ClientLP1/ClientLP1)-1 51(ODU1LP1/ODU1LP1)-1 9(TX7/RX7)-1
4(TX2/RX2)-1 201(ClientLP1/ClientLP1)-2 3
5(TX3/RX3)-1 201(ClientLP1/ClientLP1)-3 10(TX8/RX8)-1
6(TX4/RX4)-1 1 201(ClientLP1/ClientLP1)-4
7(TX5/RX5)-1 201(ClientLP1/ClientLP1)-5 2
8(TX6/RX6)-1 201(ClientLP1/ClientLP1)-6
201(ClientLP1/ClientLP1)-7
201(ClientLP1/ClientLP1)-8 TOM
Cross-connect module Cross-connect module Cross-connect module
The internal cross-connection of the board, which needs to be configured on the NMS
The internal cross-connection of the board, which needs to be configured on the NMS
NOTE
l Only the RX7/TX7 and RX8/TX8 optical ports can be used as WDM-side optical ports.
l A cross-connection can be configured between any client-side port and any ClientLP port.
Legend Information
Figure 3-6 shows legend information about U2000 operations.
Procedure
Step 1 Set the Board Mode of the TN11TOM board to Cascading mode.
Operation Example:
1
3
2
4
6
5
NOTE
In cascading mode, only RX7/TX7 and RX8/TX8 can be used as the WDM-side optical ports.
1. For the application of the single transmitting and single receiving on the WDM side, set RX7/TX7 or
RX8/TX8 as the WDM-side optical port.
2. For the application of the dual-fed and selectively receiving on the WDM side, set both RX7/TX7 and
RX8/TX8 as the WDM-side optical ports.
3. If Type of a port is set to Line Side Color Optical Port, ensure that an optical module transmitting the
same wavelength signals as the corresponding port of the M40 board has been configured on the port.
Step 3 Optional: When the client service type is ,Service Mode must be set to OTN Mode.
Operation Example:
1
Step 4 Configure the service type for the ports on the TN11TOM board.
Operation Example:
4
2
NOTICE
l Modifying the service type leads to a service interruption.
l When configuring a GE service, make sure that the service encapsulation types specified
for the transmitter and receiver are the same.
Step 5 Configure the cross-connections from the RX/TX ports to the ClientLP ports on the
TN11TOM board for the Any services that are sent to the board. Note that the figure assumes
that the client service type is FE. For other services, the configuration is similar.Operation
Example:
NOTE
Step 6 Configure ODU1 cross-connections from the ClientLP ports to the ODU1LP ports on the
TN11TOM board.Operation Example:
NOTE
Step 7 Configure OTU1 cross-connections between the ODU1LP ports and WDM-side
ports.Parameters of the working channel,Operation Example:
1
NOTE
The working channel port and the protection channel port are for dual feeding. The service on the working
channel must be set as bidirectional, and the service on the protection channel must be set as unidirectional.
In this example, port 10 (RX8/TX8) is the working channel port, and port 9 (RX7/TX7) is the protection
channel port.
Step 8 Optional: Configure selective receiving at the WDM side of the TN11TOM board.Operation
Example:
6
2
NOTE
For the application of dual-fed and selectively receiving on the WDM side, this step is mandatory.
----End
Application Diagram
Figure 3-7 shows the position of the TN11TOM board in a WDM system where the
TN11TOM board works in non-cascading ODU1 tributary mode.
Figure 3-7 Position of the TN11TOM board in a WDM system (scenario 3: ODU1 tributary
mode (non-cascading))
4xODU1 1xOTU2 1xOTU2 4xODU1
RX1 TX1
TOM TOM
FC100, FICON, FE, TX1 RX1 FC100, FICON, FE,
GE, STM-1, OC-3, 1 1 GE, STM-1, OC-3,
STM-4, OC-12, STM-4, OC-12,
4×ODU1
4×ODU1
8×Any
8×Any
STM-16, OC-48 MUX/ MUX/ STM-16, OC-48
NS2 NS2
, FC200, FICON DMUX DMUX , FC200, FICON
Express, DVB-ASI, RX8 TX8 Express, DVB-ASI,
ESCON, FDDI, 4 4 ESCON, FDDI,
OTU1 TX8 RX8 OTU1
Cross-Connection Diagram
Figure 3-8 shows the cross-connection diagram of the TN11TOM board.
Figure 3-8 Cross-connection diagram of the TN11TOM board (scenario 3: ODU1 tributary
mode (non-cascading))
WDM side
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:1
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:2 Line board
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:3 in standard
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:4 mode
51(ODU1LP1/ODU1LP1)-1 Line/PID
51(ODU1LP1/ODU1LP1)-2 board in
51(ODU1LP1/ODU1LP1)-3 compatible
Cross-connect 51(ODU1LP1/ODU1LP1)-4 mode
module
Client side
3(TX1/RX1)-1 201(ClientLP1/ClientLP1)-1
4(TX2/RX2)-1 201(ClientLP1/ClientLP1)-2
5(TX3/RX3)-1 201(ClientLP1/ClientLP1)-3
201(ClientLP1/ClientLP1)-4
6(TX4/RX4)-1
7(TX5/RX5)-1 1 202(ClientLP2/ClientLP2)-1 2
202(ClientLP2/ClientLP2)-2
8(TX6/RX6)-1
9(TX7/RX7)-1 203(ClientLP3/ClientLP3)-1
203(ClientLP3/ClientLP3)-2 TOM
10(TX8/RX8)-1 203(ClientLP3/ClientLP3)-3
203(ClientLP3/ClientLP3)-4
204(ClientLP4/ClientLP4)-1
204(ClientLP4/ClientLP4)-2
The internal cross-connection of the board, which needs to be configured on the NMS
The client side of the TOM board are cross-connected to the WDM side of other boards,
which needs to be configured on the NMS
NOTE
A cross-connection can be configured between any client-side port and any ClientLP port.
Legend Information
Figure 3-9 shows legend information about U2000 operations.
Procedure
Step 1 Set Board Mode to Non-cascading mode.Operation Example:
1 3
Step 2 Optional: When the client service type is ,Service Mode must be set to OTN Mode.
Operation Example:
1
Step 3 Configure the service type for the ports on the TN11TOM board.
Operation Example:
4
2
NOTICE
l Modifying the service type leads to a service interruption.
l When configuring a GE service, make sure that the service encapsulation types specified
for the transmitter and receiver are the same.
Step 4 Configure the cross-connections from the RX/TX ports to the ClientLP ports on the
TN11TOM board for the Any services that are sent to the board. Operation Example:
NOTE
Complete the settings as shown in the following figure. Note that the figure assumes that the client service
type is FE. For other services, the configuration is similar.
The service type must be the same as Service Type in the WDM Interface window of the TN11TOM board.
In this configuration, you can set Service Level to GE or ANY. If you set Service Level to ANY, you can set
Service Type to a specific service, such as FE.
Step 5 Configure a bidirectional ODU1 cross-connection between the TN12NS2 line board and the
TN11TOM board.Operation Example:
NOTE
This step uses the compatible mode board as an example.Repeat to configure the remaining cross-
connections between the TN11TOM and TN12NS2 boards.
----End
Application Diagram
Figure 3-10 shows the position of the TN11TOM board in a WDM system where the
TN11TOM board works in non-cascading ODU1 tributary-line mode.
Figure 3-10 Position of the TN11TOM board in a WDM system (scenario 4: ODU1 tributary-
line mode (non-cascading))
4xOTU1 4xOTU1
4×ODU1
4×OTU1
4×ODU1
4×OTU1
, STM-4, OC-12, , STM-4, OC-12,
4×Any
4×Any
DVB-ASI, ESCON, MUX/ MUX/ DVB-ASI, ESCON,
FDDI, FC200, FICON DMUX DMUX FDDI, FC200,
TX8 RX8
Express, STM-16, RX4 RX4 FICON Express,
OC-48 STM-16, OC-48
TX4 RX8 TX8
TX4
Any Any
Cross-Connection Diagram
Figure 3-11 shows the cross-connection diagram of the TN11TOM board.
Figure 3-11 Cross-connection diagram of the TN11TOM board (scenario 4: ODU1 tributary-
line mode (non-cascading))
Client side WDM side
The internal cross-connection of the board, which needs to be configured on the NMS
NOTE
l All RX/TX optical ports can be used as WDM-side optical ports. This section uses the type of ports
7(RX5/TX5), 8(RX6/TX6), 9(RX7/TX7) and 10(RX8/TX8) to be used as WDM-side optical ports
as an example.
l A cross-connection can be configured between any ODU1LP port and any WDM-side port.
Legend Information
Figure 3-12 shows legend information about U2000 operations.
Procedure
Step 1 Set Board Mode to Non-cascading mode.Operation Example:
1 3
1
3
2
4
6
5
NOTE
Step 3 Optional: When the client service type is ,Service Mode must be set to OTN Mode.
Operation Example:
1
Step 4 Configure the service type for the ports on the TN11TOM board.
Operation Example:
4
2
NOTICE
l Modifying the service type leads to a service interruption.
l When configuring a GE service, make sure that the service encapsulation types specified
for the transmitter and receiver are the same.
Step 5 Configure the cross-connections from the RX/TX ports to the ClientLP ports on the
TN11TOM board for the Any services that are sent to the board. Note that the figure assumes
that the client service type is FE. For other services, the configuration is similar.Operation
Example:
NOTE
Step 6 Configure ODU1 cross-connections from the ClientLP ports to the ODU1LP ports on the
TN11TOM board.Operation Example:
NOTE
Step 7 Configure a cross-connection between the ODU1LP port and any WDM-side port on the
TN11TOM board.Operation Example:
1
NOTE
Configure a cross-connection between the ODU1LP port and any WDM-side port, and select the port for
which the port type is changed in Step 2.
Repeat to configure the remaining OTU1 services.
----End
Application Diagram
Figure 3-13 shows the position of the TN11TOM board in a WDM system in which the
TN11TOM board works as an electrical regeneration board and its ports work in ODU1
tributary-line mode.
Figure 3-13 Position of the TN11TOM board in a WDM system (scenario 5: ODU1 tributary-
line mode (electrical regeneration board))
4xOTU1 4xOTU1
4×OTU1
DMUX MUX
RX4 TX4
4xOTU1 4xOTU1
4×OTU1
4×OTU1
MUX DMUX
TX4 RX4
Cross-Connection Diagram
Figure 3-14 shows the cross-connection diagram of the TN11TOM board.
Figure 3-14 Cross-connection diagram of the TN11TOM board (scenario 5: ODU1 tributary-
line mode (electrical regeneration board))
Client side WDM side
The internal cross-connection of the board, which needs to be configured on the NMS
NOTE
l All RX/TX optical ports can be used as WDM-side optical ports. This section uses the type of ports
7(RX5/TX5), 8(RX6/TX6), 9(RX7/TX7) and 10(RX8/TX8) to be used as WDM-side optical ports
as an example.
l A cross-connection can be configured between any client-side port and any ClientLP port.
l A cross-connection can be configured between any ODU1LP port and any WDM-side port.
Legend Information
Figure 3-15 shows legend information about U2000 operations.
Procedure
Step 1 Set Board Mode to Non-cascading mode.Operation Example:
1 3
1
3
2
4
6
5
NOTE
Step 3 Configure the service mode for the ports on the TN11TOM board.Operation Example:
1
NOTE
Because the service type is OTU-1, set Service Mode of ports to OTN Mode.
Step 4 Set the service type to OTU-1 for the port. Operation Example:
4
2
Step 5 Configure the cross-connections from the RX/TX ports to the ClientLP ports on the
TN11TOM board for the OTU1 services that are input to the board.Operation Example:
1
NOTE
Repeat to configure the remaining OTU1 services.
Step 6 Configure the cross-connections from the ClientLP ports to the ODU1LP ports on the
TN11TOM board for the ODU1 services.Operation Example:
NOTE
Repeat to configure the remaining OTU1 services.
Step 7 Configure a cross-connection between the ODU1LP port and any WDM-side port.Operation
Example:
1
NOTE
Selected in the WDM-side optical portsStep 2to modefy the Port type of port
Repeat to configure the remaining OTU1 services.
----End
Board Description
Working
mode
Cascading l A maximum of eight multi-rate (< 2.5 Gbit/s) client-side services can
mode be input to the TN52TOM board through the SFP module on the
client side.
l The services are then multiplexed into different timeslots of one or
two ODU0 services or one ODU1 service.
l Each group of ClientLP ports, for example, 201(ClientLP1/
ClientLP1)-1 to 201(ClientLP1/ClientLP1)-8 ports, can access a
maximum of eight client-side services.
Non-cascading l A maximum of eight multi-rate (< 2.5 Gbit/s) client-side services can
mode be input to the TN52TOM board through the SFP module on the
client side.
l The services are then multiplexed into different timeslots of one to
eight ODU0 services or one to four ODU1 services.
l Each group of ClientLP ports, for example, 201(ClientLP1/
ClientLP1)-1 to 201(ClientLP1/ClientLP1)-4 ports, can access a
maximum of four client-side services.
Table 3-4 Mapping between the working modes and the mapping path of the TN52TOM
board
Board Configuration Port Working Mode Mapping Path
Working Scenario
mode
a: "Any" in the table indicates the client-side service supported in the corresponding
application scenario.
NOTE
l [->ODU1]: indicates that "ODU1" is optional. For example, in non-cascading ODU0 tributary mode,
there are two service signal flows: Any->ODU0 and Any->ODU0->ODU1.
l None (not for ports): indicates that the resources at this port are not used and are released to other
ports.
Applicat The following port working mode scenarios are only supported by the OptiX
ion OSN 8800.
scenario l Application Scenario 11: Non-cascading ODU1_ODU0 mode (OTU1-
s >ODU1->ODU0)
l Application Scenario 12: Non-cascading ODU1_ANY_ODU0 re-
encapsulation mode (OTU1->ODU1->Any->ODU0)
The following port working mode application scenarios are only supported by
the OptiX OSN 6800 and OptiX OSN 3800.
l Application Scenario 8: Non-cascading ODU1_ANY_ODU0_ODU1 re-
encapsulation mode (OTU1->ODU1->Any->ODU0->ODU1)
Cross- l The OptiX OSN 8800 does not support distributed cross-connection.
connect l For the OptiX OSN 6800,
– The TN52TOM board can cross-connect a maximum of six Any services
through the backplane.
– The TN52TOM boards in paired slots can cross-connect Any services.
l For the OptiX OSN 3800,
– The TN52TOM board can cross-connect a maximum of six Any services
through the backplane.
– The TN52TOM boards in a mesh slot group support cross-connections
of Any services between each other.
– Inter-board ODU1 cross-connections between the TN52TOM and
TN52NS2 boards, if required, should be configured in such a manner
that the ClientLP3-1 port on the TN52TOM board is cross-connected to
the ODU1LP1-3 port on the TN52NS2 board and the ClientLP5-1 port
on the TN52TOM board is cross-connected to the ODU1LP1-2 port on
the TN52NS2 board.
Item Description
WDM- In the cascading tributary-line mode, only RX7/TX7 and RX8/TX8 can be used
side as the WDM-side optical ports.
optical In the non-cascading tributary-line mode, all RX/TX optical ports can be used
ports as WDM-side optical ports.
In the tributary mode, none of the RX/TX optical ports can be used as WDM-
side optical ports.
Port In non-cascading board working mode, the ports on the board can be set to
working different port working modes.
mode
The actions that are labeled "optional" in the preceding figure are required only in specific
scenarios. The following provides the details:
l Configure the service mode:
– If the service type is OTU1, set Service Mode to OTN Mode for the port.
– If the service type is any other service, retain the default value CLIENT Mode for
the port.
l Configure the cross-connections between AnyLP ports:
– This operation is mandatory for scenario 8 "ODU1_ANY_ODU0_ODU1 re-
encapsulation mode (non-cascading)" and scenario 9 "ODU1_ANY_ODU0_ODU1
re-encapsulation tributary-line mode (non-cascading)".
– This operation is not required for any other scenarios.
l Configure intra-board 1+1 protection:
– This operation is mandatory for the application of "dual-fed and selectively
receiving on the WDM side" in the Tributary-Line Mode.
– This operation is not required for any other scenarios.
Application Diagram
Figure 3-17 and Figure 3-18 show the position of the TN52TOM board in a WDM system in
which the TN52TOM board works in cascading ODU0 tributary mode (Any->ODU0(-
>ODU1)).
RX1 RX1
TOM TOM
TX1 M M TX1
U U
FE, GE, X X FE, GE,
2×ODU0
1×ODU1
1×ODU1
2×ODU0
N N
8×Any
FC100, FICON,
8×Any
/ / FC100, FICON,
DVB-ASI, SDI, S D S DVB-ASI, SDI,
D
ESCON, FDDI RX8 2 2
M M RX8 ESCON, FDDI
U U
TX8 X X TX8
Figure 3-18 Position of the TN52TOM in a WDM system (scenario 1: Any->ODU0) (OptiX
OSN 8800)
2xODU0 1xOTU2 1xOTU2 2xODU0
2×ODU0
N N
8×Any
FC100, FICON, FC100, FICON,
2×ODU0
8×Any
/ /
DVB-ASI, SDI, S D S DVB-ASI, SDI,
D
ESCON, FDDI 2 M 2 ESCON, FDDI
RX8 M TX8
U U
2 2 2 2
TX8 X X RX8
Cross-Connection Diagram
Figure 3-19 and Figure 3-20 show the cross-connection diagram of the TN52TOM board.
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:1 Line
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:2 board in
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:3 standard
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:4 mode
51(ODU1LP1/ODU1LP1)-1 Line/PID
51(ODU1LP1/ODU1LP1)-2 board in
51(ODU1LP1/ODU1LP1)-3 compatible
Cross-connect 51(ODU1LP1/ODU1LP1)-4 mode
module
Client side
161(ODU0LP1
3(TX1/RX1)-1 201(ClientLP1/ClientLP1)-1
4(TX2/RX2)-1 201(ClientLP1/ClientLP1)-2 /ODU0LP1)-1
5(TX3/RX3)-1 201(ClientLP1/ClientLP1)-3 2
6(TX4/RX4)-1 201(ClientLP1/ClientLP1)-4
7(TX5/RX5)-1 1 201(ClientLP1/ClientLP1)-5 3
8(TX6/RX6)-1 201(ClientLP1/ClientLP1)-6
9(TX7/RX7)-1 201(ClientLP1/ClientLP1)-7
201(ClientLP1/ClientLP1)-8 161(ODU0LP1
10(TX8/RX8)-1 202(ClientLP2/ClientLP2)-1
202(ClientLP2/ClientLP2)-2 /ODU0LP1)-2
202(ClientLP2/ClientLP2)-3
202(ClientLP2/ClientLP2)-4
202(ClientLP2/ClientLP2)-5
202(ClientLP2/ClientLP2)-6
202(ClientLP2/ClientLP2)-7
202(ClientLP2/ClientLP2)-8 TOM
Cross-connect module Cross-connect module Cross-connect module
The internal cross-connection of the board, which needs to be configured on the NMS
The straight-through of the board, which does not need to be configured on the NMS
The client side of the TOM board are cross-connected to the WDM side of other boards,
which needs to be configured on the NMS
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:1-ODU0:1
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:1-ODU0:2 Line/PID
board in
standard
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:4-ODU0:1 mode
Other board 1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:4-ODU0:2
161(ODU0LP1/ODU0LP1)-1
161(ODU0LP1/ODU0LP1)-2 Line/PID
board in
compatible
164(ODU0LP4/ODU0LP4)-1 mode
Cross-connect 164(ODU0LP4/ODU0LP4)-2
module
Client side
3(TX1/RX1)-1 201(ClientLP1/ClientLP1)-1
4(TX2/RX2)-1 201(ClientLP1/ClientLP1)-2
5(TX3/RX3)-1 1 201(ClientLP1/ClientLP1)-3
6(TX4/RX4)-1 201(ClientLP1/ClientLP1)-4
7(TX5/RX5)-1 201(ClientLP1/ClientLP1)-5
8(TX6/RX6)-1 201(ClientLP1/ClientLP1)-6 2
9(TX7/RX7)-1 201(ClientLP1/ClientLP1)-7
201(ClientLP1/ClientLP1)-8 TOM
10(TX8/RX8)-1 202(ClientLP2/ClientLP2)-1
202(ClientLP2/ClientLP2)-2
202(ClientLP2/ClientLP2)-3
202(ClientLP2/ClientLP2)-4
202(ClientLP2/ClientLP2)-5
202(ClientLP2/ClientLP2)-6
202(ClientLP2/ClientLP2)-7
202(ClientLP2/ClientLP2)-8
Cross-connect module Cross-connect module
Legend Information
Figure 3-21 shows legend information about U2000 operations.
Procedure
Step 1 ConfigureBoard Working ModeandPort Working Modefor the TN52TOM
board.Operation Example:
NOTE
Port Working Modeis ODU0 mode (Any->ODU0(->ODU1)).
Step 2 Configure Service Type of the TN52TOM board according to the service planning. Operation
Example:
NOTICE
l Modifying the service type leads to a service interruption.
l When configuring a GE service, make sure that the service encapsulation types specified
for the transmitter and receiver are the same.
NOTE
l If you set Service Type to Any, you must set the service rate in Client Service Bearer Rate
(Mbit/s).
l The board can receive the FE/FDDI/DVB-ASI/SDI/ESCON/GE/FC100/FICON services at the
same time, but the total rate of these services must be less than or equal to 2.5 Gbit/s.
l If a channel of the ClientLP1 port and a channel of the ClientLP2 port are identified by the same
number, these two channels cannot be used at the same time. For example, if the 201(ClientLP1/
ClientLP1)-1 service type is configured, the 202(ClientLP2/ClientLP2)-1 service type cannot be
configured.
l Only one GE service can be input through each group of ClientLP ports.
l The total rate of services that are input at each group of ClientLP ports, such as 201(ClientLP1/
ClientLP1)-1 to 201(ClientLP1/ClientLP)-8, cannot be greater than 1.25 Gbit/s.
Step 3 Configure the cross-connections from the RX/TX ports to the ClientLP ports on the
TN52TOM board for the Any services that are input to the board.Operation Example:
1
NOTE
The service type must be the same as Service Type in the WDM Interface window of the TN52TOM board.
In this configuration, you can set Level to GE or ANY. If you set Level to ANY, you can set Service Type to
a specific service, such as FE.
Repeat Step 3 to configure the remaining services.
Step 4 Configure electrical cross-connections for the ODU1 services between the TN52TOM and
TN52NS2 boards.Operation Example:
1
NOTE
This configuration is only supported by the OptiX OSN 6800 and OptiX OSN 3800.
This step uses the compatible mode board as an example.
When ODU1 cross-connections are created, ODU0 cross-connections from the ClientLP port to the
ODU0LP port on the TN52TOM board are automatically created.
Step 5 Configure electrical cross-connections for the two ODU0 services between the TN52TOM
and TN52NS2 boards.Operation Example:
NOTE
----End
Application Diagram
Figure 3-22 lists two conditions in which the TN52TOM board works in cascading ODU0
tributary-line mode. Perform the configurations according to the network plan.
l Dual-fed and selectively receiving on the WDM side: The TN52TOM board receives a
maximum of six services on the client side. The other two client-side ports work as
WDM-side ports, selectively receiving services.
l Single transmitting and single receiving on the WDM side: The TN52TOM board
receives a maximum of seven services on the client side. The other client-side port works
as a WDM-side port.
RX1 RX1
TOM RX7 TOM
TX7
TX1 MUX/ MUX/ TX1
RX7 DMUX DMUX TX7
FE, GE, FE, GE,
FC100, FICON, FC100, FICON,
2×ODU0
1×ODU1
1×ODU1
2×ODU0
1×OTU1
1×OTU1
6×Any
6×Any
DVB-ASI, SDI, DVB-ASI, SDI,
ESCON, FDDI ESCON, FDDI
RX6 TX8 RX8 RX6
MUX/ MUX/
RX8 DMUX DMUX TX8
TX6 TX6
Any Any
RX1 TX1
TOM TOM
TX1 RX1
FE, GE, FE, GE,
TX8 RX8
2×ODU0
FC100, FICON,
2×ODU0
1×ODU1
1×ODU1
1×OTU1
7×Any
DVB-ASI, SDI, MUX/ MUX/
RX8 DMUX TX8 DVB-ASI, SDI,
ESCON, FDDI DMUX
RX7 TX7ESCON, FDDI
TX7 RX7
Any Any
Cross-Connection Diagram
Figure 3-23 shows the cross-connection diagram of the TN52TOM board.
The internal cross-connection of the board, which needs to be configured on the NMS
The straight-through of the board, which does not need to be configured on the NMS
The internal cross-connection of the board, which needs to be configured on the NMS
The straight-through of the board, which does not need to be configured on the NMS
Legend Information
Figure 3-24 shows legend information about U2000 operations.
Procedure
Step 1 ConfigureBoard Working ModeandPort Working Modefor the TN52TOM
board.Operation Example:
NOTE
Port Working Modeis ODU0 mode (Any->ODU0(->ODU1)).
Step 2 Configure the working mode for the TN52TOM board.Operation Example:
1
3
6
5
7
8
NOTE
In cascading mode, only RX7/TX7 and RX8/TX8 can be used as the WDM-side optical ports.
l For the application of the single transmitting and single receiving on the WDM side, set RX7/TX7
or RX8/TX8 as the WDM-side optical port.
l For the application of the dual-fed and selectively receiving on the WDM side, set both RX7/TX7
and RX8/TX8 as the WDM-side optical ports.
If Type of a port is set to Line Side Color Optical Port, ensure that an optical module transmitting the
same wavelength signals as the corresponding port of the M40 board has been configured on the port.
Step 3 Configure Service Type of the TN52TOM board according to the service planning. Operation
Example:
NOTICE
l Modifying the service type leads to a service interruption.
l When configuring a GE service, make sure that the service encapsulation types specified
for the transmitter and receiver are the same.
NOTE
l If you set Service Type to Any, you must set the service rate in Client Service Bearer Rate
(Mbit/s).
l The board can receive the FE/FDDI/DVB-ASI/SDI/ESCON/GE/FC100/FICON services at the
same time, but the total rate of these services must be less than or equal to 2.5 Gbit/s.
l If a channel of the ClientLP1 port and a channel of the ClientLP2 port are identified by the same
number, these two channels cannot be used at the same time. For example, if the 201(ClientLP1/
ClientLP1)-1 service type is configured, the 202(ClientLP2/ClientLP2)-1 service type cannot be
configured.
l Only one GE service can be input through each group of ClientLP ports.
l The total rate of services that are input at each group of ClientLP ports, such as 201(ClientLP1/
ClientLP1)-1 to 201(ClientLP1/ClientLP)-8, cannot be greater than 1.25 Gbit/s.
Step 4 Configure the cross-connections from the RX/TX ports to the ClientLP ports on the
TN52TOM board for the Any services that are input to the board.Operation Example:
1
NOTE
The service type must be the same as Service Type in the WDM Interface window of the TN52TOM board.
In this configuration, you can set Level to GE or ANY. If you set Level to ANY, you can set Service Type to
a specific service, such as FE.
Repeat Step 4 to configure the remaining services.
NOTE
The working channel port and the protection channel port are the two ports used for dual feeding. The service
on the working channel must be set as bidirectional, and the service on the protection channel must be set as
unidirectional. In this example, port 10(RX8/TX8) is the working channel port, and port 9(RX7/TX7) is the
protection channel port.
Parameters of the working channel,Operation Example:
Step 6 Configure selective receiving at the WDM side of the TN52TOM board.Operation Example:
6
2
----End
Application Diagram
Figure 3-25 shows the position of the TN52TOM board in a WDM system where the
TN52TOM board works in cascading ODU1 tributary mode.
RX1 TX1
TOM TOM
TX1 RX1
FE, STM-1, STM-4, M M FE, STM-1, STM-4,
STM-16, OC-3, OC- U U STM-16, OC-3, OC-
12, OC-48, FC100, X X 12, OC-48, FC100,
1×ODU1
1×ODU1
N N
8×Any
8×Any
Cross-Connection Diagram
Figure 3-26 shows the cross-connection diagram of the TN52TOM board.
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:1
Line board
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:2
in standard
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:3
mode
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:4
51(ODU1LP1/ODU1LP1)-1
Line/PID
51(ODU1LP1/ODU1LP1)-2
board in
51(ODU1LP1/ODU1LP1)-3
compatible
51(ODU1LP1/ODU1LP1)-4
Cross-connect mode
module
Client side
3(TX1/RX1)-1 201(ClientLP1/ClientLP1)-1
4(TX2/RX2)-1 201(ClientLP1/ClientLP1)-2
5(TX3/RX3)-1 201(ClientLP1/ClientLP1)-3 2
6(TX4/RX4)-1 1 201(ClientLP1/ClientLP1)-4 TOM
7(TX5/RX5)-1 201(ClientLP1/ClientLP1)-5
8(TX6/RX6)-1 201(ClientLP1/ClientLP1)-6
9(TX7/RX7)-1 201(ClientLP1/ClientLP1)-7
10(TX8/RX8)-1 201(ClientLP1/ClientLP1)-8
Cross-connect module Cross-connect module
The internal cross-connection of the board, which needs to be configured on the NMS
The client side of the TOM board are cross-connected to the WDM side of other boards,
which needs to be configured on the NMS
Legend Information
Figure 3-27 shows legend information about U2000 operations.
Procedure
Step 1 ConfigureBoard Working ModeandPort Working Modeof the TN52TOM board.Operation
Example:
NOTE
Port Working Modemust beODU1 mode (Any->ODU1).
Step 2 Configure Service Type of the TN52TOM board according to the service plan. Operation
Example:
NOTICE
l Modifying the service type will lead to service interruption.
l When configuring a GE service, make sure that the service encapsulation types specified
for the transmitter and receiver are the same.
NOTE
l If you set Service Type to Any, you must set the service rate in Client Service Bearer Rate
(Mbit/s).
l The board can receive the FE/FDDI/STM-1/OC-3/DVB-ASI/SDI/ESCON/STM-4/OC-12/GE/
FC100/FICON/STM-16/OC-48/FC200/FICON Express/HD-SDI services at the same time, but the
total rate of the services must be less than or equal to 2.5 Gbit/s.
l If a channel of the ClientLP1 port and a channel of the ClientLP2 port are identified by the same
number, these two channels cannot be used at the same time. For example, if the 201(ClientLP1/
ClientLP1)-1 service type is configured, the 202(ClientLP2/ClientLP2)-1 service type cannot be
configured.
l The total rate of services that are received by each group of ClientLP ports, such as
201(ClientLP1/ClientLP1)-1 to 201(ClientLP1/ClientLP1)-8, cannot be higher than 1.25 Gbit/s.
l Each group of ClientLP ports can access only one service that has a rate higher than 1.25 Gbit/s,
and this service can be configured on only the first channel of the ClientLP port.
Step 3 Configure the cross-connections from the RX/TX ports to the ClientLP ports on the
TN52TOM board for the Any services that are input to the board. Operation Example:
1
NOTE
The service type must be the same as Service Type in the WDM Interface window of the TN52TOM board.
In this configuration, you can set Level to GE or ANY. If you set Level to ANY, you can set Service Type to
a specific service, such as FE.
Repeat Step 3 to configure the remaining services.
Step 4 Configure electrical cross-connections for the ODU1 services between the TN52TOM and
TN52NS2 boards.Operation Example:
1
NOTE
----End
Application Diagram
Figure 3-28 shows two applications where the TN52TOM board works in cascading ODU1
tributary-line mode. Perform configurations according to the network design.
l Dual-fed selectively receiving on the WDM side: The TN52TOM board receives a
maximum of six channels of services on the client side and the other two client-side
ports work as WDM-side ports, dual-fed selectively receiving services.
l Single transmitting and single receiving on the WDM side: The TN52TOM board
receives a maximum of seven channels of services on the client side and the other client-
side port works as a WDM-side port.
1×ODU1
1×ODU1
1×OTU1
1×OTU1
6×Any
48, FC100, FC200,
6×Any
48, FC100, FC200,
FICON, FICON
FICON, FICON TX8 RX8
Express, HD-SDI, RX6 MUX/ MUX/ RX6 Express, HD-SDI,
DVB-ASI, SDI,
DVB-ASI, SDI, RX8 DMUX DMUX TX8
ESCON, FDDI
ESCON, FDDI TX6 TX6
Any Any
RX1 TX1
TOM TOM
FE, GE, STM-1, TX1 RX1 FE, GE, STM-1,
STM-4, STM-16, STM-4, STM-16,
OC-3, OC-12, OC- TX8 RX8 OC-3, OC-12, OC-
1×ODU1
1×ODU1
1×OTU1
1×OTU1
7×Any
7×Any
48, FC100, FC200, MUX/ MUX/ 48, FC100, FC200,
FICON, FICON RX8 TX8 FICON, FICON
DMUX DMUX
Express, HD-SDI, RX7 TX7 Express, HD-SDI,
DVB-ASI, SDI, DVB-ASI, SDI,
ESCON, FDDI TX7 RX7 ESCON, FDDI
Any Any
Cross-Connection Diagram
Figure 3-29 shows the cross-connection diagram of the TN52TOM board.
The internal cross-connection of the board, which needs to be configured on the NMS
The straight-through of the board, which does not need to be configured on the NMS
The internal cross-connection of the board, which needs to be configured on the NMS
The straight-through of the board, which does not need to be configured on the NMS
Legend Information
Figure 3-30 shows legend information about U2000 operations.
Procedure
Step 1 ConfigureBoard Working ModeandPort Working Mode of the TN52TOM board.Operation
Example:
Step 2 Configure the working mode for the TN52TOM board.Operation Example:
1
3
6
5
7
8
NOTE
In cascading mode, only RX7/TX7 and RX8/TX8 can be used as the WDM-side optical ports.
l For the application of the single transmitting and single receiving on the WDM side, set RX7/TX7
or RX8/TX8 as the WDM-side optical port.
l For the application of the dual-fed and selectively receiving on the WDM side, set both RX7/TX7
and RX8/TX8 as the WDM-side optical ports.
If Type of a port is set to Line Side Color Optical Port, ensure that an optical module transmitting the
same wavelength signals as the corresponding port of the M40 board has been configured on the port.
Step 3 Configure Service Type of the TN52TOM board according to the service plan.Operation
Example:
NOTICE
l Modifying the service type will lead to service interruption.
l When configuring a GE service, make sure that the service encapsulation types specified
for the transmitter and receiver are the same.
NOTE
l If you set Service Type to Any, you must set Service Rate(Mbit/s).
l If you set Service Type to Any, you must set the service rate in Client Service Bearer Rate
(Mbit/s).
l The board can receive the FE/FDDI/STM-1/OC-3/DVB-ASI/SDI/ESCON/STM-4/OC-12/GE/
FC100/FICON/STM-16/OC-48/FC200/FICON Express/HD-SDI services at the same time, but the
total rate of the services must be less than or equal to 2.5 Gbit/s.
l Services can be input at the six or seven pairs of client-side optical ports at a maximum rate of 2.5
Gbit/s.
l A ClientLP port can access only one service that has a rate higher than 1.25 Gbit/s, and this
service can be configured on only the first channel of the ClientLP port.
Step 4 Configure the cross-connections from the RX/TX ports to the ClientLP ports on the
TN52TOM board for the Any services that are input to the board.Operation Example:
1
NOTE
The service type must be the same as Service Type in the WDM Interface window of the TN52TOM board.
In this configuration, you can set Level to GE or ANY. If you set Level to ANY, you can set Service Type to
a specific service, such as FE.
Repeat Step 4 to configure the remaining services.
NOTE
The working channel port and the protection channel port are the two ports used for dual feeding. The service
on the working channel must be set as bidirectional, and the service on the protection channel must be set as
unidirectional. In this example, port 10(RX8/TX8) is the working channel port, and port 9(RX7/TX7) is the
protection channel port.
Parameters of the working channel,Operation Example:
Step 6 Configure selective receiving at the WDM side of the TN52TOM board.Operation Example:
6
2
----End
Application Diagram
Figure 3-31 and Figure 3-32 show the position of the TN52TOM board in a WDM system
where the TN52TOM board works in non-cascading ODU0 tributary mode (Any->ODU0[-
>ODU1]).
RX1 TX1
TOM TOM
TX1 M M RX1
1 1 1 1
U U
FE, GE, FE, GE,
X X
8×ODU0
4×ODU1
4×ODU1
8×ODU0
FC100, FICON, N N FC100, FICON,
8×Any
8×Any
/ /
DVB-ASI, SDI, S S DVB-ASI, SDI,
D D
ESCON, FDDI 2 2
RX8 M M TX8 ESCON, FDDI
4 4 U U 4 4
TX8 X X RX8
RX1 TX1
TOM TOM
TX1 M M RX1
1 1 1 1
FE, GE, U U
X X FE, GE,
8×ODU0
FC100, FICON,
8×ODU0
N N FC100, FICON,
8×Any
8×Any
DVB-ASI, SDI, / /
S D S DVB-ASI, SDI,
ESCON, FDDI D
2 M 2 TX8 ESCON, FDDI
RX8 M
U U
8 8 X X 8 8 RX8
TX8
Cross-Connection Diagram
Figure 3-33 and Figure 3-34 show the cross-connection diagram of the TN52TOM board.
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:1 Line/PID
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:2 board in
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:3 standard
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:4 mode
51(ODU1LP1/ODU1LP1)-1 Line/PID
51(ODU1LP1/ODU1LP1)-2 board in
51(ODU1LP1/ODU1LP1)-3 compatible
Cross-connect 51(ODU1LP1/ODU1LP1)-4 mode
module
Client side
3(TX1/RX1)-1 201(ClientLP1/ClientLP1)-1
4(TX2/RX2)-1 201(ClientLP1/ClientLP1)-2
5(TX3/RX3)-1 201(ClientLP1/ClientLP1)-3
201(ClientLP1/ClientLP1)-4 161(ODU0LP1
6(TX4/RX4)-1 /ODU0LP1)-1
1 202(ClientLP2/ClientLP2)-1 3 2
7(TX5/RX5)-1 202(ClientLP2/ClientLP2)-2
8(TX6/RX6)-1 202(ClientLP2/ClientLP2)-3
9(TX7/RX7)-1 202(ClientLP2/ClientLP2)-4
10(TX8/RX8)-1 203(ClientLP3/ClientLP3)-1 162(ODU0LP2
203(ClientLP3/ClientLP3)-2 /ODU0LP2)-1
204(ClientLP4/ClientLP4)-1
204(ClientLP4/ClientLP4)-2
205(ClientLP5/ClientLP5)-1
205(ClientLP5/ClientLP5)-2
205(ClientLP5/ClientLP5)-3
205(ClientLP5/ClientLP5)-4 163(ODU0LP3
206(ClientLP6/ClientLP6)-1 /ODU0LP3)-1
206(ClientLP6/ClientLP6)-2
206(ClientLP6/ClientLP6)-3
206(ClientLP6/ClientLP6)-4
TOM 207(ClientLP7/ClientLP7)-1 164(ODU0LP4
207(ClientLP7/ClientLP7)-2
208(ClientLP8/ClientLP8)-1 /ODU0LP4)-1
208(ClientLP8/ClientLP8)-2
Cross-connect module Cross-connect module Cross-connect module
The internal cross-connection of the board, which needs to be configured on the NMS
The straight-through of the board, which does not need to be configured on the NMS
The client side of the TOM board are cross-connected to the WDM side of other boards,
which needs to be configured on the NMS
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:1-ODU0:1
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:1-ODU0:2
Line/PID
board in
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:4-ODU0:1 standard
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:4-ODU0:2 mode
Other board
161(ODU0LP1/ODU0LP1)-1
161(ODU0LP1/ODU0LP1)-2 Line/PID
board in
compatible
164(ODU0LP4/ODU0LP4)-1 mode
Cross-connect 164(ODU0LP4/ODU0LP4)-2
module
Client side
3(TX1/RX1)-1 201(ClientLP1/ClientLP1)-1
4(TX2/RX2)-1 201(ClientLP1/ClientLP1)-2
5(TX3/RX3)-1 1 201(ClientLP1/ClientLP1)-3
6(TX4/RX4)-1 201(ClientLP1/ClientLP1)-4
7(TX5/RX5)-1 202(ClientLP2/ClientLP2)-1
8(TX6/RX6)-1 202(ClientLP2/ClientLP2)-2 2
9(TX7/RX7)-1 202(ClientLP2/ClientLP2)-3
202(ClientLP2/ClientLP2)-4
10(TX8/RX8)-1 203(ClientLP3/ClientLP3)-1
203(ClientLP3/ClientLP3)-2
204(ClientLP4/ClientLP4)-1 TOM
204(ClientLP4/ClientLP4)-2
205(ClientLP5/ClientLP5)-1
205(ClientLP5/ClientLP5)-2
205(ClientLP5/ClientLP5)-3
205(ClientLP5/ClientLP5)-4
206(ClientLP6/ClientLP6)-1
206(ClientLP6/ClientLP6)-2
206(ClientLP6/ClientLP6)-3
206(ClientLP6/ClientLP6)-4
207(ClientLP7/ClientLP7)-1
207(ClientLP7/ClientLP7)-2
208(ClientLP8/ClientLP8)-1
208(ClientLP8/ClientLP8)-2
Cross-connect module Cross-connect module
The internal cross-connection of the board, which needs to be configured on the NMS
The client side of the TOM board are cross-connected to the WDM side of other boards,
which needs to be configured on the NMS
Legend Information
Figure 3-35 shows legend information about U2000 operations.
Procedure
Step 1 ConfigureBoard Working ModeandPort Working Modefor the TN52TOM
board.Operation Example:
NOTE
Port Working Modemust beODU0 mode (Any->ODU0[->ODU1]).
Step 2 Configure Service Type of the TN52TOM board according to the service planning. Operation
Example:
NOTICE
l Modifying the service type leads to a service interruption.
l When configuring a GE service, make sure that the service encapsulation types specified
for the transmitter and receiver are the same.
NOTE
l If you set Service Type to Any, you must set the service rate in Client Service Bearer Rate
(Mbit/s).
l The board can receive the FE/FDDI/DVB-ASI/SDI/ESCON/GE/FC100/FICON services at the
same time, but the total rate of these services must be less than or equal to 2.5 Gbit/s.
l If a channel of the ClientLP1 port and a channel of the ClientLP2 port are identified by the same
number, these two channels cannot be used at the same time. For example, if the 201(ClientLP1/
ClientLP1)-1 service type is configured, the 202(ClientLP2/ClientLP2)-1 service type cannot be
configured.
l Only one GE service can be input through each group of ClientLP ports.
l The total rate of services that are input at each group of ClientLP ports, such as 201(ClientLP1/
ClientLP1)-1 to 201(ClientLP1/ClientLP)-8, cannot be greater than 1.25 Gbit/s.
Step 3 Configure the cross-connections from the RX/TX ports to the ClientLP ports on the
TN52TOM board for the Any services that are input to the board.Operation Example:
NOTE
The service type must be the same as Service Type in the WDM Interface window of the TN52TOM board.
In this configuration, you can set Level to GE or ANY. If you set Level to ANY, you can set Service Type to
a specific service, such as FE.
Repeat Step 3 to configure the remaining services.
Step 4 Configure electrical cross-connections for the ODU1 services between the TN52TOM and
TN52NS2 boards.Operation Example:
NOTE
This configuration is only supported by the OptiX OSN 6800 and 3800.
This step uses the compatible mode board as an example.
When ODU1 cross-connections are created, ODU0 cross-connections from the ClientLP port to
ODU0LP on the TN52TOM board are automatically created.
Step 5 Configure electrical cross-connections for the two ODU0 services between the TN52TOM
and TN52NS2 boards.Operation Example:
1
3
NOTE
Repeat to configure a cross-connection for the remaining ODU0 services between the TN52TOM and
TN52NS2 boards.
This configuration is only supported by the OptiX OSN 8800.
This step uses the compatible mode board as an example.
----End
Application Diagram
Figure 3-36 shows two conditions where the TN52TOM board works in non-cascading
ODU0 tributary-line mode. Perform configurations according to the network plan.
l Dual-fed selectively receiving on the WDM side: The TN52TOM board receives a
maximum of four channels of services on the client side and the other two client-side
ports work as WDM-side ports, selectively receiving services.
l Single transmitting and single receiving on the WDM side: The TN52TOM board
receives a maximum of six channels of services on the client side and the other client-
side port works as a WDM-side port.
Figure 3-36 Position of the TN52TOM board in a WDM system (scenario 6: Any->ODU0-
>ODU1->OTU1)
Dual-fed selectively receiving on the WDM side:
2xOTU1 2xOTU1
2×ODU1
4×ODU0
FC100, FICON,
4×ODU0
2×ODU1
2×OTU1
2×OTU1
4×Any
4×Any
DVB-ASI, SDI, TX7 RX7 DVB-ASI, SDI,
ESCON, FDDI ESCON, FDDI
RX4 RX7 TX7 RX4
MUX/ MUX/
TX8 DMUX RX8
DMUX
TX4 TX4
RX8 TX8
Any Any
RX1 TX1
TOM TOM
TX7 RX7
TX1 RX1
FE, GE, RX7 TX7
FE, GE,
FC100, FICON,
2×ODU1
2×OTU1
4×ODU0
2×ODU1
2×OTU1
FC100, FICON,
4×ODU0
6×Any
6×Any
Any Any
Cross-Connection Diagram
Figure 3-37 shows the cross-connection diagram of the TN52TOM board.
The internal cross-connection of the board, which needs to be configured on the NMS
The straight-through of the board, which does not need to be configured on the NMS
The internal cross-connection of the board, which needs to be configured on the NMS
The straight-through of the board, which does not need to be configured on the NMS
NOTE
All RX/TX optical ports can be used as WDM-side optical ports. This section uses the type of ports
7(RX5/TX5), 8(RX6/TX6), 9(RX7/TX7) and 10(RX8/TX8) to be used as WDM-side optical ports as an
example.
Legend Information
Figure 3-38 shows legend information about U2000 operations.
Procedure
Step 1 ConfigureBoard Working ModeandPort Working Modefor the TN52TOM
board.Operation Example:
4
2
NOTE
Set Board Working Mode to Non-cascading mode and Port Working Mode to ODU0 tributary-line
mode (Any->ODU0->ODU1->OTU1).
Only the ClientLP1 and ClientLP3 support ODU0 tributary-line mode (Any->ODU0->ODU1->OTU1).
l Before setting the working modes of the ClientLP1 port to ODU0 tributary-line mode (Any->ODU0-
>ODU1->OTU1), set the working modes of the ClientLP5 port to None (not for ports).
l Before setting the working modes of the ClientLP3 port to ODU0 tributary-line mode (Any->ODU0-
>ODU1->OTU1), set the working modes of the ClientLP7 port to None (not for ports).
1
3
6
5
7
8
NOTE
Step 3 Configure Service Type of the TN52TOM board according to the service plan.Operation
Example:
NOTICE
l Modifying the service type will lead to service interruption.
l When configuring a GE service, make sure that the service encapsulation types specified
for the transmitter and receiver are the same.
NOTE
l If you set Service Type to Any, you must set the Service Rate(Mbit/s).
l The board can receive the FE/FDDI/DVB-ASI/SDI/ESCON/GE/FC100/FICON services at the
same time, but the total rate of the services must be less than or equal to 5 Gbit/s.
l If a channel of the ClientLP1 port and a channel of the ClientLP2 port are identified by the same
number, these two channels cannot be used at the same time. For example, if the 201(ClientLP1/
ClientLP1)-1 channel is configured with a service type, you cannot configure a service type for the
202(ClientLP2/ClientLP2)-1 channel. Service configurations at the ClentLP3 and ClientLP4,
ClientLP5 and ClientLP6, and ClientLP7 and ClientLP8 ports must also comply with this
restriction.
l Only one GE service can be input through each group of ClientLP ports.
l The total rate of services that are received by each group of ClientLP ports, such as
201(ClientLP1/ClientLP1)-1 to 201(ClientLP1/ClientLP1)-8, cannot be higher than 1.25 Gbit/s.
Step 4 Configure the cross-connections from the RX/TX ports to the ClientLP ports on the
TN52TOM board for the Any services that are input to the board.Operation Example:
NOTE
The service type must be the same as Service Type in the WDM Interface window of the TN52TOM board.
In this configuration, you can set Level to GE or ANY. If you set Level to ANY, you can set Service Type to
a specific service, such as FE.
Repeat Step 4 to configure the remaining services.
NOTE
The working channel port and the protection channel port are the two ports used for dual feeding. The service
on the working channel must be set as bidirectional, and the service on the protection channel must be set as
unidirectional. In this example, port 10(RX8/TX8) is the working channel port, and port 9(RX7/TX7) is the
protection channel port.
Parameters of the working channel,Operation Example:
Step 6 Configure selective receiving at the WDM side of the TN52TOM board.Operation Example:
6
2
----End
Application Diagram
Figure 3-39 and Figure 3-40 show the position of the TN52TOM board in a WDM system
where the TN52TOM board works in non-cascading ODU1 tributary mode (OTU1/Any-
>ODU1).
Figure 3-39 Position of the TN52TOM board in a WDM system (scenario 7: OTU1->ODU1)
4xODU1 1xOTU2 1xOTU2 4xODU1
RX1 RX1
TOM TOM
TX1 1 1 TX1
4×ODU1
4×ODU1
4×OTU1
4×OTU1
OTU1 4 MUX/ MUX/ OTU1
NS2 NS2 4
DMUX DMUX
RX8 RX8
TX8 4 4
TX8
ODU1 ODU1
Figure 3-40 Position of the TN52TOM board in a WDM system (scenario 7:Any->ODU1)
4xODU1 1xOTU2 1xOTU2 4xODU1
RX1 TX1
TOM TOM
FE, GE, STM-1, TX1 RX1 FE, GE, STM-1,
STM-4, STM-16, 1 1 STM-4, STM-16,
OC-3, OC-12, OC- OC-3, OC-12, OC-
4×ODU1
4×ODU1
8×Any
8×Any
48, FC100, FC200, MUX/ MUX/ 48, FC100, FC200,
NS2 NS2
FICON, FICON DMUX DMUX FICON, FICON
Express, HD-SDI, RX8 TX8 Express, HD-SDI,
DVB-ASI, SDI, 4 4 DVB-ASI, SDI,
ESCON, FDDI TX8 RX8 ESCON, FDDI
Cross-Connection Diagram
Figure 3-41 shows the cross-connection diagram of the TN52TOM board.
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:1
Line/PID
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:2 board in
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:3 standard
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:4 mode
51(ODU1LP1/ODU1LP1)-1 Line/PID
51(ODU1LP1/ODU1LP1)-2 board in
51(ODU1LP1/ODU1LP1)-3 compatible
mode
Cross-connect 51(ODU1LP1/ODU1LP1)-4
module
Client side
3(TX1/RX1)-1 201(ClientLP1/ClientLP1)-1
4(TX2/RX2)-1 201(ClientLP1/ClientLP1)-2
5(TX3/RX3)-1 201(ClientLP1/ClientLP1)-3
201(ClientLP1/ClientLP1)-4
6(TX4/RX4)-1
7(TX5/RX5)-1 1 203(ClientLP3/ClientLP3)-1 2
203(ClientLP3/ClientLP3)-2
8(TX6/RX6)-1
9(TX7/RX7)-1 205(ClientLP5/ClientLP5)-1
205(ClientLP5/ClientLP5)-2 TOM
10(TX8/RX8)-1 205(ClientLP5/ClientLP5)-3
205(ClientLP5/ClientLP5)-4
207(ClientLP7/ClientLP7)-1
207(ClientLP7/ClientLP7)-2
The internal cross-connection of the board, which needs to be configured on the NMS
The client side of the TOM board are cross-connected to the WDM side of other boards,
which needs to be configured on the NMS
Legend Information
Figure 3-42 shows legend information about U2000 operations.
Procedure
Step 1 ConfigureBoard Working ModeandPort Working Modefor the TN52TOM
board.Operation Example:
Set Board Working Mode to Non-cascading mode and Port Working Mode to ODU1
mode (OTU1/Any->ODU1).
Step 2 Optional: Configure the service mode for the ports on the TN52TOM board.Operation
Example:
NOTE
l If the service type is OTU-1, set Service Mode to OTN Mode for the port.
l If the service type is another service, retain the default value Client Modefor the port.
Step 3 Set the service type of the TN52TOM board according to the service plan. Operation
Example:
NOTICE
l Modifying the service type will lead to service interruption.
l When configuring a GE service, make sure that the service encapsulation types specified
for the transmitter and receiver are the same.
NOTE
l If you set Service Type to Any, you must set the Service Rate(Mbit/s).you also must set the
service rate in Client Service Bearer Rate (Mbit/s).
l The board can receive the FC100/FICON/GE/STM-4/OC-12/DVB-ASI/ESCON/FDDI/FE/SDI/
STM-1/OC-3/FC200/FICON Express/HD-SDI/STM-16/OC-48/OTU1 services at the same time,
but the total rate of the services must be less than or equal to 10 Gbit/s.
l A ClientLP port can access only one service that has a rate higher than 1.25 Gbit/s, and this
service can be configured on only the first channel of the ClientLP port.
Step 4 Configure the cross-connections from the RX/TX ports to the ClientLP ports on the
TN52TOM board for the Any services that are input to the board.Operation Example:
NOTE
The service type must be the same as Service Type in the WDM Interface window of the TN52TOM board.
In this configuration, you can set Level to GE or ANY. If you set Level to ANY, you can set Service Type to
a specific service, such as FE.
Repeat Step 4 to configure the remaining services.
Step 5 Configure electrical cross-connections for the ODU1 services between the TN52TOM and
TN52NS2 boards.Operation Example:
The inter-board ODU1 cross-connections between the TN52TOM and TN52NS2 boards must
be configured as shown below.
205(ClientLP5/ClientLP5) 51(ODU1LP/ODU1LP)-2
203(ClientLP3/ClientLP3) 51(ODU1LP/ODU1LP)-3
207(ClientLP7/ClientLP7) 51(ODU1LP/ODU1LP)-4
NOTE
----End
Application Diagram
Figure 3-43 shows the position of the TN52TOM board in a WDM system where the
TN52TOM board works in non-cascading ODU1 tributary mode (OTU1->ODU1->Any-
>ODU0->ODU1).
Figure 3-43 Position of the TN52TOM board in a WDM system (scenario 8: OTU1->ODU1-
>Any->ODU0->ODU1)
4xODU1 1xOTU2 1xOTU2 4xODU1
RX1 RX1
TOM TOM
TX1 1 1 M M 1 1 TX1
U U
X X
8×ODU0
8×Any
4×ODU1
4×ODU1
4×ODU1
4×ODU1
4×OTU1
8×ODU0
4×OTU1
64×Any
N N
64×Any
8×Any
8×Any
8×Any
32×Any
/ /
32×Any
OTU1 4 4 OTU1
S D S
D
2 M 2
RX8 M RX8
U U
4 4 4 4
TX8 X X TX8
Cross-Connection Diagram
Figure 3-44 shows the cross-connection diagram of the TN52TOM board.
1(IN1/OUT1)-OCh:1-ODU2:1-ODU1:1 Line/PID
1(IN1/OUT1)-OCh:1-ODU2:1-ODU1:2 board in
1(IN1/OUT1)-OCh:1-ODU2:1-ODU1:3 standard
1(IN1/OUT1)-OCh:1-ODU2:1-ODU1:4 mode
51(ODU1LP1/ODU1LP1)-1 Line/PID
51(ODU1LP1/ODU1LP1)-2 board in
51(ODU1LP1/ODU1LP1)-3 compatible
Cross-connect
51(ODU1LP1/ODU1LP1)-4 mode
module
Client side
234(AnyLP2/AnyLP2)-1 241(AnyLP9/AnyLP9)-1
203(ClientLP7
7(TX5/RX5)-1 /ClientLP7)-1
234(AnyLP2/AnyLP2)-8 241(AnyLP9/AnyLP9)-8
242(AnyLP10/AnyLP10)-1 163(ODU0LP3
8(TX6/RX6)-1 /ODU0LP3)-1
236(AnyLP4/AnyLP4)-1 242(AnyLP10/AnyLP10)-8
9(TX7/RX7)-1
The internal cross-connection of the board, which needs to be configured on the NMS
The straight-through of the board, which does not need to be configured on the NMS
The client side of the TOM board are cross-connected to the WDM side of other boards,
which needs to be configured on the NMS
Legend Information
Figure 3-45 shows legend information about U2000 operations.
Procedure
Step 1 ConfigureBoard Working ModeandPort Working Modefor the TN52TOM
board.Operation Example:
2 4
NOTE
Set Board Working Mode to Non-cascading mode and Port Working Mode to
ODU1_ANY_ODU0_ODU1 re-encapsulation mode (OTU1->ODU1->Any->ODU0->ODU1).
Step 2 Set the service mode for the ports on the TN52TOM board to OTN Mode.Operation
Example:
When the service type is OTU-1, Service Mode must be set to OTN Mode for ports.
Step 3 Set the service type of the TN52TOM board toOTU-1.Operation Example:
NOTE
l The board can receive a maximum of four OTU1 services at the same time.
l When configuring internal cross-connections for Any services on the TN52TOM board, set the
service type to the same as the type of services that are encapsulated into the OTU1 services
received on the client side of the TN52TOM board. For example, if FE services are encapsulated
into OTU1 services on the upstream board of the TN52TOM board, set the service type to FE
when configuring the internal cross-connections for Any services on the TN52TOM board.
l The source and sink of an Any cross-connection must have the same channel service type. For
example, to configure a cross-connection from the AnyLP1-1 port to the AnyLP5-1 port, set the
channel service types for the two ports to the same value.
l The sum of the service rates of all channels on the AnyLP5 port must not be larger than 1.25G,
which is also the case for the AnyLP6- AnyLP12 ports.
Step 4 Configure the cross-connections from the RX/TX ports to the ClientLP ports on the
TN52TOM board for the Any services that are input to the board.Operation Example:
Configure any intra-board OTU1 cross-connection between the client-side and ClientLP ports.
Ensure that the ports are identical to those configured in steps Step 2 and Step 3.
Repeat Step 4 to configure the remaining OTU1 services.
Step 5 Configure internal cross-connections for Any services on the TN52TOM board.Operation
Example:
NOTE
The AnyLP1 port can only be cross-connected to the AnyLP5 or AnyLP6 port. The AnyLP2 port can
only be cross-connected to the AnyLP7 or AnyLP8 port, and so on.
Repeat Step 5to configure the remaining Any services.
Step 6 Configure ODU1 cross-connections between the TN52TOM and TN52NS2 boardsOperation
Example:
NOTE
----End
Application Diagram
Figure 3-46 shows the position of the TN52TOM board in a WDM system where the
TN52TOM board works in non-cascading ODU1 tributary-line mode (OTU1->ODU1->Any-
>ODU0->ODU1->OTU1).
Figure 3-46 Position of the TN52TOM board in a WDM system (scenario 9: OTU1->ODU1-
>Any->ODU0->ODU1->OTU1)
2xOTU1 2xOTU1
TX3 RX3
RX1 TOM RX3 TX3 TOM RX1
MUX/ MUX/
TX1 TX4 DMUX DMUX RX4 TX1
RX4 TX4
32×Any
32×Any
2×ODU1
4×ODU0
4×ODU0
2×ODU1
2×OTU1
2×OTU1
2×ODU1
2×ODU1
2×OTU1
2×OTU1
16×Any
16×Any
OTU1 TX5 OTU1
RX5
RX2 RX5 TX5 RX2
MUX/ MUX/
TX2 TX6 DMUX DMUX RX6
TX2
RX6 TX6
Cross-Connection Diagram
Figure 3-47 shows the cross-connection diagram of the TN52TOM board.
234(AnyLP2/AnyLP2)-8 239(AnyLP7/AnyLP7)-8
240(AnyLP8/AnyLP8)-1
240(AnyLP8/AnyLP8)-8
The internal cross-connection of the board, which needs to be configured on the NMS
The straight-through of the board, which does not need to be configured on the NMS
NOTE
All RX/TX optical ports can be used as WDM-side optical ports. This section uses the type of ports
7(RX5/TX5), 8(RX6/TX6), 9(RX7/TX7) and 10(RX8/TX8) to be used as WDM-side optical ports as an
example.
Legend Information
Figure 3-48 shows legend information about U2000 operations.
Procedure
Step 1 ConfigureBoard Working ModeandPort Working Modefor the TN52TOM
board.Operation Example:
1
3
5
4
NOTE
l Set Board Working Mode to Non-cascading mode and Port Working Mode to
ODU1_ANY_ODU0_ODU1 re-encapsulation tributary-line mode (OTU1->ODU1->Any->ODU0-
>ODU1->OTU1).
l The ClientLP5 and ClientLP7 ports do not support the non-cascading ODU1_ANY_ODU0_ODU1 re-
encapsulation tributary-line mode (OTU1->ODU1->Any->ODU0->ODU1->OTU1) mode.
l Before the working modes of the ClientLP1 and ClientLP3 ports are set to ODU1_ANY_ODU0_ODU1
re-encapsulation tributary-line mode (OTU1->ODU1->Any->ODU0->ODU1->OTU1), the working
modes of the ClientLP5 and ClientLP7 ports must be set to None (not for ports).
1
3
6
5
7
8
NOTE
Step 3 Set the service mode for the ports on the TN52TOM board to OTN Mode.Operation
Example:
When the service type is OTU-1, Service Mode must be set to OTN Mode for ports.
Step 4 Configure the service mode for the ports on the TN52TOM board toOTU-1.Operation
Example:
Step 5 Configure the cross-connections from the RX/TX ports to the ClientLP ports on the
TN52TOM board for the OTU1 services that are input to the board.Operation Example:
Step 6 Configure internal cross-connections for Any services on the TN52TOM board.Operation
Example:
1
NOTE
The AnyLP1 port can only be cross-connected to the AnyLP5 or AnyLP6 port. The AnyLP2 port can
only be cross-connected to the AnyLP7 or AnyLP8 port, and so on.
Repeat Step 6to configure the remaining Any services.
NOTE
The working channel port and the protection channel port are the two ports for dual feeding. The service on
the working channel must be set as bidirectional, and the service on the protection channel must be set as
unidirectional. In this example, port 7(RX5/TX5) and 10(RX8/TX8) are the working channel port, and port
8(RX6/TX6) and 9(RX7/TX7) are the protection channel port.
Step 8 Configure the realization of the dual-fed and selectively receiving on the WDM side of the
TN11TOM board.Operation Example:
6
2
6
2
NOTE
For the application of "the dual-fed and selectively receiving on the WDM side", the steps above.
----End
Application Diagram
Figure 3-49 and Figure 3-50 show the position of the TN52TOM board in a WDM system
where the TN52TOM board works in non-cascading ODU1 tributary-line mode (OTU1/Any-
>ODU1->OTU1). Perform configurations according to the network design.
l Figure 3-49 shows a scenario where OTU1 signals are electrically regenerated.
l Figure 3-50 shows a scenario where the TN52TOM board works in tributary-line mode
and receives Any signals.
– Dual-fed selectively receiving on the WDM side: The TN52TOM board receives a
maximum of four channels of services on the client side and the other four client-
side ports work as WDM-side ports, two of which selectively receive services.
– Single transmitting and single receiving on the WDM side: The TN52TOM board
receives a maximum of six channels of services on the client side. The other two
client-side ports work as WDM-side ports.
Figure 3-49 Position of the TN52TOM board in a WDM system (scenario 10: OTU1-
>ODU1->OTU1)
Electrical regeneration of four OTU1 optical signals:
4xOTU1 4xOTU1
TOM
RX1 TX5
D
RX2 TX6 M
4×ODU1
4×OTU1
4×OTU1
M
U
U RX3 TX7 X
X RX4
TX8
TX1 RX5
D
M TX2
4×ODU1
4×OTU1
4×OTU1
RX6 M
U
X TX3 RX7 U
X
TX4 RX8
Figure 3-50 Position of the TN52TOM board in a WDM system (scenario 10: Any->ODU1-
>OTU1)
Dual-fed selectively receiving on the WDM side:
2xOTU1 2xOTU1
2×ODU1
2×ODU1
2×OTU1
2×OTU1
4×Any
4×Any
2 x FC200/FICON Express/ TX7 RX7 2 x FC200/FICON Express/
HD-SDI/STM-16/OC-48/ RX4 RX7 TX7 RX4 HD-SDI/STM-16/OC-48/
OTU1 MUX/ MUX/ OTU1
TX8 DMUX DMUX RX8
TX4 TX4
RX8 TX8
Any Any
4×ODU1
4×OTU1
4×ODU1
4×OTU1
4×Any
4×Any
Any Any
Cross-Connection Diagram
Figure 3-51 and Figure 3-52 show the cross-connection diagram of the TN52TOM board.
Figure 3-51 Cross-connection diagram of the TN52TOM board (scenario 10: OTU1->ODU1-
>OTU1)
The internal cross-connection of the board, which needs to be configured on the NMS
The straight-through of the board, which does not need to be configured on the NMS
Figure 3-52 Cross-connection diagram of the TN52TOM board (scenario 10: Any->ODU1-
>OTU1)
OTU1/Any->ODU1->OTU1 mode. Single transmitting and single receiving
Client side WDM side
The internal cross-connection of the board, which needs to be configured on the NMS
The straight-through of the board, which does not need to be configured on the NMS
NOTE
All RX/TX optical ports can be used as WDM-side optical ports. This section uses the type of ports
7(RX5/TX5), 8(RX6/TX6), 9(RX7/TX7) and 10(RX8/TX8) to be used as WDM-side optical ports as an
example.
Legend Information
Figure 3-53 shows legend information about U2000 operations.
Procedure
Step 1 ConfigureBoard Working ModeandPort Working Modefor the TN52TOM
board.Operation Example:
4
2
NOTE
l Set Board Working Mode to Non-cascading mode and Port Working Mode to ODU1 tributary-line
mode (OTU1/Any->ODU1->OTU1).
l For the 201(ClientLP1/ClientLP1)-207(ClientLP7/ClientLP7) ports, set Port Working Mode to ODU1
tributary-line mode (OTU1/Any->ODU1->OTU1).
1
3
6
5
7
8
NOTE
Step 3 Optional: Configure the service mode toOTN Modefor the ports on the TN52TOM
board.Operation Example:
NOTE
l For the application of "Electrical regeneration of four OTU1 optical signals", set Service Mode of
the four RX/TX ports to OTN Mode.
l For the application of "Dual-fed selectively receiving on the WDM side" and "Single transmitting
and single receiving on the WDM side", retain the default value Client Mode for the four RX/TX
ports.
Step 4 Optional: Set the service type toOTU-1of the TN52TOM board.Operation Example:
NOTE
For the application of "Electrical regeneration of four OTU1 optical signals", set Service Type of the
four RX/TX ports to OTU-1.
For the application of "Dual-fed selectively receiving on the WDM side" and "Single transmitting and
single receiving on the WDM side", the board can receive the FC200, FICON Express, HD-SDI,
STM-16, OC-48, FC100, FICON, GE, STM-4, OC-12, DVB-ASI, ESCON, FDDI, FE, SDI, STM-1,
and OC-3 services at the same time, but the total rate of the services must be less than or equal to 10
Gbit/s.
Step 5 Configure the cross-connections from the RX/TX ports to the ClientLP ports on the
TN52TOM board for the Any services that are input to the board.Operation Example:
1
NOTE
The service type must be the same as Service Type in the WDM Interface window of the TN52TOM board.
In this configuration, you can set Level to GE or ANY. If you set Level to ANY, you can set Service Type to
a specific service, such as FE.
Repeat Step 5 to configure the remaining services.
NOTE
Step 7 Optional: Configure the realization of the dual-fed and selectively receiving on the WDM
side of the TN11TOM board.Operation Example:
6
2
6
2
NOTE
For the application of "the dual-fed and selectively receiving on the WDM side", the steps above.
----End
Application Diagram
Figure 3-54 shows the position of the TN52TOM board in a WDM system where the
TN52TOM board works in non-cascading ODU1 tributary mode.
Figure 3-54 Position of the TN52TOM board in a WDM system (scenario 11: OTU1-
>ODU1->ODU0)
8xODU0 1xOTU2 1xOTU2 8xODU0
RX1 RX1
TOM TOM
TX1 1 1 M M 1 1 TX1
U U
X X
8×ODU0
8×ODU0
4×ODU1
4×ODU1
4×OTU1
4×OTU1
N N OTU1
8×Any
8×Any 4
OTU1 4 / /
S D S
D
2 M 2
RX8 M RX8
U U
8 8 8 8
X X TX8
TX8
Cross-Connection Diagram
Figure 3-55 shows the cross-connection diagram of the TN52TOM board.
Figure 3-55 Cross-connection diagram of the TN52TOM board (scenario 11: OTU1->ODU1-
>ODU0)
WDM side
1(IN1/OUT1)-OCh:1-ODU2:1-ODU1:1-ODU0:1
1(IN1/OUT1)-OCh:1-ODU2:1-ODU1:1-ODU0:2 Line/PID
board in
standard
1(IN1/OUT1)-OCh:1-ODU2:1-ODU1:4-ODU0:1 mode
1(IN1/OUT1)-OCh:1-ODU2:1-ODU1:4-ODU0:2
161(ODU0LP1/ODU0LP1)-1
161(ODU0LP1/ODU0LP1)-2 Line/PID
board in
compatible
Cross-connect 164(ODU0LP4/ODU0LP4)-1 mode
module 164(ODU0LP4/ODU0LP4)-2
Client side
The internal cross-connection of the board, which needs to be configured on the NMS
The straight-through of the board, which does not need to be configured on the NMS
The client side of the TOM board are cross-connected to the WDM side of other boards,
which needs to be configured on the NMS
Legend Information
Figure 3-56 shows legend information about U2000 operations.
Procedure
Step 1 ConfigureBoard Working ModeandPort Working Modefor the TN52TOM
board.Operation Example:
NOTE
l Set Board Working Mode to Non-cascading mode and Port Working Mode to ODU1_ODU0 mode
(OTU1->ODU1->ODU0).
Step 2 Set the service mode for the ports on the TN52TOM board to OTN Mode.Operation
Example:
Step 3 Set the service type of the TN52TOM board to OTU-1.Operation Example:
Step 4 Configure the cross-connections from the RX/TX ports to the ClientLP ports on the
TN52TOM board.Operation Example:
1
NOTE
----End
Application Diagram
Figure 3-57 shows the position of the TN52TOM board in a WDM system where the
TN52TOM board works in non-cascading ODU1 tributary mode.
Figure 3-57 Position of the TN52TOM board in a WDM system (scenario 12: OTU1-
>ODU1->Any->ODU0)
8xODU0 1xOTU2 1xOTU2 8xODU0
RX1 RX1
TOM TOM
TX1 1 1 M M 1 1 TX1
U U
X X
4×ODU1
8×ODU0
4×OTU1
32×Any
64×Any
8×ODU0
4×ODU1
4×OTU1
64×Any
32×Any
N N
8×Any
8×Any
OTU1 4 / / 4 OTU1
S D S
D
2 M 2
RX8 M RX8
U U
8 8 8 8
TX8 X X TX8
Cross-Connection Diagram
Figure 3-58 shows the port configuration of the TN52TOM board.
Figure 3-58 Cross-connection diagram of the TN52TOM board (scenario 12: OTU1->ODU1-
>Any->ODU0)
WDM side
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:1-ODU0:1
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:1-ODU0:2
Line/PID
board in
standard
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:4-ODU0:1
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:4-ODU0:2
mode
161(ODU0LP1/ODU0LP1)-1
Line/PID
161(ODU0LP1/ODU0LP1)-2
board in
compatible
Cross-connect 164(ODU0LP4/ODU0LP4)-1 mode
module 164(ODU0LP4/ODU0LP4)-2
Client side
The internal cross-connection of the board, which needs to be configured on the NMS
The straight-through of the board, which does not need to be configured on the NMS
The client side of the TOM board are cross-connected to the WDM side of other boards,
which needs to be configured on the NMS
Legend Information
Figure 3-59 shows legend information about U2000 operations.
Procedure
Step 1 ConfigureBoard Working ModeandPort Working Modefor the TN52TOM
board.Operation Example:
NOTE
l Set Board Working Mode to Non-cascading mode and Port Working Mode to ODU1_ANY_ODU0
re-encapsulation mode (OTU1->ODU1->Any->ODU0).
Step 2 Set the service mode for the ports on the TN52TOM board to OTN Mode.Operation
Example:
Step 3 Set the service type of the TN52TOM board toOTU-1.Operation Example:
NOTE
l The board can receive a maximum of four OTU1 services at the same time.
l When configuring internal cross-connections for Any services on the TN52TOM board, set the
service type to the same as the type of services that are encapsulated into the OTU1 services
received on the client side of the TN52TOM board. For example, if FE services are encapsulated
into OTU1 services on the upstream board of the TN52TOM board, set the service type to FE
when configuring the internal cross-connections for Any services on the TN52TOM board.
l The source and sink of an Any cross-connection must have the same channel service type. For
example, to configure a cross-connection from the AnyLP1-1 port to the AnyLP5-1 port, set the
channel service types for the two ports to the same value.
l The sum of the service rates of all channels on the AnyLP5 port must not be larger than 1.25G,
which is also the case for the AnyLP6- AnyLP12 ports.
Step 4 Configure the cross-connections from the RX/TX ports to the ClientLP ports on the
TN52TOM board for the Any services that are input to the board. Operation Example:
1
Configure any intra-board OTU1 cross-connection between the client-side and ClientLP ports.
Ensure that the ports are identical to those configured in steps 2 and 3.
Repeat Step 4 to configure the remaining OTU1 services.
Step 5 Configure internal cross-connections for Any services on the TN52TOM board.Operation
Example:
NOTE
The AnyLP1 port can only be cross-connected to the AnyLP5 or AnyLP6 port. The AnyLP2 port can
only be cross-connected to the AnyLP7 or AnyLP8 port, and so on.
Repeat Step 5 to configure the remaining Any services.
Step 6 Configure ODU0 cross-connections between the TN52TOM and TN52NS2 boards.Operation
Example:
NOTE
----End
The THA and TOA board can be configured with different port working modes and is
applicable to various scenarios accordingly. You need to manually configure the board by
station on the NMS for the application scenarios.
The THA and TOA boards are almost the same except for the number of optical ports. The
THA board provides 16 optical ports while the TOA board provides 8 optical ports. This
chapter uses the TOA board as an example for illustration. The descriptions and configuration
of the THA board are similar to those of the TOA board.
The THA board differs from the TOA board in the following aspects:
l The client-side ports 3(TX1/RX1) to 10(TX8/RX8) on the THA board can be configured
with cross-connections only to the LP ports 201(ClientLP1/ClientLP1)-1 to
208(ClientLP8/ClientLP8)-1; the client-side ports 11(TX9/RX9) to 18(TX16/RX16) on
the THA board can be configured with cross-connections only to the LP ports
209(ClientLP9/ClientLP9)-1 to 216(ClientLP16/ClientLP16)-1.
l The THA board cannot receive SDI, HD-SDI and HDSDIRBR services on the client
side.
l The THA board does not support ODUflex non-convergence mode (Any->ODUflex).
Therefore, all configurations related to this port working mode are applicable only to the
TOA board.
4.1 Overview of the Working Mode
Each port on the TOA board can work in different modes so that services can be processed on
different paths.
4.2 Configuration Procedures
Six port working modes are available for the TOA board on the NMS. The port for the None
(not for ports) mode does not require configurations. The other five modes require
configurations.
4.3 Scenario 1: ODU0 non-convergence mode (Any->ODU0)
This section describes the configuration process of the TOA board works in ODU0 non-
convergence mode.
The TOA board supports six port working modes listed in Table 4-1. You can set the port
working modes on the NMS.
NOTE
None (not for ports): indicates that the resources at the port in this mode are not used and are released to
other ports.
Configure the
port type
Configure the
service mode
Configure the
service type
Configure the
ODUflex tolerance for
the line board
Configure cross-
connections from the
client side to LP ports
In the flowchart, the mandatory actions are required for each port working mode and optional
actions vary according to port working modes.
The optional actions must be configured in the following scenarios:
l Configure the port type: Port Type must be set to Client Side Color Optical Port when
colored optical signals are received on the client side.
l Configure the timeslot configuration mode: ODU Timeslot Configuration Mode must
be set for the line board that is interconnected with the TOA board.
– When the port working mode of the TOA board is ODUflex, ODU Timeslot
Configuration Mode must be set to Assign random for the line board that is
interconnected with the TOA board.
– In other port working modes, set ODU Timeslot Configuration Mode for the line
board to the same as the value that is set on the interconnected line board. The
recommended value is Assign random.
l Configure the service mode: When Service Type is set to OTU1, Service Mode must be
set to OTN Mode first.
l Configure the ODUflex tolerance(ppm): For the line board which is interconnected with
the TOA board, configure this parameter when the port of the TOA board works in
ODUflex mode. This parameter is reserved and optional in configuring service types
which are currently supported.
l Configure cross-connections from the client side to ClientLP ports:
– Compatible Mode: This action is required only for the ODU0 non-convergence
mode and ODU1 convergence mode.
– Standard Mode: This action is required only for the ODU1 convergence mode.
The following describes the configuration procedure and involved parameter settings for each
mode.
l Table 4-2 describes the configuration procedure for the ODU0 non-convergence mode.
l Table 4-3 describes the configuration procedure for the ODU1 non-convergence mode.
l Table 4-4 describes the configuration procedure for the ODU1 convergence mode.
l Table 4-5 describes the configuration procedure for the ODU1_ODU0 mode.
l Table 4-6 describes the configuration procedure for the ODUflex non-convergence
mode.
Service - - - - Custom,
Type PACKET,
FC400,
FC800, or
3GSDI
NOTE
For the TOA
board, only
support
FC400 and
3GSDI.
Source ID of the slot ID of the slot ID of the slot ID of the slot ID of the slot
Slot where the where the where the where the where the
TOA board is TOA board TOA board is TOA board TOA board
housed is housed housed is housed is housed
Source 1 1 1 1 or 2 1
Optical
Channe
l
Sink ID of the slot ID of the slot ID of the slot ID of the slot TN53NQ2,
Slot where the where the where the where the TN53ND2,
interconnected interconnecte interconnected interconnecte TN53NS2
board is d board is board is d board is
houseda houseda houseda houseda
Sink 1 or 2 1 to 4 1 to 4 1 or 2 OCH:1-
Optical ODU2:1-
Channe ODUflex:1
l to OCH:1-
ODU2:1-
ODUflex:2
Occupi - - - - It cannot be
ed set manually.
ODUT l The value
Uk is 4 when
Timesl the
ots service
type is
FC400.
l The value
is 3 when
the
service
type is
3GSDI.
Service - - - - The
Rate(bi parameter
t/s) value is
automatically
displayed
according to
the value of
Occupied
ODUTUk
Timeslots.
l There is no mapping between source optical ports and sink optical ports. For example, if
you set the source optical port to 201(ClientLP1/ClientLP1), you can set the sink optical
port to 161(ODU0LP1/ODU0LP1) or any other ODU0LP port on the board in the sink
slot.
l a: The interconnected board can be
– Standard mode:
TN53ND2 / TN53NQ2 / TN53NS2 / TN55NPO2 / TN55NPO2E / TN54ENQ2
– Compatible mode:
TN52ND2 / TN52NQ2 / TN54NQ2 / TN52NS2 / TN52NS3 / TN54NS3 /
TN54NPO2 / TN54ENQ2
Legend Information
Figure 4-2 shows legend information about U2000 operations.
Application Diagram
Figure 4-3 lists the condition where the TOA board works in ODU0 non-convergence mode.
Figure 4-3 Position of the TOA in a WDM system (Scenario 1: ODU0 non-convergence
mode (Any->ODU0))
8xODU0 1xOTU2 1xOTU2 8xODU0
1 1 M M 1 1
RX1 RX1
U U
FE/FDDI/GE/STM-1/ X X FE/FDDI/GE/STM-1/
8×ODU0
8×ODU0
8×ODU0
8×ODU0
N N
8×Any
8×Any
STM-4/OC-3/OC-12/ / / STM-4/OC-3/OC-12/
S D S
FC100/FICON/DVB- D FC100/FICON/DVB-
2 M 2
ASI/ESCON/SDI TX8 M TX8 ASI/ESCON/SDI
U U
8 8 8 8
RX8 X X RX8
Cross-Connection Diagram
Figure 4-4 and Figure 4-5 shows the port configuration of the TOA board.
Figure 4-4 Cross-connection diagram of the TOA board (Scenario 1: ODU0 non-convergence
mode (Any->ODU0))(compatible mode)
WDM side
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:1-ODU0:1
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:1-ODU0:2
Line/PID board in
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:4-ODU0:1 standard mode
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:4-ODU0:2
161(ODU0LP1/ODU0LP1)-1
161(ODU0LP1/ODU0LP1)-2
Line/PID board in
compatible mode
164(ODU0LP4/ODU0LP4)-1
164(ODU0LP4/ODU0LP4)-2
Cross-connect module
Client side
3(TX1/RX1)-1 201(ClientLP1/ClientLP1)-1
1
4(TX2/RX2)-1 201(ClientLP1/ClientLP1)-2
2
5(TX3/RX3)-1 202(ClientLP2/ClientLP2)-1
6(TX4/RX4)-1 202(ClientLP2/ClientLP2)-2
7(TX5/RX5)-1
TOA
8(TX6/RX6)-1
9(TX7/RX7)-1 208(ClientLP8/ClientLP8)-1
10(TX8/RX8)-1 208(ClientLP8/ClientLP8)-2
The internal cross-connection of the board, which needs to be configured on the NMS
The client side of the TOA board are cross-connected to the WDM side of other boards,
which needs to be configured on the NMS
(standard
mode)
(compatible
mode)
Figure 4-5 Cross-connection diagram of the TOA board (Scenario 1: ODU0 non-convergence
mode (Any->ODU0)) (standard mode)
WDM side
1(IN1/OUT1)-OCh:1-ODU2:1-ODU1:1-ODU0:1
1(IN1/OUT1)-OCh:1-ODU2:1-ODU1:1-ODU0:2
Line/PID
board in
1(IN1/OUT1)-OCh:1-ODU2:1-ODU1:4-ODU0:1 standard
1(IN1/OUT1)-OCh:1-ODU2:1-ODU1:4-ODU0:2 mode
161(ODU0LP1/ODU0LP1)-1
161(ODU0LP1/ODU0LP1)-2 Line/PID
board in
compatible
164(ODU0LP4/ODU0LP4)-1 mode
164(ODU0LP4/ODU0LP4)-2
Cross-connect module
Client side
3(TX1/RX1)-1
1
4(TX2/RX2)-1
5(TX3/RX3)-1
6(TX4/RX4)-1
7(TX5/RX5)-1 TOA
8(TX6/RX6)-1
9(TX7/RX7)-1
10(TX8/RX8)-1
Cross-connect module
The client side of the TOA board are cross-connected to the WDM side of other boards,
which needs to be configured on the NMS
(standard
mode)
(compatible
mode)
Procedure
Step 1 Configure the working mode for the TOA board.Set Port Working Mode to ODU0 non-
convergence mode (Any->ODU0)
Operation Example:
4 3
Step 2 Optional: According to the network plan, set the port type in Path View.
Operation Example:
Step 3 Configure Service Type of the TOA board according to the service planning.
Operation Example:
NOTICE
Modifying the service type will lead to service interruption.
NOTE
l Two channels (channel 1 and channel 2) are available at each ClientLP port. Set the service type for
only one of the two channels. When the TOA board is interconnected with a TN52TOM board, the
channel where you set the service type must be the same as the channel where the service type is set
on the TN52TOM board. When the TOA board is interconnected with another board, set the service
type for channel 1.
Step 4 Configure cross-connections from the client side to ClientLP ports on the TOA board. This
step is mandatory only when the TOA board is in compatible mode. While in standard mode,
implement Step 5.
Operation Example:
NOTE
l The service type must be the same as Service Type in the WDM Interface window of the TOA board.
l In this configuration, you can set Level to GE or ANY. If you set Level to ANY, you can set Service
Type to specific service, such as FE.
NOTE
The preceding configuration is for port 3 (RX1/TX1). For other ports, if Port Working Mode is set to
ODU0 non-convergence mode (Any->ODU0), note the following difference in cross-connection
configuration:
l Retain the same values for the other parameters except Source Optical Port and Sink Optical Port.
l For each of the remaining seven services, set Source Optical Port to a value in the range of 4(RX2/
TX2) to 10(RX8/TX8) and Sink Optical Port to a value in the range of 202(ClientLP2/ClientLP2)
to 208(ClientLP8/ClientLP8). The sink optical port number must match the source optical port
number. That is, if the source optical port is RXi/TXi, the sink optical port must be ClientLPi.
l Set Sink Optical Channel to 1 or 2. Set it to the channel for which you configure the service type in
Step 3.
Step 5 Configure ODU0-level cross-connections from ClientLP port on the TOA board to other
boards.
Operation Example:
l When the TOA board is in compatible mode, set the cross-connection parameters as
follows.
l When the TOA board is in standard mode, set the cross-connection parameters as
follows.
NOTE
The preceding configuration is for port 3 (RX1/TX1). For other ports, if Port Working Mode is set to ODU0
non-convergence mode (Any->ODU0), note the following difference in cross-connection configuration:
l Retain the same values for the other parameters except Source Optical Port.
l When the TOA board is in compatible mode, set Source Optical Port to a value in the range of
202(ClientLP2/ClientLP2) to 208(ClientLP8/ClientLP8). When the board is in standard mode, set
Source Optical Port to a value in the range of 4(RX2/TX2) through 10(RX8/TX8).The sink optical
port channel does not need to match the source optical port number.
----End
Legend Information
Figure 4-6 shows legend information about U2000 operations.
Application Diagram
Figure 4-7 lists the condition where the TOA board works in ODU1 non-convergence mode.
Figure 4-7 Position of the TOA in a WDM system (Scenario 2: ODU1 non-convergence
mode (Any->ODU1))
8xODU1 2xOTU2 2xOTU2 8xODU1
1 1 M M 1 1
RX1 U U RX1
X X
8×ODU1
8×ODU1
8×ODU0
8×ODU0
N N
8×Any
8×Any
HD-SDI/STM–16/ / / HD-SDI/STM–16/
OC-48/FC200/FICON D D D OC-48/FC200/FICON
D
Express/OTU1 2 M 2 Express/OTU1
TX8 M TX8
U U
8 8 8 8
RX8 X X RX8
Cross-Connection Diagram
Figure 4-8 and Figure 4-9 shows the port configuration of the TOA board.
Figure 4-8 Cross-connection diagram of the TOA board (Scenario 2: ODU1 non-convergence
mode (Any->ODU1))(compatible mode)
WDM side
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:1
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:2 Line/PID board in
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:3 standard mode
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:4
51(ODU1LP1/ODU1LP1)-1
51(ODU1LP1/ODU1LP1)-2 Line/PID board in
51(ODU1LP1/ODU1LP1)-3 compatible mode
51(ODU1LP1/ODU1LP1)-4
Cross-connect module
Client side
3(TX1/RX1)-1 201(ClientLP1/ClientLP1)-1
4(TX2/RX2)-1 202(ClientLP2/ClientLP2)-1 1
5(TX3/RX3)-1 203(ClientLP3/ClientLP3)-1
6(TX4/RX4)-1 204(ClientLP4/ClientLP4)-1
7(TX5/RX5)-1 205(ClientLP5/ClientLP5)-1 TOA
8(TX6/RX6)-1 206(ClientLP6/ClientLP6)-1
9(TX7/RX7)-1 207(ClientLP7/ClientLP7)-1
10(TX8/RX8)-1 208(ClientLP8/ClientLP8)-1
The straight-through of the board, which does not need to be configured on the NMS
The client side of the TOA board are cross-connected to the WDM side of other boards,
which needs to be configured on the NMS
(standard
mode)
(compatible
mode)
Figure 4-9 Cross-connection diagram of the TOA board (Scenario 2: ODU1 non-convergence
mode (Any->ODU1)) (standard mode)
WDM side
1(IN1/OUT1)-OCh:1-ODU2:1-ODU1:1 Line/PID
1(IN1/OUT1)-OCh:1-ODU2:1-ODU1:2 board in
1(IN1/OUT1)-OCh:1-ODU2:1-ODU1:3 standard
1(IN1/OUT1)-OCh:1-ODU2:1-ODU1:4 mode
51(ODU1LP1/ODU1LP1)-1 Line/PID
51(ODU1LP1/ODU1LP1)-2 board in
51(ODU1LP1/ODU1LP1)-3 compatible
51(ODU1LP1/ODU1LP1)-4 mode
Cross-connect module
Client side
3(TX1/RX1)-1
1
4(TX2/RX2)-1
5(TX3/RX3)-1
6(TX4/RX4)-1
TOA
7(TX5/RX5)-1
8(TX6/RX6)-1
9(TX7/RX7)-1
10(TX8/RX8)-1
Cross-connect module
The client side of the TOA board are cross-connected to the WDM side of other boards,
which needs to be configured on the NMS
(standard
mode)
(compatible
mode)
Procedure
Step 1 Configure the working mode for the TOA board.Set Port Working Mode to ODU1 non-
convergence mode (OTU1/Any->ODU1)
Operation Example:
4 3
.
Step 2 Optional: According to the network plan, set the port type in Path View.
Operation Example:
Step 3 Set Service Mode of the TOA board to OTN Mode. This configuration is for the TOA board
in compatible mode, not in standard mode.
Operation Example:
注
NOTE
2
: The default value of Service Mode is Client Mode. When you set Service Type to OTU-1, set
Service Mode to OTN Mode
Step 4 Configure Service Type of the TOA board according to the service planning.
Operation Example:
NOTICE
Modifying the service type will lead to service interruption.
4
1
l When the TOA board is in standard mode, set the cross-connection parameters as
follows.
4
1
NOTE
The preceding configuration is for port 3 (RX1/TX1). For other ports, if Port Working Mode is set to ODU1
non-convergence mode (OTU1/Any->ODU1), note the following difference in cross-connection
configuration:
l Retain the same values for the other parameters except Source Optical Port.
l When the TOA board is in compatible mode, set Source Optical Port to a value in the range of
202(ClientLP2/ClientLP2) to 208(ClientLP8/ClientLP8).When the TOA board is in standard mode, set
Source Optical Port to a value in the range of 4(RX2/TX2) to 10(RX8/TX8). The sink optical port
channel does not need to match the source optical port number.
----End
Legend Information
Figure 4-10 shows legend information about U2000 operations.
Application Diagram
Figure 4-11 lists the condition where the TOA board works in ODU1 convergence mode.
Figure 4-11 Position of the TOA in a WDM system (Scenario 3: ODU1 convergence mode
(n*Any->ODU1))
(1~8)xODU1 2xOTU2 2xOTU2 (1~8)xODU1
(1~8)×ODU1
DVB-ASI/SDI/ESCON/ X X DVB-ASI/SDI/ESCON/
8×ODU0
8×ODU0
N N
8×Any
8×Any
STM-4/OC- / / STM-4/OC-
D D D
12/GE/FC100/ D 12/GE/FC100/
2 M 2
FICON/FC200/ TX8 M TX8 FICON/FC200/
FICON Express/SDI/ U U FICON Express/SDI/
HD-SDI/HD-SDIRBR RX8 X X RX8 HD-SDI/HD-SDIRBR
Cross-Connection Diagram
Figure 4-12 shows the port configuration of the TOA board.
Figure 4-12 Cross-connection diagram of the TOA board (Scenario 3: ODU1 convergence
mode (n*Any->ODU1))(compatible mode)
WDM side
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:1 Line/PID
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:2 board in
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:3 standard
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:4 mode
51(ODU1LP1/ODU1LP1)-1 Line/PID
51(ODU1LP1/ODU1LP1)-2 board in
51(ODU1LP1/ODU1LP1)-3 compatibl
51(ODU1LP1/ODU1LP1)-4 e mode
Cross-connect module
Client side
2
5(TX3/RX3)-1 1 201(ClientLP1/ClientLP1)-7
201(ClientLP1/ClientLP1)-8
6(TX4/RX4)-1 202(ClientLP2/ClientLP2)-1 202(ClientLP2/ClientLP2)-1
7(TX5/RX5)-1
202(ClientLP2/ClientLP2)-8
TOA
8(TX6/RX6)-1
208(ClientLP8/ClientLP8)-1 208(ClientLP8/ClientLP8)-1
9(TX7/RX7)-1
10(TX8/RX8)-1
208(ClientLP8/ClientLP8)-7
208(ClientLP8/ClientLP8)-8
Cross-connect module Multiplexing module Cross-connect module
The virtual path of the board, which does not need to be configured on the NMS
The internal cross-connection of the board, which needs to be configured on the NMS
The client side of the TOA board are cross-connected to the WDM side of other boards, which
needs to be configured on the NMS
(standard
mode)
Figure 4-13 Cross-connection diagram of the TOA board (Scenario 3: ODU1 convergence
mode (n*Any->ODU1)) (standard mode)
WDM side
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:1
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:2 Line/PID board in
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:3 standard mode
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:4
51(ODU1LP1/ODU1LP1)-1
51(ODU1LP1/ODU1LP1)-2 Line/PID board in
51(ODU1LP1/ODU1LP1)-3 compatible mode
51(ODU1LP1/ODU1LP1)-4
Cross-connect module
Client side
201(ConvGroup1/Conv 2
5(TX3/RX3)-1 1
Group1)-8
202(ConvGroup2/Conv 202(ConvGroup2/Conv
6(TX4/RX4)-1
Group2)-1 Group2)-1
7(TX5/RX5)-1
202(ConvGroup2/Conv TOA
8(TX6/RX6)-1 Group2)-8
208(ConvGroup8/Conv
9(TX7/RX7)-1 208(ConvGroup8/Conv Group8)-1
Group8)-1
10(TX8/RX8)-1
208(ConvGroup8/Conv
Group8)-8
Cross-connect module Multiplexing module Cross-connect module
The virtual path of the board, which does not need to be configured on the NMS
The internal cross-connection of the board, which needs to be configured on the NMS
The client side of the TOA board are cross-connected to the WDM side of other boards, which
needs to be configured on the NMS
(standard
mode)
(compatible
mode)
Procedure
Step 1 Configure the working mode for the TOA board. Set Port Working Mode to ODU1
convergence mode (n*Any->ODU1).
Operation Example:
4 3
Step 2 Optional: According to the network plan, set the port type in Path View.
Operation Example:
Step 3 Configure Service Type of the TOA board according to the service planning.
Operation Example:
NOTICE
Modifying the service type will lead to service interruption.
NOTE
l Only channel 1, for example, 201(ClientLP1/ClientLP1)-1, in each group of ClientLP ports can
receive services with rates higher than 1.25 Gbit/s.
l The total rate of services received by each group of ClientLP ports, for example, 201(ClientLP1/
ClientLP1)-1 to 201(ClientLP1/ClientLP1)-8, cannot exceed 2.5 Gbit/s.
l The total rate of services received by all ClientLP ports from 201(ClientLP1/ClientLP1)-1 to
208(ClientLP1/ClientLP1)-8, cannot exceed 20 Gbit/s.
Step 4 Configure cross-connections from the client side to ClientLP or ConvGroup ports on the TOA
board.
Operation Example:
l When the TOA board is in compatible mode, set the cross-connection parameters as
follows.
1
4
NOTE
When STM-16 services are received on the client side, these services must be provisioned on the first
optical channel of each ClientLP port, and the client-side ports must map to intra-board logical ports.
For example, services from 3(RX1/TX1)-1 must be cross-connected to 201(ClientLP1/ClientLP1)-1,
services from 4(TX2/RX2)-1 must be cross-connected to 202(ClientLP2/ClientLP2)-1, and so on.
l When the TOA board is in standard mode, set the cross-connection parameters as
follows.
1
4
NOTE
The service type must be the same as Service Type in the WDM Interface window of the TOA board.
In this configuration, you can set Level to GE or ANY. If you set Level to ANY, you can set Service Type to
specific service, such as FE.
The preceding configuration is for port 3 (RX1/TX1). For other ports, if Port Working Mode
is set to ODU1 convergence mode (n*Any->ODU1), note the following difference in cross-
connection configuration:
l Retain the same values for the other parameters except Source Optical Port and Sink
Optical Port.
l When the TOA board is in compatible mode, set Source Optical Port to a value in the
range of 4(RX2/TX2) to 10(RX8/TX8) and Sink Optical Port to a value in the range of
202(ClientLP2/ClientLP2) to 208(ClientLP8/ClientLP8). When the TOA board is in
standard mode, set Source Optical Port to a value in the range of 4(RX2/TX2) to
10(RX8/TX8) and Sink Optical Port to a value in the range of 202(ConvGroup2/
ConvGroup2) to 208(ConvGroup8/ConvGroup8). The sink optical port number must
match the source optical port number. That is, if the source optical port is RXi/TXi, the
sink optical port must be ClientLPi or ConvGroupi.
Step 5 Configure ODU1-level cross-connections from ClientLP ports to the WDM side on the TOA
board.
Operation Example:
l When the TOA board is in compatible mode, set the cross-connection parameters as
follows.
4
1
l When the TOA board is in standard mode, set the cross-connection parameters as
follows.
4
1
NOTE
The preceding configuration is for port 3 (RX1/TX1). For other ports, if Port Working Mode is set to ODU1
convergence mode (n*Any->ODU1), note the following difference in cross-connection configuration:
l Retain the same values for the other parameters except Source Optical Port.
l When the TOA board is in compatible mode, set Source Optical Port to a value in the range of
202(ClientLP2/ClientLP2) to 208(ClientLP8/ClientLP8). When the TOA board is in standard mode, set
Source Optical Port to a value in the range of 202(ConvGroup2/ConvGroup2) to 208(ConvGroup8/
ConvGroup8). The sink optical port channel does not need to match the source optical port number.
----End
Legend Information
Figure 4-14 shows legend information about U2000 operations.
Application Diagram
Figure 4-15 lists the condition where the TOA board works in ODU1 convergence mode.
Figure 4-15 Position of the TOA in a WDM system (Scenario 4: ODU1_ODU0 mode
(OTU1->ODU1->ODU0))
16xODU0 2xOTU2 2xOTU2 16xODU0
TOA TOA
RX1 RX1
1 1 M M 1 1
TX1 U U TX1
X X
16×ODU0
16×ODU0
8×ODU1
8×OTU1
8×ODU1
8×OTU1
8×ODU0
8×ODU0
N N
OTU1 D
/ /
D OTU1
D D
2 M 2
RX8 M RX8
U U
TX8 16 16 X X 16 16 TX8
Cross-Connection Diagram
Figure 4-16 shows the port configuration of the TOA board.
Figure 4-16 Cross-connection diagram of the TOA board (Scenario 4: ODU1_ODU0 mode
(OTU1->ODU1->ODU0))(compatible mode)
WDM side
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:1-ODU0:1
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:1-ODU0:2
Line/PID board
in standard
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:4-ODU0:1 mode
1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:4-ODU0:2
161(ODU0LP1/ODU0LP1)-1
161(ODU0LP1/ODU0LP1)-2
Line/PID board
in compatible
164(ODU0LP4/ODU0LP4)-1 mode
164(ODU0LP4/ODU0LP4)-2
Cross-connect module
Client side
The straight-through of the board, which does not need to be configured on the NMS
The virtual path of the board, which does not need to be configured on the NMS
The client side of the TOA board are cross-connected to the WDM side of other boards,
which needs to be configured on the NMS
(standard
mode)
Figure 4-17 Cross-connection diagram of the TOA board (Scenario 4: ODU1_ODU0 mode
(OTU1->ODU1->ODU0)) (standard mode)
WDM side
1(IN1/OUT1)-OCh:1-ODU2:1-ODU1:1-ODU0:1
1(IN1/OUT1)-OCh:1-ODU2:1-ODU1:1-ODU0:2
Line/PID
board in
1(IN1/OUT1)-OCh:1-ODU2:1-ODU1:4-ODU0:1 standard
1(IN1/OUT1)-OCh:1-ODU2:1-ODU1:4-ODU0:2 mode
161(ODU0LP1/ODU0LP1)-1
161(ODU0LP1/ODU0LP1)-2 Line/PID
board in
compatible
164(ODU0LP4/ODU0LP4)-1
mode
164(ODU0LP4/ODU0LP4)-2
Cross-connect module
Client side
3(TX1/RX1)-1 3(TX1/RX1)-1
3(TX1/RX1)-2
1
4(TX2/RX2)-1 4(TX2/RX2)-1
4(TX2/RX2)-2
TOA
9(TX7/RX7)-1 9(TX7/RX7)-1
9(TX7/RX7)-2
10(TX8/RX8)-1 10(TX8/RX8)-1
10(TX8/RX8)-2
The virtual path of the board, which does not need to be configured on the NMS
The client side of the TOA board are cross-connected to the WDM side of other boards, which
needs to be configured on the NMS
(standard
mode)
(compatible
mode)
Procedure
Step 1 Configure the working mode for the TOA board. Set Port Working Mode to ODU1_ODU0
mode (OTU1->ODU1->ODU0).
Operation Example:
4 3
Step 2 Optional: According to the network plan, set the port type in Path View.
Operation Example:
Step 3 Set Service Mode of the TOA board to OTN Mode.This configuration is for the TOA board
in compatible mode, not in standard mode.
Operation Example:
注
NOTICE
Modifying the service type will lead to service interruption.
Step 5 Configure ODU0-level cross-connections from the TOA board to other boards.
Operation Example:
l When the TOA board is in compatible mode, set the cross-connection parameters as
follows.
1
4
l When the TOA board is in standard mode, set the cross-connection parameters as
follows.
1
4
NOTE
The preceding configuration is for port 3 (RX1/TX1). For other ports, if Port Working Mode is set to
ODU1_ODU0 mode (OTU1->ODU1->ODU0), note the following difference in cross-connection
configuration:
l Retain the same values for the other parameters except Source Optical Port.
l When the TOA board is in compatible mode, set Source Optical Port to a value in the range of
162(ODU0LP2/ODU0LP2) to 168(ODU0LP8/ODU0LP8). When the TOA board is in standard mode, set
Source Optical Port to a value in the range of 4(RX2/TX2) to 10(RX8/TX8). The sink optical port
channel does not need to match the source optical port number.
----End
Legend Information
Figure 4-18 shows legend information about U2000 operations.
Application Diagram
Figure 4-19 lists the condition where the TOA board works in ODUflex non-convergence
mode.
Figure 4-19 Position of the TOA in a WDM system (Scenario 5: ODUflex non-convergence
mode (Any->ODUflex))
l 3G-SDI<->ODUflex
5xODUflex 4xOTU2 4xOTU2 5xODUflex
5x3G-SDI/3G-SDIRBR
RX1 1 1 1 1 RX1
U U
X X
5xODUflex
5xODUflex
3G-SDI N / N 3G-SDI
5 /
3G-SDIRBR Q Q 5 3G-SDIRBR
D D
2 M 2
TX8 M TX8
U U
5 5 5 5
RX8 X X RX8
l FC400/FICON4G<->ODUflex
4xODUflex 4xOTU2 4xOTU2 4xODUflex
4xFC400/FICON4G
RX1
4xFC400/FICON4G
U U
X X
4xODUflex
4xODUflex
N / N
4xFC400/ 4 / 4xFC400/
Q D Q 4
FICON4G D FICON4G
2 M 2
TX8 M TX8
U U
4 4 4 4
RX8 X X RX8
Cross-Connection Diagram
Figure 4-20 and Figure 4-21 shows the port configuration of the TOA board.
Figure 4-20 Cross-connection diagram of the TOA board (Scenario 5: ODUflex non-
convergence mode (Any->ODUflex))(compatible mode)
WDM side
1(IN1/OUT1)-OCH:1-ODU2:1-ODUflex:1
1(IN1/OUT1)-OCH:1-ODU2:1-ODUflex:2
Line board
2(IN2/OUT2)-OCH:1-ODU2:1-ODUflex:1
2(IN2/OUT2)-OCH:1-ODU2:1-ODUflex:2
Client side
3(TX1/RX1)-1 201(ClientLP1/ClientLP1)-1
1 2
4(TX2/RX2)-1 202(ClientLP2/ClientLP2)-1
5(TX3/RX3)-1 203(ClientLP3/ClientLP3)-1
6(TX4/RX4)-1 204(ClientLP4/ClientLP4)-1
7(TX5/RX5)-1 205(ClientLP5/ClientLP5)-1
TOA
8(TX6/RX6)-1 206(ClientLP6/ClientLP6)-1
9(TX7/RX7)-1 207(ClientLP7/ClientLP7)-1
10(TX8/RX8)-1 208(ClientLP8/ClientLP8)-1
The straight-through of the board, which does not need to be configured on the NMS
The client side of the TOA board are cross-connected to the WDM side of other boards,
which needs to be configured on the NMS
Figure 4-21 Cross-connection diagram of the TOA board (Scenario 5: ODUflex non-
convergence mode (Any->ODUflex)) (standard mode)
WDM side
1(IN1/OUT1)-OCh:1-ODU2:1-ODUflex:1
Line board 1(IN1/OUT1)-OCh:1-ODU2:1-ODUflex:2
2(IN2/OUT2)-OCh:1-ODU2:1-ODUflex:1
2(IN2/OUT2)-OCh:1-ODU2:1-ODUflex:2
Cross-connect module
Client side
3(TX1/RX1)-1
1
4(TX2/RX2)-1
5(TX3/RX3)-1
6(TX4/RX4)-1
7(TX5/RX5)-1 TOA
8(TX6/RX6)-1
9(TX7/RX7)-1
10(TX8/RX8)-1
Cross-connect module
The client side of the TOA board are cross-connected to the WDM
side of other boards, which needs to be configured on the NMS
Procedure
Step 1 Configure the working mode for the TOA board. Set Port Working Mode to ODUflex non-
convergence mode (Any->ODUflex).
Operation Example:
4 3
Step 2 Optional: According to the network plan, set the port type in Path View.
Operation Example:
Step 3 Optional: The available values for ODU Timeslot Configuration Mode is Assign random
only.
Operation Example:
Step 4 Configure Service Type of the TOA board according to the service planning.
Operation Example:
NOTICE
Modifying the service type will lead to service interruption.
Step 5 Configure ODUflex-level cross-connections from ClientLP port on the TOA board to other
boards.
Operation Example:
l When the TOA board is in compatible mode, set the cross-connection parameters as
follows.
1
4
l When the TOA board is in standard mode, set the cross-connection parameters as
follows.
1
4
NOTE
3
: When the service type is set to 3G-SDI/3G-SDIRBR, a maximum of five cross-connections
can be configured; for service type FC400/FICON4G, a maximum of four cross-connections.
The preceding configuration is for port 3 (RX1/TX1). For other ports, if Port Working Mode is set to
ODUflex non-convergence mode (Any->ODUflex), note the following difference in cross-connection
configuration:
l Retain the same values for the other parameters except Source Optical Port.
l When the TOA board is in compatible mode, set Source Optical Port to a value in the range of
202(ClientLP2/ClientLP2) to 208(ClientLP8/ClientLP8). When the TOA board is in standard
mode, set Source Optical Port to a value in the range of 4(RX2/TX2) to 10(RX8/TX8). The value
of Sink Optical Channel is automatically generated by the system.
----End
The LOA board can be configured with different port working modes and is applicable to five
scenarios accordingly. You need to manually configure the board by station on the NMS for
the application scenarios.
The LOA board supports six port working modes listed in Table 5-1. You can set the port
working modes on the NMS.
NOTE
l [->ODU1]: indicates that "ODU1" is optional. For example, in ODU0 non-convergence mode, two
service signal flows are available: Any->ODU0->ODU2->OTU2 and Any->ODU0->ODU1-
>ODU2->OTU2.
l None (not for ports): indicates that the resources at the port in this mode are not used and are
released to other ports.
Configure the
port type
Configure the
service mode
Configure the
service type
Configure the
ODUflex tolerance for
the line board
Configure cross-
connections from the
client side to LP ports
In the flowchart, the mandatory actions are required for each port working mode and optional
actions vary according to port working modes.
l Configure the port type: Port Type must be set to Client Side Color Optical Port when
colored optical signals are received on the client side.
l Configure the timeslot configuration mode: ODU Timeslot Configuration Mode must
be set for the line side of the LOA board.
– When the signal flow is from ODU0 or ODUflex to ODU2, ODU Timeslot
Configuration Mode must be set to Assign random.
– When the signal flow is ODU0 -> ODU1 -> ODU2, ODU Timeslot Configuration
Mode must be set to Assign consecutive.
– When the signal flow is from Any or ODU1 to ODU2 directly, ODU Timeslot
Configuration Mode can be set to Assign consecutive or Assign random.
However, the value must be the same as the value that is set on the interconnected
LOA or line board.
l Configure the service mode: When Service Type is set to OTU1, Service Mode must be
set to OTN Mode first.
l Configure the ODUflex tolerance(ppm): when the port of the TOA board works in
ODUflex mode, this parameter can be configured. This parameter is reserved and
optional in configuring service types which are currently supported.
l Configure cross-connections from the client side to LP ports: This action is required only
for the ODU0 non-convergence mode and ODU1 convergence mode.
The following describes the configuration procedure and involved parameter settings for each
mode.
l Table 5-2 describes the configuration procedure for the ODU0 non-convergence mode.
l Table 5-3 describes the configuration procedure for the ODU1 non-convergence mode.
l Table 5-4 describes the configuration procedure for the ODU1_ODU0 mode.
l Table 5-5 describes the configuration procedure for the ODUflex non-convergence
mode.
l Table 5-6 describes the configuration procedure for the ODU2 non-convergence mode.
N Action Description
o.
N Action Description
o.
N Action Description
o.
N Action Description
o.
N Action Description
o.
Table 5-7 Parameters for configuring ODUk-level cross-connections from LP ports to the
WDM side
Paramete ODU0 ODU1 ODU1_OD ODUflex ODU2
r Non- Non- U0 Mode Non- Non-
Convergenc Convergenc Convergenc Convergen
e Mode e Mode e Mode ce Mode
Service - - - Custom, -
Type PACKET,
FC400,
FC800,
3GSDI, or
InfiniBand
2.5G,
NOTE
For the LOA
board, only
support
FC400,
FC800,
3GSDIRBR
and 3GSDI.
Source ID of the slot ID of the slot ID of the slot ID of the slot ID of the slot
Slot/Sink where the where the where the where the where the
Slot LOA board LOA board LOA board LOA board LOA board
is housed is housed is housed is housed is housed
Source 1 or 2 1 1 or 2 1 1
Optical
Channel
Occupied - - - It cannot be -
ODUTUk set manually.
Timeslots l The value
is 4 when
the
service
type is
FC400.
l The value
is 7 when
the
service
type is
FC800.
l The value
is 3 when
the
service
type is
3GSDI.
Service - - - The -
Rate(bit/s) parameter
value is
automatically
displayed
according to
the value of
Occupied
ODUTUk
Timeslots.
a: When the LOA board receives FC800 services, set Source Optical Port only to
201(ClientLP1/ClientLP1) and Sink Optical Channel only to OCH:1-ODU2:1-
ODUflex:1.
Legend Information
Figure 5-2 shows legend information about U2000 operations.
Application Diagram
Figure 5-3 lists the condition where the LOA board works in ODU0 non-convergence mode.
Figure 5-3 Position of the LOA in a WDM system (Scenario 1: ODU0 non-convergence
mode (Any->ODU0[->ODU1]->ODU2->OTU2))
1xOTU2 1xOTU2
LOA LOA
TX1 RX1
M M
RX1 U U TX1
FE/FDDI/GE/STM-1/ OUT X X IN FE/FDDI/GE/STM-1/
8×ODU0
4×ODU1
1×ODU2
1×OTU2
8×ODU0
1×ODU2
4×ODU1
1×OTU2
8×ODU0
8×ODU0
8×ODU0
8×ODU0
8×ODU0
8×ODU0
STM-4/OC-3/OC-12/ / / STM-4/OC-3/OC-12/
IN OUT
FC100/FICON/DVB- D D FC100/FICON/DVB-
ASI/ESCON/SDI TX8 M M RX8 ASI/ESCON/SDI
U U
RX8 X X TX8
Cross-Connection Diagram
Figure 5-4 shows the port configuration of the LOA board.
Figure 5-4 Cross-connection diagram of the LOA board (Scenario 1: ODU0 non-convergence
mode (Any->ODU0[->ODU1]->ODU2->OTU2))
The service signal flow is Any->ODU0->ODU2->OTU2:
Client side WDM side
1
3(RX1/TX1)-1 201(ClientLP1/ClientLP1)-1 IN/OUT–OCH:1–ODU2:1–ODU0:1
1 201(ClientLP1/ClientLP1)-2
4(RX2/TX2)-1 202(ClientLP2/ClientLP2)-1 IN/OUT–OCH:1–ODU2:1–ODU0:2
1 202(ClientLP2/ClientLP2)-2 2
5(RX3/TX3)-1 203(ClientLP3/ClientLP3)-1 IN/OUT–OCH:1–ODU2:1–ODU0:3
1 203(ClientLP3/ClientLP3)-2
6(RX4/TX4)-1 204(ClientLP4/ClientLP4)-1 IN/OUT–OCH:1–ODU2:1–ODU0:4
204(ClientLP4/ClientLP4)-2
1
7(RX5/TX5)-1 205(ClientLP5/ClientLP5)-1 IN/OUT–OCH:1–ODU2:1–ODU0:5
205(ClientLP5/ClientLP5)-2
1
8(RX6/TX6)-1 206(ClientLP6/ClientLP6)-1 IN/OUT–OCH:1–ODU2:1–ODU0:6
1 206(ClientLP6/ClientLP6)-2
9(RX7/TX7)-1 207(ClientLP7/ClientLP7)-1 IN/OUT–OCH:1–ODU2:1–ODU0:7
1 207(ClientLP7/ClientLP7)-2
10(RX8/TX8)-1 208(ClientLP8/ClientLP8)-1 IN/OUT–OCH:1–ODU2:1–ODU0:8
208(ClientLP8/ClientLP8)-2
1
3(RX1/TX1)-1 201(ClientLP1/ClientLP1)-1 IN/OUT–OCH:1–ODU2:1–ODU1:1–ODU0:1
1 201(ClientLP1/ClientLP1)-2
4(RX2/TX2)-1 202(ClientLP2/ClientLP2)-1 IN/OUT–OCH:1–ODU2:1–ODU1:1–ODU0:2
1 202(ClientLP2/ClientLP2)-2
5(RX3/TX3)-1 203(ClientLP3/ClientLP3)-1 2 IN/OUT–OCH:1–ODU2:1–ODU1:2–ODU0:1
1 203(ClientLP3/ClientLP3)-2
6(RX4/TX4)-1 204(ClientLP4/ClientLP4)-1 IN/OUT–OCH:1–ODU2:1–ODU1:2–ODU0:2
204(ClientLP4/ClientLP4)-2
1
7(RX5/TX5)-1 205(ClientLP5/ClientLP5)-1 IN/OUT–OCH:1–ODU2:1–ODU1:3–ODU0:1
205(ClientLP5/ClientLP5)-2
1
8(RX6/TX6)-1 206(ClientLP6/ClientLP6)-1 IN/OUT–OCH:1–ODU2:1–ODU1:3–ODU0:2
1 206(ClientLP6/ClientLP6)-2
9(RX7/TX7)-1 207(ClientLP7/ClientLP7)-1 IN/OUT–OCH:1–ODU2:1–ODU1:4–ODU0:1
1 207(ClientLP7/ClientLP7)-2
10(RX8/TX8)-1 208(ClientLP8/ClientLP8)-1 IN/OUT–OCH:1–ODU2:1–ODU1:4–ODU0:2
208(ClientLP8/ClientLP8)-2
Procedure
Step 1 Configure Port Working Mode to ODU0 non-convergence mode (Any->ODU0[->ODU1]-
>ODU2->OTU2) for the LOA board.
Operation Example:
4 3
Step 2 Optional: According to the network plan, set the port type in Path View.
Operation Example:
3 4
2
5
3
:
l If the service signal flow is Any->ODU0->ODU2->OTU2, set ODU Timeslot
Configuration Mode to Assign random for the LOA board.
l If the service signal flow is Any->ODU0->ODU1->ODU2->OTU2, set ODU Timeslot
Configuration Mode to Assign consecutive for the LOA board.
Step 4 Configure Service Type of the LOA board according to the service planning.
Operation Example:
2
1
NOTE
2
:
l Modifying the service type will lead to service interruption.
l The board can receive the FE/FDDI/GE/STM-1/STM-4/OC-3/OC-12/FC100/FICON/DVB-ASI/
ESCON/SDI services at the same time, but the total rate of the services must be less than or equal to 1.25
Gbit/s.
l Two channels (channel 1 and channel 2) are available at each LP port. Set the service type for only one of
the two channels. When the LOA board is interconnected with a TN52TOM board, the channel where
you set the service type must be the same as the channel where the service type is set on the TN52TOM
board. When the LOA board is interconnected with another board, set the service type for channel 1.
Step 5 Configure cross-connections from the client side to LP ports on the LOA board.
Operation Example:
NOTE
The service type must be the same as Service Type in the WDM Interface window of the LOA board.
In this configuration, you can set Level to GE or ANY. If you set Level to ANY, you can set Service Type to
specific service, such as FE.
NOTE
The preceding configuration is for port 3 (RX1/TX1). For other ports, if Port Working Mode is set to
ODU0 non-convergence mode (Any->ODU0[->ODU1]->ODU2->OTU2), note the following
difference in cross-connection configuration:
l Retain the same values for the other parameters except Source Optical Port and Sink Optical Port.
l Set Source Optical Port to a value in the range of 4(RX2/TX2) to 10(RX8/TX8) and Sink Optical
Port to a value in the range of 202(ClientLP2/ClientLP2) to 208(ClientLP8/ClientLP8). The sink
optical port number must match the source optical port number. That is, if the source optical port is
RXi/TXi, the sink optical port must be ClientLPi.
Step 6 Configure ODU0-level cross-connections from LP ports to the WDM side on the LOA board.
Operation Example:
l When the ODU Timeslot Configuration Mode is Assign random.
NOTE
The preceding configuration is for port 3 (RX1/TX1). For other ports, if Port Working Mode is set to
ODU0 non-convergence mode (Any->ODU0[->ODU1]->ODU2->OTU2), note the following
difference in cross-connection configuration:
l Retain the same values for the other parameters except Source Optical Port.
l Set Source Optical Port to a value in the range of 202(ClientLP2/ClientLP2) to 208(ClientLP8/
ClientLP8). The sink optical port channel does not need to match the source optical port number.
----End
Legend Information
Figure 5-5 shows legend information about U2000 operations.
Application Diagram
Figure 5-6 lists the condition where the LOA board works in ODU1 non-convergence mode.
Figure 5-6 Position of the LOA in a WDM system (Scenario 2: ODU1 non-convergence
mode (OTU1/Any->ODU1->ODU2->OTU2))
1xOTU2 1xOTU2
LOA LOA
TX1 RX1
M M
RX1 U U TX1
HD-SDI/HD-SDIRBR/ OUT X HD-SDI/HD-SDIRBR/
X IN
4×ODU1
1×ODU2
1×OTU2
1×ODU2
4×ODU1
1×OTU2
8×ODU0
8×ODU0
8×ODU0
8×ODU0
STM–16/OC-48/ / / STM–16/OC-48/
FC200/FICON 4 IN OUT 4 FC200/FICON
D D
Express/OTU1 M M Express/OTU1
TX8 RX8
U U
RX8 X X TX8
Cross-Connection Diagram
Figure 5-7 shows the port configuration of the LOA board.
Figure 5-7 Cross-connection diagram of the LOA board (Scenario 2: ODU1 non-convergence
mode (OTU1/Any->ODU1->ODU2->OTU2))
3(RX1/TX1)-1 201(ClientLP1/ClientLP1)-1
IN/OUT–OCH:1–ODU2:1–ODU1:1
4(RX2/TX2)-1 202(ClientLP2/ClientLP2)-1
1
5(RX3/TX3)-1 203(ClientLP3/ClientLP3)-1 IN/OUT–OCH:1–ODU2:1–ODU1:2
6(RX4/TX4)-1 204(ClientLP4/ClientLP4)-1
7(RX5/TX5)-1 205(ClientLP5/ClientLP5)-1
IN/OUT–OCH:1–ODU2:1–ODU1:3
8(RX6/TX6)-1 206(ClientLP6/ClientLP6)-1
9(RX7/TX7)-1 207(ClientLP7/ClientLP7)-1
IN/OUT–OCH:1–ODU2:1–ODU1:4
10(RX8/TX8)-1 208(ClientLP8/ClientLP8)-1
Procedure
Step 1 Configure Port Working Mode to ODU1 non-convergence mode (OTU1/Any->ODU1-
>ODU2->OTU2) for the LOA board.
Operation Example:
4 3
Step 2 Optional: According to the network plan, set the port type in Path View.
Operation Example:
3 4
2
5
NOTE
2
: The default value of Service Mode is Client Mode. When you set Service Type to OTU-1, set
Service Mode to OTN Mode.
Step 4 Configure Service Type of the LOA board according to the service planning.
Operation Example:
2
1
NOTICE
Step 5 Configure ODU1-level cross-connections from LP ports to the WDM side on the LOA board.
Operation Example:
1 4
NOTE
The preceding configuration is for port 3 (RX1/TX1). For other ports, if Port Working Mode is set to
ODU1 non-convergence mode (OTU1/Any->ODU1->ODU2->OTU2), note the following difference
in cross-connection configuration:
l Retain the same values for the other parameters except Source Optical Port.
l Set Source Optical Port to a value in the range of 202(ClientLP2/ClientLP2) to 208(ClientLP8/
ClientLP8). The sink optical port channel does not need to match the source optical port number.
----End
Legend Information
Figure 5-8 shows legend information about U2000 operations.
Application Diagram
Figure 5-9 lists the condition where the LOA board works in ODU1_ODU0 mode.
Figure 5-9 Position of the LOA in a WDM system (Scenario 3: ODU1_ODU0 mode (OTU1-
>ODU1->ODU0[->ODU1]->ODU2->OTU2))
1xOTU2 1xOTU2
4×ODU1
1×ODU2
1×OTU2
1×ODU2
4×ODU1
8×ODU0
4×ODU1
1×OTU2
8×ODU0
8×ODU0
8×ODU0
8×ODU0
8×ODU0
8×ODU0
8×ODU0
8×ODU0
/ /
OTU1 4 IN OUT 4 OTU1
D D
TX8 M M
RX8
U U
RX8 X X TX8
Cross-Connection Diagram
Figure 5-10 shows the port configuration of the LOA board.
Figure 5-10 Cross-connection diagram of the LOA board (Scenario 3: ODU1_ODU0 mode
(OTU1->ODU1->ODU0[->ODU1]->ODU2->OTU2))
201(ClientLP1/ClientLP1)-1 IN/OUT–OCH:1–ODU2:1–ODU0:1
3(RX1/TX1)-1
201(ClientLP1/ClientLP1)-2
4(RX2/TX2)-1 202(ClientLP2/ClientLP2)-1 IN/OUT–OCH:1–ODU2:1–ODU0:2
202(ClientLP2/ClientLP2)-2
1
203(ClientLP3/ClientLP3)-1 IN/OUT–OCH:1–ODU2:1–ODU0:3
5(RX3/TX3)-1
203(ClientLP3/ClientLP3)-2
6(RX4/TX4)-1 204(ClientLP4/ClientLP4)-1 IN/OUT–OCH:1–ODU2:1–ODU0:4
204(ClientLP4/ClientLP4)-2
7(RX5/TX5)-1 205(ClientLP5/ClientLP5)-1 IN/OUT–OCH:1–ODU2:1–ODU0:5
205(ClientLP5/ClientLP5)-2
8(RX6/TX6)-1 206(ClientLP6/ClientLP6)-1
IN/OUT–OCH:1–ODU2:1–ODU0:6
206(ClientLP6/ClientLP6)-2
9(RX7/TX7)-1 207(ClientLP7/ClientLP7)-1
IN/OUT–OCH:1–ODU2:1–ODU0:7
207(ClientLP7/ClientLP7)-2
10(RX8/TX8)-1 208(ClientLP8/ClientLP8)-1
208(ClientLP8/ClientLP8)-2 IN/OUT–OCH:1–ODU2:1–ODU0:8
201(ClientLP1/ClientLP1)-1
3(RX1/TX1)-1
201(ClientLP1/ClientLP1)-2 IN/OUT–OCH:1–ODU2:1–ODU1:1–ODU0:1
4(RX2/TX2)-1 202(ClientLP2/ClientLP2)-1
202(ClientLP2/ClientLP2)-2 IN/OUT–OCH:1–ODU2:1–ODU1:1–ODU0:2
1
203(ClientLP3/ClientLP3)-1
5(RX3/TX3)-1
203(ClientLP3/ClientLP3)-2 IN/OUT–OCH:1–ODU2:1–ODU1:2–ODU0:1
6(RX4/TX4)-1 204(ClientLP4/ClientLP4)-1
204(ClientLP4/ClientLP4)-2 IN/OUT–OCH:1–ODU2:1–ODU1:2–ODU0:2
7(RX5/TX5)-1 205(ClientLP5/ClientLP5)-1
205(ClientLP5/ClientLP5)-2 IN/OUT–OCH:1–ODU2:1–ODU1:3–ODU0:1
8(RX6/TX6)-1 206(ClientLP6/ClientLP6)-1
206(ClientLP6/ClientLP6)-2 IN/OUT–OCH:1–ODU2:1–ODU1:3–ODU0:2
9(RX7/TX7)-1 207(ClientLP7/ClientLP7)-1
207(ClientLP7/ClientLP7)-2 IN/OUT–OCH:1–ODU2:1–ODU1:4–ODU0:1
10(RX8/TX8)-1 208(ClientLP8/ClientLP8)-1
208(ClientLP8/ClientLP8)-2 IN/OUT–OCH:1–ODU2:1–ODU1:4–ODU0:2
Procedure
Step 1 Configure Port Working Mode to ODU1_ODU0 mode (OTU1->ODU1->ODU0[-
>ODU1]->ODU2->OTU2) for the LOA board.
Operation Example:
4 3
Step 2 Optional: According to the network plan, set the port type in Path View.
Operation Example:
3 4
2
5
Step 3 Optional: Configure the timeslot configuration mode of the LOA board.
Operation Example:
3
:
l If the service signal flow is OTU1->ODU1->ODU0->ODU2->OTU2, set ODU
Timeslot Configuration Mode to Assign random.
l If the service signal flow is OTU1->ODU1->ODU0->ODU1->ODU2->OTU2, set ODU
Timeslot Configuration Mode to Assign consecutive.
Step 4 Set Service Mode to OTN Mode of the LOA board.
Operation Example:
NOTICE
Modifying the service type will lead to service interruption.
Step 6 Configure ODU0-level cross-connections from LP ports to the WDM side on the LOA board.
Operation Example:
l When the ODU Timeslot Configuration Mode is Assign random.
z
4
1
3
z
4
1
z
4
1
3
z
4
1
z
4
1
NOTE
This mode can be configured on a maximum of four ports, with each port configured with two cross-
connections.
The preceding configuration is for port 3 (RX1/TX1). For other ports, if Port Working Mode is set to
ODU1_ODU0 mode (OTU1->ODU1->ODU0[->ODU1]->ODU2->OTU2), note the following difference in
cross-connection configuration:
l Retain the same values for the other parameters except Source Optical Port and Sink Optical Channel.
l Set any three of the 202(ClientLP2/ClientLP2)-208(ClientLP8/ClientLP8) ports as Source Optical Port
and set Source Optical Channel to 1 and 2 to configure the cross-connections. The value of Sink
Optical Channel is automatically generated by the system.
----End
Legend Information
Figure 5-11 shows legend information about U2000 operations.
Application Diagram
Figure 5-12 lists the condition where the LOA board works in ODUflex non-convergence
mode.
Figure 5-12 Position of the LOA in a WDM system (Scenario 4: ODUflex non-convergence
mode (Any->ODUflex->ODU2->OTU2))
1xOTU2 1xOTU2
LOA LOA
TX1 RX1
M M
RX1 U U TX1
OUT IN
2×ODUflex
2×ODUflex
3G-SDI/3G-SDIRBR/ X X 3G-SDI/3G-SDIRBR/
1×ODU2
1×OTU2
1×ODU2
1×OTU2
8×ODU0
8×ODU0
8×ODU0
8×ODU0
FC400/ / / FC400/
IN
FICON4/FC800/ D D OUT FICON4/FC800/
FICON8G TX2 M M RX2 FICON8G
U U
RX2 X X TX2
Cross-Connection Diagram
Figure 5-13 shows the port configuration of the LOA board.
Figure 5-13 Cross-connection diagram of the LOA board (Scenario 4: ODUflex non-
convergence mode (Any->ODUflex->ODU2->OTU2))
Client side WDM side
3(RX1/TX1)-1 201(ClientLP1/ClientLP1)-1
4(RX2/TX2)-1 202(ClientLP2/ClientLP2)-1
1 IN/OUT-OCH:1-ODU2:1-ODUflex:1
5(RX3/TX3)-1 203(ClientLP3/ClientLP3)-1
6(RX4/TX4)-1 204(ClientLP4/ClientLP4)-1
7(RX5/TX5)-1 205(ClientLP5/ClientLP5)-1
8(RX6/TX6)-1 206(ClientLP6/ClientLP6)-1
10(RX8/TX8)-1 208(ClientLP8/ClientLP8)-1
Procedure
Step 1 Configure the working mode for the LOA board.Set Port Working Mode to ODUflex non-
convergence mode (Any->ODUflex->ODU2->OTU2)
Operation Example:
4 3
NOTE
2
:When the RX1/TX1 port receives the FC800 service, set Port Working Mode to ODUflex
non-convergence mode (Any->ODUflex->ODU2->OTU2) only for port LP1. And set Port Working
Mode to None (not for ports) for the other seven LP ports.
Step 2 Optional: According to the network plan, set the port type in Path View.
Operation Example:
3 4
2
5
Operation Example:
Step 4 Configure Service Type of the LOA board according to the service planning.
Operation Example:
NOTICE
2
:
l Modifying the service type will lead to service interruption.
l The board can receive the 3GSDI/3GSDIRBR/FC400/FICON4G/FC800/FICON8G
services.
l In this scenario, any two of the RX1/TX1 to RX8/TX8 ports receive and transmit 3GSDI/
3GSDIRBR/FC400/FICON4G services, and only the RX1/TX1 port receives and
transmits FC800/FICON8G services.
l The FICON4G service and the FC400 service are processed identically. For the FICON4G
service, you can configure it as the FC400 service on the U2000.
l The FICON8G service and the FC800 service are processed identically. For the FICON8G
service, you can configure it as the FC800 service on the U2000.
Step 5 Configure ODUflex-level cross-connections from LP ports to the WDM side on the LOA
board.
Operation Example:
1
4
NOTE
3
: When the service type is set to FC800/FICON8G, only one cross-connection can be
configured; for service type 3G-SDI/3G-SDIRBR/FC400/FICON4G, a maximum of two cross-
connections can be configured.
The preceding configuration is for port 3(RX1/TX1). When the service type is set to 3G-SDI/3G-
SDIRBR/FC400/FICON4G, another cross-connection can be configured. Note the following difference
in the cross-connection configuration:
l Retain the same values for the other parameters except Source Optical Port and Sink Optical Port.
l Set Source Optical Port to a value in the range of 202(ClientLP2/ClientLP2) to 208(ClientLP8/
ClientLP8) and Sink Optical Port to OCH:1-ODU2:1-ODUflex:2.
----End
Legend Information
Figure 5-14 shows legend information about U2000 operations.
Application Diagram
Figure 5-15 lists the condition where the LOA board works in ODU2 non-convergence mode.
Figure 5-15 Position of the LOA in a WDM system (Scenario 5: ODU2 non-convergence
mode (Any->ODU2->OTU2))
1xOTU2 1xOTU2
LOA LOA
M M
U U
RX1 OUT X X IN TX1
1×ODU2
1×OTU2
1×ODU2
1×OTU2
8×ODU0
8×ODU0
FC800/ / / FC800/
TX1 IN D D OUT RX1 FICON8G
FICON8G
M M
U U
X X
Cross-Connection Diagram
Figure 5-16 shows the port configuration of the LOA board.
Figure 5-16 Cross-connection diagram of the LOA board (Scenario 5: ODU2 non-
convergence mode (Any->ODU2->OTU2))
Client side WDM side
1
3(RX1/TX1)-1 201(ClientLP1/ClientLP1)-1 IN/OUT-OCH:1-ODU2:1
Procedure
Step 1 Configure Port Working Mode to ODU2 non-convergence mode (Any->ODU2->OTU2)
for the LOA board.
Operation Example:
4 3
NOTE
2
:Set Port Working Mode to None (not for ports) for the other ports in the same way.
Step 2 Optional: According to the network plan, set the port type in Path View.
Operation Example:
3 4
2
5
Step 3 Set Service Type to FC800 only for the RX1/TX1 port.
Operation Example:
1 2
Step 4 Configure ODU2-level cross-connections from LP ports to the WDM side on the LOA board.
Operation Example:
1
4
----End
This topic describes the procedure and example of configuring services by station when an
LDC board runs at different rates and in different port working modes.
Configure the
service type
Configure service
cross-connections Mandatory
Optional
N Action Description
o.
Prerequisites
You are an NMS user with " NE operator" privilege or higher.
M M
U U
X X
RX1 TX1
1×ODUflex
1×ODUflex
1x FC3200/ / / 1x FC3200/
1x FC1600/ D D 1x FC1600/
TX1 RX1
M M
U U
X X
1×ODU4
1×OTU4
1×ODU4
1×OTU4
OUT IN
IN OUT
1×ODUflex
1×ODUflex
RX2 TX2
1x FC3200/ 1x FC3200/
1x FC1600 1x FC1600
TX2 RX2
A
LDC
RX1/TX1
1:ODUflex-ODU4:1-OTU4:1
IN1/OUT1
RX2/TX2
2:ODUflex-ODU4:1-OTU4:1
B
LDC
RX1/TX1
1:OTU4-ODU4:1-ODUflex:1
IN1/OUT1
RX2/TX2
1:OTU4-ODU4:1-ODUflex:2
Legend Information
Figure 6-2 shows legend information about U2000 operations.
Procedure
Step 1 Set the line-side rate mode of a board.
NOTE
If service cross-connections have been configured, delete the service cross-connections of the LDC board
first, and then verify that the service type of the client-side port is None. The line-side rate mode can be
changed only when the service type of the client-side port is None.
In the following scenarios, the line-side rate cannot be changed to 100G_QPSK.
l If the Port Working Mode of the optical port 4(RX2/TX2) is ODU4 non-convergence mode(Any-
>ODU4), the line-side rate cannot be switched to 100G_QPSK.
l If the Port Working Mode of the optical port 3(RX1/TX1) is ODU4 non-convergence mode(Any-
>ODU4) and that of the optical port 4(RX2/TX2) is ODUflex non-convergence mode(Any-
>ODUflex), the line-side rate cannot be switched to 100G_QPSK.
l If Port Working Mode for optical port 3 (RX1/TX1) or optical port 4 (RX2/TX2) is ODUflex FC
mode (FC->ODUflex), the line-side rate cannot be switched to 100G_QPSK.
Step 2 Set the port working mode. For details, see 14.1 Configuring the Working Mode.
NOTE
l If the port rate mode is 100G_QPSK, set the port working mode to ODUflex non-convergence mode
(Any->ODUflex).
l If the port rate mode is 200G_16QAM, set the port working mode ODUflex FC mode (FC->ODUflex).
Step 3 Configure the board service type. For details, see 14.3 Configuring the Service Type.
1 3
----End
Result
After the creation is completed, the following information is displayed.
Prerequisites
You are an NMS user with " NE operator" privilege or higher.
RX1 X X TX1
1×ODUflex
1x FC1600/ / / 1x FC1600/
1x FC3200 TX1 D D RX1 1x FC3200
M M
U U
1×ODUC2
1×OTUC2
1×ODUC2
X X
1×OTUC2
OUT IN
IN OUT
1×ODUflex
1×ODUflex
RX2 TX2
1x FC1600/ 1x FC1600/
1x FC3200 TX2 RX2 1x FC3200
A
LDC
RX1/TX1
1:ODUflex FC-ODUC2:1-OTUC2:1
IN1/OUT1
RX2/TX2
2:ODUflex FC-ODUC2:1-OTUC2:1
B
LDC
RX1/TX1
1:OTUC2-ODUC2:1-ODUflex FC:1
IN1/OUT1
RX2/TX2
1:OTUC2-ODUC2:1-ODUflex FC:1
Legend Information
Figure 6-3 shows legend information about U2000 operations.
Procedure
Step 1 Set the line-side rate mode of a board.
NOTE
If service cross-connections have been configured, delete the service cross-connections of the LDC board
first, and then verify that the service type of the client-side port is None. The line-side rate mode can be
changed only when the service type of the client-side port is None.
Step 2 Set the port working mode. For details, see 14.1 Configuring the Working Mode.
NOTE
l If the port rate mode is 100G_QPSK, set the port working mode to ODUflex non-convergence mode
(Any->ODUflex).
l If the port rate mode is 200G_16QAM, set the port working mode ODUflex FC mode (FC->ODUflex).
Step 3 Configure the board service type. For details, see 14.3 Configuring the Service Type.
1 3
1
3
----End
Result
After the creation is completed, the following information is displayed.
Universal line boards support hybrid transmission of OTN, SDH, and packet services. This
topic describes the configuration procedures when a universal line board receives different
services.
Figure 7-1 General configuration procedure for receiving SDH or packet services
Start
Configure board
WDM port attributes.
Configure virtual
ports and mapping
paths.
Check
configurations.
End
NOTE
l When receiving packet or SDH services, the universal line board does not support the Assign
consecutive mode, but only supports the Assign random mode. In this case, the universal line
board only can be interconnected with an board that supports Assign random mode.
l When receiving OTN services, the universal line board can be interconnected with an board that
does not support timeslot mode settings.
4 Configure SDH When SDH services are provisioned on the universal line
services. board, this step is mandatory.
For details about the configuration procedure, see 11
Configuring the SDH Services.
Configure packet When packet services are provisioned on the universal line
services. board, this step is mandatory.
NOTE
When the HUNS3 board is used to receive and transmit packet
services, Line Rate of the ODUk channels mapped by ETH virtual
ports must be set to Standard Mode. For details, see Configuring
the Line Rate.
For details about the configuration procedure, see 13
Configuring Ethernet Services (Packet).
Prerequisites
l You are an NMS user with " NE operator" privilege or higher.
l The universal line board must be created.
l The license for universal line board has been correctly loaded. For details about the
license, see Feature License in the Feature Description.
l The NE license authorization for the universal line board has been set. For details, see
Setting License in the Commissioning Guide.
Background Information
After ETH virtual ports and mapping paths are created, Layer 2 links can be automatically
discovered by 9.6 Searching for WDM Trails so that the U2000 can automatically compute
tunnel routes.
After the trail search is completed, you can choose Inventory > Link Management from the
main menu to view the found Layer 2 links in the window that is displayed. If no Layer 2 link
is found, see Manually Creating a Layer 2 Link.
Legend Information
Figure 7-2 shows legend information about U2000 operations.
Procedure
Step 1 In the NE Explorer,configure SDH or ETH virtual ports to the universal line board
l Operation Example:To add an SDH virtual port,
3 4
1
5
3
1
5
4
Step 2 Optional: Click Port and select the desired virtual port number based on the service plan.
Operation Example:
Step 3 Click the Mapped ODUk drop-down list and select a desired ODUk mapping path.
Operation Example:
Table 7-2 Parameters for configuring virtual ports and mapping paths
Parameter Value Range Description
Bandwidth GE, 2GE, 10GE, nGE Specifies the maximum bandwidth of services
Default: GE received or transmitted on a port.
NOTE
You are advised to set the maximum bandwidth of a port
based on the actual packet traffic on the network.
Relationship with Other Parameters:
This parameter is valid only when Port Type is set
to ETH.
Mapped The available Specifies the physical port number used for
ODUk mapping path is mapping a virtual port into ODUk.
related to the type of NOTE
universal line board, When packet or SDH services are provisioned, the
the port type and universal line boards support only the Assign random
level/bandwidth that mode, but do not support the Assign consecutive mode
and the relevant mapping path.
have been set.
----End
Follow-up Procedure
To adjust the number of SDH and packet services carried on a universal line board, you can
perform the following steps to adjust the number of SDH and ETH virtual ports accordingly:
1. Select a virtual port to be adjusted, and delete it.
Operation Example:
Prerequisites
l You are an NMS user with " NE operator" privilege or higher.
l The universal line board must be created.
l The license for universal line board has been correctly loaded. For details about the
license, see Feature License in the Feature Description.
l The NE license authorization for the universal line board has been set. For details, see
Setting License in the Commissioning Guide.
l You have created OCh trails.
Background Information
After ETH virtual ports and mapping paths are created, Layer 2 links can be automatically
discovered by 9.6 Searching for WDM Trails so that the U2000 can automatically compute
tunnel routes.
After the trail search is completed, you can choose Inventory > Link Management from the
main menu to view the found Layer 2 links in the window that is displayed. If no Layer 2 link
is found, see Manually Creating a Layer 2 Link.
Procedure
Step 1 From the main menu of the U2000, choose Service > WDM Trail > Configure Service
Mapping.
Step 3 In the main topology on the right pane, double-click the NEs for which you want to set
service mapping in turn.
Step 5 Select a desired OCh trail from the Trail Name drop-down list.
NOTE
When Service Mapping is set to ETH and Carried Service is set to ODUflex, the Timeslot
(ODTUk.ts,1-8) parameter is available.
Step 7 Click Details. The detailed service mapping information will be displayed in the lower part of
the right pane.
Step 8 Click Channel to select the channel for which you want to set service mapping.
Step 9 Click Configure. The U2000 will create the selected service mapping.
----End
Follow-up Procedure
After service mapping is successfully configured, an ODUk server trail will be created, on
which you can directly configure SDH and packet service trails.
This chapter describes how to configure the TN52TOM, THA/TOA, and LOA boards in
station service package mode to achieve one-click configuration. In station service package
mode, multiple configurations such as configuring port working modes and service types are
performed on a single NMS GUI, facilitating operations and improving configuration
efficiency. The station service package mode is applicable only to some fixed scenarios.
NOTE
You can also configure the TN52TOM, THA/TOA, and LOA boards in manual station mode. In this
mode, you need to perform various operations such as configuring port working modes and service types
on multiple NMS GUIs. The configuration process is complex but applicable to various scenarios. For
details about the manual station mode, see the related sections for manually configuring the TN52TOM,
THA/TOA, and LOA boards by station.
8.1 Overview of the Service Packages
Service packages enable one-click configuration of typical services by issuing multiple
configuration commands in batches, facilitating product deployment commissioning and
reducing maintenance costs. The configuration commands include commands for configuring
working modes, service types, cross-connections, and port types. Configuration contents vary
according to boards and service packages. Currently, service packages are available to the
TN52TOM, THA/TOA, and LOA boards.
8.2 Configuring Service Packages
You can configure service packages for multiple boards in batches or configure the service
package for each board separately.
Table 8-1 Service packages for the TN52TOM board in cascading mode and the
corresponding configuration contents
Service Port Working Service Type Port Type Cross-Connection
Package Mode Configuration
Name
Table 8-2 Service packages for the TN52TOM board in non-cascading mode and the
corresponding configuration contents
Service Port Working Service Type Port Type Cross-Connection
Package Mode Configuration
Name
NOTE
Only the compatible mode of the THA and TOA boards supports service packages.
Table 8-3 lists the service packages for the TOA board and the corresponding configuration
contents.
Table 8-3 Service packages for the TOA board and the corresponding configuration contents
Service Port Working Mode Service Type
Package
Name
Table 8-4 Service packages for the LOA board and the corresponding configuration contents
Servic Port Service ODU Cross- Cross-
e Working Type Timeslot Connections Connections
Packag Mode Configurat from the from the LP
e ion Mode Client Side ports to the
Name to LP Ports WDM side
Prerequisite
l You are an NMS user with " NE operator" privilege or higher.
l The boards that support service packages must be created.
l No cross-connection or protection is configured on the board.
l Port Type is not set to Line Side Color Optical Port for the port in tributary-line
integrated mode on the TN52TOM board.
Precautions
l Existing services on a board will be interrupted if you configure service packages on the
board.
l After a service package is configured for a board, you can change the working mode,
service type, and cross-connections at a port as required. After the change, the
configurations on the board will be different from the fixed configuration contents of the
service package.
Configuration Process
Start
Yes
No
Are the configurations
successful?
Yes
End
NOTE
Legend Information
Figure 8-2 shows legend information about U2000 operations.
NE Batch Configuration
This mode helps you configure service packages for all involved boards in batches on the
NMS.
In the main menu interface entrance:
Step 1 In the Service Package Configuration window, click the Board Type drop-down list to
select the required board type.
Operation Example:
Step 2 In the Service Package window, select the name of the service package that you want to
configure and click Apply To.... In the Select Board dialog box that is displayed, all subnets
containing the selected board type are displayed. Select the boards where you want to
configure the service package and click OK.
Operation Example:
2 3
NOTE
2
To configure service packages for all boards on the NMS, click the Physical Root check
box.
3
When configuring service packages, you can choose whether creating cross-connection or
not.
Step 4 The Configuring Service Package for Boards dialog box is displayed to show the operation
progress. After the operation is completed, the Operation Result dialog box is displayed.
----End
Step 1 In the NE Explorer, select the required board and choose Configuration > Service Package
from the Function Tree.
Operation Example:
3 4
NOTE
3
:When configuring service packages can choose whether to create a cross.
Step 3 The Configuring Service Package for Boards dialog box is displayed to show the operation
progress. After the operation is completed, the Operation Result dialog box is displayed.
----End
Operation Result
l If "Operation succeeded" is displayed in the Operation Result dialog box, click Close to
complete the operation.
l If "Operation failed" or "Operation partially succeeded" is displayed in the Operation
Result dialog box, click Details to view the cause. The possible causes are listed in the
following table. Handle the problem based on the displayed cause.
Cause Solution
Invalid port type Change the port type of all ports on the board
corresponding to the value of Object to client-side ports.
Configuration Verification
After a service package is completed, verify that the service package is successfully
configured.
Step 1 In the NE Explorer, select the board where the service package is configured and choose
Configuration > WDM Interface from the Function Tree. Verify that the value of Service
Type is correctly set for the required ports according to the configured service package.
Operation Example:
Step 2 In the NE Explorer, select the board where the service package is configured and choose
Configuration > Working Mode from the Function Tree. Verify that the values of Board
Working Mode and Port Working Mode are correctly set according to the configured
service package.
Operation Example:
NOTE
3
:Verify the value of Board Working Mode only for the TN52TOM board.
Step 3 If the board is TN52TOM, select the required NE in the NE Explorer and choose
Configuration > WDM Service Management from the Function Tree. Click the WDM
Cross-Connection Configuration tab and verify that the WDM cross-connections are
correctly configured according to the configured service package.
Operation Example:
Step 4 If the board is TN52TOM and the configured service package is Tributary line 7*STM-1/
OC3->ODU1, Tributary line 7*FE->ODU0, or 4*OTU1 REG, select the NE where the
service package is configured in the Main Topology. Double-click the NE icon to open the NE
panel. In the NE panel, select and right-click the required board, and then choose Path View
from the shortcut menu that is displayed. Right-click the required port and choose Modify
Port from the shortcut menu that is displayed. Verify that the value of Type is correctly set
according to the configured service package.
Operation Example:
3 4
5
----End
You can configure WDM services in end-to-end mode by searching for trails and creating
trails at different layers. In addition, the NMS provides the signal flow diagram that visually
displays the signal flow and the transmission media layer route of trails. This facilitates
operations and improves the maintenance efficiency.
After you create fibers and configure services for WDM equipment on the U2000, the trail
information does not exist in the network layer of the U2000. To manage WDM trails, you
need to search for the data of cross-connections and fiber connections over the network to
generate end-to-end WDM trails at the network layer of the U2000.
9.9 Configuration Example: 10GE LAN->ODU2->OTU2 Under Client 1+1 Protection
9.10 Parameters: End to End Service Configuration
In this user interface, you can configure WDM trails.
Currently, the U2000 provides OTN trail models in compliance with ITU-T G.872. OTN trails
include the following types:
l Client trails
l ODUk trails
l OTUk trails
l OCh trails
l OMS trails
l OTS trails
l OSC trails
NOTE
l The first six types of OTN trails are related with services while OSC trails are only related with
supervisory optical signals.
l OTS trails cannot be deleted on the U2000. Instead, they can be deleted only by removing fiber
connections.
The rate level of an ODUk/OTUk trail varies with the value of k, as shown in Table 9-1.
ODU0 1.25
ODU1/OTU1 2.5
ODU2/OTU2 10
ODU3/OTU3 40
ODU4/OTU4 100
Trail Model
Figure 9-1 shows the relationships between different trail types and locations.
M40
D40
OA OA
F F
T L I I L T
U U
D40
M40
OA OA
OTS trail
OMS trail
L: Line board
OCh trail T: Tributary board
ODUk trail
Client trail
When configuring an end-to-end service, users can directly create a client service trail without creating
the electrical-layer server trail. After the service trail is created, the electrical-layer server trail will be
automatically created.
Configure logical fiber Configure logical fiber Configure logical fiber Configure logical fiber Configure logical fiber Configure logical fiber
connections connections connections connections connections connections
Configure cross-
Configure wavelength Configure wavelength connection (TX/RX Configure wavelength Configure wavelength Configure wavelength
port<-> LP port)
Create OCh trail Create OCh trail Configure wavelength Create OCh trail Create OCh trail Create OCh trail
Configure service
Search WDM trail Search WDM trail Create OCh trail Configure service type Search WDM trail
type
System creates
Configure Service Configure Service Create client trail Configure Service
ODUk trail
type type type
automatically
Create client trail Create client trail Create client trail Create client trail
The end-to-end WDM trail configuration flow varies with the board type. For details on each
step in the flowchart, refer to Table 9-2.
1 Configure l WDM trails can be searched out and created only when logical
logical fiber fiber connections are correct.
connections.
N Step Remarks
o
.
3 Configure the l Set the board working mode and port working mode based on the
working mode. current application and service mapping path. Therefore, in the
multiple applications, the boards enable services to be processed
differently.
l Set Working Mode for the port in the Create WDM Trail
window when creating ODUk trails or client trails using the
board that supports multiple application scenarios. For details,
refer to 9.4 Creating ODUk Trails and 9.5 Creating Client
Trails.
4 Configure the l Service transmission is possible only when the service type
service type. configured for WDM ports is consistent with the type of the
transmitted service.
l When creating client trails in an end-to-end configuration mode,
set the Service Type for the port in the Create WDM Trail
window. For details, refer to 9.5 Creating Client Trails.
5 Create OCh OCh trails that traverse dynamic OADMs must be manually created
trails. and those that do not traverse dynamic OADMs already exist and
can be searched out.
6 Create ODUk ODUk trails with cross-connections need to be created and those
trails. with no cross-connection already exist and can be searched out.
NOTE
Users can create an end-to-end client service trail directly without creating the
electrical-layer server trail. After the service trail is created, the electrical-
layer server trail will be automatically created.
Prerequisites
You are an NMS user with "Operator Group" privilege or higher.
The logical fiber connections on the trail must be established.
Background Information
M40
D40
OA OA OA OA
F F F F
T L I I ROADM I I L T
U U U U
M40
D40
OA OA OA OA
D40 M40
L
T: Tributary Board
OCh TraiN
L: Line Board
T
l When Board Mode of a regenerator board is set to Electrical Relay Mode, the OCh
trail is terminated on the regenerator board. For example, for a service traversing a
regenerator board, as shown in Figure 9-4, four unidirectional OCh trails are generated
using the E2E trail management function.
Figure 9-4 OCh trails of a service that traversing an electrical regenerator board
IN1 OUT1
T L L L T
OUT2 IN2
l When Board Mode of a regenerator board is set to Optical Relay Mode, a complete
bidirectional OCh trail is generated using the E2E trail management function. Figure 9-5
shows the OCh trail.
Figure 9-5 OCh trail of a service that traversing an optical regenerator board
IN1 OUT1
T L L L T
OUT2 IN2
T: Tributary Board
OCh Trail
L: Line Board
NOTE
l If the Auto Calculation check box is selected during trail creation, route calculation is triggered when
you specify the source, sink, or route constraints, or configure protection. If the route calculation is
successful, the calculation result can be queried in the topology view and the server route list; otherwise,
an error message is displayed indicating the failure causes.
l If the Auto Calculation check box is deselected, routes are not automatically calculated when you create
a trail. You can click Calculate Route to check the correctness of a route.
l After an optical cross-connection is created for an MCS0816 board, view the WDM interface attribute
McsSwitch Status of the MCS0816 board. If the value is on, the optical cross-connection is successfully
created and services are normal. If the value is off, the optical cross-connection is successfully created
and the OCh trail search succeeds, but services are unavailable and an MCS_SWITCH_BLOCKED alarm
is reported. The possible cause is as follows: When two optical cross-connections to the same sink port
are created, the actual wavelengths on the two source ports are the same, causing a conflict.
Procedure
Step 1 On the main menu of the U2000, choose Service > WDM Trail > Create WDM Trail.
Step 3 Click Browse on the right side of the Source field. In the displayed dialog box, select the
required NE and specify a port on the NE as the source port of the E2E trail. Then use the
same procedure to specify the sink port.
NOTE
If the message "There is no server trail between the source and the sink" is displayed, check the
following information with the design document:
l Wavelength and band settings for the source and sink ports of the OCh trail
l Logical fiber connections for the source and sink ports of the OCh trail
If any of this information is incorrect, the OCh trail fails to be created.
Step 4 Optional: If the routes that are automatically computed are different from the planned ones,
you must specify route constraints.
l Method 1: Specify route constraints in the Create WDM Trails window.
a. Click the Explicit Link tab. Right-click the blank area and choose Add from the
shortcut menu. In the Add Explicit Link window, you can search for the existing
server trails and set them as the explicit links of the trails to be created.
b. Click the Explicit Node tab. Right-click in a blank area and choose Add NE
Restriction or Add Board/Port Restriction from the shortcut menu. In the
window that is displayed, you can search for an NE, a board or a port and set them
as the explicit nodes for the trails to be created.
NOTE
When the E2E trail traverses an optical regeneration site, you must specify the INx/OUTx port on
the optical regeneration board that the forward trail traverses and the INx/OUTx port on the
optical regeneration board that the reverse trail traverses.
c. Click the Excluded Node tab. Right-click in a blank area and choose Add NE
Restriction from the shortcut menu. In the window that is displayed, you can
search for an NE and set it as the excluded nodes for the trails to be created.
l Method 2: You can also specify route constraints in the topology view. When you create
a service, the server links of the OMS level are automatically filtered and displayed in
green in the topology view. After routes are successfully calculated, the working route is
displayed in blue between the source and sink NEs.
a. Specify the explicit link. Click a server link in green between the source and sink
NEs. In the dialog box that is displayed, specify the explicit server trails of all levels
for the service. Click the trail again to cancel the selection.
b. Specify the explicit node. Right-click the desired NE, choose Set Explicit Node >
NE or Set Explicit Node > Board/Port from the shortcut menu, and set an NE, a
board or a port as the explicit nodes for the trails to be created. This selected NE is
marked with . Double-click the NE again to cancel the selection.
c. Specify the excluded node. Right-click the desired NE, choose Set Excluded Node
> NE or Set Excluded Node > Board/Port from the shortcut menu, and set an NE,
a board or a port as the excluded nodes for the trails to be created. The selected NE
is marked with . Double-click the NE again to cancel the selection.
Step 5 After the trail computation is complete, the server-layer route information of the to-be-created
trail and the port attribute list are displayed at the bottom of the topology view.
l Click the Server Layer Route Details tab to view the server-layer route information of
the working and protection trails.
l Click the Port Attributes Settings tab to view and modify the port attributes of the to-
be-created trail and its server-layer trails.
Step 6 Optional: Before deploying the configuration of a service, you can perform the following
operations as required.
l Select the Activate the Trail check box. The trail is then delivered to the NE layer after
it is created successfully. Otherwise, the trail configuration data is saved only on the
U2000.
l If the network design clearly specifies that the OPA function is not required, in the OPA
Mode dialog box, set the optical power adjustment mode to Manual for the OCh trail to
be created.
Step 7 Click Apply to complete the trail settings. The Create Trail dialog box is displayed, which
shows the trail creation progress. Wait until the Operation Result dialog box displays the
message Operation succeeded.
----End
Troubleshooting
If route computation fails during the trail creation, a dialog box indicating a route computation
failure will be displayed on the U2000. Click Analyze Route to analyze the root cause based
on the information displayed in Route Fault Analysis.
Follow-up Procedure
To view the new trails, click Browse Trail in the Operation Result dialog box. The new
trails are displayed in the Manage WDM Trail window.
Prerequisites
You are an NMS user with "Operator Group" privilege or higher.
Background Information
l If the Auto Calculation check box is selected during trail creation, route calculation is
triggered when you specify the source, sink, or route constraints, or configure protection.
If the route calculation is successful, the calculation result can be queried in the topology
view and the server route list; otherwise, an error message is displayed indicating the
failure causes.
l If the Auto Calculation check box is deselected, routes are not automatically calculated
when you create a trail. You can click Calculate Route to check the correctness of a
route.
Procedure
Step 1 On the main menu of the U2000, choose Service > WDM Trail > Create WDM Trail.
Step 2 In the displayed window, set Level to the required ODUk level, for example, ODU1.
NOTE
l When Level is set to ODU2 or ODU3, the Rate parameter has two values: Standard Mode and Speedup
Mode. When the WDM-side signal is OTU2e or OTU3e, or when the client-side signal is 10GE LAN and
Port Mapping is set to Bit Transparent Mapping (11.1 G) for the client-side port, set this parameter to
Speedup Mode. In any other cases, set this parameter to Standard Mode.
l When the trail level is ODUflex, set Service Type to the same value as the service type configured in the
NE Explorer.
Step 3 Click Browse to the right of the Source field. In the displayed Select Board Port-Source
dialog box, select the required NE and specify a port on the NE as the source port of the E2E
trail.
NOTE
In the Select Board Port-Source window, click Working Mode Setting to set Working mode for the port
when using the board that supports multiple application scenarios.
Then use the same procedure to specify the sink port.
Step 4 Optional: If the routes that are automatically computed are different from the planned ones,
you must specify route constraints.
l Method 1: Specify route constraints in the Create WDM Trails window.
a. Click the Explicit Link tab. Right-click in a blank area and choose Add from the
shortcut menu. In the Add Explicit Link window, search for the existing server
trails and set them as the explicit links of the trails to be created. Select the Select
Channel check box and select the channels for the explicit links. If no channel is
selected for the explicit links, the U2000 automatically calculates route channels.
b. Click the Explicit Node tab. Right-click in a blank area and choose Add NE
Restriction or Add Board/Port Restriction from the shortcut menu. In the
window that is displayed, you can search for an NE, a board or a port and set them
as the explicit nodes for the trails to be created.
c. Click the Excluded Node tab. Right-click in a blank area and choose Add NE
Restriction from the shortcut menu. In the window that is displayed, you can
search for an NE and set it as the excluded nodes for the trails to be created.
l Method 2: You can also specify route constraints in the topology view. When you create
a service, the server links of the OCh level are automatically filtered and displayed in
green in the topology view. After routes are successfully calculated, the working route is
displayed in blue between the source and sink NEs.
a. Specify the explicit link. Click a server link in green between the source and sink
NEs. In the dialog box that is displayed, specify the explicit server link for the
service.
Select the Select Channel check box and select the channels for the explicit links.
If no channel is selected for the explicit links, the U2000 automatically calculates
route channels.
b. Specify the explicit node. Right-click the desired NE, choose Set Explicit Node >
NE or Set Explicit Node > Board/Port from the shortcut menu, and set an NE, a
board or a port as the explicit nodes for the trails to be created. The selected NE is
marked with . Double-click the NE again to cancel the selection.
c. Specify the excluded node. Right-click the desired NE, choose Set Excluded Node
> NE or Set Excluded Node > Board/Port from the shortcut menu, and set an NE,
a board or a port as the excluded nodes for the trails to be created. The selected NE
is marked with . Double-click the NE again to cancel the selection.
Step 5 After the trail computation is complete, the server-layer route information of the to-be-created
trail, the list of new dynamic cross-connections, and the port attribute list are displayed at the
bottom of the topology view.
l Click the Server Layer Route Details tab to view the server-layer route information of
the working and protection trails.
l Click the Create Cross-Connection tab to view new dynamic cross-connections.
The user can modify the level of the pass-through cross-connections on the intermediate
pass-through node by selecting a value from the Traversal Level drop-down list. The
default level is the smallest granularity.
l Click the Port Attributes Settings tab to view and modify the port attributes of the to-
be-created trail and its server-layer trails, excluding the port attributes of the OMS and
OTS trails.
Step 6 Optional: Select the Activate the Trail check box. The trail is then delivered to the NE layer
after it is created successfully. Otherwise, the trail configuration data is saved only on the
U2000.
Step 7 Click Apply to complete the trail settings. The Create Trail dialog box is displayed, showing
the trail creation progress. Wait until the Operation Result dialog box displays the message
Operation succeeded.
----End
Troubleshooting
If route computation fails during the trail creation, a dialog box indicating a route computation
failure will be displayed on the U2000. Click Analyze Route to analyze the root cause based
on the information displayed in Route Fault Analysis.
Follow-up Procedure
To view the new trails, click Browse Trail in the Operation Result dialog box. The new
trails are displayed in the Manage WDM Trail window.
Prerequisites
You are an NMS user with "Operator Group" privilege or higher.
Background Information
l When OTUk services are used both on the source and sink, client trails cannot be created
and managed in E2E mode.
l If the Auto Calculation check box is selected during trail creation, route calculation is
triggered when you specify the source, sink, or route constraints, or configure protection.
If the route calculation is successful, the calculation result can be queried in the topology
view and the server route list; otherwise, an error message is displayed indicating the
failure causes.
l If the Auto Calculation check box is deselected, routes are not automatically calculated
when you create a trail. You can click Calculate Route to check the correctness of a
route.
Procedure
Step 1 On the main menu of the U2000, choose Service > WDM Trail > Create WDM Trail.
Step 3 Select the required service rate from the Rate field according to the information in the design
document.
Channel check box and select the channels for the explicit links. If no channel is
selected for the explicit links, the U2000 automatically calculates route channels.
b. Click the Explicit Node tab. Right-click in a blank area and choose Add NE
Restriction or Add Board/Port Restriction from the shortcut menu. In the
window that is displayed, you can search for an NE, a board or a port and set them
as the explicit nodes for the trails to be created.
c. Click the Excluded Node tab. Right-click in a blank area and choose Add NE
Restriction from the shortcut menu. In the window that is displayed, you can
search for an NE and set it as the excluded nodes for the trails to be created.
l Method 2: You can also specify route constraints in the topology view. When you create
a service, the server links of the OCh level are automatically filtered and displayed in
green in the topology view. After routes are successfully calculated, the working route is
displayed in blue between the source and sink NEs.
a. Specify the explicit link. Click a server link in green between the source and sink
NEs. In the dialog box that is displayed, specify the explicit server link for the
service.
Select the Select Channel check box and select the channels for the explicit links.
If no channel is selected for the explicit links, the U2000 automatically calculates
route channels.
b. Specify the explicit node. Right-click the desired NE, choose Set Explicit Node >
NE or Set Explicit Node > Board/Port from the shortcut menu, and set an NE, a
board or a port as the explicit nodes for the trails to be created. The selected NE is
marked with . Double-click the NE again to cancel the selection.
c. Specify the excluded node. Right-click the desired NE, choose Set Excluded Node
> NE or Set Excluded Node > Board/Port from the shortcut menu, and set an NE,
a board or a port as the excluded nodes for the trails to be created. The selected NE
is marked with . Double-click the NE again to cancel the selection.
Step 6 After the trail computation is complete, the server-layer route information of the to-be-created
trail, the list of new dynamic cross-connections, and the port attribute list are displayed at the
bottom of the topology view.
l Click the Server Layer Route Details tab to view the server-layer route information of
the working and protection trails.
l Click the Create Cross-Connection tab to view new dynamic cross-connections.
The user can modify the level of the pass-through cross-connections on the intermediate
pass-through node by selecting a value from the Traversal Level drop-down list. The
default level is the smallest granularity.
l Click the Port Attributes Settings tab to view and modify the port attributes of the to-
be-created trail and its server-layer trails, excluding the port attributes of the OMS and
OTS trails.
Step 7 Optional: Select the Activate the Trail check box. The trail is then delivered to the NE layer
after it is created successfully. Otherwise, the trail configuration data is saved only on the
U2000.
Step 8 Click Apply to complete the trail settings. The Create Trail dialog box is displayed, showing
the trail creation progress. Wait until the Operation Result dialog box displays the message
Operation succeeded.
Step 9 Click Close to close the dialog box.
----End
Troubleshooting
If route computation fails during the trail creation, a dialog box indicating a route computation
failure will be displayed on the U2000. Click Analyze Route to analyze the root cause based
on the information displayed in Route Fault Analysis.
Follow-up Procedure
To view the new trails, click Browse Trail in the Operation Result dialog box. The new
trails are displayed in the Manage WDM Trail window.
Prerequisites
l You are an NMS user with "Maintenance Group" privilege or higher.
l Logical fiber connections have been configured correctly.
Procedure
Step 1 On the main menu of the U2000, choose Service > WDM Trail > Search for WDM Trail.
Step 2 In the Advanced Settings area, set various processing policies associated with trail searching.
Step 3 On the lower right of the window, click Next to start trail searching. Wait until the status of
the progress bar reaches 100%.
----End
Follow-up Procedure
1. In the Main Topology view, choose Service > WDM Trail > Manage WDM Trail
from the Main Menu.
2. On the Basic Settings tab, select the level of the service being queried for Level.
3. Click Filter All.
In Manage WDM Trail, Check whether the trails on the subnet being queried are
consistent with the network design.
Prerequisites
l You are an NMS user with " NE operator" privilege or higher.
l The Client, ODUk, OTUk, or OCh trail has been searched or created.
Procedure
Step 1 Choose Service > WDM Trail > Manage WDM Trail from the Main Menu.
Step 2 The Set Trail Browse Filter Criteria dialog box is displayed. Set the filter criteria and view
the desired trails in the trail list.
NOTE
Step 3 Select one or more unactivated trails, right-click and choose Active from the shortcut menu.
NOTE
For an OCh trail, you can choose Active or Active(with Attenuation Restored) to activate the trail.
l Active indicates that the optical attenuation is the default one after the OCh trail is activated.
l Active (with Attenuation Restored) indicates that the modifiable optical attenuation is the one set on
the NMS before the trail is activated on an activated OCh trail.
Step 4 In the displayed Confirm dialog box, click Yes. The displayed Result dialog box indicates
that the operation is successful.
Step 5 Click Close.
----End
Service Requirements
On the network shown in Figure 9-6, ONEs A, B, C, and D form a ring network. All the NEs
function as OADM stations. The service requirements are as follows:
l User1 and User2 communicate with each other. One bidirectional OTN service is
configured between station A and station C.
l One GE service is added and dropped for User1 and User2 each.
l ODUk SNCP protection is configured.
21-TOM
E 04- 16- W NMS
NQ2 NQ2
W A E
04-
16-
NQ2
NQ2 D
B 16-
04-
NQ2
NQ2 C
W
E
OADM
User2
Boards Configured
Two NQ2 boards and one TOM board must be configured at stations A and C each. Two NQ2
boards must be configured at stations B and D each.
NQ2 NQ2
1(IN1/ 71(ODU2L 51(ODU1L 51(ODU1L 71(ODU2L 1(IN1/
OUT1) P/ODU2LP) P/ODU1LP) P/ODU1LP) P/ODU2LP) OUT1)
NQ2 TOM
1(IN1/ 71(ODU2L 51(ODU1L 201(ClientLP1/Cli 3(RX1/TX1)
OUT1) P/ODU2LP) P/ODU1LP) entLP1)-1 4(RX2/TX2)
2(IN2/ 72(ODU2L 203(ClientLP3/Cli 5(RX3/TX3)
52(ODU1L
OUT2) P/ODU2LP) entLP3)-1 6(RX4/TX4)
P/ODU1LP)
3(IN2/ 73(ODU2L 53(ODU1L 205(ClientLP5/Cli 7(RX5/TX5)
OUT2) P/ODU2LP) P/ODU1LP) entLP5)-1 8(RX6/TX6)
4(IN2/ 74(ODU2L 54(ODU1L 207(ClientLP7/Cli 9(RX7/TX7)
OUT2) P/ODU2LP) P/ODU1LP) entLP7)-1 10(RX8/TX8)
Prerequisite
l You are an NMS user with "Administrators" privilege.
l A license for trail management must be available.
l The OCh server trail must be searched out.
l The physical and logical fiber connections between and inside all relevant stations must
be established correctly.
Precautions
NOTE
The value of TN52TOM Board Mode is NON-Cascading mode by default. In this case, the 201 (ClientLP1/
ClientLP1) and 205(ClientLP5/ ClientLP5) ports can access a maximum of four services, and the 203
(ClientLP3/ ClientLP3) and 207 (ClientLP7/ ClientLP7) ports can access a maximum of two services.
NOTE
A ClientLP port can access only one service that has a rate higher than 1.25 Gbit/s, and this service can
be configured in only the first channel of the ClientLP port.
The total rate of services accessed by a ClientLP port must be equal to or lower than 2.5 Gbit/s.
The client-side eight pairs of optical ports can access services at a maximum rate of 10 Gbit/s.
The client-side ports can be grouped as required.
Background Information
ODUk SNCP is classified into three types: SNC/I, SNC/N, and SNC/S. The difference among
the three types is that they have different monitoring abilities and therefore are triggered by
different conditions.
NOTICE
n If you need to change Service Mode of a board, deactivate the services on the
board first. Note that deactivation interrupts the services.
n For a 51NQ2 board, the default value of Service Mode is ODU1. For a 52NQ2
board, the default value of Service Mode is AUTO. You can change the value to
ODU1 or retain the default value.
cannot pass through. The sign is shown on the NE. Double-click the NE again to
cancel your selection.
10. Optional: Click Specify Route Channel and the Specify Route Channel dialog box is
displayed. Select a path and click OK.
11. Click the Protection Setting tab, and set the SNCP protection route.
– Right-click the NEA that dual feeds services and choose Set Dual-Feed Point from
the shortcut menu. In the upper left corner of the NEA icon, is displayed.
– Right-click the NEC that dual feeds services and choose Set Selective-Receiving
Point from the shortcut menu. In the upper left corner of the NEC icon, is
displayed.
12. Right-click on the Node list window and choose Set SNCP Parameter. In the displayed
Set SNCP Parameter window, set SNCP Type of NEs A and C to SNC/N. Click OK.
13. Click the General Attributes set the basic trail attributes, including the name and ID.
14. Click Apply. A dialog box is displayed, indicating that the operation is successful. Click
Close.
NOTE
Select the Activate the trail check box. The trail is then delivered to the NE layer after it is
created successfully. Otherwise, the trail configuration data is saved only on the U2000.
1. Choose Service > WDM Trail > Create WDM Trail from the Main Menu.
2. Make the following settings in the Create WDM Trail window:
– Level: Client
– Direction: Bidirectional
– Rate: GE
3. Double-click NE A in Physical Root. Then, select the TOM board in slot 21 in the
displayed Select Board Port window and make the following settings:
– Available Timeslots/Port: 3(RX1/TX1)
– Channel: 1
4. Click OK
5. Double-click NE C in Physical Root. Then, select the TOM board in slot 21 in the
displayed Select Board Port window and make the following settings:
– Available Timeslots/Port: 3(RX1/TX1)
– Channel: 1
6. Click OK.
7. Click the General Attributes tab to set the basic trail attributes, including the name and
ID.
8. Click Apply. A dialog box is displayed, indicating that the operation is successful. Click
Close.
NOTE
Select the Activate the trail check box. The trail is then delivered to the NE layer after it is
created successfully. If you do not select the Activate the trail check box, the trail configuration
data is saved only on the U2000.
NOTE
The preceding configuration procedure is described based on the scenario of ODU1 SNCP
protection. In this scenario, cross-connect and pass-through services of the ODU1 level and optical
ports 51-54 on the line board must be configured. If ODU0 SNCP protection is configured, cross-
connect and pass-through services of the ODU0 level and optical ports 161-176 on the line board
must be configured. If no SNCP protection is configured, you do not need to create ODUk server
trails but directly create client trails.
----End
Result
Step 1 Choose Service > WDM Trail > WDM Trail Management from the Main Menu and select
the proper filter criteria for the trails.
NOTE
You can filter other trails based on the source and sink of the new trail.
Step 2 In the WDM Trail Management window, verify that the trail is correctly created.
----End
Postrequisite
None.
Service Requirements
On the network shown in Figure 9-7, stations A and B (both are OTM stations) form a P2P
network. The service requirements are as follows:
l User1 and User2 communicate with each other. One bidirectional OTU2 service is
configured between stations A and B.
l One 10GE LAN service is added and dropped to/from User1 and User2 each.
l Client 1+1 protection is configured.
NMS
User1 A B User2
NE(9-811) NE(9-812)
OTM
Signal flow
TO1/RI1
RX2/TX2 ODU2:1-OCH:1 IN2/OUT2
TI/RO
RX1/TX1 ODU2:1-OCH:1 IN1/OUT1
TO2/RI2
RX2/TX2 ODU2:1-OCH:1 IN2/OUT2
TDX ND2
NE(9-811)
TO1/RI1
TO2/RI2
IN2/OUT2 OCH:1-ODU2:1
RX2/TX2
ND2 TDX
NE(9-812)
Prerequisites
l You are an NMS user with "Administrators" privilege.
l Inter- and intra-station physical and logical fiber connections have been correctly
created.
l OCh trails have been searched out or created.
c. Click OK. In the Result dialog box that is displayed, click Close. The created
protection group is displayed.
2. Configure client 1+1 protection at station B. For details, see 1.
3. Create a client trail.
a. From the main menu, choose Service > WDM Trail > Create WDM Trail.
ii. Select the service receiving port and channel and click OK.
d. Configure the sink port. For details, see 3.c.
e. Select Auto-Calculation. In Server Layer Route Details, verify that Source and
Sink of the trail are the same as planned. On the Port Attributes Settings tab,
configure the FEC type of the upstream and downstream boards.
f. Click Apply. The Result dialog box is displayed, indicating that the operation was
successful. Click Close.
Result
To view the created trail, choose Service > WDM Trail > Manage WDM Trail from the
main menu. In the Manage WDM Trail window that is displayed, set the criteria to search
for the new trail.
SPC First Checked, Unchecked When checked, you can create ASON-
WDM trail, if the trail passes through
the ASON domain.
Explicit For example: NE7 Specifies the explicit NE for the trail to
Node be created.
Click Explicit Node for more
information.
Excluded For example: NE7 Indicates the excluded node of the trail.
Node Click Excluded Node for more
information.
Protectio Node list Dual-Fed Point To set or cancel the dual-fed point,
n Setting right-click the NE on the topology and
select Set Dual-Feed Point or Cancel
Dual-Feed Point from the shortcut
menu.
Set SNCP SNCP Type Specifies the SNCP type. For example,
Parameter SNC/N.
Specify Source For example: NE6 Indicates the source of the server layer
Route trail.
Channel
Sink For example: NE7 Indicates the sink of the server layer
trail.
NE List For example: NE1 Indicates the NE that the trail traverses.
This topic describes the procedure and example of configuring services in E2E mode when an
LDC board runs at different rates and in different port working modes.
Configure the
service type
Optional
N Action Description
o.
Service Requirements
On the network shown in Figure 10-2, sites A and B form a point-to-point network, and both
sites are OTM sites. The service requirements are as follows:
l User1 and User2 communicate with each other. One bidirectional OTUC2 service is
configured between sites A and B.
l Two 100GE services are added to and dropped from User1 and User2 each.
NMS
User1 A B User2
NE1 NE2
12-TN11LDC 12-TN11LDC
OTM
Boards Configured
In this example, one TN11LDC board is configured at site A and site B separately.
A
LDC
RX1/TX1
1:ODU4-ODUC2:1-OTUC2:1
IN1/OUT1
RX2/TX2
2:ODU4-ODUC2:1-OTUC2:1
B
LDC
RX1/TX1
1:OTUC2-ODUC2:1-ODU4:1
IN1/OUT1
RX2/TX2
1:OTUC2-ODUC2:1-ODU4:2
Prerequisites
l You are an NMS user with "Administrators" privilege.
l Inter- and intra-site physical and logical fiber connections have been correctly created.
Background Information
The line-side rate modes, port working modes, and service types of the boards at sites A and
B must be set to the same values.
Legend Information
Figure 10-4 shows legend information about U2000 operations.
Procedure
1. Configure the line-side rate mode of the boards at sites A and B.
Configuration example at site A:
1
3
NOTE
If service cross-connections have been configured, delete the service cross-connections of the LDC
board first, and then verify that the service type of the client-side port is None. The line-side rate mode
can be changed only when the service type of the client-side port is None.
2. Configure the port working mode at sites A and B respectively. For details, see 14.1
Configuring the Working Mode.
Configuration example at site A:
3. Configure the board service type for the boards at sites A and B respectively. For details,
see 14.3 Configuring the Service Type.
Configuration example at site A:
1 3
4. Search for WDM trails. For details, see 9.6 Searching for WDM Trails.
Result
To view the created trail, choose Service > WDM Trail > Manage WDM Trail from the
main menu. In the Manage WDM Trail window that is displayed, set the criteria to search
for the new trail.
Service Requirements
On the network shown in Figure 10-5, sites A and B form a point-to-point network, and both
sites are OTM sites. The service requirements are as follows:
l User1 and User2 communicate with each other. One bidirectional OTU4 service is
configured between sites A and B.
l Two FC1600 services are added to and dropped from User1 and User2 each.
NMS
User1 A B User2
NE1 NE2
12-TN11LDC 12-TN11LDC
OTM
Boards Configured
In this example, one TN11LDC board is configured at site A and site B separately.
A
LDC
RX1/TX1
1:ODUflex-ODU4:1-OTU4:1
IN1/OUT1
RX2/TX2
2:ODUflex-ODU4:1-OTU4:1
B
LDC
RX1/TX1
1:OTU4-ODU4:1-ODUflex:1
IN1/OUT1
RX2/TX2
1:OTU4-ODU4:1-ODUflex:2
Prerequisites
l You are an NMS user with "Administrators" privilege.
l Inter- and intra-site physical and logical fiber connections have been correctly created.
Background Information
The line-side rate modes, port working modes, and service types of the boards at sites A and
B must be set to the same values.
Legend Information
Figure 10-7 shows legend information about U2000 operations.
Procedure
1. Configure the line-side rate mode of the boards at sites A and B.
Configuration example at site A:
NOTE
If service cross-connections have been configured, delete the service cross-connections of the LDC
board first, and then verify that the service type of the client-side port is None. The line-side rate mode
can be changed only when the service type of the client-side port is None.
In the following scenarios, the line-side rate cannot be changed to 100G_QPSK.
l If the Port Working Mode of the optical port 4(RX2/TX2) is ODU4 non-convergence
mode(Any->ODU4), the line-side rate cannot be switched to 100G_QPSK.
l If the Port Working Mode of the optical port 3(RX1/TX1) is ODU4 non-convergence
mode(Any->ODU4) and that of the optical port 4(RX2/TX2) is ODUflex non-convergence
mode(Any->ODUflex), the line-side rate cannot be switched to 100G_QPSK.
l If Port Working Mode for optical port 3 (RX1/TX1) or optical port 4 (RX2/TX2) is ODUflex
FC mode (FC->ODUflex), the line-side rate cannot be switched to 100G_QPSK.
2. Create the first channel of FC1600 services in E2E mode.
a. Choose Service > WDM Trail > Create WDM Trail from the main menu.
ii. Click Working Mode Settings, and set the working mode to ODUflex non-
convergence mode(Any->ODUflex).
iii. Set the sink port using the same method. After the setting is completed, the
interface shown in the following figure is displayed.
iv. Select Auto-Calculation and click Apply to complete the creation of a Client
trail.
3. Create the second channel of FC1600 services with reference to 2.
NOTE
When creating the second channel of FC1600 services, you must select 4(RX2/TX2) as the source and
sink ports.
Result
To view the created trail, choose Service > WDM Trail > Manage WDM Trail from the
main menu. In the Manage WDM Trail window that is displayed, set the criteria to search
for the new trail.
Service Requirements
On the network shown in Figure 10-8, sites A and B form a point-to-point network, and both
sites are OTM sites. The service requirements are as follows:
l User1 and User2 communicate with each other. One bidirectional OTU4 service is
configured between sites A and B.
l Two FC3200 services are added to and dropped from User1 and User2 each.
NMS
User1 A B User2
NE1 NE2
12-TN11LDC 12-TN11LDC
OTM
Boards Configured
In this example, one TN11LDC board is configured at site A and site B separately.
A
LDC
RX1/TX1
1:ODUflex FC-ODUC2:1-OTUC2:1
IN1/OUT1
RX2/TX2
2:ODUflex FC-ODUC2:1-OTUC2:1
B
LDC
RX1/TX1
1:OTUC2-ODUC2:1-ODUflex FC:1
IN1/OUT1
RX2/TX2
1:OTUC2-ODUC2:1-ODUflex FC:1
Prerequisites
l You are an NMS user with "Administrators" privilege.
l Inter- and intra-site physical and logical fiber connections have been correctly created.
Background Information
The line-side rate modes, port working modes, and service types of the boards at sites A and
B must be set to the same values.
Legend Information
Figure 10-10 shows legend information about U2000 operations.
Procedure
1. Configure the line-side rate mode of the boards at sites A and B.
Configuration example at site A:
NOTE
If service cross-connections have been configured, delete the service cross-connections of the LDC
board first, and then verify that the service type of the client-side port is None. The line-side rate mode
can be changed only when the service type of the client-side port is None.
2. Create the first channel of FC3200 services in E2E mode.
a. Choose Service > WDM Trail > Create WDM Trail from the main menu.
ii. Click Working Mode Settings, and set the working mode to ODUflex FC
mode(FC->ODUflex).
iii. Set the sink port using the same method. After the setting is completed, the
interface shown in the following figure is displayed.
iv. Select Auto-Calculation and click Apply to complete the creation of a Client
trail.
3. Create the second channel of FC3200 services with reference to 2.
NOTE
When creating the second channel of FC3200 services, you must select 4(RX2/TX2) as the source and
sink ports.
Result
To view the created trail, choose Service > WDM Trail > Manage WDM Trail from the
main menu. In the Manage WDM Trail window that is displayed, set the criteria to search
for the new trail.
Service Requirements
On the network shown in Figure 10-11, sites A and B form a point-to-point network, and both
sites are OTM sites. The service requirements are as follows:
l User1 and User2 communicate with each other. One bidirectional OTUC2 service is
configured between sites A and B.
l Two 100GE services are added to and dropped from User1 and User2 each.
NMS
User1 A B User2
NE1 NE2
12-TN11LDC 12-TN11LDC
OTM
Boards Configured
In this example, one TN11LDC board is configured at site A and site B separately.
A
LDC
RX1/TX1
1:ODUflex-ODU4-ODUC2:1-OTUC2:1
IN1/OUT1
RX2/TX2
2:ODUflex-ODU4-ODUC2:1-OTUC2:1
B
LDC
RX1/TX1
1:OTUC2-ODUC2:1-ODU4-ODUflex:1
IN1/OUT1
RX2/TX2
1:OTUC2-ODUC2:1-ODU4-ODUflex:2
Prerequisites
l You are an NMS user with "Administrators" privilege.
l Inter- and intra-site physical and logical fiber connections have been correctly created.
Background Information
The line-side rate modes, port working modes, and service types of the boards at sites A and
B must be set to the same values.
When creating a service, if you specify the service timeslot according to the actual rate, see
Procedure (Customizing ODUflex Timeslots); if you use the default service timeslot, see
Procedure (Default ODUflex Timeslots).
Legend Information
Figure 10-13 shows legend information about U2000 operations.
1
3
NOTE
If service cross-connections have been configured, delete the service cross-connections of the LDC
board first, and then verify that the service type of the client-side port is None. The line-side rate mode
can be changed only when the service type of the client-side port is None.
2. Configure the board service type for the boards at sites A and B respectively. For details,
see 14.3 Configuring the Service Type.
Configuration example at site A:
1 3
a. Choose Service > WDM Trail > Create WDM Trail from the main menu.
NOTE
The timeslot value ranges from 1 to 80. Set it based on the used bandwidth.
c. Set the source and sink.
i. In the physical topology on the right, double-click the source NE and set the
source port.
ii. Click Working Mode Settings, and set the working mode to ODUflex non-
convergence mode(Any->ODUflex).
iii. Set the sink port using the same method. After the setting is completed, the
interface shown in the following figure is displayed.
1
3
NOTE
If service cross-connections have been configured, delete the service cross-connections of the LDC
board first, and then verify that the service type of the client-side port is None. The line-side rate mode
can be changed only when the service type of the client-side port is None.
2. Create the first channel of 100GE services in E2E mode.
a. Choose Service > WDM Trail > Create WDM Trail from the main menu.
ii. Click Working Mode Settings, and set the working mode to ODUflex non-
convergence mode(Any->ODUflex).
iii. Set the sink port using the same method. After the setting is completed, the
interface shown in the following figure is displayed.
Result
To view the created trail, choose Service > WDM Trail > Manage WDM Trail from the
main menu. In the Manage WDM Trail window that is displayed, set the criteria to search
for the new trail.
This topic describes how to configure the SDH services on the U2000 by providing an
example.
Context
NOTICE
l Two AUX boards are required for the OptiX OSN 8800 T16 equipmemt configured with
SDH services.
l Disable the warm backup function when configuring SDH services.
l When MSP and SNCP are coupled, set the hold-off time to ensure that MSP switching
happens before SNCP switching. After SDH services have been configured, forbid the
start and stop of the MSP.
single ring network. You need configure a bidirectional path service on the tangent node
where the service enters the sink ring network from the source ring network.
11.15 Configuring the MSP Intersecting Ring Services
The service configuration of the MSP intersecting ring is complicated, but the inter-ring
service has low capacity and perfect protection mechanism. Both the MSP intersecting ring
and MSP tangent ring can protect the service when one fiber is cut in the local MSP ring. But
only the MSP intersecting ring can protect the service when one intersecting node is faulty.
Therefore, the MSP intersecting ring is applicable to the scenario where the service on the
single intersecting node must be protected.
11.16 Configuring the SNCP Tangent Ring Services
With respect to the physical topology, the SNCP tangent ring is similar to the MSP tangent
ring. It can protect the service in two SNCP rings when one fiber is cut in one single SNCP
ring. For service configuration of the SNCP tangent ring, you should focus on the tangent
node. Each bidirectional service that passes by the tangent node must be configured with four
pairs of protection groups.
11.17 Configuring the SNCP Intersecting Ring Services
When compared to the SNCP tangent ring, the SNCP intersecting ring has the complicated
service configuration method, but has perfect protection mechanism. Both the SNCP
intersecting ring and SNCP tangent ring can protect the service when one fiber is cut in the
local SNCP ring. But only the SNCP intersecting ring can protect the service when one
intersecting node is faulty. Therefore, the SNCP intersecting ring is applicable to the scenario
where the service on the single intersecting node must be protected.
11.18 Configuring the Services on Two Tangent SNCP and MSP Rings
The topology of two tangent SNCP and MSP rings is similar to the topology of two tangent
MSP rings and the topology of two tangent SNCP rings. This topic focuses on the
configuration of the SDH services on the tangent NE.
11.19 Configuring the Services on Two Intersecting SNCP and MSP Rings
The topology of two intersecting SNCP and MSP rings is similar to the topology of two
intersecting MSP rings and the topology of two intersecting SNCP rings. This topic focuses
on the configuration of the SDH services on the intersecting NEs.
11.20 Configuration Task Collection
This section describes basic operations involved in SDH service configuration, such as
configuring SDH cross-connections, configuring the protection subnet, configuring path
overhead for SDH services and so on.
Unidirectional Service
The unidirectional service indicates the service that is received and transmitted through
different routing. A unidirectional service created between NE A and NE B can only be
transmitted from NE A (source) to NE B (sink) or only be transmitted from NE B (sink) to
NE A (source).
Bidirectional Service
The bidirectional service indicates the service that is received and transmitted through the
same routing. For a bidirectional service created between NE A and NE B, the service can be
transmitted and received from NE A to NE B or from NE B to NE A.
MSP
The multiplex section protection (MSP) provides a function that switches the signals from the
working section to the protection section.
SNCP Principle
The sub-network connection protection (SNCP) is defined by the ITU-T Recommendations.
With 1+1 single-ended switching function, the SNCP is used for services that travel in
different subnets. The SNCP is characterized by the dual-fed and selective-receiving mode.
Tangent Rings
The tangent ring indicates an SDH network topology where two ring networks are connected
by a public NE and all inter-ring services must pass through the tangent point for
transmission. If the tangent NE is faulty, the inter-ring services are interrupted. Thus, the
tangent NE is very important for the entire network.
Intersecting Rings
The intersecting ring indicates two ring networks that are connected by two public node NEs
to implement an intra-ring connection. The inter-ring services are simultaneously transmitted
and received over two intersecting NEs. The inter-ring services are simultaneously
transmitted and received over two intersecting NEs. If one intersecting NE is faulty, services
are not affected. Thus, the protection capability of the intersecting ring topology is much
stronger than the protection capability of the tangent ring topology.
automatically created on the U2000. If the unidirectional SNCP service is configured, only the
selective receiving service can be automatically configured on the U2000.
Figure 11-1 shows a point-to-point non-protection chain. In this example, NE1 and NE2 use
SL64 boards for transmitting SDH services.
7
7
Figure 11-2 shows the signal flow and timeslot allocation. In this example, one VC-4 service
is added to or dropped from NE1 and NE2.
Figure 11-2 Signal flow and timeslot allocation of services on a non-protection chain
线路
1×VC4 板 1×VC4
7 7
VC4: VC4-1
NE1 NE2
Line board Line board Line board Line board
2-SL64 7-SL64 2-SL64 7-SL64
Prerequisites
l The physical topology of the network must be created.
l The NEs, boards, and fibers must be created on the U2000.
l The created protection subnet must be consistent with the actual network topology. For
details about how to create the protection subnet, see 11.20.2.1 Configuring a Non-
Protection Chain.
Procedure
Step 1 Configure SDH services for the source NE (NE1).
1. Select NE1 from the NE Explorer, and then choose Configuration > SDH Service
Configuration from the Function Tree.
2. Click Create on the lower-right pane to display the Create SDH Service dialog box. Set
the parameters that are required, and then click OK.
Parameter Value in Description
This
Example
Source Slot Shelf0(subr In this example, the SL64 board in slot 2 of NE1 is
ack)-2- used as the source board. Therefore, set this
SL64-1(SD parameter to 2-SL64-1(SDH-1).
H-1)
Sink Slot Shelf0(subr In this example, the SL64 board in slot 7 of NE1 is
ack)-7- used as the sink line board. Therefore, set this
SL64-1(SD parameter to 7-SL64-1(SDH-1).
H-1)
Activate Yes -
Immediately
Step 2 Configure SDH services for the sink NE (NE2) by referring to Step 1.
Source Slot Shelf0(subra In this example, the SL64 board in slot 2 of NE1 is used
ck)-2- as the source board. Therefore, set this parameter to 2-
SL64-1(SDH SL64-1(SDH-1).
-1)
Source Timeslot 1 In this example, one VC-4 is required between NE1 and
Range(e.g.1,3-6) NE2, and the service source uses the first VC-4.
Therefore, set this parameter to 1.
Sink Slot Shelf0(subra In this example, the SL64 board in slot 7 of NE1 is used
ck)-7- as the sink line board. Therefore, set this parameter to
SL64-1(SDH 7-SL64-1(SDH-1).
-1)
Sink Timeslot 1 In this example, one VC-4 is required between NE1 and
Range(e.g.1,3-6) NE2, and the service sink uses the first VC-4.
Therefore, set this parameter to 1.
Activate Yes -
Immediately
Step 3 Verify the service configurations by referring to 11.20.1.3 Verifying the Service
Configuration.
----End
Related Tasks
If the services are configured incorrectly, delete them by following instructions in 11.20.4.2
Deleting SDH Services.
6 6
Figure 11-4 Signal flow and timeslot allocation of services on a non-protection chain
线路
1×STM-64 板 1×STM-64
6 6
VC4-64C-51(V_SDH-1)
NE1 NE2
Line board Universal line board Line board Universal line board
2-SL64 6-HSNS4 2-SL64 6-HSNS4
Prerequisites
l The physical topology of the network must be created.
Procedure
Step 1 Configure virtual port mapping for the NE1-NE2 chain subnet with reference to Table 11-1.
For details about the operation, see 11.20.6 Configuring Virtual Ports and Mapping in
End-to-End Mode .
Table 11-1 Service planning: virtual port mapping of a universal line board
Parameter Value in Description
This
Example
Carried Service ODU4 In this example, the HSNS4 board converts the received
service signals into one OTU4 signal for transmission,
and the corresponding service level is ODU4.
Segment NE1-NE2 In this example, the HSNS4 board in slot 6 of NE1 and
the HSNS4 board in slot 6 of NE2 are used as the
source and sink universal line boards.
Physical Link Shelf0(subra In this example, SDH virtual port 51(V_SDH-1) is used
Information ck)-6-54HS as the STM-64 service transmission port.
NS4-51(V_S
DH_1)-
Shelf0(subra
ck)-6-54HS
NS4-51(V_S
DH_1)
1. Choose Service > SDH Trail > Create SDH Trail from the main menu.
2. Set SDH trail parameters with reference to Table 11-3.
3. After confirming service-layer route information, complete the service creation.
Source Slot NE1- In this example, the SL64 board in slot 2 of NE1 is used
Shelf0(subra as the source board.
ck)-2-
SL64-1(SDH
-1)
Sink Slot NE2- In this example, the SL64 board in slot 2 of NE2 is used
Shelf0(subra as the sink board.
ck)-2-
SL64-1(SDH
-1)
Step 4 Verify that the services are correctly configured with reference to 11.20.1.3 Verifying the
Service Configuration.
----End
Related Tasks
If the services are configured incorrectly, delete them by following instructions in 11.20.4.2
Deleting SDH Services.
8
NE1 12
12 8
Two-fiber bidirectional
NE2 NE4
non-protection ring
8
12
Line board 8-SL64
Line board 12-SL64 NE3
12 8
Figure 11-6 Signal flow and timeslot allocation of the services on the non-protection ring
NE1:
1×VC4
Line board Line board
2-SL64 8-SL64
VC4:VC4-1
8
NE2: NE1
Line board Line board
8-SL64 12-SL64 12
VC4:VC4-1
NE4 线路板
Pass-through service NE2 Non-protection ring
12 NE3
VC4:VC4-1
NE3:
Traffic direction
Prerequisites
l The physical topology of the network must be created.
l The NEs, boards, and fibers must be created on the U2000.
l The created protection subnet must be consistent with the actual network topology. For
details about how to create the protection subnet, see 11.20.2.2 Configuring a Non-
Protection Ring.
Procedure
Step 1 Configure SDH services for the source NE (NE1).
1. Select NE1 from the NE Explorer, and then choose Configuration > SDH Service
Configuration from the Function Tree.
2. Click Create on the lower-right pane to display the Create SDH Service dialog box. Set
the parameters that are required, and then click OK.
Source Slot Shelf0(subra In this example, the SL64 board in slot 2 of NE1 is
ck)-2- used as the source board. Therefore, set this parameter
SL64-1(SD to 2-SL64-1(SDH-1).
H-1)
Sink Slot Shelf0(subra In this example, the SL64 board in slot 8 of NE1 is
ck)-8- used as the sink line board. Therefore, set this
SL64-1(SD parameter to 8-SL64-1(SDH-1).
H-1)
Activate Yes -
Immediately
Step 2 Configure SDH services for the sink NE (NE3) by referring to Step 1.
Parameter Value in Description
This
Example
Source Slot Shelf0(subra In this example, the SL64 board in slot 2 of NE3 is used
ck)-2- as the source board. Therefore, set this parameter to 2-
SL64-1(SDH SL64-1(SDH-1).
-1)
Sink Slot Shelf0(subra In this example, the SL64 board in slot 12 of NE3 is used
ck)-12- as the sink line board. Therefore, set this parameter to 12-
SL64-1(SDH SL64-1(SDH-1).
-1)
Sink Timeslot 1 In this example, one VC-4 is required between NE1 and
Range(e.g. NE3, and the service sink uses the first VC-4. Therefore,
1,3-6) set this parameter to 1.
Activate Yes -
Immediately
Source Slot Shelf0(subra In this example, the SL64 board in slot 12 of NE2 is
ck)-12- used as the source line board. Therefore, set this
SL64-1(SD parameter to 12-SL64-1(SDH-1).
H-1)
Sink Slot Shelf0(subra In this example, the SL64 board in slot 8 of NE2 is
ck)-8- used as the sink line board. Therefore, set this
SL64-1(SD parameter to 8-SL64-1(SDH-1).
H-1)
Activate Yes -
Immediately
Step 4 Verify the service configurations by referring to 11.20.1.3 Verifying the Service
Configuration.
----End
Related Tasks
If the services are configured incorrectly, delete them by following instructions in 11.20.4.2
Deleting SDH Services.
8 8
NE2 NE1
Line board 2-SL64 Line board 2-SL64
Line board 8-SL64 Line board 8-SL64
Line board 12-SL64 Line board 12-SL64
As shown in Figure 11-8, the signal flow and timeslot allocation are as follows:
l Traffic direction from NE1 to NE2: NE1→NE2
Services are added to the source NE (NE1) and are transmitted from the working path
and protection path at the same time. Then, the services are dropped from the sink NE
(NE2), which selects the services from the working path.
l Traffic direction from NE2 to NE1: NE2→NE1
Services are added to the source NE (NE2) and are transmitted on the working path and
protection path at the same time. Then, the services are dropped from the sink NE (NE1),
which selects the services from the working path.
l Services between NE1 and NE2 use the first VC-4 (VC4:VC4-1) on the SDH link
between NE1 and NE2. The service capacity is one VC-4.
When the working path from NE1 to NE2 becomes faulty, in the case of single-ended
switching, the signal flow is as follows:
l Traffic direction from NE1 to NE2: NE1→NE2
Services are added to the source NE (NE1) and are transmitted on the working path and
protection path at the same time. Then, the services are dropped from the sink NE (NE2),
which selects the services from the protection path.
l The services from NE2 to NE1 are not affected, and the traffic direction is NE2→NE1.
Services are added to the source NE (NE2) and are transmitted on the working path and
protection path at the same time. Then, the services are dropped from the sink NE (NE1),
which selects the services from the working path.
When the working path from NE1 to NE2 becomes faulty, in the case of dual-ended
switching, the traffic flow is as follows:
l Traffic direction from NE1 to NE2: NE1→NE2
Services are added to the source NE (NE1) and are transmitted on the working path and
protection path at the same time. Then, the services are dropped from the sink NE (NE2),
which selects the services from the protection path.
l Traffic direction from NE2 to NE1: NE2→NE1
Services are added from the source NE (NE2) and are transmitted on the working path
and protection path at the same time. Then, the services are dropped from the sink NE
(NE1), which selects the services from the protection path.
Figure 11-8 Signal flow and timeslot allocation of the 1+1 linear MSP service
12 12
VC4:VC4-1 VC4:VC4-1
1xVC4 1xVC4
8 8
NE2: NE1:
Line Line Line Line Line Line
board board board board board board
2-SL64 8-SL64 12-SL64 2-SL64 8-SL64 12-SL64
Traffic direction of
the working path
Traffic direction of
the protection path
Prerequisites
l The physical topology of the network must be created.
l The NEs, boards, and fibers must be created on the U2000.
l The created protection subnet must be consistent with the actual network topology. For
details about how to create the protection subnet, see 11.20.2.4 Creating a Linear MS
Protection Subnet.
Procedure
Step 1 Configure SDH services on the source NE (NE1).
1. Select NE1 from the NE Explorer, and then choose Configuration > SDH Service
Configuration from the Function Tree.
2. Click Create on the lower-right pane to display the Create SDH Service dialog box. Set
the parameters that are required, and then click OK.
Source Slot Shelf0(subra In this example, the SL64 board in slot 2 of NE1 is
ck)-2- used as the source board of bidirectional services from
SL64-1(SD NE1 to NE2. Therefore, set this parameter to 2-
H-1) SL64-1(SDH-1).
Sink Slot Shelf0(subra In this example, the SL64 board in slot 12 of NE1 is
ck)-12- used as the sink line board. Therefore, set this
SL64-1(SD parameter to 12-SL64-1(SDH-1).
H-1)
Activate Yes -
Immediately
Click , and select NE2 from the displayed NE Navigator. Click OK.
Source Slot Shelf0(subra In this example, the SL64 board in slot 12 of NE2 is used
ck)-12- as the source line board. Therefore, set this parameter to
SL64-1(SDH 12-SL64-1(SDH-1).
-1)
Sink Slot Shelf0(subra In this example, the SL64 board in slot 2 of NE2 is used
ck)-2- as the sink board of bidirectional services from NE1 to
SL64-1(SDH NE2. Therefore, set this parameter to 2-SL64-1(SDH-1).
-1)
Sink Timeslot 1 In this example, one VC-4 is required between NE1 and
Range(e.g. NE2, and the service sink uses the first VC-4. Therefore,
1,3-6) set this parameter to 1.
Activate Yes -
Immediately
Step 3 Verify the service configurations by referring to 11.20.1.3 Verifying the Service
Configuration.
----End
Related Tasks
If the services are configured incorrectly, delete them by following instructions in 11.20.4.2
Deleting SDH Services.
8 8
NE2 NE1
Line board 2-SL64 Line board 2-SL64
Line board 8-SL64 Line board 8-SL64
Line board 12-SL64 Line board 12-SL64
The difference between the 1:1 linear MSP service and the 1+1 linear MSP service is as
follows:
l In the case of the 1+1 linear MSP service, services are transmitted on the working path
and protection path at the same time. The sink NE selects the services from the working
path.
l In the case of the 1:1 linear MSP service, services are transmitted only on the working
path. Services are switched to the protection path for transmission only when the
working path becomes faulty.
Figure 11-10 Signal flow and timeslot allocation of the 1:1 linear MSP service
12 12
VC4:VC4-1 VC4:VC4-1
1xVC4 1xVC4
8 8
NE2: NE1:
Line Line Line Line Line Line
board board board board board board
2-SL64 8-SL64 12-SL64 2-SL64 8-SL64 12-SL64
Traffic direction of
the working path
Traffic direction of
the protection path
Prerequisites
l The physical topology of the network must be created.
l The NEs, boards, and fibers must be created on the U2000.
l The created protection subnet must be consistent with the actual network topology. For
details about how to create the protection subnet, see 11.20.2.4 Creating a Linear MS
Protection Subnet.
Procedure
Step 1 At NE1, configure SDH services on the source NE.
1. Select NE1 from the NE Explorer, and then choose Configuration > SDH Service
Configuration from the Function Tree.
2. Click Create on the lower-right pane to display the Create SDH Service dialog box. Set
the parameters that are required, and then click OK.
Source Slot Shelf0(subra In this example, the SL64 board in slot 2 of NE1 is
ck)-2- used as the source line board. Therefore, set this
SL64-1(SD parameter to 2-SL64-1(SDH-1).
H-1)
Sink Slot Shelf0(subra In this example, the SL64 board in slot 12 of NE1 is
ck)-12- used as the sink line board. Therefore, set this
SL64-1(SD parameter to 12-SL64-1(SDH-1).
H-1)
Activate Yes -
Immediately
Click , and select NE2 from the displayed NE Navigator. Click OK.
Source Slot Shelf0(subra In this example, the SL64 board in slot 12 of NE2 is used
ck)-12- as the source line board. Therefore, set this parameter to
SL64-1(SDH 12-SL64-1(SDH-1).
-1)
Sink Slot Shelf0(subra In this example, the SL64 board in slot 2 of NE2 is used
ck)-2- as the sink line board. Therefore, set this parameter to 2-
SL64-1(SDH SL64-1(SDH-1).
-1)
Sink Timeslot 1 In this example, one VC-4 is required, and the service
Range(e.g. sink uses the first VC-4. Therefore, set this parameter to
1,3-6) 1.
Activate Yes -
Immediately
Step 3 Verify the service configurations by referring to 11.20.1.3 Verifying the Service
Configuration.
----End
Related Tasks
If the services are configured incorrectly, delete them by following instructions in 11.20.4.2
Deleting SDH Services.
8 12
NE1
12 8
MSP Ring
NE2 NE4
8 12
8 12
NE1
NE2:
Line board Line board
8-SL64 12-SL64 12
VC4:VC4-1 线路
Service pass-through NE2 MSP Ring NE4 板
12 NE3 8
NE3:
Line board Line board
service route
Prerequisites
l The physical network topology must be created.
l NEs, boards, and fibers must be created on the U2000.
l A protection subnet must be created and be consistent with the actual topology. For
details about how to create a protection subnet, see 11.20.2.3 Creating an MS Ring
Protection Subnet.
Procedure
Step 1 Configure the SDH service on NE1 (source NE).
1. Select NE1 in the NE Explorer. Choose Configuration > SDH Service Configuration
from the Function Tree.
2. Click Create in the lower right portion of the window to set required parameters in the
Create SDH Service dialog box that is displayed. Click OK.
Source Slot Shelf0(subra In this example, the SL64 board in slot 2 of NE1 is
ck)-2- used as the source board. Therefore, set this parameter
SL64-1(SD to 2-SL64-1(SDH-1).
H-1)
Sink Slot Shelf0(subra In this example, the SL64 board in slot 8 of NE1 is
ck)-8- used as the sink board. Therefore, set this parameter to
SL64-1(SD 8-SL64-1(SDH-1).
H-1)
Activate Yes -
Immediately
Step 2 Configure SDH services for the sink NE (NE3) by referring to Step 1.
Parameter Value in Value Description
This
Example
Source Slot Shelf0(subra In this example, the SL64 board in slot 12 of NE3 is used
ck)-12- as the source board.
SL64-1(SDH
-1)
Sink Slot Shelf0(subra In this example, the SL64 board in slot 2 of NE3 is used
ck)-2- as the sink board. Therefore, set this parameter to 2-
SL64-1(SDH SL64-1(SDH-1).
-1)
Sink Timeslot 1 In this example, one VC-4 is required, and the service
Range(e.g. sink uses the first VC-4. Therefore, set this parameter to
1,3-6) 1.
Activate Yes -
Immediately
Source Slot Shelf0(subra In this example, the SL64 board in slot 12 of NE2 is
ck)-12- used as the source board.
SL64-1(SD
H-1)
Sink Slot Shelf0(subra In this example, the SL64 board in slot 8 of NE2 is
ck)-8- used as the sink board. Therefore, set this parameter to
SL64-1(SD 8-SL64-1(SDH-1).
H-1)
Activate Yes -
Immediately
Step 4 Verify the service configurations by referring to 11.20.1.3 Verifying the Service
Configuration.
----End
Related Tasks
If the services are configured incorrectly, delete them by following instructions in 11.20.4.2
Deleting SDH Services.
7 13
NE1
12 8
13 7
Four-fiber
NE2 bidirectional MSP ring NE4
8 7 13
12
to the protection path for transmission. Then, the services pass through NE3 and NE4
and finally are dropped from NE1.
The comparison between the four-fiber bidirectional MSP service and the two-fiber
bidirectional MSP service is as follows:
l The four-fiber bidirectional MSP service and the two-fiber bidirectional MSP service use
the uniform route.
l In the case of the four-fiber bidirectional MSP service, different optical fibers are used
for the working timeslot and protection timeslot. That is, one optical fiber is used for
carrying the working service, and the other optical fiber is used for protection. In the
case of the two-fiber bidirectional MSP service, the same optical fiber is used for the
working timeslot and protection timeslot. That is, a certain capacity of the optical fiber is
used for carrying the working service, and a certain capacity of the optical fiber is used
for protection.
Figure 11-14 Signal flow and timeslot allocation of the four-fiber bidirectional MSP service
1xVC4 NE1:
Line board Line board
2-SL64 8-SL64
VC4:VC4-1 8
NE2:
NE1
Line board Line board
8-SL64 12-SL64 12
VC4:VC4-1 线路
Services pass NE2 Four-fiber NE4 板
through bidirectional MSP ring
8
NE3
Traffic direction of the
forward working path
Traffic direction of the
backward working path
12
Traffic direction of the
forward protection path VC4:VC4-1 NE3:
Traffic direction of the Line board Line board
backward protection path 1xVC4
2-SL64 12-SL64
Prerequisites
l The physical topology of the network must be created.
l NEs, boards, and fibers must be created on the U2000.
l A protection subnet must be created and be consistent with the actual topology. For
details about how to create a protection subnet, see 11.20.2.3 Creating an MS Ring
Protection Subnet.
Procedure
Step 1 At NE1, configure SDH services on the source NE.
1. Select NE1 from the NE Explorer, and then choose Configuration > SDH Service
Configuration from the Function Tree.
2. Click Create on the lower-right pane to display the Create SDH Service dialog box. Set
the parameters that are required, and then click OK.
Parameter Value in Description
This
Example
Source Slot Shelf0(subra In this example, the SL64 board in slot 2 of NE1 is
ck)-2- used as the source line board. Therefore, set this
SL64-1(SD parameter to 2-SL64-1(SDH-1).
H-1)
Sink Slot Shelf0(subra In this example, the SL64 board in slot 8 of NE1 is
ck)-8- used as the sink line board. Therefore, set this
SL64-1(SD parameter to 8-SL64-1(SDH-1).
H-1)
Activate Yes -
Immediately
Click , and select NE2 from the displayed NE Navigator. Click OK.
Source Slot Shelf0(subra In this example, the SL64 board in slot 12 of NE2 is used
ck)-12- as the source line board. Therefore, set this parameter to
SL64-1(SDH 12-SL64-1(SDH-1).
-1)
Sink Slot Shelf0(subra In this example, the SL64 board in slot 8 of NE2 is used
ck)-8- as the sink line board. Therefore, set this parameter to 8-
SL64-1(SDH SL64-1(SDH-1).
-1)
Sink Timeslot 1 In this example, one VC-4 is required, and the service
Range(e.g. sink uses the first VC-4. Therefore, set this parameter to
1,3-6) 1.
Activate Yes -
Immediately
Click , and select NE3 from the displayed NE Navigator. Click OK.
Source Slot Shelf0(subra In this example, the SL64 board in slot 12 of NE3 is used
ck)-12- as the source line board. Therefore, set this parameter to
SL64-1(SDH 12-SL64-1(SDH-1).
-1)
Sink Slot Shelf0(subra In this example, the SL64 board in slot 2 of NE3 is used
ck)-2- as the sink line board. Therefore, set this parameter to 2-
SL64-1(SDH SL64-1(SDH-1).
-1)
Sink Timeslot 1 In this example, one VC-4 is required and the service sink
Range(e.g. uses the first VC-4. Therefore, set this parameter to 1.
1,3-6)
Activate Yes -
Immediately
Step 4 Verify the service configurations by referring to 11.20.1.3 Verifying the Service
Configuration.
----End
Related Tasks
If the services are configured incorrectly, delete them by following instructions in 11.20.4.2
Deleting SDH Services.
17 18
NE1
1 17
NE2 Transoceanic MSP ring NE4
17 1
Line board 1-SL64 Line board 1-SL64
NE3
Line board 17-SL64 18 17 Line board 17-SL64
17 18
NE2: NE1
Line board Line board
1-SL64 17-SL64 1
VC4:VC4-1 线路
Services pass through NE2 Transoceanic MSP ring NE4 板
17
18 NE3 17
NE3:
Line board Line board Line board
1-SL64 17-SL64 18-SL64
1×VC4
Traffic direction
If a fault occurs on the section between NE1 and NE2, protection switching occurs on the
original source NE (NE1) and sink NE (NE3). This prevents the path loopback and shortens
the service transmission distance. Figure 11-17 shows the signal flow and timeslot allocation
after the switching.
Figure 11-17 Signal flow and timeslot allocation after the switching
NE1:
1×VC4
Line board Line board Line board
1-SL64 17-SL64 18-SL64
VC4:VC4-1
17 18
NE1
VC4:VC4-1
Service 1
NE2: pass-through
Line board Line board
NE2 Transoceanic MSP ring NE4
1-SL64 17-SL64
17
18 NE3 17
NE3:
Line board Line board Line board
1-SL64 17-SL64 18-SL64
1×VC4 Traffic direction
NOTE
When the transoceanic MS is in the switched state, the extra services on the protection paths that are not
preempted by the working services during the switching are restored one minute after the switching is
performed.
Prerequisites
l The physical topology of the network must be created.
l NEs, boards, and fibers must be created on the U2000.
l A protection subnet must be created and be consistent with the actual topology. For
details about how to create a protection subnet, see 11.20.2.3 Creating an MS Ring
Protection Subnet.
Precautions
All nodes on a transoceanic MSP ring must use the transoceanic protocol. Otherwise,
protection switching fails to work properly.
Transoceanic MSs do not support lower order services.
Procedure
Step 1 Configure SDH services for the source NE (NE1).
1. In the NE Explorer, select NE1 and then choose Configuration > SDH Service
Configuration from the Function Tree.
2. Click Create in the lower-right pane and set required parameters in the Create SDH
Service dialog box that is displayed. Then, click OK.
Parameter Value in Description
This
Example
Source Slot Shelf0(subra In this example, the SL64 board in slot 1 of NE1 is
ck)-1- used as the source board. Therefore, set this parameter
SL64-1(SD to 1-SL64-1(SDH-1).
H-1)
Sink Slot Shelf0(subra In this example, the SL64 board in slot 17 of NE1 is
ck)-17- used as the sink board. Therefore, set this parameter to
SL64-1(SD 17-SL64-1(SDH-1).
H-1)
Activate Yes -
Immediately
Step 2 Configure SDH services for the sink NE (NE3) by referring to Step 1.
Source Slot Shelf0(subra In this example, the SL64 board in slot 18 of NE3 is used
ck)-18- as the source board. Therefore, set this parameter to 18-
SL64-1(SDH SL64-1(SDH-1).
-1)
Sink Slot Shelf0(subra In this example, the SL64 board in slot 1 of NE3 is used
ck)-1- as the sink board. Therefore, set this parameter to 1-
SL64-1(SDH SL64-1(SDH-1).
-1)
Sink Timeslot 1 In this example, one VC-4 is required, and the service
Range(e.g. sink uses the first VC-4. Therefore, set this parameter to
1,3-6) 1.
Activate Yes -
Immediately
Source Slot Shelf0(subra In this example, the SL64 board in slot 1 of NE2 is
ck)-1- used as the source board. Therefore, set this parameter
SL64-1(SD to 1-SL64-1(SDH-1).
H-1)
Sink Slot Shelf0(subra In this example, the SL64 board in slot 17 of NE2 is
ck)-17- used as the sink board. Therefore, set this parameter to
SL64-1(SD 17-SL64-1(SDH-1).
H-1)
Activate Yes -
Immediately
Step 4 Verify the service configurations by referring to 11.20.1.3 Verifying the Service
Configuration.
----End
Related Tasks
If the services are configured incorrectly, delete them by following instructions in 11.20.4.2
Deleting SDH Services.
Figure 11-18 shows an SNCP ring consisting of four NEs. All NEs on the ring use SL64
boards for transmitting SDH services.
8 12
NE1
12 8
NE2 SNCP Ring NE4
8 12
8 12
NE1 NE2 和 NE4:
SDH service Working board Working board
VC4 8-SL64 12-SL64
12 8
VC4:VC4-1
SNCP 线路 VC4:VC4-1
Service pass-through NE2 Ring NE4 板 Service pass-through
8 12
12 NE3 8
VC4:VC4-1 VC4:VC4-1
NE3:
SNCP protection group Working board Protection board Sink board
1xVC4 Group1 12-SL64 8-SL64 2-SL64
Prerequisites
l The physical network topology must be created.
l NEs, boards, and fibers must be created on the U2000.
Procedure
Step 1 Configure the SDH service on NE1 (source NE).
1. Select NE1 in the NE Explorer. Choose Configuration > SDH Service Configuration
from the Function Tree.
2. Click Create SNCP Service in the lower right portion of the window to set required
parameters in the Create SNCP Service dialog box that is displayed. Click OK.
WTR Time(s) 600 When the time after the original working path is
restored to normal reaches the preset WTR time,
revertive switching occurs. This parameter is
valid only when Revertive Mode is set to
Revertive.
Wor Source Slot Shelf0(sub In this example, the SL64 board in slot 8 of NE1
king rack)-8- is used as the source board of the working
Ser SL64-1(S service. Therefore, set this parameter to 8-
vice DH-1) SL64-1(SDH-1).
Sink Slot Shelf0(sub In this example, the SL64 board in slot 2 of NE1
rack)-2- is used as the sink board. Therefore, set this
SL64-1(S parameter to 2-SL64-1(SDH-1).
DH-1)
Prot Source Slot Shelf0(sub In this example, the SL64 board in slot 12 of
ecti rack)-12- NE1 is used as the source board of the protection
on SL64-1(S service. Therefore, set this parameter to 12-
Ser DH-1) SL64-1(SDH-1).
vice
Source 1 In this example, one VC-4 is required, and the
Timesolt service source uses the first VC-4. Therefore, set
Range(e.g. this parameter to 1.
1,3-6)
Activate Yes -
Immediately
Step 2 Configure the SDH service on the sink NE (NE3). See Step 1 to configure the SDH service
on NE3.
Parameter Value in Value Description
This
Example
WTR Time(s) 600 When the time after the original working path is
restored to normal reaches the preset WTR time,
revertive switching occurs. This parameter is valid
only when Revertive Mode is set to Revertive.
Wor Source Slot Shelf0(subr In this example, the SL64 board in slot 12 of NE3 is
king ack)-12- used as the source board of the working service.
Serv SL64-1(SD Therefore, set this parameter to 12-
ice H-1) SL64-1(SDH-1).
Sink Slot Shelf0(subr In this example, the SL64 board in slot 2 of NE3 is
ack)-2- used as the sink board. Therefore, set this parameter
SL64-1(SD to 2-SL64-1(SDH-1).
H-1)
Prot Source Slot Shelf0(subr In this example, the SL64 board in slot 8 of NE3 is
ectio ack)-8- used as the source board of the protection service.
n SL64-1(SD Therefore, set this parameter to 8-SL64-1(SDH-1).
Serv H-1)
ice
Source 1 In this example, one VC-4 is required, and the
Timesolt service source uses the first VC-4. Therefore, set
Range(e.g. this parameter to 1.
1,3-6)
Source Slot Shelf0(subra In this example, the SL64 board in slot 12 of NE2 is
ck)-12- used as the source board. Therefore, set this parameter
SL64-1(SD to 12-SL64-1(SDH-1).
H-1)
Sink Slot Shelf0(subra In this example, the SL64 board in slot 8 of NE2 is
ck)-8- used as the sink board. Therefore, set this parameter to
SL64-1(SD 8-SL64-1(SDH-1).
H-1)
Activate Yes -
Immediately
Step 4 Configure the pass-through service on NE4. See Step 3 to configure the SDH service on NE4.
The configuration method and parameter setting are the same as those of NE2.
Step 5 Verify the service configurations by referring to 11.20.1.3 Verifying the Service
Configuration.
----End
Related Tasks
If the services are configured incorrectly, delete them by following instructions in 11.20.4.2
Deleting SDH Services.
4 6
NE1
6 4
NE2 SNCP Ring NE4
4 6
Universal Line Board 4-HSNS4 Universal Line Board 4-HSNS4
Universal Line Board 6-HSNS4 NE3 Universal Line Board 6-HSNS4
6 4
4 6
NE1 NE2 and NE4:
SDH Service Source board Sink board
VC4-64C 4-HSNS4 6-HSNS4
6 4
VC4-64C-51(V_SDH-1)
线路 VC4-64C-51(V_SDH-1)
Service pass-through SNCP Ring
NE2 NE4 板 Service pass-through
4 6
6 NE3 4
VC4-64C-51(V_SDH-1) VC4-64C-51(V_SDH-1)
NE3:
SNCP Working Protection Sink
1xSTM-64 protection group board board board
Group1 6-HSNS4 4-HSNS4 2-SL64
Prerequisites
l The physical network topology must be created.
l NEs, boards, and fibers must be created on the U2000.
l OCh trails are searched out.
Procedure
Step 1 Configure virtual port mappings for the NE1-NE2, NE2-NE3, NE3-NE4, and NE4-NE1 ring
subnet with reference to Table 11-4. For details about the operation, see 11.20.6 Configuring
Virtual Ports and Mapping in End-to-End Mode .
Table 11-4 Service planning: virtual port mapping of a universal line board
Parameter Value in Description
This
Example
Carried Service ODU4 In this example, the HSNS4 board converts the received
service signals into one OTU4 signal for transmission,
and the corresponding service level is ODU4.
Segment NEx-NEy In this example, the HSNS4 board in slot 4 of NEx and
the HSNS4 board in slot 6 of NEy are used as the
source and sink universal line boards.
Step 2 Search WDM trails. For details, see 9.6 Searching for WDM Trails.
Source Slot NE1- In this example, the SL64 board in slot 2 of NE1 is
Shelf0(subr used as the source board.
ack)-2-
SL64-1(SD
H-1)
Sink Slot NE3- In this example, the SL64 board in slot 2 of NE3 is
Shelf0(subr used as the sink board.
ack)-2-
SL64-1(SD
H-1)
Step 4 Verify that the services are correctly configured with reference to 11.20.1.3 Verifying the
Service Configuration.
----End
Related Tasks
If the services are configured incorrectly, delete them by following instructions in 11.20.4.2
Deleting SDH Services.
Figure 11-22 shows an SNCP ring with a non-protection chain. This ring consists of five NEs
and all NEs on the ring use SL64 boards for transmitting SDH services.
NE5
8 13 Line board 2-SL64
NE1
Line board 12-SL64
13 8 Non-protection NE5
SNCP ring chain
NE2 NE4
8 13
12 12
Line board 8-SL64 NE3 NE4
Line board 13-SL64 13 8 Line board 8-SL64
Line board 12-SL64
Line board 13-SL64
Figure 11-23 shows the signal flow and timeslot allocation. One VC-4 service is transmitted
between NE3 and NE5.
In the case of the services on the SNCP ring, the traffic direction in this example is configured
as follows:
In the actual configuration, you can plan other proper working paths and protection paths
according to the requirement.
Figure 11-23 Signal flow and timeslot allocation of the services on the SNCP ring with a non-
protection chain
NE1: VC4:VC4-1 Services pass through
SDH Service Service
service source sink
VC4 13-SL64 8-SL64
NE4:
SNCP Working Protection Service
13 protection service service
NE2: VC4:VC4-1 Services pass through 8 group sink
NE1 source source
SDH Service Service Protection 13-SL64 8-SL64 12-SL64
service source sink group 1
VC4 13-SL64 8-SL64 13 8 VC4:VC4-1
线路
NE2 SNCP ring NE4 板 1×VC4
12 12
Non-protection
8 13 NE5
chain
VC4:VC4-1
SDH Service Service
service source sink
13 NE3 8
VC4 12-SL64 2-SL64
VC4:VC4-1 VC4:VC4-1
NE3: Traffic direction of the
working service
SNCP Working Protection Traffic direction of the
protection Service
service service protection service
group source source sink
1×VC4 Traffic direction of services on
Protection 13-SL64 8-SL64 2-SL64 the the non-protection chain
group 1
Prerequisites
l The physical topology of the network must be created.
l NEs, boards, and fibers must be created on the U2000.
l A protection subnet must be created and be consistent with the actual topology. For
details about how to create a protection subnet, see 11.20.2.1 Configuring a Non-
Protection Chain.
Procedure
Step 1 Configure SDH services on the source NE (NE3).
1. Select NE3 from the NE Explorer, and then choose Configuration > SDH Service
Configuration from the Function Tree.
2. Click Create SNCP Service to display the Create SNCP Service dialog box. Set the
parameters that are required. Click OK.
WTR Time(s) 600 When the time after the original working path is
restored to normal reaches the preset WTR time,
revertive switching occurs. This parameter is
valid only when Revertive Mode is set to
Revertive.
Wor Source Slot Shelf0(sub In this example, the SL64 board in slot 13 of
king rack)-13- NE3 is used as the source board of the working
Ser SL64-1(S service. Therefore, set this parameter to 13-
vice DH-1) SL64-1(SDH-1).
Sink Slot Shelf0(sub In this example, the SL64 board in slot 2 of NE3
rack)-2- is used as the sink board of the working service.
SL64-1(S Therefore, set this parameter to 2-
DH-1) SL64-1(SDH-1).
Prot Source Slot Shelf0(sub In this example, the SL64 board in slot 8 of NE3
ecti rack)-8- is used as the source board of the protection
on SL64-1(S service. Therefore, set this parameter to 8-
Ser DH-1) SL64-1(SDH-1).
vice
Source 1 In this example, one VC-4 is required between
Timeslot NE3 and NE5, and the service source uses the
Range(e.g. first VC-4. Therefore, set this parameter to 1.
1,3-6)
Activate Yes -
Immediately
WTR Time(s) 600 When the time after the original working path is
restored to normal reaches the preset WTR time,
revertive switching occurs. This parameter is
valid only when Revertive Mode is set to
Revertive.
Wor Source Slot Shelf0(sub In this example, the SL64 board in slot 13 of
king rack)-13- NE4 is used as the source board of the working
Ser SL64-1(S service. Therefore, set this parameter to 13-
vice DH-1) SL64-1(SDH-1).
Prot Source Slot Shelf0(sub In this example, the SL64 board in slot 8 of NE4
ecti rack)-8- is used as the source board of the protection
on SL64-1(S service. Therefore, set this parameter to 8-
Ser DH-1) SL64-1(SDH-1).
vice
Source 1 In this example, one VC-4 is required between
Timeslot NE3 and NE5, and the service source uses the
Range(e.g. first VC-4. Therefore, set this parameter to 1.
1,3-6)
Activate Yes -
Immediately
Source Slot Shelf0(subra In this example, the SL64 board in slot 13 of NE2 is
ck)-13- used as the source line board. Therefore, set this
SL64-1(SD parameter to 13-SL64-1(SDH-1).
H-1)
Sink Slot Shelf0(subra In this example, the SL64 board in slot 8 of NE2 is
ck)-8- used as the sink line board. Therefore, set this
SL64-1(SD parameter to 8-SL64-1(SDH-1).
H-1)
Activate Yes -
Immediately
Step 4 Configure pass-through services on NE1. Refer to Step 3 and configure SDH services on
NE1. Use the same configuration method and set the parameters so that they can be consistent
with the set parameters of NE2.
Step 5 Configure services on the non-protection chain at NE5.
1. Select NE5 from the NE Explorer, and then choose Configuration > SDH Service
Configuration from the Function Tree.
2. Click Create to display the Create SDH Service dialog box. Set the parameters that are
required. Click OK.
Parameter Value in Description
This
Example
Source Slot Shelf0(subra In this example, the SL64 board in slot 2 of NE5 is
ck)-2- used as the source board. Therefore, set this parameter
SL64-1(SD to 2-SL64-1(SDH-1).
H-1)
Sink Slot Shelf0(subra In this example, the SL64 board in slot 12 of NE5 is
ck)-12- used as the sink line board. Therefore, set this
SL64-1(SD parameter to 12-SL64-1(SDH-1).
H-1)
Activate Yes -
Immediately
Step 6 Verify the service configurations by referring to 11.20.1.3 Verifying the Service
Configuration.
----End
Related Tasks
If the services are configured incorrectly, delete them by following instructions in 11.20.4.2
Deleting SDH Services.
Figure 11-24 Networking diagram of a two-fiber bidirectional MSP ring with a non-
protection chain
Line board 8-SL64
Line board 13-SL64
NE5
8 13 Line board 2-SL64
NE1
Line board 12-SL64
13 8 Non-protection NE5
Two-fiber bidirectional NE4 chain
NE2
MSP ring
8 13
12 12
Line board 8-SL64 NE3 NE4
Line board 13-SL64 13 8 Line board 8-SL64
Line board 12-SL64
Line board 13-SL64
NOTE
On a ring network, the long path and short path are determined by the number of intermediate NEs
instead of by the geographical distance. In Figure 11-25, if the service is transmitted from NE3 to NE4,
NE3->NE4 is the short path, and NE3->NE2->NE1->NE4 is the long path.
Figure 11-25 Signal flow and timeslot allocation of the service on the MSP ring with a non-
protection chain
8 13
NE1 NE4:
Line board Line board
13-SL64 12-SL64
13 8
VC4:VC4-1
NE3:
Line board Line board
8-SL64 2-SL64
1×VC4 Traffic direction
of the MSP ring
Traffic direction of the
non-protection chain
Prerequisites
l The physical topology of the network must be created.
l NEs, boards, and fibers must be created on the U2000.
l Protection subnets must be created and be consistent with the actual topology. For details
about how to create a protection subnet, see 11.20.2.1 Configuring a Non-Protection
Chain and 11.20.2.3 Creating an MS Ring Protection Subnet.
Procedure
Step 1 Configure SDH services on the source NE (NE3).
1. Select NE3 from the NE Explorer, and then choose Configuration > SDH Service
Configuration from the Function Tree.
2. Click Create on the lower-right pane to display the Create SDH Service dialog box. Set
the parameters that are required, and then click OK.
Source Slot Shelf0(subr In this example, the SL64 board in slot 2 of NE3 is
ack)-2- used as the source line board. Therefore, set this
SL64-1(SD parameter to 2-SL64-1(SDH-1).
H-1)
Sink Slot Shelf0(subr In this example, the SL64 board in slot 8 of NE3 is
ack)-8- used as the sink line board. Therefore, set this
SL64-1(SD parameter to 8-SL64-1(SDH-1).
H-1)
Activate Yes -
Immediately
Source Slot Shelf0(subra In this example, the SL64 board in slot 2 of NE5 is used
ck)-2- as the source line board. Therefore, set this parameter to
SL64-1(SDH 2-SL64-1(SDH-1).
-1)
Source Timeslot 1 In this example, one VC-4 is required between NE3 and
Range(e.g.1,3-6) NE5, and the service source uses the first VC-4.
Therefore, set this parameter to 1.
Sink Slot Shelf0(subra In this example, the SL64 board in slot 12 of NE5 is
ck)-12- used as the sink line board. Therefore, set this
SL64-1(SDH parameter to 12-SL64-1(SDH-1).
-1)
Sink Timeslot 1 In this example, one VC-4 is required between NE3 and
Range(e.g.1,3-6) NE5, and the service sink uses the first VC-4.
Therefore, set this parameter to 1.
Activate Yes -
Immediately
Source Slot Shelf0(subr In this example, the SL64 board in slot 13 of NE4 is
ack)-13- used as the source line board. Therefore, set this
SL64-1(SD parameter to 13-SL64-1(SDH-1).
H-1)
Sink Slot Shelf0(subr In this example, the SL64 board in slot 12 of NE4 is
ack)-12- used as the sink line board. Therefore, set this
SL64-1(SD parameter to 12-SL64-1(SDH-1).
H-1)
Activate Yes -
Immediately
Step 4 Verify the service configurations by referring to 11.20.1.3 Verifying the Service
Configuration.
----End
Related Tasks
If the services are configured incorrectly, delete them by following instructions in 11.20.4.2
Deleting SDH Services.
8 13
NE1
13 8
Line board 13 - SL64
NE2 MSP ring 1 NE4
Line board 8 - SL64
8 13
NE3 Line board 7-SL64
13 8 Line board 8-SL64
7 12 Line board 12-SL64
Line board 13-SL64
13 8
Line board 13 - SL64
NE5 MSP ring 2 NE7
Line board 8 - SL64
8 13
NE6
13 8
VC4:VC4-1 VC4:VC4-1
8 13
NE2: NE1
VC4:VC4-1
Service pass-through MSP Ring1 线路板
NE2 NE4
8 13
NE3
13 8
NE3:
Line board Line board VC4:VC4-1
13-SL64 7-SL64
7 12
13 8
VC4:VC4-1
MSP Ring2
Service pass-through NE5 NE7
NE5:
8 13
Line board Line board
8-SL64 13-SL64
13 NE6 8
VC4:VC4-1 VC4:VC4-1
NE6:
Line board Line board
2-SL64 13-SL64
service route
Prerequisites
l The physical network topology must be created.
l NEs, boards, and fibers must be created on the U2000.
l The protection subnets of the two MSP tangent rings must be created and be consistent
with the actual topology. For details about how to create the protection subnets, see
11.20.2.3 Creating an MS Ring Protection Subnet.
Procedure
Step 1 Configure the SDH service on NE1 (source NE).
1. Select NE1 in the NE Explorer. Choose Configuration > SDH Service Configuration
from the Function Tree.
2. Click Create in the lower right portion of the window to set required parameters in the
Create SDH Service dialog box that is displayed. Click OK.
Source Slot Shelf0(subra In this example, the SL64 board in slot 2 of NE1 is
ck)-2- used as the source board. Therefore, set this parameter
SL64-1(SD to 2-SL64-1(SDH-1).
H-1)
Sink Slot Shelf0(subra In this example, the SL64 board in slot 8 of NE1 is
ck)-8- used as the sink board. Therefore, set this parameter to
SL64-1(SD 8-SL64-1(SDH-1).
H-1)
Activate Yes -
Immediately
Step 2 Configure the SDH service on NE6 (sink NE) by referring to Step 1.
Parameter Value in Value Description
This
Example
Source Slot Shelf0(subra In this example, the SL64 board in slot 13 of NE6 is used
ck)-13- as the source board. Therefore, set this parameter to 13-
SL64-1(SDH SL64-1(SDH-1).
-1)
Sink Slot Shelf0(subra In this example, the SL64 board in slot 2 of NE6 is used
ck)-2- as the sink board. Therefore, set this parameter to 2-
SL64-1(SDH SL64-1(SDH-1).
-1)
Sink Timeslot 1 In this example, one VC-4 is required, and the service
Range(e.g. sink uses the first VC-4. Therefore, set this parameter to
1,3-6) 1.
Activate Yes -
Immediately
Source Slot Shelf0(subra In this example, the SL64 board in slot 13 of NE2 is
ck)-13- used as the source board. Therefore, set this parameter
SL64-1(SD to 13-SL64-1(SDH-1).
H-1)
Sink Slot Shelf0(subra In this example, the SL64 board in slot 8 of NE2 is
ck)-8- used as the sink board. Therefore, set this parameter to
SL64-1(SD 8-SL64-1(SDH-1).
H-1)
Activate Yes -
Immediately
Step 4 Configure the pass-through service on NE5. See Step 3 to configure the SDH service on NE5.
The configuration method and parameter setting are the same as those of NE2.
For the MSP tangent rings, you only need to configure a bidirectional path service on the tangent point
to ensure that services in one ring can be transmitted to the other ring. The services in two MSP rings are
respectively protected by their local rings.
1. Select NE3 in the NE Explorer. Choose Configuration > SDH Service Configuration
from the Function Tree.
2. Click Create in the lower right portion of the window to set required parameters in the
Create SDH Service dialog box that is displayed. Click OK.
Parameter Value in Value Description
This
Example
Source Slot Shelf0(subra In this example, the SL64 board in slot 13 of NE3 is
ck)-13- used as the source board. Therefore, set this parameter
SL64-1(SD to 12-SL64-1(SDH-1).
H-1)
Sink Slot Shelf0(subra In this example, the SL64 board in slot 7 of NE3 is
ck)-7- used as the sink board. Therefore, set this parameter to
SL64-1(SD 7-SL64-1(SDH-1).
H-1)
Activate Yes -
Immediately
Step 6 Verify the service configurations by referring to 11.20.1.3 Verifying the Service
Configuration.
----End
Related Tasks
If the services are configured incorrectly, delete them by following instructions in 11.20.4.2
Deleting SDH Services.
Figure 11-28 shows two MSP intersecting rings consisting of eight MSTP NEs. NE3
functions as the working intersecting NE and NE8 functions as the protection intersecting NE.
In this example, one VC-4 service is added to the ring network from NE1 and dropped from
the sink NE (NE6). All NEs on the rings use SL64 boards for transmitting SDH services.
8 13
NE1
13 8
NE2 MSP Ring1 NE4
8 13
NE3 NE8 8
8 13 Line board 7-SL64
13
Line board 8-SL64
13 8
NE5 MSP Ring2 NE7
8 13
NE6
13 8
Figure 11-29 shows the service signal flow and timeslot allocation.
l On the working node (NE3), you need to configure two SNCP protection groups.
Normally, the service flow of the selected working path is NE1←→NE2←→NE3←→
NE5←→NE6, which is consistent with the service flow on the MSP tangent ring.
– When services travel to MSP ring 2 from the MSP ring 1, SNCP protection group 1
selectively receives one service.
– When the service travels to MSP ring 1 from the MSP ring 2, SNCP protection
group 2 selectively receives the service.
NOTE
For higher-order SNCP protection groups 1 and 2, HPUNEQ must be configured as a switching
condition. Otherwise, services will be interrupted during service restoration.
l On NE3, configure pass-through services from the board in slot 13 to the board in slot 8.
On NE8, configure pass-through services from the board in slot 13 to the board in slot 7.
These pass-through services are protection sources of SNCP protection group 1 on NE3.
l On NE3, configure pass-through services from the board in slot 7 to the board in slot 12.
On NE8, configure pass-through services from the board in slot 7 to the board in slot 13.
These pass-through services are protection sources of SNCP protection group 2 on NE3.
The MSP intersecting ring and MSP tangent ring topologies implement protection for the
service when two fibers are cut in two MSP rings respectively. However, only the MSP
intersecting ring can protect the service when one intersecting node is faulty.
Figure 11-29 Signal flow and timeslot allocation of the MSP intersecting ring
NE1: VC4:VC4-1
1xVC4
Line board Line board
2-SL64 8-SL64
8 13
NE1
VC4:VC4-1
Service pass-through
13 8
NE3: VC4:VC4-1
unidirectional service service 8 13
cross-connection source sink
cross-connection1 13-SL64 8-SL64
13 NE3 NE8 8
8 13
cross-connection2 7-SL64 12-SL64
12 7
7 12
13 8
8 13
VC4:VC4-1
Service pass-through
13 NE6 8
VC4:VC4-1 NE6:
Line board Line board
2-SL64 13-SL64
1xVC4
working path
protection path
Prerequisites
l The physical network topology must be created.
l NEs, boards, and fibers must be created on the U2000.
l The protection subnets of the two MSP intersecting rings must be created and be
consistent with the actual topology. For details about how to create the protection
subnets, see 11.20.2.3 Creating an MS Ring Protection Subnet.
Procedure
Step 1 See Steps 1-4 in 11.14.3 Configuration Process to configure services on NE1, NE2, NE5,
and NE6.
Step 2 Configure the service from MSP ring 1 to MSP ring 2 on NE3 (working intersecting node).
1. Configure the pass-through service from the board housed in slot 13 to the board housed
in slot 8 on NE3.
– Select NE3 in the NE Explorer. Choose Configuration > SDH Service
Configuration from the Function Tree.
– Click Create in the lower right portion of the window to set required parameters in
the Create SDH Service dialog box that is displayed. Click OK.
Parameter Value in Value Description
This
Example
Source Slot Shelf0(subr In this example, the SL64 board in slot 13 of NE3
ack)-13- is used as the source board. Therefore, set this
SL64-1(SD parameter to 13-SL64-1(SDH-1).
H-1)
Sink Slot Shelf0(subr In this example, the SL64 board in slot 8 of NE3 is
ack)-8- used as the sink board. Therefore, set this
SL64-1(SD parameter to 8-SL64-1(SDH-1).
H-1)
Activate Yes -
Immediatel
y
2. Configure SNCP protection group 1 according to the SNCP group plan of NE3.
– Select NE3 in the NE Explorer. Choose Configuration > SDH Service
Configuration from the Function Tree.
– Click Create SNCP Service in the lower right portion of the window to set
required parameters in the Create SNCP Service dialog box that is displayed. Click
OK.
Parameter Value in Value Description
This
Example
WTR Time(s) 600 When the time after the original working path
is restored to normal reaches the preset WTR
time, revertive switching occurs. This
parameter is valid only when Revertive
Mode is set to Revertive.
Pro Source Slot Shelf0(su In this example, the SL64 board in slot 12 of
tect brack)-12 NE3 is used as the source board of the
ion - protection service. Therefore, set this
Ser SL64-1(S parameter to 12-SL64-1(SDH-1).
vic DH-1)
e
Source 1 In this example, one VC-4 is required, and the
Timeslot service source uses the first VC-4. Therefore,
Range(e.g. set this parameter to 1.
1,3-6)
Activate Yes -
Immediately
NOTICE
You are advised to set the hold-off time to a value that is longer than maximum
MSP switching time (50 ms). If the hold-off time is set to 0 ms, the MSP may
perform multiple unnecessary switchovers in the case that the fiber between NE2
and NE3 is cut.
– Choose Configuration > SNCP Service Control from the Function Tree, double-
click Switching Condition for Working Service and Protection Service
respectively, and select HPUNEQ. Click Apply.
Step 3 Configure the service from MSP ring 2 to MSP ring 1 on NE3 (working intersecting node).
1. Configure the pass-through service from the board housed in slot 7 to the board housed
in slot 12 on NE3.
– Select NE3 in the NE Explorer. Choose Configuration > SDH Service
Configuration from the Function Tree.
– Click Create in the lower right portion of the window to set required parameters in
the Create SDH Service dialog box that is displayed. Click OK.
Source Slot Shelf0(subr In this example, the SL64 board in slot 7 of NE3 is
ack)-7- used as the source board. Therefore, set this
SL64-1(SD parameter to 7-SL64-1(SDH-1).
H-1)
Sink Slot Shelf0(subr In this example, the SL64 board in slot 12 of NE3
ack)-12- is used as the sink board. Therefore, set this
SL64-1(SD parameter to 12-SL64-1(SDH-1).
H-1)
Activate Yes -
Immediatel
y
2. Configure SNCP protection group 2 according to the SNCP group plan of NE3.
– Select NE3 in the NE Explorer. Choose Configuration > SDH Service
Configuration from the Function Tree.
– Click Create SNCP Service in the lower right portion of the window to set
required parameters in the Create SNCP Service dialog box that is displayed. Click
OK.
Parameter Value in Value Description
This
Example
WTR Time(s) 600 When the time after the original working path
is restored to normal reaches the preset WTR
time, revertive switching occurs. This
parameter is valid only when Revertive
Mode is set to Revertive.
Pro Source Slot Shelf0(su In this example, the SL64 board in slot 8 of
tect brack)-8- NE3 is used as the source board of the
ion SL64-1(S protection service. Therefore, set this
Ser DH-1) parameter to 8-SL64-1(SDH-1).
vic
e Source 1 In this example, one VC-4 is required, and the
Timeslot service source uses the first VC-4. Therefore,
Range(e.g. set this parameter to 1.
1,3-6)
Activate Yes -
Immediately
NOTICE
It is recommended that you set the hold-off time to a value that is longer than maximum
MSP switching time (50 ms). If the hold-off time is set to 0 ms, the MSP may perform
multiple unnecessary second switchovers in the case that the fiber between NE2 and
NE3 is cut.
Step 4 Configure the pass-through service between MSP ring 1 and MSP ring 2 on NE8.
1. Select NE8 in the NE Explorer. Choose Configuration > SDH Service Configuration
from the Function Tree.
2. Click Create in the lower right portion of the window to set required parameters in the
Create SDH Service dialog box that is displayed. Click OK.
Parameter Value in Value Description
This
Example
Source Slot Shelf0(subra In this example, the SL64 board in slot 13 of NE8 is
ck)-13- used as the source board. Therefore, set this parameter
SL64-1(SD to 13-N2SL64-1(SDH-1).
H-1)
Sink Slot Shelf0(subra In this example, the SL64 board in slot 7 of NE8 is
ck)-7- used as the sink board. Therefore, set this parameter to
SL64-1(SD 7-N2SL64-1(SDH-1).
H-1)
Activate Yes -
Immediately
Step 5 Verify the service configurations by referring to 11.20.1.3 Verifying the Service
Configuration.
----End
Related Tasks
If the services are configured incorrectly, delete them by following instructions in 11.20.4.2
Deleting SDH Services.
8 13
NE1
13 8
Line board 13 -SL64
NE2 SNCP Ring1 NE4
Line board 8 -SL64
8 13
NE3 Line board 7-SL64
13 8 Line board 8-SL64
7 12 Line board 12-SL64
Line board 13-SL64
13 8
Line board13-SL64
NE5 SNCP Ring2 NE7
Line board 8-SL64
8 13
NE6
13 8
8 13
NE1 NE2 and NE4 :
service service
SDH service source source
13 8 VC4 8-SL64 13-SL64
VC4:VC4-1 VC4:VC4-1
SNCP Ring1 线路板
Service pass-through NE2 NE4 Service pass-through
8 13
NE3:
13 8
8 13
13 NE6 8
VC4:VC4-1 VC4:VC4-1
NE6:
Prerequisites
l The physical network topology must be created.
l NEs, boards, and fibers must be created on the U2000.
Procedure
Step 1 Configure the SDH service on NE1 (source NE).
1. Select NE1 in the NE Explorer. Choose Configuration > SDH Service Configuration
from the Function Tree.
2. Click Create SNCP Service in the lower right portion of the window to set required
parameters in the Create SNCP Service dialog box that is displayed. Click OK.
Parameter Value in Value Description
This
Example
WTR Time(s) 600 When the time after the original working path is
restored to normal reaches the preset WTR time,
revertive switching occurs. This parameter is
valid only when Revertive Mode is set to
Revertive.
Wor Source Slot Shelf0(sub In this example, the SL64 board in slot 13 of
king rack)-13- NE1 is used as the source board of the working
Ser SL64-1(S service. Therefore, set this parameter to 13-
vice DH-1) SL64-1(SDH-1).
Sink Slot Shelf0(sub In this example, the SL64 board in slot 2 of NE1
rack)-2- is used as the sink board. Therefore, set this
SL64-1(S parameter to 2-SL64-1(SDH-1).
DH-1)
Prot Source Slot Shelf0(sub In this example, the SL64 board in slot 8 of NE1
ecti rack)-8- is used as the source board of the protection
on SL64-1(S service. Therefore, set this parameter to 8-
Ser DH-1) SL64-1(SDH-1).
vice
Source 1 In this example, one VC-4 is required, and the
Timeslot service source uses the first VC-4. Therefore, set
Range(e.g. this parameter to 1.
1,3-6)
Activate Yes -
Immediately
Step 2 Configure the SDH service on NE6 (sink NE) by referring to Step 1.
Parameter Value in Value Description
This
Example
WTR Time(s) 600 When the time after the original working path is
restored to normal reaches the preset WTR time,
revertive switching occurs. This parameter is valid
only when Revertive Mode is set to Revertive.
Wor Source Slot Shelf0(subr In this example, the SL64 board in slot 13 of NE6 is
king ack)-13- used as the source board of the working service.
Serv SL64-1(SD Therefore, set this parameter to 13-
ice H-1) SL64-1(SDH-1).
Sink Slot Shelf0(subr In this example, the SL64 board in slot 2 of NE6 is
ack)-2- used as the sink board. Therefore, set this parameter
SL64-1(SD to 2-SL64-1(SDH-1).
H-1)
Prot Source Slot Shelf0(subr In this example, the SL64 board in slot 8 of NE6 is
ectio ack)-8- used as the source board of the protection service.
n SL64-1(SD Therefore, set this parameter to 8-SL64-1(SDH-1).
Serv H-1)
ice
Source 1 In this example, one VC-4 is required, and the
Timeslot service source uses the first VC-4. Therefore, set
Range(e.g. this parameter to 1.
1,3-6)
Source Slot Shelf0(subra In this example, the SL64 board in slot 13 of NE2 is
ck)-13- used as the source board. Therefore, set this parameter
SL64-1(SD to 12-SL64-1(SDH-1).
H-1)
Sink Slot Shelf0(subra In this example, the SL64 board in slot 8 of NE2 is
ck)-8- used as the sink board. Therefore, set this parameter to
SL64-1(SD 8-N2SL64-1(SDH-1).
H-1)
Activate Yes -
Immediately
NOTE
In this example, NE4, NE5, and NE7 are pass-through NEs. The configuration method and
parameter setting are the same as those of NE2. See substeps a-b in Step 3.
According to the configuration principle of the SNCP tangent rings, you need to configure four SNCP
protection groups for each bidirectional service. The configuration combination of protection groups is
not fixed. You can configure the protection group according to actual requirements. The following
configuration is considered as a reference.
1. Select NE3 in the NE Explorer. Choose Configuration > SDH Service Configuration
from the Function Tree.
2. Click Create SNCP Service in the lower right portion of the window. Select Configure
SNCP Tangent Ring on the lower right of the Create SNCP Service dialog box that is
displayed and set the required parameters.
Parameter Value in Value Description
This
Example
WTR Time(s) 600 When the time after the original working path is
restored to normal reaches the preset WTR time,
revertive switching occurs. This parameter is
valid only when Revertive Mode is set to
Revertive.
Wor Source Slot Shelf0(sub In this example, the SL64 board in slot 13 of
king rack)-13- NE3 is used as the source board of the working
Ser SL64-1(S service. Therefore, set this parameter to 13-
vice DH-1) SL64-1(SDH-1).
Prot Source Slot Shelf0(sub In this example, the SL64 board in slot 8 of NE3
ecti rack)-8- is used as the source board of the protection
on SL64-1(S service. Therefore, set this parameter to 8-
Ser DH-1) SL64-1(SDH-1).
vice
Source 1 In this example, one VC-4 is required, and the
Timeslot service source uses the first VC-4. Therefore, set
Range(e.g. this parameter to 1.
1,3-6)
Sink Slot Shelf0(sub In this example, the SL64 board in slot 7 of NE3
rack)-7- is used as the sink board. Therefore, set this
SL64-1(S parameter to 7-SL64-1(SDH-1).
DH-1)
Activate Yes -
Immediately
Step 5 Verify the service configurations by referring to 11.20.1.3 Verifying the Service
Configuration.
----End
Related Tasks
If the services are configured incorrectly, delete them by following instructions in 11.20.4.2
Deleting SDH Services.
8 13
NE1
13 8
NE2 SNCP Ring1 NE4
8 13
NE3 NE8 8
8 13 Line board 7-SL64
13
Line board 8-SL64
13 8
NE5 SNCP Ring2 NE7
8 13
NE6
13 8
receive the service respectively. In the normal situation, the flow direction of the
selected working source is NE1-NE2-NE3.
– SNCP protection group 1 on NE6 selectively receives the service that enters SNCP
ring 2. In the normal situation, the flow direction of the selected working source is
NE3-NE5-NE6.
l Normally, the service flow direction from SNCP ring 2 to SNCP ring 1 is NE6-NE7-
NE8-NE4-NE1.
– On NE8, configure pass-through services from the board in slot 12 to the board in
slot 7. These pass-through services are working sources of SNCP protection group 2
on NE3.
– On NE3, configure pass-through services from the board in slot 7 to the board in
slot 12. These pass-through services are protection sources of SNCP protection
group 2 on NE8.
– When the services are transmitted from SNCP ring 2 to SNCP ring 1, SNCP
protection group 1 on NE8 and SNCP protection group 2 on NE3 selectively
receive the service respectively. Normally, the flow direction of the selected
working source is NE6-NE7-NE8.
– SNCP protection group 1 on NE1 selectively receives the service that enters SNCP
ring 1. In the normal situation, the flow direction of the selected working source is
NE8-NE4-NE1.
The service flow direction in the SNCP tangent ring is consistent with the service flow
direction on SNCP intersecting ring. Both the SNCP intersecting ring and SNCP tangent ring
can implement protection for the service when two fibers are cut in two MSP rings
respectively. But only the SNCP intersecting ring can protect the service when one
intersecting node is faulty.
Figure 11-33 Signal flow and timeslot allocation of the SNCP intersecting ring
NE1:
VC4:VC4-1 VC4:VC4-1
8 13
NE1
13 8
VC4:VC4-1
Service pass-through VC4:VC4-1
NE3: VC4:VC4-1 NE2 SNCP Ring1 NE4
线路板
Service pass-through
13 8
8 13
13 NE6 8
VC4:VC4-1 VC4:VC4-1
NE6:
working path
protection path
Prerequisites
l The physical network topology must be created.
l NEs, boards, and fibers must be created on the U2000.
Procedure
Step 1 See Steps 1-3 in 11.16.3 Configuration Process to configure services on NE1, NE2, NE4,
NE5, and NE7.
Step 2 Configure the SDH service on NE3 (intersecting NE).
1. On NE3, configure pass-through services from the board in slot 13 to the board in slot 8.
These pass-through services are protection sources of SNCP protection group 1 on NE8.
– Select NE3 in the NE Explorer. Choose Configuration > SDH Service
Configuration from the Function Tree.
– Click Create in the lower right portion of the window to set required parameters in
the Create SDH Service dialog box that is displayed. Click OK.
Parameter Value in Description
This
Example
Sink Slot Shelf0(subrac In this example, the SL64 board in slot 8 of NE3
k)-8- is used as the sink board. Therefore, set this
SL64-1(SDH- parameter to 8-SL64-1(SDH-1).
1)
Activate Yes -
Immediatel
y
2. On NE3, configure pass-through services from the board in slot 7 to the board in slot 12.
These pass-through services are protection sources of SNCP protection group 2 on NE8.
– On NE3, configure pass-through services from the board in slot 7 to the board in
slot 12 by referring to Step 2.1.
Parameter Value in Description
This
Example
Source Slot Shelf0(subrac In this example, the SL64 board in slot 7 of NE3
k)-7- is used as the source board. Therefore, set this
SL64-1(SDH- parameter to 7-SL64-1(SDH-1).
1)
Activate Yes -
Immediatel
y
3. Configure SNCP protection group 1 according to the SNCP group plan of NE3.
– Select NE3 in the NE Explorer. Choose Configuration > SDH Service
Configuration from the Function Tree.
– Click Create SNCP Service in the lower right portion of the window to set
required parameters in the Create SNCP Service dialog box that is displayed. Click
OK.
Parameter Value in Description
This
Example
WTR Time(s) 600 When the time after the original working path
is restored to normal reaches the preset WTR
time, revertive switching occurs. This
parameter is valid only when Revertive
Mode is set to Revertive.
Pro Source Slot Shelf0(su In this example, the SL64 board in slot 8 of
tect brack)-8- NE3 is used as the source board of the
ion SL64-1(S protection service. Therefore, set this
Ser DH-1) parameter to 8-SL64-1(SDH-1).
vic
e Source 1 In this example, one VC-4 is required, and the
Timeslot service source uses the first VC-4. Therefore,
Range(e.g. set this parameter to 1.
1,3-6)
Activate Yes -
Immediately
4. Configure SNCP protection group 2 according to the SNCP group plan of NE3.
– The method of configuring protection group 2 is the same as the method of
configuring protection group 1. Configure protection group 2 by referring to Step
2.3.
WTR Time(s) 600 When the time after the original working path
is restored to normal reaches the preset WTR
time, revertive switching occurs. This
parameter is valid only when Revertive
Mode is set to Revertive.
Pro Source Slot Shelf0(su In this example, the SL64 board in slot 7 of
tect brack)-7- NE3 is used as the source board of the
ion SL64-1(S protection service. Therefore, set this
Ser DH-1) parameter to 7-SL64-1(SDH-1).
Activate Yes -
Immediately
Source Slot Shelf0(subr In this example, the SL64 board in slot 8 of NE8 is
ack)-8- used as the source board. Therefore, set this
SL64-1(SD parameter to 8-SL64-1(SDH-1).
H-1)
Sink Slot Shelf0(subr In this example, the SL64 board in slot 13 of NE8
ack)-13- is used as the sink board. Therefore, set this
SL64-1(SD parameter to 13-SL64-1(SDH-1).
H-1)
Activate Yes -
Immediatel
y
2. On NE8, configure pass-through services from the board in slot 12 to the board in slot 7.
These pass-through services are working sources of SNCP protection group 2 on NE3.
– On NE8, configure pass-through services from the board in slot 12 to the board in
slot 7 by referring to Step 2.1.
Parameter Value in Value Description
This
Example
Source Slot Shelf0(subr In this example, the SL64 board in slot 12 of NE8
ack)-12- is used as the source board. Therefore, set this
SL64-1(SD parameter to 12-SL64-1(SDH-1).
H-1)
Sink Slot Shelf0(subr In this example, the SL64 board in slot 7 of NE8 is
ack)-7- used as the sink board. Therefore, set this
SL64-1(SD parameter to 7-SL64-1(SDH-1).
H-1)
Activate Yes -
Immediatel
y
3. Configure SNCP protection group 1 according to the SNCP group plan of NE8.
– On NE8, configure SNCP protection group 1 by referring to Step 2.3.
Parameter Value in Value Description
This
Example
WTR Time(s) 600 When the time after the original working path
is restored to normal reaches the preset WTR
time, revertive switching occurs. This
parameter is valid only when Revertive
Mode is set to Revertive.
Pro Source Slot Shelf0(su In this example, the SL64 board in slot 8 of
tect brack)-8- NE8 is used as the source board of the
ion SL64-1(S protection service. Therefore, set this
Ser DH-1) parameter to 8-SL64-1(SDH-1).
vic
e Source 1 In this example, one VC-4 is required, and the
Timeslot service source uses the first VC-4. Therefore,
Range(e.g. set this parameter to 1.
1,3-6)
Activate Yes -
Immediately
4. Configure SNCP protection group 2 according to the SNCP group plan of NE8.
– The method of configuring protection group 2 is the same as the method of
configuring protection group 1. Configure protection group 2 by referring to Step
2.3.
Parameter Value in Value Description
This
Example
WTR Time(s) 600 When the time after the original working path
is restored to normal reaches the preset WTR
time, revertive switching occurs. This
parameter is valid only when Revertive
Mode is set to Revertive.
Pro Source Slot Shelf0(su In this example, the SL64 board in slot 7 of
tect brack)-7- NE8 is used as the source board of the
ion SL64-1(S protection service. Therefore, set this
Ser DH-1) parameter to 7-SL64-1(SDH-1).
vic
e Source 1 In this example, one VC-4 is required, and the
Timeslot service source uses the first VC-4. Therefore,
Range(e.g. set this parameter to 1.
1,3-6)
Activate Yes -
Immediately
Step 4 Verify the service configurations by referring to 11.20.1.3 Verifying the Service
Configuration.
----End
Related Tasks
If the services are configured incorrectly, delete them by following instructions in 11.20.4.2
Deleting SDH Services.
case of two tangent MSP and SNCP rings, SNCP protection groups need to be configured for
the service that is selectively received on the MSP ring and for the service that is dually
transmitted on the SNCP ring at the tangent point.
Figure 11-34 shows the networking diagram of two tangent MSP and SNCP rings. The
tangent NE is NE3. The SL64 boards are installed on all the NEs as line boards to transmit the
SDH services.
Figure 11-34 Networking diagram of two tangent MSP and SNCP rings
Line Board 2-SL64
Line Board 8-SL64
Line Board 13-SL64
13 8
NE5 NE7
8 13
Line Board 8-SL64
Line Board 13-SL64 NE6
13 8
As shown in Figure 11-35, the signal flow and NE configuration of two tangent MSP and
SNCP rings are as follows:
l The signal flow of the working service in the SNCP group is NE1←→NE2←→NE3.
l The signal flow of the protection service is NE1←→NE4←→NE3.
l The service flow of the multiplex section is NE5←→NE6.
l The tangent NE (NE3) is configured with one protection group.
l Services are configured so that they pass through NE2, NE4, and NE5.
Figure 11-35 Signal flow and timeslot allocation of two tangent MSP and SNCP rings
1xVC4 NE1:
SNCP Protection Working Protectio
Service Sink
Group Source n Source
Protecton group 1 8-SL64 13-SL64 2-SL64
8 13
NE1
NE2 and NE4:
:
13
8
13 NE3
8
NE3:
SNCP Protection Working Protection Service
Group Source Source Sink
Protection Group 1 13-SL64 8-SL64 7-SL64
7 12
13
8
VC4-1:VC4-1
NE5 MSP ring NE7
pass-through service
8 13
NE5:
SDH Service Servuce Source Service Source
NE6:
Flow of the working service Service Service
SDH Serice
Source Sink
Flow of the protection service
VC4 13-SL64 2-SL64
1xVC4
Prerequisites
l The physical network topology must be established.
l NEs, boards, and fibers must be created on the U2000.
l The MSP protection subnet must be created and must be consistent with the actual
topology. For details about how to create the MSP protection subnet, see 11.20.2.3
Creating an MS Ring Protection Subnet.
l You must be familiar with the information about 11.18.2 Signal Flow and Timeslot
Allocation.
Procedure
Step 1 To configure the SDH service of the source NE (NE1), do as follows:
NOTE
When you configure an SNCP service, you can select the SNCP switching conditions.
1. Select NE1 in the NE Explorer, and then choose Configuration > SDH Service
Configuration from the Function Tree.
2. Click Create SNCP Service at the lower right. Then, the Create SNCP Service dialog
box is displayed. Set the parameters in the dialog box, and then click OK.
Hold-Off Time 0 This parameter takes the default value and need
(100ms) not be specified.
WTR Time(s) 600 After the working path is restored to normal, the
switching restoration occurs if the normal state
lasts for 600s. This parameter is valid only
when Revertive Mode is set to Revertive.
Wor Source Slot Shelf0(subr In this example, the SL64 board in slot 8 is the
king ack)-8- source board of the working service (see Figure
Ser SL64-1(SD 11-34). You can select a different source board
vice H-1) depending on the actual situation.
Source VC4 - -
Prot Source Slot Shelf0(subr In this example, the SL64 board in slot 13 is the
ecti ack)-13- source board of the protection service (see
on SL64-1(SD Figure 11-34). You can select a different source
Ser H-1) board depending on the actual situation.
vice
Source VC4 - -
Sink Slot Shelf0(subr In this example, the SL64 board in slot 2 is the
ack)-2- sink board (see Figure 11-34). You can select a
SL64-1(SD different sink board depending on the actual
H-1) situation.
Sink VC4 - -
Sink Timeslot 1-5 In this example, the total service capacity that is
Range(e.g.1,3-6) planned is 1xVC4 (see Figure 11-35). Hence,
set Source Timeslot Range(e.g.1,3-6) to 1,
because Level of the service is set to VC4.
Click , and select NE3 from the NE Navigator that is displayed. Click OK. Refer to
Step 1 and configure the SDH service on NE3. Set the parameters listed in the following
table.
WTR Time(s) 600 After the working path is restored to normal, the
switching restoration occurs if the normal state lasts
for 600s. This parameter is valid only when
Revertive Mode is set to Revertive.
Wor Source Slot Shelf0(subr In this example, the SL64 board in slot 13 is the
king ack)-13- source board of the working service (see Figure
Serv SL64-1(SD 11-34). You can select a different source board
ice H-1) depending on the actual situation.
Source VC4 - -
Prot Source Slot Shelf0(subr In this example, the SL64 board in slot 8 is the
ectio ack)-8- source board of the protection service (see Figure
n SL64-1(SD 11-34). You can select a different source board
Serv H-1) depending on the actual situation.
ice
Source VC4 - -
Sink Slot Shelf0(subr In this example, the SL64 board in slot 7 is the sink
ack)-7- board (see Figure 11-34). You can select a different
SL64-1(SD sink board depending on the actual situation.
H-1)
Sink VC4 - -
1. Click , and select NE6 from the NE Navigator that is displayed. Click OK.
2. Select NE6 in the NE Explorer, and then choose Configuration > SDH Service
Configuration from the Function Tree.
3. Click Create on the lower right of the window. Then, the Create SDH Service dialog
box is displayed. Set the parameters in the dialog box, and then click OK.
Parameter Value in Description
This
Example
Direction Bidirectional In this example, the services are transmitted and received
over the same path, that is, the transmitted service and
received service are bidirectional services. Hence, set
Direction of the services to Bidirectional.
Source Slot Shelf0(subra In this example, the SL64 board in slot 13 is the source
ck)-13- line board (see Figure 11-34).You can select different
SL64-1(SDH source boards depending on the actual situation.
-1)
Source VC4 - -
Sink Slot Shelf0(subra In this example, the SL64 board in slot 2 is the sink board
ck)-2- (see Figure 11-34). You can select a different sink board
SL64-1(SDH depending on the actual situation.
-1)
Sink VC4 - -
Sink Timeslot 1 In this example, the total service capacity that is planned
Range(e.g. is 1xVC4 (see Figure 11-35). Hence, set Source Timeslot
1,3-6) Range(e.g.1,3-6) to 1, because Level of the service is set
to VC4.
Step 4 Configure the pass-through services on NE2, NE4, and NE5. Refer to Step 3 and configure
the VC4-1:VC4-1 pass-through service from the board in slot 13 to the board in slot 8.
Parameter Value in Description
This
Example
Direction Bidirectional In this example, the services are transmitted and received
over the same path, that is, the transmitted service and
received service are bidirectional services. Hence, set
Direction of the services to Bidirectional.
Source Slot Shelf0(subra In this example, the SL64 board in slot 13 is the source
ck)-13- line board (see Figure 11-34). You can select a different
SL64-1(SDH source board depending on the actual situation.
-1)
Source VC4 - -
Sink Slot Shelf0(subra In this example, the SL64 board in slot 8 is the sink line
ck)-8- board (see Figure 11-34). You can select a different sink
SL64-1(SDH board depending on the actual situation.
-1)
Sink VC4 - -
Sink Timeslot 1 In this example, the total service capacity that is planned
Range(e.g. is 1xVC4 (see Figure 11-35). Hence, set Source Timeslot
1,3-6) Range(e.g.1,3-6) to 1, because Level of the service is set
to VC4.
Step 5 Verify the service configurations by referring to 11.20.1.3 Verifying the Service
Configuration.
----End
Related Tasks
If the services are configured incorrectly, delete them by following instructions in 11.20.4.2
Deleting SDH Services.
Figure 11-36 Networking diagram of two intersecting MSP and SNCP rings
Line Board 2-SL64
Line Board 8-SL64
Line Board 13-SL64
8 13
NE1
13 8
Line Board 8-SL64
Line Board 13-SL64 NE2 NE3
8 13
NE4 NE5
12 8 12 8 Line Board 7-SL64
Line Board 8-SL64
7 13 7 13 Line Board 12-SL64
Line Board 13-SL64
13 8
Line Board 8-SL64
Line Board 13-SL64 NE6 NE7
8 13
NE8
13 8
l The signal flow of the protection service in the SNCP protection group is NE1←→NE3
←→NE5←→NE4.
l The service flow of the multiplex section is NE6←→NE8.
l One intersecting NE (NE4) is configured with one protection group.
l Services are configured so that they pass through the other intersecting NE (NE5).
l Services are configured so that they pass through NE2, NE3, and NE6.
Figure 11-37 Signal flow and timeslot allocation of two intersecting MSP and SNCP rings
Add or drop 1xVC4
services
NE1:
SNCP Protection Protection Service
Working Source
Group Source Sink
8-SL64 13-SL64 2-SL64
Protection group 1
8 VC4-1:VC4-1
13 pass-through service
NE1
13 8
13 7
13 13 8
7
13
8 NE8
13 8
NE8:
SDH Service Service Source Service Source
Prerequisites
l The physical topology of the network must be created.
l NEs, boards, and fibers must be created on the U2000.
l The MSP protection subnet must be created and must be consistent with the actual
topology. For details about how to create the MSP protection subnet, see 11.20.2.3
Creating an MS Ring Protection Subnet.
l You must be familiar with the information about 11.19.2 Signal Flow and Timeslot
Allocation.
Procedure
Step 1 To configure the SDH service of the source NE (NE1), do as follows:
NOTE
When you configure an SNCP service, you can select the SNCP switching conditions.
1. Select NE1 in the NE Explorer, and then choose Configuration > SDH Service
Configuration from the Function Tree.
2. Click Create SNCP Service on the lower right of the window. Then, the Create SNCP
Service dialog box is displayed. Set the parameters in the dialog box, and then click OK.
Parameter Value in Description
This
Example
Hold-Off Time 0 This parameter takes the default value and need
(100ms) not be specified.
WTR Time(s) 600 After the working path is restored to normal, the
switching restoration occurs if the normal state
lasts for 600s. This parameter is valid only
when Revertive Mode is set to Revertive.
Wor Source Slot Shelf0(subr In this example, the SL64 board in slot 8 is the
king ack)-8- source board of the working service (see Figure
Ser SL64-1(SD 11-36). You can select a different source board
vice H-1) depending on the actual situation.
Source VC4 - -
Prot Source Slot Shelf0(subr In this example, the SL64 board in slot 13 is the
ecti ack)-13- source board of the protection service (see
on SL64-1(SD Figure 11-36). You can select a different source
Ser H-1) board depending on the actual situation.
vice
Source VC4 - -
Sink Slot Shelf0(subr In this example, the SL64 board in slot 2 is the
ack)-2- sink board (see Figure 11-36). You can select a
SL64-1(SD different sink board depending on the actual
H-1) situation.
Sink VC4 - -
Click ,and select NE4 from the NE Navigator that is displayed. Click OK. Refer to Step
1 and configure the SDH service on NE4. Set the parameters listed in the following table.
WTR Time(s) 600 After the working path is restored to normal, the
switching restoration occurs if the normal state lasts
for 600s. This parameter is valid only when
Revertive Mode is set to Revertive.
Wor Source Slot Shelf0(subr In this example, the SL64 board in slot 12 is the
king ack)-12- source board of the working service (see Figure
Serv SL64-1(SD 11-36). You can select a different source board
ice H-1) depending on the actual situation.
Source VC4 - -
Prot Source Slot Shelf0(subr In this example, the SL64 board in slot 13 is the
ectio ack)-13- source board of the protection service (see Figure
n SL64-1(SD 11-36). You can select a different source board
Serv H-1) depending on the actual situation.
ice
Source VC4 - -
Sink Slot Shelf0(subr In this example, the SL64 board in slot 7 is the sink
ack)-7- board (see Figure 11-36). You can select a different
SL64-1(SD sink board depending on the actual situation.
H-1)
Sink VC4 - -
1. Click , and select NE8 from the NE Navigator that is displayed. Click OK.
2. Select NE8 in the NE Explorer, and then choose Configuration > SDH Service
Configuration from the Function Tree.
3. Click Create on the lower right of the window. Then, the Create SDH Service dialog
box is displayed. Set the parameters in the dialog box, and then click OK.
Parameter Value in Description
This
Example
Direction Bidirectional In this example, the services are transmitted and received
over the same path, that is, the transmitted service and
received service are bidirectional services. Hence, set
Direction of the services to Bidirectional.
Source Slot Shelf0(subra In this example, the SL64 board in slot 13 is the source
ck)-13- line board (see Figure 11-36). You can select a different
SL64-1(SDH source board depending on the actual situation.
-1)
Source VC4 - -
Sink Slot Shelf0(subra In this example, the SL64 board in slot 2 is the sink board
ck)-2- (see Figure 11-36). You can select a different sink board
SL64-1(SDH depending on the actual situation.
-1)
Sink VC4 - -
Sink Timeslot 1 In this example, the total service capacity that is planned
Range(e.g. is 1xVC4 (see Figure 11-37). Hence, set Source Timeslot
1,3-6) Range(e.g.1,3-6) to 1, because Level of the service is set
to VC4.
Step 4 Configure the pass-through services on NE2, NE3, and NE6. Refer to Step 3 and configure
the VC4-1:VC4-1 pass-through service from the board in slot 13 to the board in slot 8.
Parameter Value in Description
This
Example
Direction Bidirectional In this example, the services are transmitted and received
over the same path, that is, the transmitted service and
received service are bidirectional services. Hence, set
Direction of the services to Bidirectional.
Source Slot Shelf0(subra In this example, the SL64 board in slot 13 is the source
ck)-13- line board (see Figure 11-36). You can select a different
SL64-1(SDH source board depending on the actual situation.
-1)
Source VC4 - -
Sink Slot Shelf0(subra In this example, the SL64 board in slot 8 is the sink line
ck)-8- board (see Figure 11-36). You can select a different sink
SL64-1(SDH board depending on the actual situation.
-1)
Sink VC4 - -
Sink Timeslot 1 In this example, the total service capacity that is planned
Range(e.g. is 1xVC4 (see Figure 11-37). Hence, set Source Timeslot
1,3-6) Range(e.g.1,3-6) to 1, because Level of the service is set
to VC4.
Step 5 Configure the pass-through service on NE5. Refer to Step 3 and configure the VC4-1:VC4-1
pass-through service from the board in slot 8 to the board in slot 7.
Parameter Value in Description
This
Example
Direction Bidirectional In this example, the services are transmitted and received
over the same path, that is, the transmitted service and
received service are bidirectional services. Hence, set
Direction of the services to Bidirectional.
Source Slot Shelf0(subra In this example, the SL64 board in slot 8 is the source line
ck)-8- board (see Figure 11-36). You can select a different
SL64-1(SDH source board depending on the actual situation.
-1)
Source VC4 - -
Sink Slot Shelf0(subra In this example, the SL64 board in slot 7 is the sink line
ck)-7- board (see Figure 11-36). You can select a different sink
SL64-1(SDH board depending on the actual situation.
-1)
Sink VC4 - -
Sink Timeslot 1 In this example, the total service capacity that is planned
Range(e.g. is 1xVC4 (see Figure 11-37). Hence, set Source Timeslot
1,3-6) Range(e.g.1,3-6) to 1, because Level of the service is set
to VC4.
Step 6 Verify the service configurations by referring to 11.20.1.3 Verifying the Service
Configuration.
----End
Related Tasks
If the services are configured incorrectly, delete them by following instructions in 11.20.4.2
Deleting SDH Services.
Prerequisites
You are an NMS user with "Guests" privilege or higher.
Procedure
Step 1 In the Workbench view, double-click Main Topology to display the main topology.
Step 3 Select Configuration > Cross-Connect Capacity Management > Lower Order Cross-
Connect Capacity from the Function Tree.
Step 4 Click Query to display information such as Max. Capacity(G), Max. VC4 Count,
Remaining Source VC4 Count, Remaining Sink VC4 Count, Remaining Sink VC3
Countand Remaining Sink VC12 Count.
NOTE
----End
Prerequisites
You are an NMS user with "Guests" privilege or higher.
Procedure
Step 1 In the Workbench view, double-click Main Topology to display the main topology.
Step 2 Select the required NE, right-click it, and choose NE Explorer from the shortcut menu.
Step 3 In the NE Explorer, select the NE and then choose Configuration > SDH Service
Configuration from the Function Tree.
Step 4 Click Query to query the service on the NE.
Step 5 Click Create and set the required parameters in the Create SDH Service dialog box that is
displayed.
Step 6 Click OK.
----End
Prerequisites
l The physical topology of the network has been created.
l NEs, boards, and fibers have been successfully created on the U2000.
l The SDH test meter has been correctly connected to the source end and the sink end, and
the corresponding service type and rate have been configured.
l You are an NMS user with "Administrators" privilege.
Impact on System
None
Background Information
When the service type and rate are set on the test meter, the "SIGNAL", "PATTERN", and
"FRAME" indicators of the 37718 SDH analyzer turn green from red and are constantly on. If
no alarm indicator is on the test meter, the SDH test meter is normally connected to the
network.
Precautions
NOTICE
Add an appropriate optical attenuator to the OUT optical interface and IN optical interface on
the board that is directly connected to the SDH meter. In this case, the damage due to
excessive optical power can be prevented for the test meter and board.
Procedure
Step 1 Respectively enable the SDH test meters at the source end and the sink end to monitor the
service switching in the network.
Step 2 In the Main Topology, click the source NE and then right-click the NE to choose NE
Explorer from the shortcut menu. In the board directory tree in the left window, select the
line board for service transmission and then choose Configuration > SDH Interface from
Function Tree.
Step 3 In the right window, select By Function. Choose Laser Switch from the drop-down list. Set
Laser Switch to Off.
Step 4 Click Apply. Confirm the relevant information in the displayed dialog boxes. Close the
Operation Result dialog box.
NOTE
By performing steps 2-4, you can close the laser that transmits services. In this case, the service in the
working path is interrupted and the service switching condition is met.
Step 5 Choose Fault > Browse Current Alarm from the Main Menu on the U2000.
Step 6 Click OK in the Filter dialog box. In the Browse Current Alarm window, you can view the
LASER_SHUT alarm reported by the line board whose laser is shut down on the source NE,
and the R_LOS alarm reported by the line board on the sink NE.
Step 7 The service interruption time read from the RESULT TS window on the test meter is equal to
the service switching time.
NOTE
On the test meter, the LONGEST and SHORTEST parameters in the RESULT TS window record the
longest switching time and the shortest switching time when the switching is performed for multiple
times. The LAST parameter records the time of the last switching.
Step 8 Query the switching state and service state on the U2000 to check whether the configuration
is correct.
NOTE
The query of the MSP ring switching status is different from the query of the SNCP switching status.
Refer to Steps 9-11 for querying the service status on the MSP ring. Refer to Steps 12-13 for querying
the SNCP service status.
Step 9 Choose Service > SDH Protection Subnet > Maintain SDH Protection Subnet from the
Main Menu on the U2000.
Step 10 Choose the Protection Subnet Maintenance tab on the right side of the SDH Protection
Subnet Common Attributes pane. Query East Status and West Status. If the status is
"Signal Fail Switching - Ring", "Signal Fail Switching - Span", or "Lockout of protection-
Span", the MSP switching is successful.
Step 11 Choose Fault > Browse Current Alarm... from the Main Menu on the U2000. If no service
alarm is reported for the working path, the service switching is successful.
NOTE
Verify the MSP ring service configuration by performing steps 10-11. The results show that the
configuration is successful.
Step 12 Click the NE to be queried in the Main Topology and then right-click the NE to choose NE
Explorer from the shortcut menu. Choose Configuration > SNCP Service Control from the
Function Tree.
Step 13 Query the parameters of Current Status, Trail Status and Active Channel to check whether
the service is switched successfully.
NOTE
The service switching and SNCP service configuration are successful if the following conditions are
satisfied: 1. The current status is SF switching. 2. The status of the working service path is SF. 3. The
status of the protection service path is normal. 4. The current path is the protection path.
----End
Prerequisites
l You are an NMS user with "Maintenance Group" privilege or higher.
l On the NM, the data of each NE must be configured, and fibers must be created
correctly.
Procedure
Step 1 Choose Service > SDH Protection Subnet > Create Unprotected Chain from the Main
Menu.
l If multiple protection subnets use one port of a board, you need to check the Resource Sharing
check box. If MSP Sharing is enabled, you can check the Resource Sharing check box to map a
port of the board to multiple MSPs. If different protection subnets use different ports of a board, do
not check this check box.
l Select the Assigned by VC4 option when there are different VC4s belonging to different protection
subnets to achieve MSP only in some channels protection.
Step 5 Select a node to create a non-protection chain. Double-click an NE in the Main Topology and
add it to the left node list.
Step 6 Click Next to display the Select Link dialog box. Set parameters, such as Physical Link
Information.
Step 7 Click Finish to deliver the configuration data. Then the Operation Result prompt box is
displayed. Click Close.
----End
Prerequisites
l You are an NMS user with "Maintenance Group" privilege or higher.
l The NE data must be configured, and fibers must be properly created.
Procedure
Step 1 Choose Service > SDH Protection Subnet > Create Unprotected Ring from the Main
Menu.
The Create Protection Subnet tab is displayed.
NOTE
l If multiple protection subnets use one port of a board, you need to check the Resource Sharing
check box. If MSP Sharing is enabled, you can check the Resource Sharing check box to map a
port of the board to multiple MSPs. If different protection subnets use different ports of a board, do
not check this check box.
l Select the Assigned by VC4 option when there are different VC4s belonging to different protection
subnets to achieve MSP only in some channels protection.
Step 5 Add nodes to the protection subnet to be created. Double-click the NE on the Main Topology
and add it to the node list in the left-hand pane.
Step 6 Click Next to proceed to the Select Link screen of the wizard. Set parameters, such as
Physical Link Information.
NOTE
l If there are multiple fibers between two NEs, select them from the Physical Link Information
drop-down list.
l If Assigned by VC4 is selected, you can select the working and protection VC4 timeslots as needed.
Step 7 Click Finish to deliver the configuration data. Then the Operation Result prompt box is
displayed. Click Close.
----End
Prerequisites
l You are an NMS user with "Maintenance Group" privilege or higher.
l The NE data must be configured, and fibers must be properly created.
Context
l The number of nodes in an MSP ring cannot exceed 16.
NOTICE
Starting the protocol controller may interrupt the service.
Procedure
Step 1 Choose Service > SDH Protection Subnet > Create 2f_MS_SPRing from the main menu.
Click OK in the Information dialog box that is displayed. The Create Protection Subnet tab
is displayed.
NOTE
To create a four-fiber bidirectional shared MSP ring, choose Service > SDH Protection Subnet >
Create 4f_MS_SPRing.
Step 3 Select the rate of the protection subnet, for example, STM-4.
l If multiple protection subnets use one port of a board, you need to check the Resource Sharing
check box. If MSP Sharing is enabled, you can check the Resource Sharing check box to map a
port of the board to multiple MSPs. If different protection subnets use different ports of a board, do
not check this check box.
l Select the Assigned by VC4 option when there are different VC4s belonging to different protection
subnets to achieve MSP only in some channels protection. For example, for an STM-16 fiber, the
VC4s 1-4 belong to an STM-4 MSP, and VC4s 5-8 belong to a PP.
l Transoceanic Protocol specifies whether the transoceanic MS protocol is used. If the transoceanic
MS protocol is used on a transoceanic ring network and a switchover occurs, services are switched
from the source and sink nodes. This significantly shortens the service interruption duration in the
case of long-distance transmission and improves the service transmission quality. Therefore, if a
transoceanic MS is configured, the Transoceanic Protocol option must be selected for use of the
transoceanic MS protocol.
Step 5 Add nodes to the protection subnet to be created. Double-click the NE on the Main Topology
to add it to the node list in the left-hand pane.
NOTE
For easy maintenance, the nodes should be added anticlockwise to the protection subnet.
Step 6 Set the attribute of the nodes. Select MSP Node in this example.
Step 7 Click Next to proceed to the Select Link screen of the wizard. Set parameters, such as
Physical Link Information.
NOTE
l If there are multiple fibers between two NEs, select them from the Physical Link Information
drop-down list.
l If Assigned by VC4 is selected, you can select the working and protection VC4 timeslots as needed.
Step 8 Click Finish to deliver the configuration data. Then the Operation Result prompt box is
displayed. Click Close.
Step 9 Right-click the protection subnet and choose Protection Subnet Attributes from the shortcut
menu.
Step 10 Click the Protection Subnet Maintenance tab to check whether the protocol controller starts.
If the protocol controller is not started, select all the NEs of the protection subnet. Right-click
in the blank space and choose Start/Stop Protocol > Start from the shortcut menu. Click Yes
every time it is displayed to ensure that the status of every Protocol Controller is Protocol
Started.
Step 11 Click the Protection Subnet Parameters tab and set the WTR time and SD Condition as
needed. Click Apply to deliver the configuration. The WTR time of all NEs in the same
protection subnet should be the same.
NOTE
----End
Prerequisites
l You are an NMS user with "Maintenance Group" privilege or higher.
l The NE data must be configured, and fibers must be properly created.
Context
Fibers that are related to a linear MSP cannot be used by other protection subnets. That is, a
linear MSP and other subnets cannot create virtual fibers together.
NOTICE
Starting the protocol controller may interrupt the service.
Procedure
Step 1 Choose Service > SDH Protection Subnet > Create 1+1 Linear MSP from the main menu.
The Create Protection Subnet tab is displayed.
NOTE
To create an M:N linear MSP subnet, choose Service > SDH Protection Subnet > Create M:N Linear
MSP.
Step 4 Set Revertive Mode and Switching Mode based on the protection type and requirements.
NOTE
l For M:N linear MS protection scheme, set the number of working links to N. M indicates the number of
protection links and cannot be set. Currently, the value is 1 only.
l Revertive Mode refers to the handling strategy adopted after the faulty line recovers to normal.
– Non-Revertive: The service does not automatically revert to the working channel after the faulty
line recovers to normal.
– Revertive: The service automatically reverts to the working channel after the faulty line recovers to
normal.
l Switching Mode refers to the switching strategy adopted after a fault occurs in the line.
– Single-ended switching: To protect services, switching occurs at the receive end when the receive
end is faulty and at the transmit end when the transmit end is faulty.
– Dual-ended switching: To protect services, the switching occurs at the receive and transmit ends
when either end is faulty.
l If multiple protection subnets use one port of a board, you need to check the Resource Sharing check
box. If different protection subnets use different ports of a board, do not check this check box.
l Select the Assigned by VC4 option when there are different VC4s belonging to different protection
subnets to achieve MSP only in some channels protection. For example, for an STM-16 fiber, the VC4s
1-4 belong to an STM-4 MSP, and VC4s 5-8 belong to a PP.
Step 5 Add nodes to the protection subnet to be created. Double-click the NE on the Main Topology
to add it to the node list in the left-hand pane.
Step 6 Click Next to proceed to the Select Link of the wizard. Set the Physical Link Information
of Working Link and Protection Link.
Step 7 Click Finish to deliver the configuration data. The Operation Result prompt box is
displayed. Click Close.
Step 8 Right-click the protection subnet and choose Protection Subnet Attributes from the shortcut
menu.
Step 9 Click the Protection Subnet Maintenance tab to check whether the protocol controller starts.
NOTE
If the protocol controller is not started, select all the NEs of the protection subnet. Right-click in the
blank space and choose Start/Stop Protocol > Start from the shortcut menu. Click Yes every time it is
displayed to ensure that the status of every Protocol Controller is Protocol Started.
Step 10 Click the Protection Subnet Parameters tab and set the WTR time and SD condition as
needed. Click Apply to deliver the configuration.
NOTE
The WTR time(s) of all NEs in the same protection subnet should be the same.
----End
Prerequisites
l You are an NMS user with "Maintenance Group" privilege or higher.
l When the cross-connections of the VC4 levels are created, you can query or set the trace
byte of the VC4.
Impact on System
Incorrect configuration of the trace byte causes interconnection failure.
Procedure
Step 1 Select the required NE, right-click it, and choose NE Explorer from the shortcut menu.
Step 2 Select the type of the trace byte.
Step 3 Click Options and the Options dialog box is displayed. Select the processing mode for the
read and write attributes of the overhead bytes.
NOTE
Step 4 Right-click the trace byte and choose the trace byte input mode from the shortcut menu.
Manual Input Click Manual Input and the Please input the overhead byte
dialog box is displayed. Choose Byte Mode and Input Mode and
enter the value of the trace byte. Click OK.
NOTE
l Choose Copy All Form Received and the contents of the trace byte received are automatically
copied to the table.
l Choose Manual Input to customize the contents of the trace byte.
Step 6 Click OK. A prompt appears telling you that the operation was successful. Click Close.
----End
Prerequisites
l You are an NMS user with "Maintenance Group" privilege or higher.
Impact on System
Incorrect configuration of byte C2 causes interconnection failure.
Procedure
Step 1 On the Main Topology, right-click the required NE and choose NE Explorer from the
shortcut menu.
Step 2 Select the service level of the C2 byte.
NOTE
l The mode must be set to Extended Mode. You can then set the C2 byte.
l The U2000 has two kinds of processing modes for the read and write attributes of the overhead
bytes, which are Extended Mode and Standard Mode. The U2000 has a stronger processing ability
for the read and write attributes of the overhead bytes in the extended mode than in the standard
mode.
Step 7 Click OK and a prompt appears telling you that the operation was successful. Click Close.
----End
Prerequisites
You are an NMS user with " NE operator" privilege or higher.
Context
NOTICE
This operation interrupts the SDH services being modified.
Procedure
Step 1 Select an NE in the NE Explorer and choose Configuration > SDH Service Configuration
from the Function Tree.
Step 2 Select an SDH service and choose Display > Expand to Unidirectional.
Step 3 Optional: If the service to be modified is active, deactivate the service by selecting it and
clicking Deactivate.
NOTICE
Service deactivation interrupts the service.
Step 4 Click OK in the Confirm dialog box each time it is displayed. The Operation Result dialog
box is displayed, indicating that the operation is successful.
Step 5 Click Close.
Step 6 After cross-connections are deactivated, modify SDH services by following the instructions in
Step 7 or Step 8.
NOTE
l The method in Step 7 allows you to modify the service source or sink, but requires that the source
and sink must be on the same board before and after the modification.
l If you fail to modify an SDH service using the method in Step 7, you can modify the service by
deleting and re-creating a service, as shown in Step 8.
Step 7 Optional: Modify an SDH service using Modify on the shortcut menu.
1. Right-click an SDH service and select Modify from the shortcut menu. The Modify
SDH Service dialog box is displayed.
2. Modify settings of Source VC4 or Sink VC4, Source Timeslot Range, and Sink
Timeslot Range.
NOTE
– For VC12 or VC3 services, you can modify either Source VC4 and Source Timeslot Range
or Sink VC4 and Sink Timeslot Range. Modification of the four parameters at a time is not
allowed.
– For VC4 services, you can modify either Source Timeslot Range or Sink Timeslot Range.
Modification of the two parameters at a time is not allowed.
3. Click OK. The Operation Result dialog box is displayed, indicating that the operation
is successful.
4. Click Close.
5. Select the modified service and click Activate.
6. Click OK. The Operation Result dialog box is displayed.
7. Click Close.
Step 8 Optional: Delete an SDH service and then create a new SDH service.
1. Select an SDH service and select Delete from the shortcut menu.
2. Click OK. The Operation Result dialog box is displayed, indicating that the operation
is successful.
3. Click Close. The service is deleted.
4. Create the service again as required by following instructions in 11.20.1.2 Creating the
SDH Service.
----End
Prerequisites
You are an NMS user with " NE operator" privilege or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > SDH Service Configuration
from the Function Tree.
Step 3 Optional: If the service to be deleted is active, you should deactivate the service. Select the
service that you want to delete and click Deactivate.
NOTICE
Deactivation will interrupt services.
----End
Prerequisites
You are an NMS user with " NE operator" privilege or higher.
Precaution
NOTICE
Converting a normal cross-connection service to an SNCP service may interrupt services.
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > SDH Service Configuration
from the Function Tree.
Step 2 Click Query to query the SDH services from the NE.
Step 3 In the Confirm dialog box, click OK. In the Operation Result dialog box, click Close.
Step 4 Select the desired normal service, click Display and choose Expand to Unidirectional from
the drop-down list. Right-click a desired normal service and choose Convert to SNCP from
the shortcut menu.
NOTE
Step 6 In the Create SNCP Service dialog box displayed, configure the protection service and click
OK.
NOTE
You need to perform the operation on the NEs that are set as the dual fed nodes and selective receiving
nodes on the source or sink, or in the cross protection subnets.
Step 7 Click Create. In the Create SDH Service dialog box displayed, configure a unidirectional
service from the service source board to the line board of another direction.
NOTE
You need to perform the operation on the NEs that are set as the dual fed nodes and selective receiving
nodes on the source or sink, or in the cross protection subnets.
Step 8 On the intermediate NE that protection services pass through, configure bidirectional pass-
through services between line boards.
NOTE
You need to perform this operation on all the intermediate NEs that protection services pass through.
----End
Prerequisites
l You are an NMS user with " NE operator" privilege or higher.
l The SNCP service has been created.
Impact on System
NOTICE
Changing an SNCP service to a normal service may interrupt services.
Procedure
Step 1 On the Main Topology, right-click the required NE and choose NE Explorer from the
shortcut menu.
Step 2 In the NE Explorer, click the NE and then choose Configuration > SDH Service
Configuration from the Function Tree.
Step 3 Optional: Click Query to check the information about the NE-side cross-connections.
Step 4 Click Display and choose Expand to Unidirectional to display the service one by one.
Right-click an SNCP service and choose Convert to Non-Protection Service from the
shortcut menu. The protection service is then deleted.
Step 5 Optional: To convert the service in the protection path into a non-protection service, select a
cross-connection in the Auto-Created Cross-Connection pane, right-click the SNCP service
and choose Convert to Non-Protection Service from the shortcut menu.
Step 7 Select a unidirectional service from the service source board to the line board of another
direction, and click Deactivate. In the Confirm dialog box displayed, click OK. In the
Operation Result dialog box displayed, click Close.
NOTE
You need to perform the operation on the NEs that are set as the dual fed nodes and selective receiving
nodes on the source or sink, or in the cross protection subnets.
Step 8 On the intermediate NE that protection services pass through, delete bidirectional pass-
through services between line boards.
----End
Prerequisites
l You are an NMS user with "Maintenance Group" privilege or higher.
l Trails in the protection subnets to be deleted must be deleted.
Procedure
Step 1 Choose Service > SDH Protection Subnet > Manage SDH Protection Subnet from the
Main Menu.
Step 2 Right-click the protection subnet to be deleted and choose Delete from the NM or Delete
from the NE or Delete All from the NM from the short-cut menu.
NOTE
Step 3 In the Operation Prompt dialog box, click Yes. After completion, the Result dialog box is
displayed.
NOTE
If Delete from the NE is selected, you need to confirm the operation once more.
----End
Prerequisites
l The NE data must be configured and fibers must be created properly.
l SDH protection subnets must be configured.
l You are an NMS user with "Maintenance Group" privilege or higher.
Procedure
Step 1 Choose Service > SDH Protection Subnet > Maintain SDH Protection Subnet from the
Main Menu. The SDH Protection Subnet Common Attributes dialog box is displayed.
Step 2 Select an SDH protection subnet from the left pane. The attribute information of the
protection subnet is displayed in the right pane.
Step 4 Click Query to query the parameters of the SDH protection subnet.
Step 5 Click the WTR Time(s) text box and enter a value.
NOTE
By default, enter 600. You can also enter a value from 300 to 720.
Step 7 Click Apply to display the Result prompt box. Then click Close.
----End
Prerequisites
l You are an NMS user with " NE operator" privilege or higher.
l The universal line board has been installed and its logical board has been created on the
NMS.
l An OCh path has been created.
Context
This configuration mode applies when all NEs on the network use universal line boards. It
does not apply when one segment of the OCh path uses an OTU board, OTN tributary board,
or OTN line board as a regeneration station or SDH cross-connections exist on the network.
Procedure
Step 1 Choose Service > WDM Trail > Configure Service Mapping from the main menu.
Step 2 Set the subnet type to Ring subnet or Chain subnet.
Step 3 Double-click the source and sink NEs for which service mapping needs to be set in the main
topology on the right side.
Step 4 Click Query Server Trails of Segment.
Step 5 Click Trail Name in the table on the left side and select the OCh path.
Step 7 Click Details. The details about service mapping are displayed in the lower right of the
window.
Step 8 Click Channel to select the channel for service mapping.
Step 9 Click Configure. The selected service mapping is created by the NMS.
----End
Follow-up Procedure
After service mapping has been configured, ODUk server layer paths are formed. Based on
these paths, users can configure SDH service paths and packet service paths directly.
12 Configuring Ethernet
Services(EoO/EoW/EoS)
This chapter describes how to configure Ethernet services based on the EoO, EoW and EoS
solution.This chapter describes how to configure Ethernet services based on the EoO and
EoW solution.
This section describes basic operations involved in Ethernet service configuration, such as
configuring the port on an Ethernet board, configuring Ethernet services, and managing the
MAC address table.
12.8 Parameters
This section describes how to configure parameters related to Ethernet services.
Private Ethernet private line (EPL) Both EPL and EVPL services are point-to-
line point (P2P) services, using a communication
service Ethernet virtual private line channel between two ends. The difference is
(EVPL) that, each EPL service exclusively uses
network resources, while multiple EVPL
services share network resources.
EPL Services
Each EPL service exclusively uses physical ports and line resources. It features high costs and
high security. As shown in Figure 12-1, the EPL service between the HQ of company A and
its branch, and the EPL service between the HQ of company B and its two branches are
transmitted using their own VCTRUNK channels. In this context, "VCTRUNK channel" is a
channel that carries Ethernet services. It can be a standard ODUk or VC container, or a virtual
container consisting of multiple concatenated standard containers.
HQ of HQ of
company A company B
NE 1
NE 2
NE 3
Branch of Branch of
company A company B
Branch of
company B
EVPL Services
Different EVPL services share the same physical ports or line resources. Therefore, the use of
EVPL services increases bandwidth utilization and reduces network costs. Different EVPL
services are distinguished by VLAN IDs or QinQ tags, ensuring high reliability. Figure 12-2
shows the application of EVPL services.
HQ of
company A HQ of
company B
NE 1
VLAN 10
VLAN 12
VLAN 11
Branch of NE 2
company A NE 3
Branch of
company B
Branch of
company B
As shown in Figure 12-2, EVPL services are classified into two types:
l EVPL services sharing the same PORT port: Data for multiple users is transmitted on the
same PORT port at a site and the data is isolated by VLAN IDs. As shown in Figure
12-2, the two EVPL services between the HQ of company B and its two branches are
identified as VLAN 11 and VLAN 12, each being transmitted over a specific
VCTRUNK channel.
l EVPL services sharing the same VCTRUNK port: Data for multiple users is transmitted
over the same VCTRUNK channel and the data is isolated by VLAN IDs. As shown in
Figure 12-2, between the HQ of company A and its branch, and between the HQ of
company B and one of its branches, two EVPL services are transmitted over the same
VCTRUNK channel and identified as VLAN 10 and VLAN 11.
EPLAN Services
Each EPLAN service exclusively uses physical ports and line resources. It features high costs
and high security. As shown in Figure 12-3, each NE has one or more IEEE 802.1d virtual
bridges (VBs). Each VB creates a forwarding table that is based on MAC addresses. The
forwarding table is updated periodically using the self-learning function of the system. The
incoming Ethernet services are transmitted through different ports based on the MAC
addresses stored in the forwarding table.
HQ of
company A
VCTRUNK2
VB PORT3
VCTRUNK1
NE 1
VCTRUNK2 VCTRUNK2
PORT3 VB VB PORT3
VCTRUNK1 VCTRUNK1
NE 2
NE 3
Branch of Branch of
company A company A
NOTE
EPLAN services cannot form a ring. Otherwise, a broadcast storm may occur. If necessary, run a
spanning tree protocol on the network or configure some ports mounted to VBs as SPOKEN ports as
required.
EVPLAN Services
EVPLAN services can dynamically share resources between multiple points after IEEE
802.1q VBs or IEEE 802.1ad VBs are established. Unlike EPLAN services, different
EVPLAN services share the same physical ports and line resources. Therefore, the use of
EVPLAN services increases bandwidth utilization and reduces network costs. Different
EVPLAN services are distinguished by VLAN IDs, ensuring high reliability. See Figure
12-4.
VCTRUNK2
PORT3 NE 1
VB
PORT4
VCTRUNK1 VCTRUNK2
VB PORT3
PORT4
VCTRUNK1
VLAN 10
VLAN 11 VLAN 11
Branch of NE 2 VLAN 10
company A NE 3 Branch of
company B
Branch of
company B Branch of
company A
NOTE
EVPLAN services cannot form a ring. Otherwise, a broadcast storm may occur. If necessary, run a
spanning tree protocol on the network or configure some ports mounted to VBs as SPOKEN ports as
required.
VLAN
VLANs cannot exchange their own Ethernet packets. Therefore, data can be isolated by
VLANs and network security is ensured.
To implement the VLAN function, the IEEE 802.1q protocol defines the Ethernet frame
format that contains the VLAN information. Compared with the ordinary Ethernet frame, the
frame with the format defined by the IEEE 802.1q protocol is added with a four-byte header.
See Figure 12-5 for more information.
Variable
6 bytes 6 bytes 4 bytes 2 bytes length 4 bytes
NOTE
The length of the data field is variable. The maximum length of the data field depends on the maximum
frame length that the equipment ports of support.
QinQ
Because Ethernet technology is deployed largely in carrier networks, which are metropolitan
area networks, implementing the 802.1Q VLAN to isolate and identifying users is limited to a
great extent. The VLAN tag domain that is defined in the IEEE 802.1Q has 12 bits, which can
represent 4K VLANs only. This cannot meet the requirements for identifying a large number
of users in metropolitan area networks. In order to increase the number of VLANs, the QinQ
technology is developed.
The QinQ technology is realized by adding a layer of 802.1Q tags to 802.1Q packets.
Therefore, the number of VLANs is increased to 4096 x 4096. With the development of the
metro Ethernet and the requirement of fine operation, QinQ double tags can be implemented
in other scenarios. The inner and outer tags can represent different information. The inner tag
(C-VLAN) represents the client and the outer tag (namely the S-VLAN) represents the
service. See Figure 12-6 for more information.
External ports on Ethernet boards (that is, external physical ports) are also referred to as
client-side ports or user-side ports, and are used to access the Ethernet services on the user
side.
Internal ports on Ethernet boards (that is, internal VCTRUNKs) are also referred to as system-
side ports or backplane-side ports in certain cases, and are used to encapsulate and map
services to the WDM side.
External VCTRUNK
port port
Backplane
Cross-connect
Service unit
L2 switching
processing
module
module
Cross-connect
unit
Ethernet Board
Table 12-2 Processing mode of Ethernet packets at ports with different tags
Directi Type of Processing Mode
on Ethernet
Packets Tag Access Hybrid
aware
Frames Discarde Adds the VLAN tags that contain the default
without d VLAN ID and VLAN priority and transparently
VLAN tags transmits Ethernet packets.
Egress Frames with Transpar Strips the VLAN l If the VLAN IDs contained
port VLAN tags ently tags and transmits in the data frames are
transmitt Ethernet packets. Default VLAN ID, strips
ed the VLAN tag and
transmits Ethernet packets.
l If the VLAN IDs contained
in the data frames are not
Default VLAN ID,
transparently transmits
Ethernet packets.
NOTE
The tag setting is valid only if the following conditions are met:
l The port type is UNI.
l The entry detection function is enabled. When the Ethernet switching board works in the Ethernet
transparent transmission state and when the entry detection function is disabled, the ports
transparently transmit the received Ethernet packets regardless of whether the Ethernet packets have
the VLAN tags.
Based on the tag aware, access, and hybrid features, adhere to the following principles when
setting the tag for a port:
l If it is certain that the data packets transmitted from the interconnected equipment have
the VLAN tags, set the local port to the tag aware mode.
l If it is certain that the data packets transmitted from the interconnected equipment do not
have the VLAN tags, set the local port to the access mode.
l If it is uncertain whether the data packets transmitted from the interconnected equipment
have the VLAN tags, set the local port to the hybrid mode.
12.2.2.2 Auto-negotiation
Ethernet rates and duplex modes vary according to the Ethernet port type. To prevent
interconnection failures between two Ethernet ports and simplify manual configuration, the
auto-negotiation mechanism is introduced.
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.
The working modes of the interconnected ports on the equipment at both ends must be the
same. Otherwise, the services are unavailable. If the working mode of the port on the opposite
equipment is full duplex and if the working mode of the port on the local equipment is auto-
negotiation, the local equipment works in the half-duplex mode. That is, the working modes
of the interconnected ports at both ends are different.
NOTE
When one port is in negotiation mode and the peer port is in non-negotiation mode, the auto-negotiation
mechanism can detects only the working rate but not the duplex mode of the peer port. In this scenario,
the auto-negotiation mechanism adheres to the "downward compatible" Ethernet negotiation rule and
selects the working mode of the lowest level . As a result, the half-duplex mode is negotiated for the
local port.
Hence, when the working mode of the port on the opposite equipment is full duplex, you need
to set working mode of the port on the local equipment to full duplex.
– Processes the received PAUSE frames but cannot transmit PAUSE frames.
l Disabled
The port does not transmit or process PAUSE frames.
Introduction
VLAN static multicast services consist of multiple EVPL or QinQ services of the same
VLAN, with the same source port but different sink ports.
A VLAN static multicast is created by links of the same type and with the same parameters
except the sink port parameter. The links are member links of the VLAN static multicast
group and the sink ports of the links are the member ports of the VLAN static multicast
group. On an Ethernet board, 2*k (1 k=1024) links are used as member links of the multicast
group.
NOTE
When services are deleted from a VLAN multicast group, the matching rules of multicast services will
be updated. Therefore, the deletion of one link from a VLAN multicast group will cause a few packets
on other links in the multicast group to be lost transiently.
Table 12-3 shows network properties of source/sink ports and supported VLAN multicast
Specification
l Table 12-4 shows the number of VLAN multicast groups and the maximum number of
sink ports for different boards.
l For VLAN multicast, only unidirectional services can be configured, and network
properties sink ports must be the same .
l The sink ports for VLAN multicast cannot be added to the LAG group.
TEM28 128 43
VB and LP
Virtual bridge (VB) is a unique concept used with Huawei products. For Ethernet data boards
that have Layer 2 switching capability, the switching domain can be divided into multiple sub-
switching domains. As a result, if no services are interconnected, different VBs cannot access
each other. Each VB has an independent configuration mode and uses an independent VLAN.
Different VBs can use the same VLAN.
A VB can contain a number of logical ports (LPs). By configuring the mounting relationship,
you can mount multiple MAC ports and VCTRUNK ports to the same VB.
Figure 12-8 shows the relationship between a VB, LP, external port, and VCTRUNK port.
Figure 12-8 Relationship between a VB, LP, external port, and VCTRUNK port
Ethernet Board
VB1
PORT1 LP1 LP4 VCTRUNK1
As shown in Figure 12-9, the same logical port may belong to one or more sub-switching domains with
different VLAN IDs. On the U2000, the same logical port can belong to multiple filtering tables for
different VLAN IDs.
Logical port
Ingress filtering The validity of VLAN tags is The validity of VLAN tags is
not checked. All the data frames checked. If the VLAN ID in the
that enter the bridge are VLAN tag is not the same as
considered as valid. defined in the VLAN filtering
table, the data frame is
discarded.
Data frame Queries the MAC address table Queries the MAC address table
forwarding mode to obtain the forwarding port to obtain the forwarding port
according to the destination according to the destination
MAC address of the data frame. MAC address and VLAN ID of
the data frame.
Broadcast range Forwards the broadcast data Forwards the broadcast frames
frames to all the ports of the to the forwarding ports defined
bridge. in the VLAN filtering table.
NOTE
To forward a Layer 2 switching service, a bridge must determine the MAC address. A bridge determines
the MAC address in one of the following ways: shared VLAN learning (SVL) or independent VLAN
learning (IVL).
l a: When the bridge adopts the SVL learning mode, the entry in the MAC address table is created
according to the source MAC address and the source port of the data frame. Entry is valid for all the
VLANs.
l b: When the bridge adopts the IVL learning mode, the entry in the MAC address table is created
according to the source MAC address, VLAN ID, and source port of the data frame. Entry is not
valid for all the VLANs.
Types of Bridges
As listed in Table 12-6 the Ethernet boards support three types of bridges.
l IEEE 802.1d bridge: This bridge does not check the contents of the VLAN tags that are
in the data frames and performs Layer 2 switching according to the destination MAC
addresses of the data frames.
l IEEE 802.1q bridge: This bridge supports isolation by using one layer of VLAN tags.
The bridge checks the contents of the VLAN tags that are in the data frames and
performs Layer 2 switching according to the destination MAC addresses and VLAN IDs.
l IEEE 802.1ad bridge: This bridge supports data frames with two layers of VLAN tags
and uses the outer S-VLAN tag to isolate data frames. It supports C-aware and S-aware
ports only. The bridge checks the contents of the VLAN tags that are in the data frames
and performs Layer 2 switching according to the destination MAC address and S-VLAN
IDs of the data frames.
VLAN filtering table. Before the packets leave the C-aware port, the S-VLAN tag is
stripped.
l Adding the S-VLAN tag based on the port and C-VLAN: The entry detection is
performed for the packets that enter the C-aware port. Then the corresponding S-VLAN
tags are added to the packets according to the mapping relationship between the C-
VLAN tags and the S-VLAN tags of the packets. If the mapping relationship does not
exist, the packets are discarded. After the S-VLAN tags are added, the packets enter the
bridge, where the packets are forwarded according to the S-VLAN filtering table. Before
the packets leave the C-aware port, the S-VLAN tag is stripped.
NOTE
l The same C-aware port supports different C-VLAN tags being mapped to different S-VLAN
tags but does not support the same C-VLAN tag being mapped to multiple S-VLAN tags.
l Performing port mounting based on the port: The packets that enter the S-aware port are
not filtered. Instead, the S-VLAN switch is performed directly. The packets must have
the S-VLAN tags. Otherwise, the packets are discarded. When the packets leave the S-
aware port, the packets are transparently transmitted.
l Performing port mounting based on the port and the S-VLAN: The entry filtering is
performed according to the preset S-VLAN tag. The packets that do not belong to the S-
VLAN are discarded. Then the packets are forwarded according to the S-VLAN filtering
table. When the packets leave the S-aware port, the packets are transparently transmitted.
In the case of the four operation types, the following conditions must be met before the
packets leave a port:
l The port is contained in the S-VLAN filtering table that is created by the user.
l The S-VLAN ID corresponding to the port must be specified when the user manually
mounts the port to the bridge.
– In the case of a C-VLAN port, the S-VLAN ID corresponding to the port is the S-
VLAN ID that is added when the packets enter the port.
– In the case of an S-VLAN port, the S-VLAN ID corresponding to the port is the S-
VLAN ID that is set when the user mounts the port to the bridge. If the S-aware
port is mounted based on the port, the S-VLAN ID is considered to contain all the
legal S-VLAN IDs.
Figure 12-10 Flowchart for configuring Ethernet services based on the EoO solution
1
Configure Configure Configure Configure
Configure Configure Configure EPLAN EVPLAN EVPLAN
Ethernet EVPL (VLAN) EVPL (QinQ)
EPL services (IEEE 802.1d (IEEE 802.1q (IEEE 802.1ad
services services services bridge) services bridge) services bridge) services
2
Configure the Configure Configure Configure Configure Configure Configure
working mode external external external external external external
of ClientLP Ethernet ports Ethernet ports Ethernet ports Ethernet ports Ethernet ports Ethernet ports
ports
3
Configure Configure Configure Configure Configure Configure
Configure the internal internal internal internal internal internal
mapping protocol Ethernet ports Ethernet ports Ethernet ports Ethernet ports Ethernet ports Ethernet ports
for VCTRUNK
ports
Modify the
QinQ type
area
Mandatory
Optional
Table 12-7 Procedure for configuring Ethernet services based on the EoO solution
N Action Description
o.
1 Configure Mandatory
Ethernet services. Configure required Ethernet services. For details, see Procedure
for Configuring Ethernet Services.
N Action Description
o.
Figure 12-11 Flowchart for configuring Ethernet services based on the EoW solution
1
Configure Configure Configure Configure
Ethernet Configure Configure Configure EPLAN EVPLAN EVPLAN
EPL services EVPL (VLAN) EVPL (QinQ) (IEEE 802.1d (IEEE 802.1q (IEEE 802.1ad
services services services bridge) services bridge) services bridge) services
2
Configure Configure Configure Configure Configure Configure
Create GE/10GE external external external external external external
inter-board cross- Ethernet ports Ethernet ports Ethernet ports Ethernet ports Ethernet ports Ethernet ports
connections
Modify the
QinQ type
area
Mandatory
Optional
Table 12-8 Procedure for configuring Ethernet services based on the EoW solution
N Action Description
o.
1 Configure Mandatory
Ethernet services. Configure required Ethernet services. For details, see Procedure
for Configuring Ethernet Services.
N Action Description
o.
Figure 12-12 Flowchart for configuring Ethernet services based on the EoS solution
1
Configure Configure Configure Configure
Configure Configure Configure EPLAN EVPLAN EVPLAN
Ethernet EPL services EVPL (VLAN) EVPL (QinQ) (IEEE 802.1d (IEEE 802.1q (IEEE 802.1ad
services services bridge) services bridge) services bridge) services
services
2
Configure Configure Configure Configure Configure Configure
Create cross- external external external external external external
connection for Ethernet ports Ethernet ports Ethernet ports Ethernet ports Ethernet ports Ethernet ports
the Ethernet
services
Configure Configure Configure Configure Configure Configure
internal internal internal internal internal internal
Ethernet ports Ethernet ports Ethernet ports Ethernet ports Ethernet ports Ethernet ports
Modify the
QinQ type
area
Mandatory
Optional
Table 12-9 Procedure for configuring Ethernet services based on the EoS solution
N Action Description
o.
1 Configure Mandatory
Ethernet services. Configure required Ethernet services. For details, see Procedure
for Configuring Ethernet Services.
Table 12-10 Difference in the procedures for configuring different Ethernet services
Action Para Difference
meter
Invol
ved
Configure Flow Setting this parameter is mandatory only in the procedure for
external/ Contr configuring EPL services.
internal ol
Ethernet
ports. Tag l For EPL services, set Entry Detection to Disabled.
Attrib l For EPLAN (IEEE 802.1d bridge), EVPL (VLAN), and
utes EVPLAN (IEEE 802.1q bridge) services, set Entry
Detection to Enabled. Set TAG, Default VLAN ID, and
VLAN Priority according to the plan.
l For EVPL (QinQ) and EVPLAN (IEEE 802.1ad bridge)
services, Tag Attributes is unnecessary.
Netwo l For EPL, EPLAN (IEEE 802.1d bridge), EVPL (VLAN), and
rk EVPLAN (IEEE 802.1q bridge) services, set Port Attributes
Attrib to UNI.
utes l For EVPL (QinQ) and EVPLAN (IEEE 802.1ad bridge)
services, set Port Attributes to C-Aware or S-Aware.
Modify the - This operation is required only in the procedures for configuring
QinQ type EVPL (QinQ) and EVPLAN (IEEE 802.1ad bridge) services.
area. This operation is optional.
Manage the - These operations are required only in the procedures for
MAC address configuring EPLAN (IEEE 802.1d bridge), EVPLAN (IEEE
table. 802.1q bridge), and EVPLAN (IEEE 802.1ad bridge) services.
These operations are mandatory.
Modify the
hub/spoken
attribute.
Create the - This operation is required only in the procedures for configuring
VLAN filter EVPLAN (IEEE 802.1q bridge) and EVPLAN (IEEE 802.1ad
table. bridge) services. This operation is mandatory.
The following describes the procedures for configuring EPL services, EVPL (VLAN), EVPL
(QinQ), EPLAN (IEEE 802.1d bridge), EVPLAN (IEEE 802.1q bridge), and EVPLAN (IEEE
802.1ad bridge) services:
Click the Flow Control tab to set parameters if the flow control
function is enabled on the external equipment to which the
Ethernet port is connected:
l When the external equipment uses the non-auto-negotiation
flow 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 Autonegotiation Flow Control Mode to
Enable Symmetric/Dissymmetric Flow Control.
N Action Description
o.
N Action Description
o.
N Action Description
o.
N Action Description
o.
Table 12-14 Procedure for configuring EPLAN (IEEE 802.1d bridge) services
N Action Description
o.
N Action Description
o.
4 Manage Create Required if Set certain MAC address entries not to age.
the MAC VLAN The parameters need to be set according to the network
address unicast. plan.
table.
Create a Required when the use of EPLAN services needs to be
blacklist disabled on certain MAC address hosts.
entry of a The parameters need to be set according to the network
MAC plan.
address.
N Action Description
o.
5 Modify the hub/spoken This operation is mandatory when you need to change
attribute. the port mounted to the bridge, the enable/disable status
of the mounted port, and the hub/spoken attribute of the
mounted port.
Table 12-15 Procedure for configuring EVPLAN (IEEE 802.1q bridge) services
N Action Description
o.
N Action Description
o.
5 Manage Create Required if Set certain MAC address entries not to age.
the MAC VLAN The parameters need to be set according to the network
address unicast. plan.
table.
Create a Required when the use of EPLAN services needs to be
blacklist disabled on certain MAC address hosts.
entry of a The parameters need to be set according to the network
MAC plan.
address.
6 Modify the hub/spoken This operation is mandatory when you need to change
attribute. the port mounted to the bridge, the enable/disable status
of the mounted port, and the hub/spoken attribute of the
mounted port.
Table 12-16 Procedure for configuring EVPLAN (IEEE 802.1ad bridge) services
N Action Description
o.
4 Create the VLAN filter Required if you set Bridge Switch Mode to IVL/
table. Ingress Filter Enable.
Set VLAN ID(e.g.1,3-6) and Selected forwarding ports
according to the network plan.
5 Manage Create Required if Set certain MAC address entries not to age.
the MAC VLAN The parameters need to be set according to the network
unicast. plan.
N Action Description
o.
6 Modify the hub/spoken This operation is mandatory when you need to change
attribute. the port mounted to the bridge, the enable/disable status
of the mounted port, and the hub/spoken attribute of the
mounted port.
Service Requirement
See Figure 12-13 for the service requirement networking diagram. The NE1, NE2, and NE3
form a ring network. All the NEs function as OADM stations. The service requirements are as
follows:
There is Ethernet communication between User1 and User2. In addition, a bidirectional EPL
service exists between stations NE1 and NE2. The working mode of the bidirectional EPL
service is set to auto-negotiation, and the bidirectional EPL service does not support the
VLAN function.
NM
NE3
IU1- IU1-
TEM28 NE1 NE2 TEM28
IU3- IU3-
TN53NS2 TN53NS2
User1 User 2
VCTRUNK1 VCTRUNK1
PORT7 PORT7
NG WDM
VCTRUNCK
equipment
IU1-TEM28 IU3-TN53NS2
OCH:1-ODU2:1-ODUflex:(1~2)
PORT7 OCH:1-ODU2:1
201(ClientLP1/
User1 VCTRUNK1 ClientLP1)-1
OCH:1-ODU2:1-ODU1:(1~4) IN/OUT
OCH:1-ODU2:1-ODU1:(1~4)-ODU0:(1~2)
OCH:1-ODU2:1-ODU0:(1~8)
NE2
IU1-TEM28 IU3-TN53NS2
OCH:1-ODU2:1-ODUflex:(1~2)
OCH:1-ODU2:1
PORT7 201(ClientLP1/
User2 VCTRUNK1 ClientLP1)-1 OCH:1-ODU2:1-ODU1:(1~4) IN/OUT
OCH:1-ODU2:1-ODU1:(1~4)-ODU0:(1~2)
OCH:1-ODU2:1-ODU0:(1~8)
Prerequisite
You must read and understand the contents of Procedure for Configuring Ethernet Services
Based on the EoO Solution.
Port Enabled PORT7: Enabled The EPL service of User1 occupies the
external port PORT7, and the enabling
status of PORT7 is set to Enabled.
MAC Loopback PORT7: Non- The MAC loopback setting is used for
Loopback fault diagnosis. When configuring a
service, set this parameter to Non-
Loopback.
PHY Loopback PORT7: Non- The PHY loopback setting is used for
Loopback fault diagnosis. When configuring a
service, set this parameter to Non-
Loopback.
4. Click the Flow Control tab. Double-click the Autonegotiation Flow Control Mode
value of the PORT7 port and choose Enable Symmetric/Dissymmetric Flow Control
from the drop-down list.
5. Click the TAG Attributes tab. After setting the parameter on this tab page, click Apply.
For details on parameter settings, see 12.8.5 Parameters: TAG Attributes.
Parameter Value Description
Entry Detection Disabled The port does not identify tags in data
packets.
6. Click the Network Attributes tab. After setting the parameter on this tab page, click
Apply. For details on parameter settings, see 12.8.6 Parameters: Network Attributes.
Parameter Value Description
3. Click the TAG Attributes tab. After setting the parameter on this tab page, click Apply.
For details on parameter settings, see 12.8.5 Parameters: TAG Attributes.
Parameter Value Description
Entry Detection Disabled The port does not identify tags in data
packets.
4. Click OK, and the created Ethernet private line service is displayed on the interface.
----End
The TEM28 board processes service differently when working in different modes. It can
work in either of the following modes:
Step 3 Configure cross-connections between the TEM28 board and TN53NS2 board.
1. In the NE Explorer, select an NE and choose Configuration > WDM Service
Management in the function tree.
2. Click the WDM Cross-Connection Configuration tab, and click New. The Create
Cross-Connection Service dialog box is displayed.
Parameter Value
Level Set the parameter value according to the Port Working Mode
value. If Port Working Mode is set to ODU0 non-convergence
mode, set Level to ODU0.
Service Type When Level is set to ODUflex, this parameter must be set to
PACKET.
Direction Bidirectional
Source Optical 1
Channel(e.g.1,3-6)
Parameter Value
Sink Optical The system automatically allocate the sink optical channel. You
Channel(e.g.1,3-6) do not need to set it.
3. Click OK.
----End
Prerequisites
l You are an NMS user with "Administrators" privilege.
l Inter- and intra-site physical and logical fiber connections have been correctly created.
l OCh trails have been searched out or created.
Procedure
1. Create a client trail as the server trail of an Ethernet private line (EPL) service.
a. From the main menu, choose Service > WDM Trail > Create WDM Trail.
b. Set the following parameters in the Create WDM Trail window:
n Level: Client
n Direction: Bidirectional
n Rate: GE
c. Set the source and sink ports based on the network plan.
i. Click Browse on the right of the Source text box. In the Select Board Port-
Source dialog box that is displayed, select the desired board as the source
board of an end-to-end (E2E) service trail.
ii. Click Working Mode Settings to set the working mode of the ClientLP1 port
to ODU0 non-convergence mode (Any->ODU0).
iii. Set the service access port to 101(AP1).
e. Click Apply. The Result dialog box is displayed, indicating that the operation is
successful. Click Close.
2. Create a bidirectional EPL trail.
a. From the main menu, choose Service > WDM Trail > Create EPL.
b. Set Port Usage Strategy to Port for the source and sink.
NOTE
d. Specify one existing client trail as the server trail of the EPL service and click Next.
e. Set port attributes in the Port Attribute Settings area as described in the following
table.
Port Type NE1-PORT7: UNI When Port Type is set to UNI for a
NE2-PORT7: UNI port, the port can identify the tag
attributes (including Tag Aware,
NE1-VCTRUNK1: Access, and Hybrid) of 802.1Q
UNI protocol packets.
NE2-VCTRUNK1:
UNI
Working Mode NE1-PORT7: Auto- The access device of the EPL service
Negotiation between User1 and User2 supports
NE2-PORT7: Auto- auto-negotiation. Therefore,
Negotiation Working Mode is set to Auto-
Negotiation.
f. Optional: Set the information about the EPL service trail. For example, set Name
and Order No..
g. Optional: Deselect the Activate the trail check box if the created trail does not
need to be delivered to an NE.
h. Click Finish. The Result dialog box is displayed, indicating that the operation is
successful.
Service Requirement
In the network shown in Figure 12-15, NE1, NE2, and NE3 form a ring network. All the NEs
are OADM NEs. The service requirement is as follows:
Two branches of user A are located at NE1 and NE2 and need to communicate with each
other.
Two branches of user B are located at NE1 and NE2 and need to communicate with each
other.
One bidirectional EVPL (VLAN) service needs to be configured between NE1 and NE2. The
working mode is auto-negotiation.
NM
NE3
A1
IU1- A2
NE1 NE2 IU1-
TEM28 TEM28
IU3- IU3-
TN53NS2 TN53NS2 B2
B1
PORT7 PORT7
VCTRUNK1
VCTRUNK1
PORT8 PORT8
NG WDM VCTRUNCK
equipment
IU1-TEM28 IU3-TN53NS2
OCH:1-ODU2:1-ODUflex:(1~2)
PORT7 OCH:1-ODU2:1
UserA1 201(ClientLP1/ IN/OUT
VCTRUNK1 OCH:1-ODU2:1-ODU1:(1~4)
UserB1 ClientLP1)-1
PORT8 OCH:1-ODU2:1-ODU1:(1~4)-ODU0:(1~2)
OCH:1-ODU2:1-ODU0:(1~8)
NE2
IU1-TEM28 IU3-TN53NS2
OCH:1-ODU2:1-ODUflex:(1~2)
PORT7 OCH:1-ODU2:1
UserA2 201(ClientLP1/ IN/OUT
VCTRUNK1 OCH:1-ODU2:1-ODU1:(1~4)
UserB2 ClientLP1)-1 OCH:1-ODU2:1-ODU1:(1~4)-ODU0:(1~2)
PORT8
OCH:1-ODU2:1-ODU0:(1~8)
Prerequisite
You must read and understand the contents of Procedure for Configuring Ethernet Services
Based on the EoO Solution.
Working Mode PORT7: Auto- The equipment that receives the EVPL
Negotiation (VLAN) service support the
PORT8: Auto- autonegotiation mode. Therefore, set
Negotiation Working Mode to Auto-Negotiation.
MAC Loopback PORT7: Non- The MAC loopback setting is used for
Loopback fault diagnosis. When configuring a
PORT8: Non- service, set this parameter to Non-
Loopback Loopback.
PHY Loopback PORT7: Non- The PHY loopback setting is used for
Loopback fault diagnosis. When configuring a
PORT8: Non- service, set this parameter to Non-
Loopback Loopback.
4. Click the TAG Attributes tab. After setting the parameter on this tab page, click Apply.
For details on parameter settings, see 12.8.5 Parameters: TAG Attributes.
Parameter Value Description
5. Click the Network Attributes tab. After setting the parameter on this tab page, click
Apply. For details on parameter settings, see 12.8.6 Parameters: Network Attributes.
Step 2 On the TEM28 board on NE1, configure the internal Ethernet port shared by the bidirectional
services between userA1 and userA2, and the bidirectional services between userB1 and
userB2.
1. In the NE Explorer, select the desired board and then choose Configuration > Ethernet
Interface Management > Ethernet Interface from the Function Tree. Then, select
Internal Port.
2. Click the Network Attributes tab. After setting the parameter on this tab page, click
Apply. For details on parameter settings, see 12.8.6 Parameters: Network Attributes.
3. Click the TAG Attributes tab. After setting the parameter on this tab page, click Apply.
For details on parameter settings, see 12.8.5 Parameters: TAG Attributes.
Entry Detection VCTRUNK1: The port does not identify tags in data
Enabled packets.
Step 3 On the TEM28 board on NE1, configure the EVPL (VLAN) service between userA1 and
userA2, and the EVPL (VLAN) service between userB1 and userB2. You need to configure
the service between ports PORT7 and VCTRUNK1 and the service between ports PORT8 and
VCTRUNK1.
1. In the NE Explorer, select the desired board and then choose Configuration > Ethernet
Service > Ethernet Line Service from the Function Tree. Click the EPL Service tab.
2. Click New at the bottom of the window. The Create Ethernet Line Service dialog box
is displayed.
3. Enter the attributes of the Ethernet private line service in the dialog box. For details on
parameter settings, see 12.8.7 Parameters: Ethernet Line Service.
Parameter Value Description
Sink C-VLAN 100 (when the source Sets the source C-VLAN.
(e.g.1,3-6) is port PORT7) NOTE
200 (when the source For EVPL services, sink C-VLAN tags for
different sources ports must be different.
is port PORT8)
4. Click OK, and the created Ethernet private line service is displayed on the interface.
----End
Step 3 Configure cross-connections between the TEM28 board and TN53NS2 board.
1. In the NE Explorer, select an NE and choose Configuration > WDM Service
Management in the function tree.
2. Click the WDM Cross-Connection Configuration tab, and click New. The Create
Cross-Connection Service dialog box is displayed.
Parameter Value
Level Set the parameter value according to the Port Working Mode
value. If Port Working Mode is set to ODU0 non-convergence
mode, set Level to ODU0.
Service Type When Level is set to ODUflex, this parameter must be set to
PACKET.
Direction Bidirectional
Source Optical 1
Channel(e.g.1,3-6)
Parameter Value
Sink Optical The system automatically allocate the sink optical channel. You
Channel(e.g.1,3-6) do not need to set it.
3. Click OK.
----End
Prerequisites
l You are an NMS user with "Administrators" privilege.
l Inter- and intra-site physical and logical fiber connections have been correctly created.
l OCh trails have been searched out or created.
Procedure
1. Create a client trail as the server trail of an Ethernet private line (EPL) service.
a. From the main menu, choose Service > WDM Trail > Create WDM Trail.
b. Set the following parameters in the Create WDM Trail window:
n Level: Client
n Direction: Bidirectional
n Rate: GE
c. Set the source and sink ports based on the network plan.
i. Click Browse on the right of the Source text box. In the Select Board Port-
Source dialog box that is displayed, select the desired board as the source
board of an end-to-end (E2E) service trail.
ii. Click Working Mode Settings to set the working mode of the ClientLP1 port
to ODU0 non-convergence mode (Any->ODU0).
iii. Set the service access port to 101(AP1).
e. Click Apply. The Result dialog box is displayed, indicating that the operation is
successful. Click Close.
2. Create an Ethernet private line (EPL) service trail between UserA1 and UserA2.
a. From the main menu, choose Service > WDM Trail > Create EPL.
b. Set the source and sink of the EPL service trail and set Port Usage Strategy to
Port+VLAN for the source and sink.
NOTE
d. Specify one existing client trail as the server trail of the EPL service and click Next.
e. Set port attributes in the Port Attribute Settings area as described in the following
table.
Default VLAN NE1-PORT7: 100 Based on the service plan, the VLAN
NE2-PORT7: 100 ID of the EPL service between
UserA1 and UserA2 is 100.
Port Type NE1-PORT7: UNI When Port Type is set to UNI for a
NE2-PORT7: UNI port, the port can identify the tag
attributes (including Tag Aware,
NE1-VCTRUNK1: Access, and Hybrid) of 802.1Q
UNI protocol packets.
NE2-VCTRUNK1:
UNI
Working Mode NE1-PORT7: Auto- The access device of the EPL service
Negotiation between UserA1 and UserA2
NE2-PORT7: Auto- supports auto-negotiation. Therefore,
Negotiation Working Mode is set to Auto-
Negotiation.
f. Optional: Set the information about the EPL service trail. For example, set Name
and Order No..
g. Optional: Deselect the Activate the trail check box if the created trail does not
need to be delivered to an NE.
h. Click Finish. The Result dialog box is displayed, indicating that the operation is
successful.
3. Refer to 2 to create an EPL service trail between UserB1 and UserB2, and set the port
attributes as described in the following table.
Parameter Value in This Description
Example
Default VLAN NE1-PORT8: 200 Based on the service plan, the VLAN
NE2-PORT8: 200 ID of the EPL service between UserB1
and UserB2 is 200.
Port Type NE1-PORT8: UNI When Port Type is set to UNI for a
NE2-PORT8: UNI port, the port can identify the tag
attributes (including Tag Aware,
NE1-VCTRUNK1: Access, and Hybrid) of 802.1Q protocol
UNI packets.
NE2-VCTRUNK1:
UNI
Working Mode NE1-PORT8: Auto- The access device of the EPL service
Negotiation between UserB1 and UserB2 supports
NE2-PORT8: Auto- auto-negotiation. Therefore, Working
Negotiation Mode is set to Auto-Negotiation.
Service Requirements
In the network shown in Figure 12-17, NE1, NE2, and NE3 form a ring network. All the NEs
are OADM NEs. The service requirement is as follows:
Two branches of user A are located at NE1 and NE2 and need to communicate with each
other.
Two branches of user B are located at NE1 and NE2 and need to communicate with each
other.
The services of user A need to be isolated from the services of user B.
One bidirectional EVPL (QinQ) service needs to be configured between NE1 and NE2. The
working mode is auto-negotiation. NE1 adds the S-VLAN1 tag to the received frames for user
A and the S-VLAN2 tag to the received frames for user B. After stripping the S-VLAN1 and
S-VLAN2 tags from the frames, NE2 sends the frames to user A and user B.
NM
NE3
NG WDM
VCTRUNCK
equipment
NE2
IU1-TEM28 IU3-TN53NS2
C-VLAN1 OCH:1-ODU2:1-ODUflex:(1~2)
PORT7 S-VLAN1 OCH:1-ODU2:1
UserA2 201(ClientLP1/ IN/OUT
VCTRUNK1 OCH:1-ODU2:1-ODU1:(1~4)
UserB2 ClientLP1)-1 OCH:1-ODU2:1-ODU1:(1~4)-ODU0:(1~2)
PORT8 S-VLAN2
C-VLAN1 OCH:1-ODU2:1-ODU0:(1~8)
Prerequisite
You must read and understand the contents of Procedure for Configuring Ethernet Services
Based on the EoO Solution.
Working Mode PORT7: Auto- The equipment for receiving the EVPL
Negotiation (QinQ) service support the auto-negotiation
PORT8: Auto- mode. Therefore, set Working Mode to
Negotiation Auto-Negotiation.
Maximum Frame PORT7: 1522 In general, the default value 1522 is used.
Length PORT8: 1522
MAC Loopback PORT7: Non- The MAC loopback setting is used for fault
Loopback diagnosis. When configuring a service, set
PORT8: Non- this parameter to Non-Loopback.
Loopback
PHY Loopback PORT7: Non- The PHY loopback setting is used for fault
Loopback diagnosis. When configuring a service, set
PORT8: Non- this parameter to Non-Loopback.
Loopback
4. Click the Network Attributes tab. After setting the parameter on this tab page, click
Apply. For details on parameter settings, see 12.8.6 Parameters: Network Attributes.
Parameter Value Description
Step 2 On the TEM28 board on NE1, configure the internal Ethernet port shared by the bidirectional
services between userA1 and userA2, and the bidirectional services between userB1 and
userB2.
1. In the NE Explorer, select the desired board and choose Configuration > Ethernet
Interface Management > Ethernet Interface from the Function Tree. Then select
Internal Port.
2. Click the Network Attributes tab. After setting the parameter on this tab page, click
Apply. For details on parameter settings, see 12.8.6 Parameters: Network Attributes.
Step 3 On the TEM28 board on NE1, configure the EVPL (QinQ) service between userA1 and
userA2, and the EVPL (QinQ) service between userB1 and userB2. You need to configure the
service between ports PORT7 and VCTRUNK1 and the service between ports PORT8 and
VCTRUNK1.
1. In the NE Explorer, select the desired board and choose Configuration > Ethernet
Service > Ethernet Line Service from the Function Tree. Click the EPL Service tab.
2. Select Display QinQ Shared Service on the lower-right pane.
3. Click New at the bottom of the window. The Create Ethernet Line Service dialog box
is displayed.
4. Enter the attributes of the Ethernet private line service in the dialog box. For details on
parameter settings, see 12.8.7 Parameters: Ethernet Line Service.
Parameter Value Description
Source Port PORT7, PORT8 Indicates the name of the source port.
Sink S-VLAN 100 (when the source Adds the S-VLAN tag.
is port PORT7)
200 (when the source
is port PORT8)
5. Click OK, and the created Ethernet private line service is displayed on the interface.
----End
The TEM28 board processes service differently when working in different modes. It can
work in either of the following modes:
Step 3 Configure cross-connections between the TEM28 board and TN53NS2 board.
1. In the NE Explorer, select an NE and choose Configuration > WDM Service
Management in the function tree.
2. Click the WDM Cross-Connection Configuration tab, and click New. The Create
Cross-Connection Service dialog box is displayed.
Parameter Value
Level Set the parameter value according to the Port Working Mode
value. If Port Working Mode is set to ODU0 non-convergence
mode, set Level to ODU0.
Service Type When Level is set to ODUflex, this parameter must be set to
PACKET.
Direction Bidirectional
Parameter Value
Source Optical 1
Channel(e.g.1,3-6)
Sink Optical The system automatically allocate the sink optical channel. You
Channel(e.g.1,3-6) do not need to set it.
3. Click OK.
----End
Service Requirement
On the network shown in Figure 12-19, the service requirements are as follows:
l Three branches (F1, F2, and F3) of user F are located at NE1, NE2, and NE4. F1 needs
to communicate with F2 and F3.
l The Ethernet equipment of user F provides Ethernet optical ports that work in auto-
negotiation mode and support VLANs. VLAN IDs and the number of VLANs, however,
are unknown and may be changed.
NOTE
The application scenarios where one branch needs to communicate with other branches are as follows:
l Branches F2 and F3 need to communicate with each other.
l Branches F2 and F3 do not need to communicate with each other.
Figure 12-19 Networking diagram for configuring EPLAN services (IEEE 802.1d bridge)
NM
NE3
IU1- IU1-
TEM28 TEM28
NE2 NE4
IU3- IU3-
TN53NS2 NE1
TN53NS2
F2 F3
The access nodes NE2 and NE4 are configured with one TEM28 board each. The EPL
services are configured to be transparently transmitted from NE2 and NE4 to NE1.
Figure 12-20 shows the signal flow of the EPLAN services (IEEE 802.1d bridge).
IU3-TN53NS2
IU1-TEM28 OCH:1-ODU2:1-ODUflex:(1~2)
OCH:1-ODU2:1
PORT7
201(ClientLP1/ OCH:1-ODU2:1-ODU1:(1~4)
User F2 VCTRUNCK1 IN/OUT
ClientLP1)-1
OCH:1-ODU2:1-ODU1:(1~4)-ODU0:(1~2)
OCH:1-ODU2:1-ODU0:(1~8)
NE1
IU3-TN53NS2
IU1-TEM28
OCH:1-ODU2:1-ODUflex:(1~2)
OCH:1-ODU2:1
201(ClientLP1/ OCH:1-ODU2:1-ODU1:(1~4) IN/OUT
VB VCTRUNCK1 OCH:1-ODU2:1-ODU1:(1~4)-ODU0:(1~2)
ClientLP1)-1
PORT7 OCH:1-ODU2:1-ODU0:(1~8)
User F1 OCH:1-ODU2:1-ODUflex:(1~2)
OCH:1-ODU2:1
202(ClientLP2/ OCH:1-ODU2:1-ODU1:(1~4) IN/OUT
VCTRUNCK2 OCH:1-ODU2:1-ODU1:(1~4)-ODU0:(1~2)
ClientLP2)-1
OCH:1-ODU2:1-ODU0:(1~8)
IU4-TN53NS2
NE4
IU3-TN53NS2
IU1-TEM28
OCH:1-ODU2:1-ODUflex:(1~2)
OCH:1-ODU2:1
PORT7
201(ClientLP1/ OCH:1-ODU2:1-ODU1:(1~4)
User F3 VCTRUNCK1 IN/OUT
ClientLP1)-1
OCH:1-ODU2:1-ODU1:(1~4)-ODU0:(1~2)
OCH:1-ODU2:1-ODU0:(1~8)
Prerequisite
You must read and understand the contents of Procedure for Configuring Ethernet Services
Based on the EoO Solution.
MAC Loopback PORT7: Non- The loopback setting is used for fault
Loopback diagnosis. When configuring a service,
set this parameter to Non-Loopback.
PHY Loopback PORT7: Non- The loopback setting is used for fault
Loopback diagnosis. When configuring a service,
set this parameter to Non-Loopback.
4. Click the TAG Attributes tab. After setting the parameter on this tab page, click Apply.
For details on parameter settings, see 12.8.5 Parameters: TAG Attributes.
Parameter Value Description
5. Click the Network Attributes tab. After setting the parameter on this tab page, click
Apply. For details on parameter settings, see 12.8.6 Parameters: Network Attributes.
NOTE
The external ports on the Ethernet boards at the source and sink ends of the accessed Ethernet
service must be set to Access, and the default VLAN ID must be set to the same value.
Step 2 Set the attributes of the internal port used by the service of TEM28 board.
1. In the NE Explorer, select the board and choose Configuration > Ethernet Interface
Management > Ethernet Interface from the Function Tree.
2. Select Internal Port.
3. Click the Network Attributes tab. After setting the parameter on this tab page, click
Apply. For details on parameter settings, see Description of the Network Attributes
Parameter.
Parameter Value Description
4. Click the TAG Attributes tab. After setting the parameter on this tab page, click Apply.
For details on parameter settings, see Description of the TAG Attributes Parameter.
Parameter Value Description
TAG VCTRUNK1: Tag For the internal port, you do not need to
Aware configure the tag header but retain the
default value, namely Tag Aware.
2. Click New.
3. Set the parameters in the Create Ethernet LAN Service dialog box that is displayed.
For details on parameter settings, see 12.8.8 Parameters: Ethernet LAN Service.
Parameter Value in Description
This
Example
VB Type 802.1d The IEEE 802.1d MAC bridge learns and forwards
the packets according to the MAC addresses of the
user packets. The information in the VLAN tags of
the user packets, however, is not considered in the
learning and forwarding process. The IEEE 802.1d
MAC bridge is used when the entire information of
the VLANs used by the client cannot be learned or
when the data between the VLANs of the client does
not need to be isolated.
Bridge SVL/Ingress When the bridge adopts the SVL learning mode, all
Switch Mode Filter Disable the VLANs share the same MAC address table. That
is, the bridge learns and forwards the packets
according to the MAC address of the user packets
only. The information in the VLAN tags of the user
packets, however, is not considered in the learning
and forwarding process.
Bridge SVL -
Learning
Mode
Ingress Filter Disabled The IEEE 802.1d MAC bridge does not detect the
VLAN tags of the received packets.
MAC Enabled -
Address Self-
learning
If normal communication is required between user F2 and user F3, skip this step.
1. Select the created bridge and click the Service Mount tab.
2. Change the Hub/Spoke attribute of the port mounted to the bridge. After setting the
parameters, click Apply.
Parameter Value Description
----End
Step 3 Configure cross-connections between the TEM28 board and TN53NS2 board.
1. In the NE Explorer, select an NE and choose Configuration > WDM Service
Management in the function tree.
2. Click the WDM Cross-Connection Configuration tab, and click New. The Create
Cross-Connection Service dialog box is displayed.
Parameter Value
Level Set the parameter value according to the Port Working Mode
value. If Port Working Mode is set to ODU0 non-convergence
mode, set Level to ODU0.
Service Type When Level is set to ODUflex, this parameter must be set to
PACKET.
Direction Bidirectional
Source Optical 1
Channel(e.g.1,3-6)
Sink Optical The system automatically allocate the sink optical channel. You
Channel(e.g.1,3-6) do not need to set it.
3. Click OK.
----End
Prerequisites
l You are an NMS user with "Administrators" privilege.
l Inter- and intra-site physical and logical fiber connections have been correctly created.
l OCh trails have been searched out or created.
Procedure
1. Create a client trail between UserF1 and UserF2 as the server trail of an Ethernet private
LAN (EPLAN) service.
a. From the main menu, choose Service > WDM Trail > Create WDM Trail.
b. Set the following parameters in the Create WDM Trail window:
n Level: Client
n Direction: Bidirectional
n Rate: GE
c. Set the source and sink ports based on the network plan.
i. Click Browse on the right of the Source text box. In the Select Board Port-
Source dialog box that is displayed, select the desired board as the source
board of an end-to-end (E2E) service trail.
ii. Click Working Mode Settings to set the working mode of the ClientLP1 port
to ODU0 non-convergence mode (Any->ODU0).
iii. Set the service access port to 101(AP1).
e. Click Apply. The Result dialog box is displayed, indicating that the operation is
successful. Click Close.
2. Refer to 1 to create a client trail between UserF1 and UserF3 as the server trail of an
EPLAN service.
3. Create an EPLAN service (IEEE 802.1d bridge).
a. From the main menu, choose Service > WDM Trail > Create EPLAN.
b. In the Selected Node area, right-click and choose Add from the shortcut menu that
is displayed to add nodes based on the network plan.
e. Set port attributes in the Port Attribute Settings area as described in the following
table.
Paramet Value in This Example Description
er
NE1 NE2 NE4
TAG PORT7: Tag PORT7: Tag PORT7: Tag The access devices of
aware aware aware UserF1, UserF2, and
VCTRUNK VCTRUNK VCTRUNK UserF3 support VLAN
1: Tag 1: Tag 1: Tag tags and the data
aware aware aware frames sent from the
access devices carry
VCTRUNK VLAN tags. Therefore,
2: Tag TAG is set to Tag
aware Aware for the ports.
f. Optional: Set the information about the EPL service trail. For example, set Name
and Order No..
g. Optional: Deselect the Activate the trail check box if the created trail does not
need to be delivered to an NE.
h. Click Finish. The Result dialog box is displayed, indicating that the operation is
successful.
4. Change the Hub/Spoke attribute of the ports mounted to the bridge.
NOTE
If normal communication is required between user F2 and user F3, skip this step.
a. Select the TEM28 board in the NE Explorer of NE1 and choose Configuration >
Ethernet Service > Ethernet LAN Service from the navigation tree.
b. Select the created bridge and click the Service Mount tab.
c. Change the Hub/Spoke attribute of the ports mounted to the bridge. After setting the
parameters, click Apply.
Parameter Value Description
equipment connected to the transmission network supports VLANs or where the VLAN
planning is open to the network operator.
Service Requirement
On the network as shown in Figure 12-21, the service requirements are as follows:
l Three branches (G1, G2, and G3) of user G are located at NE1, NE2, and NE4
respectively. G2 and G3 do not need to communicate with each other.
l Three branches (H1, H2, and H3) of user H are located at NE1, NE2, and NE4
respectively.
l The service of user G needs to be isolated from the service of user H.
l The Ethernet equipment of user G and user H provides Ethernet electrical ports that work
in auto-negotiation mode and do not support VLANs.
Figure 12-21 Networking diagram for configuring EVPLAN services (IEEE 802.1q bridge)
NM
PORT8 PORT8
VCTRUNK1 NE3 VCTRUNK2
PORT7 PORT7
IU1- IU1-
TEM28 TEM28
IU3- NE2 NE4 IU3-
H2 TN53NS2 NE1 TN53NS2 H3
IU1- G3
G2
TEM28
H1 IU3- IU4- G1
TN53NS2 TN53NS2
VB1 VLAN 200 VB1 VLAN 100
NG WDM
equipment VCTRUNCK
IU3-TN53NS2
IU1-TEM28 OCH:1-ODU2:1-ODUflex:(1~2)
PORT7 OCH:1-ODU2:1
User H2 201(ClientLP1/
VCTRUNCK1 OCH:1-ODU2:1-ODU1:(1~4) IN/OUT
User G2 ClientLP1)-1
PORT8 OCH:1-ODU2:1-ODU1:(1~4)-ODU0:(1~2)
OCH:1-ODU2:1-ODU0:(1~8)
NE1
IU1-TEM28 IU3-TN53NS2
OCH:1-ODU2:1-ODUflex:(1~2)
VLAN100 OCH:1-ODU2:1
PORT7 201(ClientLP1/
User H1 OCH:1-ODU2:1-ODU1:(1~4) IN/OUT
VCTRUNCK1 ClientLP1)-1 OCH:1-ODU2:1-ODU1:(1~4)-ODU0:(1~2)
OCH:1-ODU2:1-ODU0:(1~8)
VB1 OCH:1-ODU2:1-ODUflex:(1~2)
202(ClientLP2/ OCH:1-ODU2:1
User G1 VCTRUNCK2 OCH:1-ODU2:1-ODU1:(1~4) IN/OUT
PORT8 ClientLP2)-1 OCH:1-ODU2:1-ODU1:(1~4)-ODU0:(1~2)
VLAN200 OCH:1-ODU2:1-ODU0:(1~8)
IU4-TN53NS2
NE4
IU3-TN53NS2
IU1-TEM28 OCH:1-ODU2:1-ODUflex:(1~2)
PORT7 OCH:1-ODU2:1
User H3 201(ClientLP1/
VCTRUNCK2 OCH:1-ODU2:1-ODU1:(1~4) IN/OUT
User G3 ClientLP1)-1
PORT8 OCH:1-ODU2:1-ODU1:(1~4)-ODU0:(1~2)
OCH:1-ODU2:1-ODU0:(1~8)
Prerequisite
You must read and understand the contents of Procedure for Configuring Ethernet Services
Based on the EoO Solution.
Enabled/ PORT7: Enabled In this example, PORT7 and PORT8 carry the
Disabled PORT8: Enabled services and Enabled/Disabled is set to
Enabled for PORT7 and PORT8.
MAC PORT7: Non-Loopback The MAC loopback setting is used for fault
Loopbac PORT8: Non-Loopback diagnosis. In this example, MAC Loopback
k is set to Non-Loopback.
PHY PORT7: Non-Loopback The PHY loopback setting is used for fault
Loopbac PORT8: Non-Loopback diagnosis. In this example, PHY Loopback
k is set to Non-Loopback.
4. Click the TAG Attributes tab. After setting the parameters, click Apply. Then, click
Close in the Operation Result dialog box that is displayed.
5. Click the Network Attributes tab. After setting the parameters, click Apply. Then, click
Close in the Operation Result dialog box that is displayed.
6. Click the Advanced Attributes tab. The parameters in the Advanced Attributes tab
page adopt the default values. For details on parameter settings, see 12.8.3 Parameters:
Advanced Attributes (External Ports).
NOTE
The external ports on the Ethernet boards at the source and sink ends of the accessed Ethernet
service must be set to Access, and the default VLAN ID must be set to the same value.
Step 2 Set the attributes of the internal ports used by the services of TEM28.
3. Click the TAG Attributes tab. After setting the parameters, click Apply. Then, click
Close in the Operation Result dialog box that is displayed. For details on parameter
settings, see Description of the TAG Attributes Parameter.
Parame Value in This Example Description
ter
Entry VCTRUNK1: Enabled The services of user G2, user G3, user H2,
Detectio VCTRUNK2: Enabled and user H3 are EVPLAN services. Therefor,
n the entry detection function must be enabled
to check whether the packets carry VLAN
tags. In this example, Entry Detection is set
to Enabled.
TAG VCTRUNK1: Tag Aware The service access equipment of user G2,
VCTRUNK2: Tag Aware user G3, user H2, and user H3 supports
VLAN tags and the transmitted data frames
do not carry VLAN tags. In this example,
TAG is set to Tag Aware for VCTRUNK1-
VCTRUNK4.
4. Click the Advanced Attributes tab. The parameters in the Advanced Attributes tab
page adopt the default values. For details on parameter settings, see Description of the
Advanced Attributes Parameter (External Port).
Step 3 Create a bridge for the TEM28 board on NE1.
1. In the NE Explorer, select the board and choose Configuration > Ethernet Service >
Ethernet LAN Service from the Function Tree.
2. Click New.
3. Set the parameters in the Create Ethernet LAN Service dialog box that is displayed.
Bridge IVL -
Learning
Mode
MAC Enabled -
Address Self-
learning
If normal communication is required between user G2 and user G3, skip this step.
1. Select the created bridge and click the Service Mount tab.
2. Change the Hub/Spoke attribute of the port that is mounted to the bridge. After setting
the parameters, click Apply. The Operation Result dialog box is displayed, indicating
that the operation is successful. Click Close.
Parameter Value in This Description
Example
Hub/Spoke PORT7: Hub If user G2 need not communicate with user G3,
VCTRUNK1: set VCTRUNK1 and VCTRUNK2 that access
Spoke the services of user G2 and user G3 to Spoke.
Ports of the Spoke attribute cannot communicate
VCTRUNK2: with each other. A port of the Hub attribute can
Spoke communicate with a port of the Spoke or Hub
PORT8: Hub attribute.
----End
The TEM28 board processes service differently when working in different modes. It can
work in either of the following modes:
Step 3 Configure cross-connections between the TEM28 board and TN53NS2 board.
1. In the NE Explorer, select an NE and choose Configuration > WDM Service
Management in the function tree.
2. Click the WDM Cross-Connection Configuration tab, and click New. The Create
Cross-Connection Service dialog box is displayed.
Parameter Value
Level Set the parameter value according to the Port Working Mode
value. If Port Working Mode is set to ODU0 non-convergence
mode, set Level to ODU0.
Service Type When Level is set to ODUflex, this parameter must be set to
PACKET.
Direction Bidirectional
Parameter Value
Source Optical 1
Channel(e.g.1,3-6)
Sink Optical The system automatically allocate the sink optical channel. You
Channel(e.g.1,3-6) do not need to set it.
3. Click OK.
----End
Service Requirement
On the network as shown in Figure 12-23, the service requirements are as follows:
l The GE services of user M and user N are sent to the transmission network at NE2 and
NE4 respectively and to the GE server at the convergence node NE1.
l The FE services of user M and user N are sent to the transmission network at NE2 and
NE4 respectively and to the FE server at the convergence node NE1.
l The GE services need to be isolated from the FE services. User M does not need to
communicate with user N.
l The data communication equipment of user M and user N provides Ethernet electrical
ports that work in auto-negotiation mode and support VLANs.
– C-VLAN ID of the GE services: 10
– C-VLAN ID of the FE services: 20
NOTE
The application scenarios where user M needs to communicate with user N are as follows:
l User M needs to communicate with user N.
l User M does not need to communicate with user N.
The operator requires that all services received from the user side should be uniformly labeled
and groomed through planned S-VLANs.
Figure 12-23 Networking diagram for configuring EVPLAN services (IEEE 802.1ad bridge)
NM
C-VLAN 10 C-VLAN 10
GE GE
PORT7 NE3 PORT7
FE FE
C-VLAN 20 C-VLAN 20
IU1- IU1-
TEM28 TEM28
NE2 NE4
IU3- IU3-
TN53NS2 NE1 TN53NS2
User M User N
IU1-
TEM28
GE FE
IU3- IU4-
TN53NS2 TN53NS2
VB1 VLAN 100 VB1 VLAN 200
VCTRUNK1 VCTRUNK2 VCTRUNK1 VCTRUNK2
PORT7 PORT8
NG WDM
VCTRUNCK
equipment
l The GE services tagged with C-VLAN ID 10 from NE2 and NE4 respectively are further
tagged with S-VLAN ID 100. When they arrive at the IEEE 802.1ad bridge of NE1 the
services are forwarded to the NE1 through Layer 2 switching.
l The FE services tagged with C-VLAN ID 20 from NE2 and NE4 respectively are further
tagged with S-VLAN ID 200. When they arrive at the IEEE 802.1ad bridge of NE1 the
services are forwarded to the NE1 through Layer 2 switching.
The access nodes NE2 and NE4 are configured with one TEM28 board each. The EVPL
services are configured to be transparently transmitted from NE2 and NE4 to NE1.
Figure 12-24 Service signal flow of the EVPLAN service (IEEE 802.1ad bridge)
NE2
IU3-TN53NS2
IU1-TEM28 OCH:1-ODU2:1-ODUflex:(1~2)
GE CVLAN 10 VLAN100 OCH:1-ODU2:1
201(ClientLP1/ OCH:1-ODU2:1-ODU1:(1~4)
User M PORT7 VCTRUNCK1 IN/OUT
ClientLP1)-1
FE CVLAN 20
VLAN200 OCH:1-ODU2:1-ODU1:(1~4)-ODU0:(1~2)
OCH:1-ODU2:1-ODU0:(1~8)
NE1
IU1-TEM28 IU3-TN53NS2
VLAN100 OCH:1-ODU2:1-ODUflex:(1~2)
PORT7 OCH:1-ODU2:1
201(ClientLP1/ OCH:1-ODU2:1-ODU1:(1~4) IN/OUT
GE VCTRUNCK1 ClientLP1)-1 OCH:1-ODU2:1-ODU1:(1~4)-ODU0:(1~2)
OCH:1-ODU2:1-ODU0:(1~8)
VB1 OCH:1-ODU2:1-ODUflex:(1~2)
OCH:1-ODU2:1
202(ClientLP2/ OCH:1-ODU2:1-ODU1:(1~4) IN/OUT
FE VCTRUNCK2
PORT8 ClientLP2)-1 OCH:1-ODU2:1-ODU1:(1~4)-ODU0:(1~2)
VLAN200 OCH:1-ODU2:1-ODU0:(1~8)
IU4-TN53NS2
NE4
IU3-TN53NS2
IU1-TEM28 OCH:1-ODU2:1-ODUflex:(1~2)
GE CVLAN 10 VLAN100 OCH:1-ODU2:1
201(ClientLP1/ OCH:1-ODU2:1-ODU1:(1~4)
User N PORT7 VCTRUNCK1 IN/OUT
ClientLP1)-1
FE CVLAN 20
VLAN200 OCH:1-ODU2:1-ODU1:(1~4)-ODU0:(1~2)
OCH:1-ODU2:1-ODU0:(1~8)
Working service of GE
WDM-side working service
Working service of FE
Prerequisite
You must read and understand the contents of Procedure for Configuring Ethernet Services
Based on the EoO Solution.
Port Enabled PORT7: Enabled Set PORT7 and PORT8 that carry the
PORT8: Enabled service to Enabled.
MAC Loopback PORT7: Non- The loopback setting is used for fault
Loopback diagnosis. When configuring a service,
PORT8: Non- set this parameter to Non-Loopback
Loopback
PHY Loopback PORT7: Non- The loopback setting is used for fault
Loopback diagnosis. When configuring a service,
PORT8: Non- set this parameter to Non-Loopback.
Loopback
4. Click the Flow Control tab. The default value of the parameter is recommended. For the
default value of the parameter, see Description of the Flow Control Parameter
(External Port).
5. Click the Network Attributes tab. After setting the parameter on this tab page, click
Apply. For details on parameter settings, see Description of the Network Attributes
Parameter.
Parameter Value Description
6. It is unnecessary to set the parameters on the TAG Attributes tab. If the port type is set
to C-Aware or S-Aware, the parameters on the TAG Attributes are meaningless.
Step 2 Set the attributes of the internal ports for the TEM28 board on NE1 used by the service
between user M and user N.
1. In the NE Explorer, select the board and then choose Configuration > Ethernet
Interface Management > Ethernet Interface from the Function Tree. Then, select
Internal Port.
2. Click the Network Attributes tab. After setting the parameter on this tab page, click
Apply. For details on parameter settings, see Description of the Network Attributes
Parameter.
Parameter Value Description
3. It is unnecessary to set the parameters on the TAG Attributes tab. If the port type is set
to C-Aware or S-Aware, the parameters on the TAG Attributes are meaningless.
Step 3 Create a bridge for the TEM28 board on NE1.
1. In the NE Explorer, select the board and then choose Configuration > Ethernet Service
> Ethernet LAN Service from the Function Tree. Click the Service Mount tab.
2. Click New on the lower right of the window. The Create Ethernet LAN Service dialog
box is displayed.
3. Enter the attributes of the Ethernet LAN service in the dialog box. For details on
parameter settings, see Description of the EPLAN Service Parameter.
4. Click Configure Mount, the Service Mount Configuration dialog box is displayed.
5. Select the mount ports in the dialog box.
NOTE
When a VC-Trunk port is mounted to different C-VLANs and S-VLANs, ensure that the values of VB
Port are the same; otherwise, a service conflict occurs.
VB 1 2 3 4
Port
C- 10 20 10 20 10 20
VL
AN
If normal communication is required between user M and user N, skip this step.
1. Select the created bridge and click the Service Mount tab.
2. Change the Hub/Spoke attribute of the port mounted to the bridge.
----End
The TEM28 board processes service differently when working in different modes. It can
work in either of the following modes:
Step 3 Configure cross-connections between the TEM28 board and TN53NS2 board.
1. In the NE Explorer, select an NE and choose Configuration > WDM Service
Management in the function tree.
2. Click the WDM Cross-Connection Configuration tab, and click New. The Create
Cross-Connection Service dialog box is displayed.
Parameter Value
Level Set the parameter value according to the Port Working Mode
value. If Port Working Mode is set to ODU0 non-convergence
mode, set Level to ODU0.
Service Type When Level is set to ODUflex, this parameter must be set to
PACKET.
Direction Bidirectional
Source Optical 1
Channel(e.g.1,3-6)
Sink Optical The system automatically allocate the sink optical channel. You
Channel(e.g.1,3-6) do not need to set it.
3. Click OK.
----End
NOTE
This section uses the LEM24 board as an example to describe how to configure Ethernet services based
on the EoW solution. The procedure for configuring the Ethernet services on the LEX4, L4G, and TBE
boards is similar to the procedure for configuring the Ethernet services on the LEM24 board.
Service Requirement
See Figure 12-25. The NE1, NE2, and NE3 form a ring network. All the NEs function as
OADM stations. The service requirements are as follows:
There is Ethernet communication between User1 and User2. In addition, a bidirectional EPL
service exists between stations NE1 and NE2. The working mode of the bidirectional EPL
service is set to auto-negotiation, and the bidirectional EPL service does not support the
VLAN function.
NM
NE3
NE1 NE2
IU3- IU3-
LEM24 LEM24
User1 User 2
VCTRUNK1 VCTRUNK1
PORT7 PORT7
NG WDM VCTRUNCK
equipment
Figure 12-26 shows the signal flow of the bidirectional EPL services between stations NE1
and NE2.
IU3-LEM24 IU3-LEM24
PORT7 PORT7
User1 VCTRUNK1 3(IN3/OUT3)-1 3(IN3/OUT3)-1 VCTRUNK1 User2
Prerequisite
Read and understand the contents of Procedure for Configuring Ethernet Services Based
on the EoW Solution.
Port Enabled PORT7: Enabled The EPL service of User1 occupies the
external port PORT7, and the enabling
status of PORT7 is set to Enabled.
MAC Loopback PORT7: Non- The MAC loopback setting is used for
Loopback fault diagnosis. When configuring a
service, set this parameter to Non-
Loopback.
PHY Loopback PORT7: Non- The PHY loopback setting is used for
Loopback fault diagnosis. When configuring a
service, set this parameter to Non-
Loopback.
4. Click the Flow Control tab. Double-click the Autonegotiation Flow Control Mode
value of the PORT7 port and choose Enable Symmetric/Dissymmetric Flow Control
from the drop-down list.
5. Click the TAG Attributes tab. After setting the parameter on this tab page, click Apply.
For details on parameter settings, see 12.8.5 Parameters: TAG Attributes.
Entry Detection Disabled The port does not identify tags in data
packets.
6. Click the Network Attributes tab. After setting the parameter on this tab page, click
Apply. For details on parameter settings, see 12.8.6 Parameters: Network Attributes.
3. Click the TAG Attributes tab. After setting the parameter on this tab page, click Apply.
For details on parameter settings, see 12.8.5 Parameters: TAG Attributes.
Entry Detection Disabled The port does not identify tags in data
packets.
4. Click OK, and the created Ethernet private line service is displayed on the interface.
----End
Service Requirement
In the network shown in Figure 12-27, NE1, NE2 and NE3 form a ring network. All the NEs
are OADM NEs. The service requirement is as follows:
Two branches of user A are located at NE1 and NE2 and need to communicate with each
other.
Two branches of user B are located at NE1 and NE2 and need to communicate with each
other.
One bidirectional EVPL (VLAN) service need to be configured between NE1 and NE2. The
working mode is auto-negotiation.
NM
NE3
UserA1
UserA2
NE1 NE2
IU3- IU3-
LEM24 LEM24 UserB2
UserB1
PORT7 PORT7
VCTRUNK1
VCTRUNK1
PORT8 PORT8
NG WDM
equipment VCTRUNCK
Figure 12-28 shows the signal flow of the bidirectional EVPL (VLAN) services between NE1
and NE2.
IU3-LEM24 IU3-LEM24
PORT7 PORT7
UserA1 UserA2
VCTRUNK1 3(IN3/OUT3)-1 3(IN3/OUT3)-1 VCTRUNK1
UserB1 UserB2
PORT8 PORT8
Prerequisite
You must read and understand the contents of Procedure for Configuring Ethernet Services
Based on the EoW Solution.
Working Mode PORT7: Auto- The equipment that receives the EVPL
Negotiation (VLAN) service support the
PORT8: Auto- autonegotiation mode. Therefore, set
Negotiation Working Mode to Auto-Negotiation.
MAC Loopback PORT7: Non- The MAC loopback setting is used for
Loopback fault diagnosis. When configuring a
PORT8: Non- service, set this parameter to Non-
Loopback Loopback.
PHY Loopback PORT7: Non- The PHY loopback setting is used for
Loopback fault diagnosis. When configuring a
PORT8: Non- service, set this parameter to Non-
Loopback Loopback.
4. Click the TAG Attributes tab. After setting the parameter on this tab page, click Apply.
For details on parameter settings, see 12.8.5 Parameters: TAG Attributes.
Parameter Value Description
5. Click the Network Attributes tab. After setting the parameter on this tab page, click
Apply. For details on parameter settings, see 12.8.6 Parameters: Network Attributes.
Step 2 On the LEM24 board on NE1, configure the internal Ethernet port shared by the bidirectional
services between userA1 and userA2, and the bidirectional services between userB1 and
userB2.
1. In the NE Explorer, select the desired board and then choose Configuration > Ethernet
Interface Management > Ethernet Interface from the Function Tree. Then, select
Internal Port.
2. Click the Network Attributes tab. After setting the parameter on this tab page, click
Apply. For details on parameter settings, see 12.8.6 Parameters: Network Attributes.
3. Click the TAG Attributes tab. After setting the parameter on this tab page, click Apply.
For details on parameter settings, see 12.8.5 Parameters: TAG Attributes.
Entry Detection VCTRUNK1: The port does not identify tags in data
Enabled packets.
Step 3 On the LEM24 board on NE1, configure the EVPL (VLAN) service between userA1 and
userA2, and the EVPL (VLAN) service between userB1 and userB2. You need to configure
the service between ports PORT7 and VCTRUNK1 and the service between ports PORT8 and
VCTRUNK1.
1. In the NE Explorer, select the desired board and then choose Configuration > Ethernet
Service > Ethernet Line Service from the Function Tree. Click the EPL Service tab.
2. Click New at the bottom of the window. The Create Ethernet Line Service dialog box
is displayed.
3. Enter the attributes of the Ethernet private line service in the dialog box. For details on
parameter settings, see 12.8.7 Parameters: Ethernet Line Service.
Parameter Value Description
Sink C-VLAN 100 (when the source Sets the source C-VLAN.
(e.g.1,3-6) is port PORT7) NOTE
200 (when the source For EVPL services, sink C-VLAN tags for
different sources ports must be different.
is port PORT8)
4. Click OK, and the created Ethernet private line service is displayed on the interface.
----End
a transmission network and need to be transmitted on the same VCTRUNK. In the case of
EVPL (QinQ) services, a layer of S-VLAN tag is added on the network side to isolate the
services of different users from each other.
Service Requirements
In the network shown in Figure 12-29, NE1, NE2 and NE3 form a ring network. All the NEs
are OADM NEs. The service requirement is as follows:
Two branches of user A are located at NE1 and NE2 and need to communicate with each
other.
Two branches of user B are located at NE1 and NE2 and need to communicate with each
other.
One bidirectional EVPL (QinQ) service need to be configured between NE1 and NE2. The
working mode is auto-negotiation. NE1 adds the S-VLAN1 tag to the received frames for user
A and the S-VLAN2 tag to the received frames for user B. After stripping the S-VLAN1 and
S-VLAN2 tags from the frames, NE2 sends the frames to user A and user B.
NM
PORT7
C-VLAN1 PORT7 C-VLAN1
VCTRUNK1
VCTRUNK1
PORT8
PORT8
NG WDM
VCTRUNCK
equipment
Figure 12-30 shows the signal flow of the bidirectional EVPL (QinQ) service between NE1
and NE2.
Prerequisite
Read and understand the contents of Procedure for Configuring Ethernet Services Based
on the EoW Solution.
Working Mode PORT7: Auto- The equipment for receiving the EVPL
Negotiation (QinQ) service support the auto-negotiation
PORT8: Auto- mode. Therefore, set Working Mode to
Negotiation Auto-Negotiation.
Maximum Frame PORT7: 1522 In general, the default value 1522 is used.
Length PORT8: 1522
MAC Loopback PORT7: Non- The MAC loopback setting is used for fault
Loopback diagnosis. When configuring a service, set
PORT8: Non- this parameter to Non-Loopback.
Loopback
PHY Loopback PORT7: Non- The PHY loopback setting is used for fault
Loopback diagnosis. When configuring a service, set
PORT8: Non- this parameter to Non-Loopback.
Loopback
4. Click the Network Attributes tab. After setting the parameter on this tab page, click
Apply. For details on parameter settings, see 12.8.6 Parameters: Network Attributes.
Parameter Value Description
Step 2 On the LEM24 board on NE1, configure the internal Ethernet port shared by the bidirectional
services between users A1 and A2, and the bidirectional services between users B1 and B2.
1. In the NE Explorer, select the desired board and choose Configuration > Ethernet
Interface Management > Ethernet Interface from the Function Tree. Then select
Internal Port.
2. Click the Network Attributes tab. After setting the parameter on this tab page, click
Apply. For details on parameter settings, see 12.8.6 Parameters: Network Attributes.
Step 3 On the LEM24 board on NE1, configure the EVPL (QinQ) service between user A1 and user
A2, and the EVPL (QinQ) service between userB1 and userB2. You need to configure the
service between ports PORT7 and VCTRUNK1 and the service between ports PORT8 and
VCTRUNK1.
1. In the NE Explorer, select the desired board and choose Configuration > Ethernet
Service > Ethernet Line Service from the Function Tree. Click the EPL Service tab.
2. Select Display QinQ Shared Service on the lower-right pane.
3. Click New at the bottom of the window. The Create Ethernet Line Service dialog box
is displayed.
4. Enter the attributes of the Ethernet private line service in the dialog box. For details on
parameter settings, see 12.8.7 Parameters: Ethernet Line Service.
Parameter Value Description
Source Port PORT7, PORT8 Indicates the name of the source port.
Sink S-VLAN 100 (when the source Adds the S-VLAN tag.
is port PORT7)
200 (when the source
is port PORT8)
5. Click OK, and the created Ethernet private line service is displayed on the interface.
----End
Service Requirement
In the network shown in Figure 12-31, the service requirements are as follows:
l Three branches (F1, F2, and F3) of user F are located at NE1, NE2, and NE4. F1 needs
to communicate with F2 and F3.
l The Ethernet equipment of user F provides Ethernet optical ports that work in auto-
negotiation mode and support VLANs. VLAN IDs and the number of VLANs, however,
are unknown and may be changed.
NOTE
The application scenarios where one branch needs to communicate with other branches as follows:
l Branches F2 and F3 need to communicate with each other.
l Branches F2 and F3 do not need to communicate with each other.
Figure 12-31 Networking diagram for configuring EPLAN services (IEEE 802.1d bridge)
NM
NE 3
IU3- IU3-
LEM24 NE 2 NE 4 LEM24
NE 1
F2 F3
VB
VCTRUNK1 VCTRUNK2
NG WDM equipment PORT7
F1
VCTRUNCK
IU3-LEM24
PORT7
3(IN3/OUT3)-1 VCTRUNCK1 User F3
Prerequisite
Read and understand the contents of Procedure for Configuring Ethernet Services Based
on the EoW Solution.
MAC Loopback PORT7: Non- The loopback setting is used for fault
Loopback diagnosis. When configuring a service,
set this parameter to Non-Loopback.
PHY Loopback PORT7: Non- The loopback setting is used for fault
Loopback diagnosis. When configuring a service,
set this parameter to Non-Loopback.
4. Click the TAG Attributes tab. After setting the parameter on this tab page, click Apply.
For details on parameter settings, see 12.8.5 Parameters: TAG Attributes.
Parameter Value Description
5. Click the Network Attributes tab. After setting the parameter on this tab page, click
Apply. For details on parameter settings, see 12.8.6 Parameters: Network Attributes.
Parameter Value Description
NOTE
The external ports on the Ethernet boards at the source and sink ends of the accessed Ethernet
service must be set to Access, and the default VLAN ID must be set to the same value.
4. Click the TAG Attributes tab. After setting the parameter on this tab page, click Apply.
For details on parameter settings, see Description of the TAG Attributes Parameter.
TAG VCTRUNK1: Tag For the internal port, you do not need to
Aware configure the tag header but retain the
default value, namely Tag Aware.
VB Type 802.1d The IEEE 802.1d MAC bridge learns and forwards
the packets according to the MAC addresses of the
user packets. The information in the VLAN tags of
the user packets, however, is not considered in the
learning and forwarding process. The IEEE 802.1d
MAC bridge is used when the entire information of
the VLANs used by the client cannot be learned or
when the data between the VLANs of the client does
not need to be isolated.
Bridge SVL/Ingress When the bridge adopts the SVL learning mode, all
Switch Mode Filter Disable the VLANs share the same MAC address table. That
is, the bridge learns and forwards the packets
according to the MAC address of the user packets
only. The information in the VLAN tags of the user
packets, however, is not considered in the learning
and forwarding process.
Bridge SVL -
Learning
Mode
Ingress Filter Disabled The IEEE 802.1d MAC bridge does not detect the
VLAN tags of the received packets.
MAC Enabled -
Address Self-
learning
If normal communication is required between user F2 and user F3, skip this step.
1. Select the created bridge and click the Service Mount tab.
2. Change the Hub/Spoke attribute of the port mounted to the bridge. After setting the
parameters, click Apply.
----End
Service Requirement
In the network shown in Figure 12-33, the service requirements are as follows:
l Three branches (G1, G2, and G3) of user G are located at NE1, NE2, and NE4
respectively. G2 and G3 do not need to communicate with each other.
l Three branches (H1, H2, and H3) of user H are located at NE1, NE2, and NE4
respectively.
l The service of user G needs to be isolated from the service of user H.
l The Ethernet equipment of user G and user H provides Ethernet electrical ports that work
in auto-negotiation mode and do not support VLANs.
Figure 12-33 Networking diagram for configuring EVPLAN services (IEEE 802.1q bridge)
NM
PORT8 PORT8
NE 3
VCTRUNK1 VCTRUNK2
PORT7 PORT7
IU3- NE 2 NE 4 IU3-
LEM24 LEM24
NE 1
H2 H3
G2 G3
IU3-
H1 LEM24 G1
NG WDM
equipment VCTRUNCK
IU3-LEM24
VLAN100 PORT7
NE1
VCTRUNCK1 User H2
3(IN3/OUT3)-1
IU3-LEM24 User G2
VLAN100 VLAN200 PORT8
PORT7
User H1 VCTRUNCK1 3(IN3/OUT3)-1
VB1 NE4
User G1 VCTRUNCK2 4(IN4/OUT4)-1 IU3-LEM24
PORT8
VLAN200 VLAN100 PORT7
VCTRUNCK2 User H3
3(IN3/OUT3)-1
User G3
VLAN200 PORT8
Prerequisite
Read and understand the contents of Procedure for Configuring Ethernet Services Based
on the EoW Solution.
Enabled/ PORT7: Enabled In this example, PORT7 and PORT8 carry the
Disabled PORT8: Enabled services and Enabled/Disabled is set to
Enabled for PORT7 and PORT8.
MAC PORT7: Non-Loopback The MAC loopback setting is used for fault
Loopbac PORT8: Non-Loopback diagnosis. In this example, MAC Loopback
k is set to Non-Loopback.
PHY PORT7: Non-Loopback The PHY loopback setting is used for fault
Loopbac PORT8: Non-Loopback diagnosis. In this example, PHY Loopback
k is set to Non-Loopback.
4. Click the TAG Attributes tab. After setting the parameters, click Apply. Then, click
Close in the Operation Result dialog box that is displayed.
Parame Value in This Example Description
ter
5. Click the Network Attributes tab. After setting the parameters, click Apply. Then, click
Close in the Operation Result dialog box that is displayed.
6. Click the Advanced Attributes tab. The parameters in the Advanced Attributes tab
page adopt the default values. For details on parameter settings, see 12.8.3 Parameters:
Advanced Attributes (External Ports).
NOTE
The external ports on the Ethernet boards at the source and sink ends of the accessed Ethernet
service must be set to Access, and the default VLAN ID must be set to the same value.
Step 2 Set the attributes of the internal ports used by the services of LEM24.
1. Select Internal Port.
2. Click the Network Attributes tab. After setting the parameters, click Apply. Then, click
Close in the Operation Result dialog box that is displayed. For details on parameter
settings, see Description of the Network Attributes Parameter.
Parame Value in This Example Description
ter
3. Click the TAG Attributes tab. After setting the parameters, click Apply. Then, click
Close in the Operation Result dialog box that is displayed. For details on parameter
settings, see Description of the TAG Attributes Parameter.
Entry VCTRUNK1: Enabled The services of user G2, user G3, user H2,
Detectio VCTRUNK2: Enabled and user H3 are EVPLAN services. Therefor,
n the entry detection function must be enabled
to check whether the packets carry VLAN
tags. In this example, Entry Detection is set
to Enabled.
TAG VCTRUNK1: Tag Aware The service access equipment of user G2,
VCTRUNK2: Tag Aware user G3, user H2, and user H3 supports
VLAN tags and the transmitted data frames
do not carry VLAN tags. In this example,
TAG is set to Tag Aware for VCTRUNK1-
VCTRUNK4.
4. Click the Advanced Attributes tab. The parameters in the Advanced Attributes tab
page adopt the default values. For details on parameter settings, see Description of the
Advanced Attributes Parameter (External Port).
Bridge IVL -
Learning
Mode
MAC Enabled -
Address Self-
learning
Step 5 Change the Hub/Spoke attribute of the port that is mounted to the bridge.
NOTE
If normal communication is required between user G2 and user G3, skip this step.
1. Select the created bridge and click the Service Mount tab.
2. Change the Hub/Spoke attribute of the port that is mounted to the bridge. After setting
the parameters, click Apply. The Operation Result dialog box is displayed, indicating
that the operation is successful. Click Close.
Parameter Value in This Description
Example
Hub/Spoke PORT7: Hub If user G2 need not communicate with user G3,
VCTRUNK1: set VCTRUNK1 and VCTRUNK2 that access
Spoke the services of user G2 and user G3 to Spoke.
Ports of the Spoke attribute cannot communicate
VCTRUNK2: with each other. A port of the Hub attribute can
Spoke communicate with a port of the Spoke or Hub
PORT8: Hub attribute.
----End
Service Requirement
In the network shown in Figure 12-35, the service requirements are as follows:
l The GE services of user M and user N are sent to the transmission network at NE2 and
NE4 respectively and to the GE server at the convergence node NE1.
l The FE services of user M and user N are sent to the transmission network at NE2 and
NE4 respectively and to the FE server at the convergence node NE1.
l The GE services need to be isolated from the FE services. User M does not need to
communicate with user N.
l The data communication equipment of user M and user N provides Ethernet electrical
ports that work in auto-negotiation mode and support VLANs.
– C-VLAN ID of the GE services: 10
– C-VLAN ID of the FE services: 20
NOTE
The application scenarios where user M needs to communicate with user N are as follows:
l User M needs to communicate with user N.
l User M does not need to communicate with user N.
Requirement of the operator requires that all services received from the user side should be
uniformly labeled and groomed through planned S-VLANs.
Figure 12-35 Networking diagram for configuring EVPLAN services (IEEE 802.1ad bridge)
NM
C-VLAN 10 C-VLAN 10
GE NE3 GE
PORT7 PORT7
FE FE
C-VLAN 20 C-VLAN 20
IU3- NE2 NE4 IU3-
LEM24 LEM24
NE1
M N
IU3-
GE FE
LEM24
PORT7 PORT8
NG WDM
equipment VCTRUNCK
l The GE services tagged with C-VLAN ID 10 from NE2 and NE4 respectively are further
tagged with S-VLAN ID 100. When they arrive at the IEEE 802.1ad bridge of NE1 the
services are forwarded to the NE1 through Layer 2 switching.
l The FE services tagged with C-VLAN ID 20 from NE2 and NE4 respectively are further
tagged with S-VLAN ID 200. When they arrive at the IEEE 802.1ad bridge of NE1 the
services are forwarded to the NE1 through Layer 2 switching.
The access nodes NE2 and NE4 are configured with one LEM24 board each. The EVPL
services are configured to be transparently transmitted from NE2 and NE4 to NE1.
Figure 12-36 Service signal flow of the EVPLAN service (IEEE 802.1ad bridge)
NE2
IU3-LEM24
VLAN100 GE CVLAN 10
NE1
IU3-LEM24 3(IN3/OUT3)-1 VCTRUNCK1 PORT7 User N
VLAN200 FE CVLAN 20
VLAN100
PORT7
GE VCTRUNCK1 3(IN3/OUT3)-1
VB1 NE4
FE VCTRUNCK2 4(IN4/OUT4)-1 IU3-LEM24
PORT8
VLAN200 VLAN100 GE CVLAN 10
3(IN3/OUT3)-1 VCTRUNCK2 PORT7 User M
VLAN200 FE CVLAN 20
Working service of GE
WDM-side working service
Working service of FE
Prerequisite
You must read and understand the contents of Procedure for Configuring Ethernet Services
Based on the EoW Solution.
Port Enabled PORT7: Enabled Set PORT7 and PORT8 that carry the
PORT8: Enabled service to Enabled.
MAC Loopback PORT7: Non- The loopback setting is used for fault
Loopback diagnosis. When configuring a service,
PORT8: Non- set this parameter to Non-Loopback
Loopback
PHY Loopback PORT7: Non- The loopback setting is used for fault
Loopback diagnosis. When configuring a service,
PORT8: Non- set this parameter to Non-Loopback.
Loopback
4. Click the Flow Control tab. The default value of the parameter is recommended. For the
default value of the parameter, see Description of the Flow Control Parameter
(External Port).
5. Click the Network Attributes tab. After setting the parameter on this tab page, click
Apply. For details on parameter settings, see Description of the Network Attributes
Parameter.
6. It is unnecessary to set the parameters on the TAG Attributes tab. If the port type is set
to C-Aware or S-Aware, the parameters on the TAG Attributes are meaningless.
Step 2 Set the attributes of the internal ports used by the service between user M and user N.
1. In the NE Explorer, select the board and then choose Configuration > Ethernet
Interface Management > Ethernet Interface from the Function Tree. Then, select
Internal Port.
2. Click the Network Attributes tab. After setting the parameter on this tab page, click
Apply. For details on parameter settings, see Description of the Network Attributes
Parameter.
3. It is unnecessary to set the parameters on the TAG Attributes tab. If the port type is set
to C-Aware or S-Aware, the parameters on the TAG Attributes are meaningless.
4. Click Configure Mount, the Service Mount Configuration dialog box is displayed.
5. Select the mount ports in the dialog box.
NOTE
When a VC-Trunk port is mounted to different C-VLANs and S-VLANs, ensure that the values of VB
Port are the same; otherwise, a service conflict occurs.
VB 1 2 3 4
Port
C- 10 20 10 20 10 20
VL
AN
If normal communication is required between user M and user N, skip this step.
1. Select the created bridge and click the Service Mount tab.
2. Change the Hub/Spoke attribute of the port mounted to the bridge.
----End
In the network shown in Figure 12-37, the service requirements are as follows:
l User A has two branches located at NE1 and NE2 respectively. two branches need to
communicate with each other through Ethernet. This requires a 100 Mbit/s bandwidth.
l User B has two branches located at NE1 and NE2 respectively. two branches need to
communicate with each other through Ethernet. This requires a 200 Mbit/s bandwidth.
l The services of user A and user B must be completely isolated.
l The Ethernet equipment of user A and user B provides 1000 Mbit/s full-duplex Ethernet
ports that do not support VLANs.
User A1 PORT1
NE1 NE2 User A2
8 8 PORT1
PORT2
User B1 PORT2 12 12
User B2
Ethernet Board 5-EGSH Ethernet Board 5-EGSH
Line Board 8-SL64 Line Board 8-SL64
Line Board 12-SL64 Line Board 12-SL64
Figure 12-38 shows the signal flow and timeslot allocation for EPL services.
Figure 12-38 Signal flow and timeslot allocation (Ethernet switching board)
NE1 :EGSH NE2 :EGSH
SDH
PORT1 EPL EPL PORT1
User A1 VCTRUNK1 VCTRUNK1
User A2
VC4-xv:VC4-1 VC4-xv:VC4-1
PORT2 EPL EPL PORT2
VCTRUNK2 VCTRUNK2
User B1
VC4-xv:VC4-2 VC4-xv:VC4-2 User B2
VC4-xv:VC4-3 VC4-xv:VC4-3
l User A:
– The first VC-4 (VC4:VC4-1) on the SDH link is used for transmitting EPL services.
– For NE1 and NE2 each, the first VC-4 (VC4-xv:VC4-1) of the EGSH board is used
to add or drop EPL services.
l User B:
– The second VC-4 (VC4:VC4-2) and the third VC-4 (VC4:VC4-3) on the SDH link
is used for transmitting EPL services.
– For NE1 and NE2 each, the second VC-4 (VC4-xv:VC4-2) and third VC-4 (VC4-
xv:VC4-3) of the EGSH board are used to add or drop EPL services.
Working Mode 1000M Full- 1000M Full- 1000M Full- 1000M Full-
Duplex Duplex Duplex Duplex
Board EGSH
Prerequisites
l You must be familiar with Flow of Configuring EPL Services.
Procedure
Step 1 Configure EPL services for users A1 and B1 on NE1.
1. Configure the attributes of the external ports (PORT 1 and PORT 2 on the EGSH board)
used by the service of users A1 and B1.
– In the NE Explorer, click the EGSH board and chooseConfiguration > Ethernet
Interface Management > Ethernet Interface from the Function Tree.
– Choose External Port.
– Click the Basic Attributes tab. After setting the parameters, click Apply.
– Click the TAG Attributes tab. After setting the parameters, click Apply.
Entry PORT1: Disabled The Tag parameter is valid only when this
Detecti PORT2: Disabled parameter is set to Enabled.
on The TAG, Default VLAN ID, and VLAN
Priority parameters are invalid when this
parameter is set to Disabled. Retain
default values for these parameters.
– Click the Network Attributes tab. After setting the parameters, click Apply.
Port PORT1: UNI Only a UNI can process the tag attribute of
Attribut PORT2: UNI IEEE 802.1q-compliant packets. Available
es tag attributes include Tag Aware, Access,
and Hybrid.
– Set the parameters in the Advanced Attributes tab to the default values.
2. Configure the attributes of the internal ports (VCTRUNK1 and VCTRUNK2 on the
EGSH board) used by the service of users A1 and B1.
– Choose Internal Port.
– Click the TAG Attributes tab. After setting the parameters, click Apply.
Param Value in This Description
eter Example
Entry VCTRUNK1: Disabled The Tag parameter is valid only when this
Detecti VCTRUNK2: Disabled parameter is set to Enabled.
on The TAG, Default VLAN ID, and VLAN
Priority parameters are invalid when this
parameter is set to Disabled. Retain
default values for these parameters.
– Click the Network Attributes tab. After setting the parameters, click Apply.
Param Value in This Description
eter Example
Port VCTRUNK1: UNI Only a UNI can process the tag attribute of
Attribut VCTRUNK2: UNI IEEE 802.1q-compliant packets. Available
es tag attributes include Tag Aware, Access,
and Hybrid.
– Click the Bound Path tab. Click Configuration. In the displayed Bound Path
Configuration dialog box, set the following parameters and click Apply.
User Paramete Value in Description
r This
Example
4. Configure the cross-connections from Ethernet services to the SDH links for users A1
and B1.
– In the NE Explorer, click NE1 and choose Configuration > SDH Service
Configuration from the Function Tree.
– Click Create in the lower part of the pane on the right. Set the required parameters
in Create SDH Service dialog box that is displayed.
User Paramete Value in Description
r This
Example
Activated Yes -
Immediate
ly
Activated Yes -
Immediate
ly
----End
l The headquarter of user A (A1) is located at NE1, and the two branches of user A (A2
and A3) are located at NE2.
l Services of user A2 and user A3 are isolated. User A2 and user A3 communicate with
user A1 using different ports and a 100 Mbit/s bandwidth.
l The Ethernet equipment of user A1, user A2, and user A3 provides 1000 Mbit/s full-
duplex Ethernet ports. The Ethernet equipment of user A1 supports VLANs, but the
Ethernet equipment of user A2 and user A3 does not support VLANs.
– The VLAN ID used by the Ethernet services between A1 and A2 is 100.
– The VLAN ID used by the Ethernet services between A1 and A3 is 200.
The signal flow of the PORT-shared EVPL (VLAN) services and the timeslot allocation to the
PORT-shared EVPL (VLAN) services are shown in Figure 12-40.
Figure 12-40 Signal flow of and timeslot allocation to PORT-shared EVPL (VLAN) services
NE1:EGSH NE2 :EGSH
SDH
VLAN Priority 0 0 - -
EVPL1 EVPL2
(PORT1←→ (PORT1←→
VCTRUNK1) VCTRUNK2)
Board EGSH
Prerequisites
l You must be familiar with Flow of Configuring EVPL Services.
Procedure
Step 1 Configure EVPL services for user A1 on NE1.
1. Set the attributes of the external port (PORT1 of the EGSH board) for user A1.
– In the NE Explorer, click the EGSH board and chooseConfiguration > Ethernet
Interface Management > Ethernet Interface from the Function Tree.
– Choose the External Port.
– Click the Basic Settings tab. After setting the parameters, click Apply.
Param Value Description
eter
– Click the TAG Attributes tab. After setting the parameters, click Apply.
Tag PORT1: Tag aware The data frames carried by PORT1 must
carry VLAN tags. Therefore, set this
parameter to Tag Aware.
Entry PORT1: Enabled The Tag parameter is valid only when this
Detecti parameter is set to Enabled.
on
– Click the Network Attributes tab. After setting the parameters, click Apply.
– Retain default values for the parameters on the Flow Control and Advanced
Attributes tab pages.
2. Configure the attributes of internal ports (VCTRUNK1 and VCTRUNK2 on EGSH
boards) for the service between user A1 and user A2 and the service between user A1
and user A3.
– Select Internal Port.
– Click the TAG Attributes tab. After setting the parameters, click Apply.
Entry VCTRUNK1: Enabled The Tag parameter is valid only when this
Detecti VCTRUNK2: Enabled parameter is set to Enabled.
on
– Click the Network Attributes tab. After setting the parameters, click Apply.
– Click the Bound Path tab. Click Configuration. In the displayed Bound Path
Configuration dialog box, set the following parameters and click Apply.
4. Configure cross-connections between Ethernet services and SDH links for the service
between user A1 and A2, and the service between A1 and A3.
– In the NE Explorer, click NE1 and choose Configuration > SDH Service
Configuration from the Function Tree.
– Click Create in the lower part of the pane on the right. Set the required parameters
in the Create SDH Service dialog box that is displayed.
User Paramete Value Description
r
Activated Yes -
Immediate
ly
Activated Yes -
Immediate
ly
----End
In the network shown in Figure 12-41, the service requirements are as follows:
l User A has two branches (A1 and A2) located respectively at NE1 and NE2. User B also
has two branches (B1 and B2) located respectively at NE1 and NE2. The branches of
each user need to communicate with each other.
l Services of user A and user B are isolated. User A and user B share a 100 Mbit/s
bandwidth because traffic peak time of the users does not overlap.
l The Ethernet equipment of user A and user B provides 1000 Mbit/s full-duplex Ethernet
ports that do not support VLANs.
l The VLAN ID 100 is added when services of user A enter the transmission network, and
stripped when the services leave the transmission network.
l The VLAN ID 200 is added when services of user B enter the transmission network, and
stripped when the services leave the transmission network.
VLAN=100
VLAN=100
User A1 PORT1
NE1 NE2 User A2
VLAN=200
8 8 PORT1
PORT2
Figure 12-42 Signal flow of and timeslot allocation to VCTRUNK-shared EVPL (VLAN)
services
NE1:EGSH NE2:EGSH
SDH
PORT1 PORT1
UserA1 EVPL1 EVPL1 User A2
VCTRUNK1 VCTRUNK1
PORT2 PORT2
VC4-xv:VC4-1 VC4-xv:VC4-1
User B1 EVPL2 EVPL2 User B2
l The first VC-4 (VC4:VC4-1) on the SDH link is used for transmitting the EVPL
services. User A and user B share VCTRUNK1 on the SDH link.
l For NE1 and NE2 each, the first VC-4 (VC4-xv:VC4-1) of the EGSH board is used to
add or drop EPL services.
Working Mode 1000M Full- 1000M Full- 1000M Full- 1000M Full-
Duplex Duplex Duplex Duplex
VLAN Priority 0 0 0 0
Prerequisites
l You must be familiar with Flow of Configuring EVPL Services.
Procedure
Step 1 Configure EVPL services for user A1 and user B1 on NE1.
1. Set the attributes of the external ports (PORT1 and PORT2 of the EGSH board) for user
A1 and user B1.
– In the NE Explorer, click the EGSH board and chooseConfiguration > Ethernet
Interface Management > Ethernet Interface from the Function Tree.
– Choose the External Port.
– Click the Basic Settings tab. After setting the parameters, click Apply.
Param Value Description
eter
– Click the TAG Attributes tab. After setting the parameters, click Apply.
Param Value Description
eter
Entry PORT1: Enabled The Tag parameter is valid only when this
Detecti PORT2: Enabled parameter is set to Enabled.
on
– Click the Network Attributes tab. After setting the parameters, click Apply.
– Retain default values for the parameters on the Flow Control and Advanced
Attributes tab pages.
2. Set the attributes of the internal port (VCTRUNK1 on the EGSH board) for services
between user A1 and user A2 and between user B1 and user B2.
– Select Internal Port.
– Click the TAG Attributes tab. After setting the parameters, click Apply.
Param Value Description
eter
Entry VCTRUNK1: Enabled The Tag parameter is valid only when this
Detecti parameter is set to Enabled.
on
– Click the Network Attributes tab. After setting the parameters, click Apply.
Param Value Description
eter
– Click the Bound Path tab. Click Configuration. In the displayed Bound Path
Configuration dialog box, set the following parameters and click Apply.
User Parameter Value Description
4. Configure cross-connections between Ethernet services and SDH links for user A1 and
user B1.
– In the NE Explorer, click NE1 and choose Configuration > SDH Service
Configuration from the Function Tree.
– Click New in the lower right portion of the window to set required parameters in the
Create SDH Service dialog box that is displayed. Click OK.
User Paramete Value Description
r
Activated Yes -
Immediate
ly
----End
Figure 12-43 shows the networking diagram. Service requirements are described as follows:
l User A has two branches (A1 and A2) located respectively at NE1 and NE2. User B also
has two branches (B1 and B2) located respectively at NE1 and NE2. The branches of
each user need to communicate with each other.
l Services of user A and user B are isolated. User A and user B share a 200 Mbit/s
bandwidth because traffic peak time of the users does not overlap.
l The Ethernet equipment of user A and user B provides 1000 Mbit/s auto-negotiation
Ethernet ports. The VLAN ID 100 is used for transmitting Ethernet services on the
transmission network.
l The S-VLAN ID 10 is added when services of user A enter the transmission network,
and stripped when the services leave the transmission network.
l The S-VLAN ID 20 is added when services of user B enter the transmission network,
and stripped when the services leave the transmission network.
C-VLAN=100
S-VLAN=10 C-VLAN=100
S-VLAN=10
C-VLAN=100 C-VLAN=100
S-VLAN=20 S-VLAN=20
User A1
NE1 NE2 User A2
PORT1
8 8 PORT1
PORT2
User B1 PORT2 12 12
User B2
Ethernet Board 5-EGSH Ethernet Board 5-EGSH
Line Board 8-SL64 Line Board 8-SL64
Line Board 12-SL64 Line Board 12-SL64
Figure 12-44 shows the signal flow of the EVPL (QinQ) services and the timeslot allocation
to the EVPL (QinQ) services.
Figure 12-44 Signal Flow and Timeslot Allocation for EVPL (QinQ) services
NE1:EGSH SDH NE2:EGSH
PORT VCTRUNK
Strip S-VLAN Label Add S-VLAN Label Strip S-VLAN Label
l The first VC-4 (VC4:VC4-1) and the second VC-4 (VC4:VC4-2) on the SDH link are
used for transmitting EVPL services between NE1 and NE2. User A and user B share
VCTRUNK1 on the SDH link.
l For NE1 and NE2 each, the first VC-4 (VC4-xv:VC4-1) and the second VC-4 (VC4-
xv:VC4-2) of the EGSH board are used to add or drop EVPL services.
Working Mode 1000M Full- 1000M Full- 1000M Full- 1000M Full-
Duplex Duplex Duplex Duplex
Source S- - - - -
VLAN
Sink S-VLAN 10 20 10 20
services of different users are isolated from each other and are transmitted on the same
VCTRUNK.
Prerequisites
l You must be familiar with Flow of Configuring EVPL Services.
Procedure
Step 1 Configure EVPL services for user A1 and user B1 on NE1.
1. Set the attributes of the external ports (PORT1 and PORT2 of the EGSH board) for user
A1 and user B1.
– In the NE Explorer, click the EGSH board and chooseConfiguration > Ethernet
Interface Management > Ethernet Interface from the Function Tree.
– Choose the External Port.
– Click the Basic Settings tab. After setting the parameters, click Apply.
– Click the Network Attributes tab. After setting the parameters, click Apply.
– The parameters on the TAG Attributes are invalid for C-Aware or S-Aware ports.
Therefore, retain default values for the parameters.
– Retain default values for the parameters on the Flow Control and Advanced
Attributes tab pages.
2. Set the attributes of the internal port (VCTRUNK1 on the EGSH board) for services
between user A1 and user A2 and between user B1 and user B2.
– Select Internal Port.
– Click the Network Attributes tab. After setting the parameters, click Apply.
– Click the Bound Path tab. Click Configuration. In the displayed Bound Path
Configuration dialog box, set the following parameters and click Apply.
User Paramete Value Description
r
– The parameters on the TAG Attributes tab page are invalid for C-Aware or S-
Aware ports. Therefore, retain default values for the parameters.
– Retain default values for the parameters on the Encapsulation/Mapping and
LCAS tab pages.
3. Configure the EPL service between user A1 and user A2 and the EPL service between
user B1 and user B2.
– Choose Configuration > Ethernet Service > Ethernet Line Service from the
Function Tree.
– In the lower part of the right pane, tick Display QinQ shared service. Click New.
– In the Create Ethernet Line Service dialog box, set the following parameters and
click Apply.
4. Configure cross-connections between Ethernet services and SDH links for user A1 and
user B1.
– In the NE Explorer, click NE1 and choose Configuration > SDH Service
Configuration from the Function Tree.
– Click New in the lower right portion of the window to set required parameters in the
Create SDH Service dialog box that is displayed. Click OK.
User Paramete Value Description
r
Activated Yes -
Immediate
ly
----End
Figure 12-45 shows the networking diagram. Service requirements are described as follows:
l User A has three branches (A1, A2, and A3). User A1 needs to communicate with user
A2 and user A3. The bandwidth for services between user A1 and user A2 or between
user A1 and user A3 is 100 Mbit/s.
l The Ethernet equipment of user A provides 1000 Mbit/s full-duplex Ethernet ports.
l Ethernet equipment of user A1, user A2, and user A3 supports VLANs. VLAN IDs and
the number of available VLAN IDs are unknown and subject to later changes.
NOTE
The application scenarios whether one branch needs to communicate with other branches are as follows:
l Branches A2 and A3 need to communicate with each other.
l Branches A2 and A3 do not need to communicate with each other.
If branches A2 and A3 need to communicate with each other, skip Step 1.4.
Figure 12-45 Networking diagram for configuring EPLAN services (IEEE 802.1d bridge)
12
8
8 NE2
NE3 12
NE1
12 8
A1
Figure 12-46 Signal flow of and timeslot allocation to EPLAN services (IEEE 802.1d bridge)
NE2: EGSH
SDH
VCTRUNK1 EPL PORT1
NE1: EGSH User A2
VC4-xv:VC4-1
VCTRUNK1
PORT1 VC4-xv:VC4-1
User A1 VCTRUNK2
NE3: EGSH
VC4-xv:VC4-2
VB1 EPL PORT1
VCTRUNK1
User A3
VC4-xv:VC4-1
l The first VC-4 (VC4:VC4-1) on the SDH link between NE1 and NE2 and the first VC-4
(VC4:VC4-1) on the SDH link between NE1 and NE3 are used for transmitting EPLAN
services.
l The first VC-4 (VC4-xv:VC4-1) of the EGSH board on NE1 and the first VC-4 (VC4-
xv:VC4-1) of the EGSH board on NE2 are used to add or drop EPLAN services between
NE1 and NE2.
l The second VC-4 (VC4-xv:VC4-2) of the EGSH board on NE1 and the first VC-4
(VC4-xv:VC4-1) of the EGSH board on NE3 are used to add or drop EPLAN services
between NE1 and NE3.
Board EGSH
VB Name VB1
VCTRUNK1 Spoke
VCTRUNK2 Spoke
Prerequisites
l You must be familiar with Flow of Configuring EPLAN Services.
Procedure
Step 1 Configure EPLAN services for user A1, user A2, and user A3 on NE1.
1. Set the attributes of the external port (PORT1 of the EGSH board) for user A1.
– In the NE Explorer, click the EGSH board and chooseConfiguration > Ethernet
Interface Management > Ethernet Interface from the Function Tree.
– Choose the External Port.
– Click the Basic Settings tab. After setting the parameters, click Apply.
Param Value Description
eter
– Click the TAG Attributes tab. After setting the parameters, click Apply.
Param Value Description
eter
Entry PORT1: Enabled The Tag parameter is valid only when this
Detecti parameter is set to Enabled.
on
– Click the Network Attributes tab. After setting the parameters, click Apply.
– Retain default values for the parameters on the Flow Control and Advanced
Attributes tab pages.
2. Set the attributes of the internal ports (VCTRUNK1 and VCTRUNK2 of the EGSH
board) for services between user A2 and user A3 on NE1.
– Select Internal Port.
– Click the TAG Attributes tab. After setting the parameters, click Apply.
Param Value Description
eter
Entry VCTRUNK1: Enabled The Tag parameter is valid only when this
Detecti VCTRUNK2: Enabled parameter is set to Enabled.
on
– Click the Network Attributes tab. After setting the parameters, click Apply.
– Click the Bound Path tab. Click Configuration. In the displayed Bound Path
Configuration dialog box, set the following parameters and click Apply.
User Parameter Value Description
Bridge Type 802.1d An IEEE 802.1d bridge learns and forwards user
packets according to the MAC addresses, instead
of the VLAN information of the packets. Set this
parameter to 802.1d if the VLAN information on
the client side is not available and service
isolation by VLAN ID is not required.
If user A2 and user A3 need to communicate with each other, go to Step 1.5.
– Select the bridge that has been created, and click the Service Mount tab.
– Modify the Hub/Spoke attribute of the mounted port. Set the following parameters
and click Apply.
Parameter Value Description
5. Configure cross-connections between Ethernet services and SDH links for services
between user A1 and user A2 and between user A1 and user A3.
– In the NE Explorer, click NE1 and choose Configuration > SDH Service
Configuration from the Function Tree.
– Click New in the lower right portion of the window to set required parameters in the
Create SDH Service dialog box that is displayed. Click OK.
User Paramete Value Description
r
Activated Yes -
Immediate
ly
Activated Yes -
Immediate
ly
----End
Figure 12-47 Networking diagram for configuring EVPLAN services (IEEE 802.1q bridge)
B2 A3
A2
Ethernet Board 5-EGSH B3
Line Board 8-SL64
Line Board 12-SL64
PORT1
PORT2 PORT1
PORT2
12 8
8 NE2
NE3 12
NE1
12 8
PORT1 PORT2
Figure 12-48 Signal flow of and timeslot allocation to EVPLAN services (IEEE 802.1q
bridge)
NE2 :EGSH
SDH PORT1
VCTRUNK1 EPL
NE1:EGSH User A 2
VC4-xv:VC4-1
VCTRUNK2 EPL PORT2
VLAN 100 VCTRUNK1 User B2
VC4-xv:VC4-2
PORT1 VC4-xv:VC4-1
User A 1
VCTRUNK2
VC4-xv:VC4-2
VLAN 200 VCTRUNK3 NE3:EGSH
PORT2
VC4-xv:VC4-3
User B1
VCTRUNK4 VCTRUNK1 EPL PORT1
VC4-xv:VC4-4 User A 3
VC4-xv:VC4-1
VB1 VCTRUNK2 EPL PORT2
User B3
VC4-xv:VC4-2
PORT VCTRUNK
Strip VLAN tag Add VLAN tag Strip VLAN tag
VLAN 0 0 - - - -
Priority
VLAN 0 0 0 0 - - - -
Priority
Board EGSH
VB Name VB1
PORT2 Hub
VCTRUNK Spoke
1
VCTRUNK Spoke
2
VCTRUNK Hub
3
VCTRUNK Hub
4
Prerequisites
l You must be familiar with Flow of Configuring EVPLAN Services.
Procedure
Step 1 Configure EVPLAN services for user A and user B on NE1.
1. Set the attributes of the external ports (PORT1 and PORT2 of the EGSH boards) for user
A1 and user B1.
– In the NE Explorer, click the EGSH board and chooseConfiguration > Ethernet
Interface Management > Ethernet Interface from the Function Tree.
– Choose the External Port.
– Click the Basic Settings tab. After setting the parameters, click Apply.
Param Value Description
eter
– Click the TAG Attributes tab. After setting the parameters, click Apply.
Param Value Description
eter
Entry PORT1: Enabled The Tag parameter is valid only when this
Detecti PORT2: Enabled parameter is set to Enabled.
on
– Click the Network Attributes tab. After setting the parameters, click Apply.
Param Value Description
eter
– Retain default values for the parameters on the Flow Control and Advanced
Attributes tab pages.
2. Set the attributes of the internal ports (VCTRUNK1, VCTRUNK2, VCTRUNK3, and
VCTRUNK4 of the EGSH board) on NE1 for user A2, user A3, user B2, and user B3.
– Select Internal Port.
– Click the TAG Attributes tab. After setting the parameters, click Apply.
Param Value Description
eter
Entry VCTRUNK1: Enabled The Tag parameter is valid only when this
Detecti VCTRUNK2: Enabled parameter is set to Enabled.
on
VCTRUNK3: Enabled
VCTRUNK4: Enabled
– Click the Network Attributes tab. After setting the parameters, click Apply.
Param Value Description
eter
– Click the Bound Path tab. Click Configuration. In the displayed Bound Path
Configuration dialog box, set the following parameters and click Apply.
User Parameter Value Description
– Click OK.
– In the Create Ethernet LAN Service dialog box, click OK.
4. Create VLAN filtering tables.
– Select the bridge that has been created, and click the VLAN Filtering tab.
– Click New.
– In the Create VLAN dialog box, create a VLAN filtering table for user A1, user
A2, and user A3.
Parameter Value Description
6. Configure cross-connections between Ethernet services and SDH links for user A2, user
A3, user B2, and user B3.
– In the NE Explorer, click NE1 and choose Configuration > SDH Service
Configuration from the Function Tree.
– Click New in the lower right portion of the window to set required parameters in the
Create SDH Service dialog box that is displayed. Click OK.
User Paramete Value Description
r
Activated Yes -
Immediate
ly
Activated Yes -
Immediate
ly
Activated Yes -
Immediate
ly
Activated Yes -
Immediate
ly
----End
According to the data plan, all services received from the user side must be uniformly labeled
and groomed using planned S-VLANs.
l S-VLAN ID of the VoIP services: 100
l S-VLAN ID of the HSI services: 200
Figure 12-49 Networking diagram for configuring EVPLAN services (IEEE 802.1ad bridge)
User A User B
12
8
8 NE2
NE3 12
NE1
12 8
VoIP
PORT1 PORT2 HSI
Figure 12-50 Signal flow and timeslot allocation for EVPLAN services (IEEE 802.1ad
bridge)
NE1:EGSH NE2:EGSH
SDH
PORT VCTRUNK
Strip S-VLAN tag Add S-VLAN tag Strip S-VLAN tag
l User A:
– The first VC-4 (VC4:VC4-1) and the second VC-4 (VC4:VC4-2) on the SDH link
are used for transmitting EVPLAN services between NE1 and NE2.
– For NE1 and NE2 each, the first VC-4 (VC4-xv:VC4-1) and the second VC-4
(VC4-xv:VC4-2) of the EGSH board are used to add or drop EVPLAN services
between NE1 and NE2.
l User B:
– The third VC-4 (VC4:VC4-3) and the fourth VC-4 (VC4:VC4-4) on the SDH link
are used for transmitting EVPLAN services between NE1 and NE3.
– For NE1 and NE3 each, the third VC-4 (VC4-xv:VC4-3) and the fourth VC-4
(VC4-xv:VC4-4) of the EGSH board are used to add or drop EVPLAN services
between NE1 and NE3.
Working Mode 1000M Full- 1000M Full- 1000M Full- 1000M Full-
Duplex Duplex Duplex Duplex
Board EGSH
VB Name VB1
VB Port 1 2 3 4
C-VLAN 10 20 10 20 10 20
VCTRUNK Spoke
1
VCTRUNK Spoke
2
Prerequisites
l You must be familiar with Flow of Configuring EVPLAN Services.
Procedure
Step 1 Configure EVPLAN services on NE1.
1. Set the attributes of the external ports (PORT1 and PORT2 of the EGSH board) used by
the VoIP server and HSI server.
– In the NE Explorer, click the EGSH board and chooseConfiguration > Ethernet
Interface Management > Ethernet Interface from the Function Tree.
– Choose the External Port.
– Click the Basic Settings tab. After setting the parameters, click Apply.
Param Value in This Description
eter Example
Workin PORT1: 1000M Full- The VoIP server and HSI server are
g Mode Duplex required to support the 1000M full-duplex
PORT2: 1000M Full- mode. Therefore, set this parameter to
Duplex 1000M Full-Duplex.
– Click the Network Attributes tab. After setting the parameters, click Apply.
– The parameters on the TAG Attributes tab page are invalid for C-Aware or S-
Aware ports. Therefore, retain default values for the parameters.
– Retain default values for the parameters on the Flow Control and Advanced
Attributes tab pages.
2. Set the attributes of the internal ports (VCTRUNK1 and VCTRUNK2 on the EGSH
board) for user A and user B.
– Select Internal Port.
– Click the Network Attributes tab. After setting the parameters, click Apply.
– The parameters on the TAG Attributes tab page are invalid for C-Aware or S-
Aware ports. Therefore, retain default values for the parameters.
– Click the Bound Path tab. Click Configuration. In the displayed Bound Path
Configuration dialog box, set the following parameters and click Apply.
Bridge Type 802.1ad The IEEE 802.1ad bridge supports data frames
with two layers of VLAN tags. Outer S-VLAN
tags are used to isolate different VLANs, and
attributes of mounted ports must be C-Aware or
S-Aware.
VB Port 1 2 3 4
C-VLAN 10 20 10 20 10 20
6. Configure cross-connections between Ethernet services and SDH links for user A and
user N.
– In the NE Explorer, click NE1 and choose Configuration > SDH Service
Configuration from the Function Tree.
– Click New in the lower right portion of the window to set required parameters in the
Create SDH Service dialog box that is displayed. Click OK.
Activated Yes -
Immediate
ly
Activated Yes -
Immediate
ly
----End
Figure 12-51 shows the networking diagram. Service requirements are described as follows:
l Services of user A1 and user B1 are received from the same Ethernet port.
l User A has two branches (A1 and A2) located respectively at NE1 and NE2. Services of
user A require a 100 Mbit/s bandwidth.
l User B has three branches (B1, B2, and B3) located respectively at NE1, NE2, and NE3.
The branches form a LAN and share a 100 Mbit/s bandwidth. Communication between
user B2 and user B3 is not required.
l The Ethernet equipment of user A and user B provides 1000 Mbit/s full-duplex Ethernet
ports.
– The VLAN ID 100 is used for transmitting services between user A1 and user A2.
– The VLAN ID 200 is used for transmitting services between user B1 and user B3
and between user B2 and user B3.
l Services of user A and user B are isolated.
Figure 12-51 Networking diagram for configuring EVPLAN services (IEEE 802.1q bridge)
B2
A2 Ethernet Board 5-EGSH
Line Board 8-SL64 B3
Line Board 12-SL64
PORT1
PORT2 PORT1
12 8
8 NE2
NE3 12
NE1
12 8
A1
VCTRUNK
B1
Figure 12-52 shows the signal flow and timeslot allocation for PORT-shared EVPL (VLAN)
services and EVPLAN services (IEEE 802.1q bridge).
Figure 12-52 Signal flow and timeslot allocation for EVPLAN services (IEEE 802.1q bridge)
NE2 :EGSH
Working Mode 1000M Full- 1000M Full- 1000M Full- 1000M Full-
Duplex Duplex Duplex Duplex
Default VLAN ID - - - -
VLAN Priority 0 - - -
VLAN 0 0 0 - - -
Priority
EVPL
(PORT1←→VCTRUNK1)
Board EGSH
Parameter NE1
EVPL
(PORT1←→VCTRUNK1)
Board EGSH
VB Name VB1
VLAN ID 200
VCTRUNK2 Spoke
VCTRUNK3 Spoke
Prerequisites
l You must be familiar with Flow of Configuring EVPL Services.
l You must be familiar with Flow of Configuring EVPLAN Services.
Procedure
Step 1 Configure EVPL (VLAN) services for user A1 on NE1. Configure EVPL services by
referring to 12.6.2.3 Configuration Process.
Step 2 Configure EVPLAN services (IEEE 802.1q bridge) between user B1 and user B2 and
between user B1 and user B3 on NE1. Configure EVPLAN services by referring to 12.6.6.3
Configuration Process.
Step 3 Configure EPL services on NE2 and NE3.
NOTE
The type of Ethernet services between NE2 and NE3 is EPL. Configure EPL services by referring to
12.6.1 Configuring EPL Services on an Ethernet Switching Board.
----End
Prerequisites
l You must be an NM user with "NE operator" authority or higher.
l The required Ethernet board must be created.
Legend Information
Figure 12-53 shows legend information about U2000 operations.
Procedure
Step 1 In the NE Explorer, set the basic attributes of the external port. For the basic attributes of the
external port on an Ethernet board, see 12.8.1 Parameters: Basic Attributes (External
Ports).
Configuration example:
3
1 4
NOTE
5
:
l Before configuring the external ports of the board, set State of the port to OOS in the Basic
Attributes tab, indicating that the port is out of service. After the preceding configurations are
complete, set the State to IS, which indicates that the port is in service.
l Set the working modes for the interconnected ports consistently. Otherwise, services will be
unavailable.
l Working Mode: By default, this parameter is set to Auto-Negotiation. That is, two ports operate in
the working mode of the highest level through pulse negotiation signals.
Step 2 Set the flow control mode of the port. For the flow control parameters of the external port on
an Ethernet boards, see 12.8.2 Parameters: Flow Control (External Ports).
Configuration example:
3
1 4
Step 3 Set the tag attributes of the external port. For the tag attributes of the external port on an
Ethernet board, see 12.8.5 Parameters: TAG Attributes.
Configuration example:
3
1 4
Step 4 Set the network attributes of the external port. For the network attributes of the external port
on an Ethernet board, see 12.8.6 Parameters: Network Attributes.
Configuration example:
3
1 4
Step 5 Set the advanced attributes of the external port. For the advanced attributes of the external
port on an Ethernet board, see 12.8.3 Parameters: Advanced Attributes (External Ports).
Configuration example:
3
1 4
----End
Prerequisites
l You must be an NM user with "NE operator" authority or higher.
l The required Ethernet board must be created.
Legend Information
Figure 12-54 shows legend information about U2000 operations.
Procedure
Step 1 In the NE Explorer, select the Ethernet board and choose Configuration > Ethernet
Interface Management > Ethernet Interface from the Function Tree.
3
1 4
3. Click Apply.
3. Click Apply.
Step 5 Set the network attributes of the internal port.
1. Click the Network Attributes tab.
2. Set the network attributes of the internal port. For the network attributes of the internal
port on an Ethernet board, see 12.8.6 Parameters: Network Attributes.
3
1 4
3. Click Apply.
Step 6 Set the advanced attributes of the internal port.
1. Click the Advanced Attributes tab.
2. Set the advanced attributes of the internal port. For the advanced attributes of the internal
port on an Ethernet board, see 12.8.4 Parameters: Advanced Attributes (Internal
Ports).
3
1
4
3. Click Apply.
----End
Prerequisites
l You must be an NM user with "NE operator" authority or higher.
l The required Ethernet board must be created.
Legend Information
Figure 12-55 shows legend information about U2000 operations.
Procedure
Step 1 In the NE Explorer, Modify the QinQ type area value.
Configuration example:
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
12.7.1.1 Configuring the External Port and 12.7.1.2 Configuring the Internal Port have
been completed.
Legend Information
Figure 12-56 shows legend information about U2000 operations.
Background Information
The configuration of service parameters on both ends of an Ethernet service must be the same.
The following are the three types of EPL services that can be configured on the NMS.
l EPL services between PORT and VCTRUNK ports.
l EPL services between VCTRUNK and VCTRUNK ports.
l EPL services between PORT and PORT ports.
NOTE
l For the above three types of services, if the source VLAN ID and sink VLAN ID are different, this
VLAN is a switched VLAN. To configure VLAN SNCP at the receive end of services, the source
VLAN ID and sink VLAN ID must be the same.
Configuration example:
NOTE
5
:
l You can set Direction to unidirectional or bidirectional.
l In Port Attributes, you can set Port Enabled and TAG for a port in the Create Ethernet Line
Service dialog box or in Ethernet Interface.
l In Port Attributes, certain parameters can be modified. If port attributes are already set, however,
retain the default values.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
12.7.1.1 Configuring the External Port and 12.7.1.2 Configuring the Internal Port have
been completed.
Context
Legend Information
Figure 12-57 shows legend information about U2000 operations.
Background Information
EVPL (QinQ) services are the Ethernet service packets that are added with an S-VLAN tag or
C-VLAN tag. In this way, the extension of VLAN ID is realized.
2
4
NOTE
6
:
l In Port Attributes, certain parameters can be modified. If port attributes are already set, however,
use the default values.
l In Port Attributes, you can set TAG for a port in Ethernet Interface.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
12.7.1.1 Configuring the External Port and 12.7.1.2 Configuring the Internal Port have
been completed.
Context
Legend Information
8
9
NOTE
7
: Modifying the ports that are mounted to the bridge may interrupt services.
10
11
12
NOTE
11
: Services are interoperable between Hub ports or between a Hub port and a Spoke port, but
are isolated between Spoke ports.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Applicable to the LEM24, LEX4 and TBE boards
Legend Information
Figure 12-59 shows legend information about U2000 operations.
Background Information
The NMS and its managed NG WDM equipment organize certain consecutively accessed
VLAN services in a group (usually service demands of the same type) to form a VLAN
group. NMS creates services, manages the QoS flow, and performs Ethernet OAM operations
according to the initial VLAN ID so that the other VLAN services in the VLAN group have
the same configuration.
l Each port supports a maximum of eight VLAN groups. The eight VLAN groups must
have different VLAN values. The port attribute can be UNI or C-aware only.
l When you create a VLAN group, if a service has been configured in the first VLAN of
the VLAN group, the VLAN group can be created, but the service may be transiently
interrupted.
l When you attempt to create a VLAN group, the VLAN group cannot be created if any
VLAN group member (not the first VLAN) has been configured with services such as
EPL services without VLAN tags, QinQ services, or services involved in VLAN
configuration such as flow configuration, Ethernet service OAM, and flow statistic
collection rule configuration.
l VLAN groups support only EVPL and QinQ services that are forwarded based on port
+VLAN attributes (the VLAN ID cannot be 0).
NOTICE
Creating a VLAN group may affect the services.
1 4
NOTE
4
:
l The value of Initial VLAN is in the range of 1 to 4095. The formula is as follows: Initial VLAN
= p x 2n. n is an integer from 0 to 12. p is an integer from 1 to 2m. m + n <= 12.
l The formula of VLAN Group Member Count depends on the value of the Initial VLAN. If the
value of Initial VLAN is 1, VLAN Group Member Count = 2n - 1.
l If the value of Initial VLAN is an integer other than 1, VLAN Group Member Count = 2n. The
value of n is the same as that in the formula of the Initial VLAN.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The port must be mounted to a VB.
Ensure that you set Bridge Switch Mode to IVL/Ingress Filter Enable. This is the only way
you can create VLANs.
Context
Legend Information
Figure 12-60 shows legend information about U2000 operations.
1
3
6
7
Step 2 Confirm that the query results are the same as the values that are set.
Configuration example:
----End
The entries in the MAC address table indicate the corresponding relationship between the
MAC addresses and the ports. The MAC address table contains the following entries:
l Dynamic entry
Indicates the entry that the bridge obtains by adopting the SVL/IVL learning mode and a
dynamic entry ages. It is lost after the Ethernet switching board is reset.
l Static entry
Indicates the entry corresponding to the MAC address and the port that the network
administrator manually adds in the MAC address table on the U2000. Dynamic entry
does not age and is not lost after the Ethernet switching board is reset.
l Blackhole entry
Indicates the entry used to discard the data frame that contains the specified destination
MAC address. It is also referred to as the MAC address disable entry. Blackhole entry is
configured by the network administrator. This entry does not age and is not lost after the
Ethernet switching board is reset.
NOTE
l If a routing entry is not updated within a specific period of time, that is, if the MAC address fails to be
learned because the new data frame from the MAC address is not received, this routing entry is
automatically deleted. This mechanism is considered as aging, and this period of time is considered as the
aging time. The default aging time of the MAC address table is five minutes and can be set by using the
NM.
l A limited number of MAC addresses can be learned at a time.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The VLAN must be created.
Context
Legend Information
Figure 12-61 shows legend information about U2000 operations.
1
3
NOTE
5
:
l The first byte of the MAC Address of VLAN unicast must be even.
l For the configuration of related parameters, see 12.8.8 Parameters: Ethernet LAN Service.
Step 2 Confirm that the query results are the same as the values that are set.
Configuration example:
----End
Prerequisites
l You are an NMS user with " NE operator" privilege or higher.
l Creating EPLAN Services has been completed.
Context
Legend Information
----End
Prerequisite
You are an NMS user with " NE operator" privilege or higher.
Legend Information
Figure 12-63 shows legend information about U2000 operations.
Background Information
If the aging time is too long, the MAC address table may save many outdated MAC address
items. This may use up the resources of the MAC address table. As a result, the MAC address
table may not be updated according to the change in the network.
If the aging time is too short, the effective MAC address items may be deleted. As a result,
packets that are broadcasted cannot find the destination MAC address, and the performance of
the network is affected.
NOTE
5
:
1-120 Hour
1-12 Day
----End
Prerequisites
l You are an NMS user with " NE operator" privilege or higher.
l Creating EPLAN Services has been completed.
Context
Legend Information
Configuration example:
1 3
2
4
Step 2 Optional: Select a MAC address to be deleted and click Clear MAC address.
Configuration example:
1 3
----End
Prerequisites
l You are an NMS user with " NE operator" privilege or higher.
l Creating EPLAN Services has been completed.
Context
Legend Information
Figure 12-65 shows legend information about U2000 operations.
Background Information
l For EVPLAN services, you can query the capacity of a MAC address table where MAC
addresses are queried based on VLAN IDs and the capacity of a MAC address table
where MAC addresses are queried based on VB logical ports.
l For EPLAN services, you can query the capacity of a MAC address table where MAC
addresses are queried based on VB logical ports.
2
4
Step 2 Query the actual number of dynamically learned MAC addresses based on the VB ports.
Configuration example:
2
4
----End
12.8 Parameters
This section describes how to configure parameters related to Ethernet services.
QinQ Type Area 0x0600 to 0xFFFF Display the QinQ type area.
Default:0x8100 This parameter indicates the
VLAN protocol used by the
packet that is transmitted by
QinQ.
NOTE
The QinQ Type Area
parameter must be set to the
same value for interconnected
boards; otherwise, traffic will
be interrupted.
Table 12-45 Parameters on the Basic Attributes tab page (external port)
Field Value Description
Table 12-46 Parameters on the Basic Attributes tab page (external port)
Field Value Description
Table 12-50 Parameters on the Flow Control tab page (external port)
Field Value Description
Table 12-51 Parameters on the Flow Control tab page (external port)
Field Value Description
Port Rates Time Slice (m) 0 to 30 Indicates the traffic rate time
Default: 0 window of an external port.
Port Rates Time Slice (m) 0 to 30 Indicates the traffic rate time
Default: 0 window of an external port.
Port Rates Time Slice (m) 0 to 30 Indicates the traffic rate time
Default: 0 window of an external port.
Table 12-55 Parameters on the Advanced Attributes tab page (external port)
Table 12-56 Parameters on the Advanced Attributes tab page (external port)
Field Value Description
Table 12-60 Parameters on the Advanced Attributes tab page (internal port)
Field Value Description
Table 12-61 Parameters on the Advanced Attributes tab page (internal port)
Field Value Description
Operation Type Values of parameters vary Sets the operation type for
with different boards and the EVPL(QinQ) services.
products. l Add S-VLAN: Adds S-
Add S-VLAN, Add S- TAG based on the PORT
VLAN and C-VLAN, Strip route.
S-VLAN, Strip S-VLAN
and C-VLAN, Transparently l Add S-VLAN and C-
transmit S-VLAN, Translate VLAN: Adds S-TAG and
S-VLAN, Transparently C-TAG based on the
transmit C-VLAN, PORT route.
Port Type UNI, C-Aware, S-Aware (for Sets the network attributes
boards that support QinQ) for a port.
Default: UNI If the port is of the UNI
type, the port processes the
tag attributes in 802.1Q and
the port has the Tag, Access,
and Hybrid attributes.
If the port is of the C-Aware
type, the port does not
process the tag attributes in
802.1Q. It determines that
the data packet carries the
C-VLAN tag and processes
only the data packet that has
the C-VLAN tag.
If the port is of the S-Aware
type, the port does not
process the tag attributes in
802.1Q. It determines that
the data packet carries the S-
VLAN tag and processes
only the data packet that has
the S-VLAN tag.
TAG Tag Aware, Access, Hybrid TAG is used to set the type
Default: Tag Aware of the processed messages.
The tag aware port only
processes the messages with
a tag, and those messages
without a tag are discarded.
However, the Access port is
quite the contrary. The
hybrid port processes the
two types of messages. It
adds a tag to the messages
without a tag according to
the VLAN ID of this port.
Bridge Switch IVL/Ingress Filter Enable, Selects the bridge switch mode.
Mode SVL/Ingress Filter
Disable
Default: IVL/Ingress
Filter Enable
Bridge Learning Values of default with Bridge Learning Mode (Ethernet LAN
Mode different bridge mode. For Service) indicates how the bridge learns
details, click the links in the MAC address. Bridge Learning
the Description column. Mode is classified into the shared VLAN
learning and independent VLAN learning
modes. The shared VLAN learning mode
indicates learning and forwarding based
on the MAC address. The independent
VLAN learning mode indicates learning
and forwarding based on the VLAN and
MAC address.
Mount Port For example: PORT1 The mount port may be the PORT port or
VC trunk port.
Operation Type Add S-VLAN base for You can perform operations as follows:
Port, Add S-VLAN base l Mounting that is based on port and for
for Port and C-VLAN, which the S-VLAN tag is added
Mount Port, Mount Port
and base for Port and S- l Mounting that is based on port and C-
VLAN VLAN and for which the S-VLAN
tag is added
l Mounting that is based on port
l Mounting that is based on port and S-
VLAN
Port Type UNI, C-Aware, S-Aware Sets the network attributes for a port.
(for boards that support If the port is of the UNI type, the port
QinQ) processes the TAG attributes in 802.1Q
Default: UNI and the port has the Tag Aware, Access
and Hybrid attributes.
If the port is of the C-Aware type, the
port does not process the tag attributes in
802.1Q. It determines that the data packet
carries no S-VLAN tag and processes
only the data packet that has the C-
VLAN tag.
If the port is of the S-Aware type, it can
identify and process the VLAN
information about the provider. If the
QinQ Type field is valid, this port treats
the outmost label carried by the packets
as S-VLAN.
TAG Access, Tag aware, Sets the tag attribute of the VB.
Hybrid
Default VLAN 1 to 4095 Sets the VLAN ID. To set the VLAN ID,
ID right-click a port, and choose VLAN
Allocation from the shortcut menu.
Then, in the dialog box displayed, set the
VLAN ID of the VB link that the port
belongs to. You can also set the VLAN
ID in the VLAN Filtering tab.
Working Mode For example: 10M Half- Displays the working modes of the
Duplex Ethernet port. Auto-Negotiation can
automatically determine the optimized
working modes of the connected ports.
This mode is easy to maintain and is
recommended.
During configuration, make sure that
working modes of the connected ports
are consistent. If the working modes are
different, the services are down.
VLAN ID 1 to 4095 Sets the VLAN ID. To set the VLAN ID,
right-click a port, and choose VLAN
Allocation from the shortcut menu.
Then, in the dialog box displayed, set the
VLAN ID of the VB link that the port
belongs to. You can also set the VLAN
ID in the VLAN Filtering tab.
MAC Address 00-00-00-00-00-01 to FE- Sets the MAC address of VLAN unicast.
FF-FF-FF-FF-FF To set the MAC address of VLAN
The first byte is an even unicast, right-click a port that is already
number. allocated with a VLAN ID, and choose
VLAN Unicast from the shortcut menu.
Then, in the dialog box displayed, set the
MAC address of VLAN unicast for the
port. You can also set the MAC address
of VLAN unicast in the VLAN Unicast
tab.
Forwarding For example: PORT1, Displays the physical port that is actually
Physical Port VCTRUNK1 attached to the VB link.
Available For example: PORT4 Displays the queried physical ports that
forwarding ports can be used for forwarding.
Selected For example: PORT4 Displays the selected ports that can be
forwarding ports used for forwarding.
Physical Port For example: PORT1 Displays the name of the port.
Bound Path For example: VC4-1- Specifies the number of the path that you
VC3(1) want to bind, including VC4 path No.
and VC12/VC3 path No. VC4-1-
VC12(1-3).
Number of Bound For example: 1 Displays the number of the bound paths.
Paths
This section describes the process of configuring Ethernet services in the packet transport
network.
VPWS MPLS
- VLAN
VPWS MPLS
- VLAN
VPLS MPLS
13.1.1.1 E-Line/E-LAN
MEF defines two types of Layer 2 Ethernet services: E-Line service using point-to-point
Ethernet virtual connection (EVC) and E-LAN service using multipoint-to-multipoint EVC.
E-Line Service
Any Ethernet service that is based on a point-to-point EVC shall be designated as an Ethernet
Line (E-Line) service type, as shown in Figure 13-1.
A
EVC1
A Metro carrier
Ethernet
EVC2
B
B
E-Line1
E-Line2
Table 13-2 shows different E-Line services and related carrier technologies.
PW Tunnel
B
QinQ link B:VLAN = 1-200
B
B
Ethernet
service UNI
A
NE4
E-LAN Service
Any Ethernet service that is based on a Multipoint-to-Multipoint Ethernet Virtual Connection
(EVC) shall be designated as an Ethernet Line (E-LAN) Service type, as shown in Figure
13-2.
A Metro carrier B
Ethernet
B
A
E-LAN MPLS
CE A
Services
Carried
by PWs Ethernet
service
NE A
PW 2
NE C
PW1
Ethernet service PSN CE C
PW Label=20
Tunnel Label=100
PW3
NE B
Ethernet
service
PW
Tunnel
CE B
Service flow
E-LAN VLAN
Services CE A
Carried
by QinQ Ethernet
service
Links NE A
Ethernet service
SVLAN NE C
PSN CE C
NE B
Ethernet
service
QinQ link
CE B Service flow
E-LAN Port
CE A
Services carrier
Carried (physical UNI
Ethernet
by Ports isolation) service
Port1 NNI
NE A
Port3
NNI Port2
Port2 NE C
Ethernet PSN
service CE C
Port 3 Port1
Port2
NE B Port 3
Ethernet
service Port1
CE B
Service flow
13.1.1.2 VPWS/VPLS
Layer 2 virtual private network (L2VPN) defined by IETF includes the virtual private wire
service (VPWS) and virtual private LAN service (VPLS). VPWS is used to provide point-to-
point service at Layer 2 and VPLS is used to simulate a local area network (LAN) in a wide
area network (WAN).
VPWS
VPWS is a Layer 2 virtual private network (VPN) technology for point-to-point transmission.
It performs one-to-one mapping between a received attachment circuit (AC) and a pseudo
wire (PW). By binding ACs and PWs in the <AC, PW, AC> format to form a virtual circuit,
VPWS achieves transparent transmission of Layer 2 services between users. Figure 13-3
shows the application of VPWS.
VPLS
VPLS is a Layer 2 VPN technology for simulating LANs. Using VPLS, each L2VPN
considers an NE as a virtual switching instance (VSI), and this VSI is used to achieve
mapping between multiple ACs and PWs, and connect multiple Ethernet LANs so that the
LANs work as if they are one LAN.
VPLS is an important technology for MANs. It can connect multiple Ethernet-powered
enterprise networks. As shown in Figure 13-4, VPLS provides LAN services across the WAN
for customer A.
PW
HQ of PW
company A VPLS
VSI AC
NE 1
PW
VPLS
PSN
NE 3
Branch of
company A
PW
VSI PW
NE 2
AC
VPLS AC Tunnel
PW Service flow
Branch of
company A
MPLS
MPLS is a type of transmission technology and it is used to transparently transmit data
packets between users. The MPLS technology includes pseudo wire edge to edge emulation
(PWE3) and MPLS tunnel.
l PWE3
PWE3 is a type of L2VPN protocol. In a packet switched network (PSN), PWE3
provides tunnels and emulates various services, for example, Ethernet services. PWE3
carries services that are received over different mediums on one MPLS network,
eliminating the need for constructing multiple networks and therefore reducing the
OPEX.
PWE3 creates point-to-point tunnels, which are separated from each other. The Layer 2
packets from users are transparently transmitted in PWs. PWs must be carried on the
MPLS Tunnel.
Branch of
company A
NE3
HQ of
company A NE1 PSN
NE2
HQ of
company B
Branch of
company B
PW Service flow
l MPLS Tunnel
The MPLS tunnel is defined by the MPLS protocol. Independent from services, the
MPLS tunnel implements end-to-end transmission and carries PWs that contain the
services. Figure 13-6 shows how the MPLS tunnel is used to transmit services.
HQ of Branch of
company A company A
NE 1 NE 2 NE 3
PSN
HQ of Branch of
company B company B
PW MPLS tunnel
QinQ
Services from the user side are carried by the QinQ link on the network side. Multiple
VLANs of the user network are encapsulated in QinQ mode into one VLAN in the transport
network. In this way, the VLAN resources in the transport network are saved. The QinQ
technology is a VLAN stacking and nesting technology. Using the QinQ technology, data
packets carry two layers of VLAN tags for the identification purpose. This removes the limit
of the original solution in which only one layer of VLAN tag is used, extending the VLAN
IDs. Figure 13-7 shows the application of the QinQ technology.
NE3
C-VLAN1
13.1.3 UNI/NNI
A UNI refers to the Ethernet port that is connected to the user equipment. A UNI is used for
the user-side configuration of an Ethernet service. An NNI refers to the Ethernet port that is
connected to the packet transport network. An NNI is used for the network-side configuration
of an Ethernet service.
UNI
l V-UNI
A V-UNI is a virtual user-network interface. Each service on a UNI corresponds to a
logical V-UNI.
A UNI can receive multiple services. That is, a UNI may correspond to multiple V-UNIs.
NNI
Based on the modes of carrying services, NNIs can be classified into three types, namely,
NNIs carrying services by ports, NNIs carrying services by PWs, and NNIs carrying services
by QinQ links.
encapsulation mode at the access ports. In this manner, multiple packets with different
VLAN tags from the user-side network can be encapsulated into the same VLAN for
transport. Therefore, the occupied VLAN resources on the transport network are
reduced. E-Line services and E-LAN services can be carried by the QinQ link on the
network side.
HQ of company A
NE 1 E-LAN
Access
Point
NE 2 NE 4
Access
Access Point
Point NE 3
Access
Point
Branch of Branch of
company A company A
Branch of
company A
l PW-carried E-LAN services, that is, virtual private LAN service (VPLS).
l Composite services, that is, E2E services that comprise different types of services. On an
OptiX OSN 8800 packet network, a composite service comprises PWE3 and VPLS
services.
A composite service contains service components and connection points. Figure 13-9 shows
the model of a composite service.
l Service components: indicate the services that constitute a composite service. For
example, for a composite service that comprises PWE3 and VPLS services, the service
components are PWE3 and VPLS services.
l Connection points: connect service components to form a composite service. Connection
points are classified into the following types, which show the connection mode of service
components.
– PW connection points: indicate that service components are connected using PWs
to form a composite service.
– Port connection points: indicate that service components are connected using
service ports (that is, UNI ports) to form a composite service.
NOTE
Before configuring an Ethernet service on a packet network in E2E mode, ensure that the optical layer of
the packet network has been commissioned and configured, and the desired NEs, logical boards, and
logical fibers have been created. For details, see the Commissioning Guide.
If a universal line board is used to receive and transmit packet services, configure ETH virtual ports of
the universal line board and ODUk mapping paths on the U2000 before configuring services following
the configuration procedure. For details, see 7.2 Configuring Virtual Ports and Mapping Paths.
In this configuration mode, the user can configure tunnel automatic protection switching
(APS) and PW APS during the configuration of a multiprotocol label switching (MPLS)
tunnel and a PWE3 service. For an Ethernet service with tunnel APS or PW APS and an
Ethernet service without tunnel APS or PW APS, the configuration procedures are the same
but the parameters that need to be set vary. For details, see 13.2.4 Configuring an MPLS
Tunnel and 13.2.6 Configuring a PWE3 Service.
This topic describes the procedure for configuring an Ethernet service without tunnel APS or
PW APS on a packet network in E2E mode, as shown in Figure 13-10.
Configure a composite
Configure a composite
Configure a PWE3 service. Configure a VPLS service. service (method 1,
service (method 2)
recommended)
Enable ETH OAM for Enable ETH OAM for Enable ETH OAM for
the service. the service. the service.
Use ETH OAM to test Use ETH OAM to test Use ETH OAM to test
service connectivity. service connectivity. service connectivity.
Configure other
Ethernet features.
Mandatory
End Optional
Prerequisites
You are an NMS user with " NE operator" privilege or higher.
Precautions
NOTE
Procedure
Step 1 In the NE Explorer, select the NE. In the navigation tree, choose Configuration > packet
configuration > MPLS Management > Basic Configuration and click Query.
Step 2 On the Basic Configuration tab, set LSR ID. For example, set it to 15.15.15.15.
NOTE
l When the LSR ID is specified for the first time, no warm-reset occurs on the NE. If the specified
LSR ID is then changed, a warm-reset occurs on the NE but does not affect services.
l If the LSR ID is modified, services will not be interrupted.
l The LSR ID cannot be modified if there are tunnels.
Step 3 Optional: On the Basic Configuration tab, set other parameters. The other parameters can
retain the default values or be modified based on the actual network plan. For details about the
parameters, see 13.5.2.1 Basic Configuration.
----End
Prerequisites
You are an NMS user with " NE operator" privilege or higher.
Procedure
Step 1 In the NE Explorer, select the NE. In the navigation tree, choose Configuration > Packet
Configuration > MPLS Management > Basic Configuration.
NOTE
For networks of the same carrier, the carrier ID must be the same. A carrier ID is a case-sensitive
alphanumeric string consisting of 0 to 6 characters (a-z, A-Z, and 0-9).
Step 3 Optional: Set other global parameters. The other parameters can retain the default values or
be modified based on the actual network plan. For details about the parameters, see MPLS-TP
OAM_Global OAM Parameters in the Feature Description.
----End
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l No IP addresses are configured for ports.
Background Information
If the IP addresses to be configured are discontinuous, many IP address resources can be
configured.
The IP address resources should not contain IP addresses in the 192.168.0.0/16 network
segment, 192.169.0.0/16 network segment, or the network segments to which LSR IDs and
NE IP addresses belong.
NOTICE
After you set IP addresses to ports manually for a NE, you must synchronize NE data to the
U2000, otherwise data inconsistency may occur between NE and U2000 and the conflict may
occur when you allocate IP addresses to ports automatically to the same NE or other NEs.
Procedure
Step 1 Specify a network segment for automatic allocation of IP addresses to ports.
1. Choose Configuration > IP Address Managementfrom the main menu from the main
menu.
2. Click New and specify the network segment for automatic allocation of IP addresses to
ports.
----End
Prerequisites
You are an NMS user with " NE operator" privilege or higher.
Procedure
Step 1 In the NE Explorer, select the NE. In the navigation tree, choose Configuration > Packet
Configuration > Interface Management > Ethernet Interface.
Step 2 Select an NNI port and set the mandatory parameters for the NNI port.
l On the Basic Attributes tab, set Port Mode to Layer 3.
l On the Layer 3 Attributes tab, set Specify IP Address to Manually and set IP Address
and IP Mask for the port.
NOTE
l Ensure that the IP address of the NNI port is not in the same network segment as that of another port
on which services have been configured or the IP address of the NE; otherwise, services may be
interrupted or the NE may be unreachable.
l Along an MPLS tunnel, the IP address of a port and that of its next-hop port must be in the same
network segment.
Step 3 Optional: Set other NNI port parameters. The other parameters can retain the default values
or be modified based on the actual service plan. For details, see 13.5.1 Parameter
Description: Attributes of Ethernet Interface.
----End
Prerequisite
l You are an NMS user with " NE operator" privilege or higher.
Background Information
l L2 links can be created by using the link search function only for EX2 and EG16
boards.
2. In the navigation tree on the left, select the NE where L2 links need to be searched for
and click . In the dialog box that indicates the search operation was successful,
click Close. The search result list is displayed.
3. In the search result list, select one or more L2 links in the Not exist state and click Creat
on the lower right of the window. In the dialog box that indicates the creation of L2 links
was successful, click Close.
4. Optional: In the Confirm dialog box that prompts Are you sure to import links as
fibers/cables, perform the following operations:
a. Click OK in the Confirm dialog box.
b. The Import Link dialog box is displayed, select one or multiple links and do as
follows:
n Click . All links in the Available Link area are moved to the
Selected Link area. This operation is applicable to batch import.
n Click . All links in the Selected Link area are moved to the
Available Link area.
NOTE
When import the link, you can set whether to allot IP address automatic on the ports of the
link.
c. Click OK. In the dialog box that prompts the success, click Close.
5. Optional: If there are links in the Conflicting state, click Delete Conflicting Links on
the lower right of the window. In the dialog box that indicates the operation was
successful, click Close to delete the links in the Conflicting state.
6. Optional: From the main menu of the U2000, choose Inventory > Link Management
to view the created L2 links.
NOTE
If a fault occurs during the link creation, the cause is displayed in the Operation Result dialog
box. You can rectify the fault based on the cause.
6. In the Create Link dialog box, click Cancel.
7. Optional: From the main menu of the U2000, choose Inventory > Link Management
to view the created L2 links.
Prerequisites
l You are an NMS user with " NE operator" privilege or higher.
l Configuring Basic Parameters of an MPLS Tunnel has been completed.
Procedure
Step 1 From the main menu of the U2000, choose Service > Tunnel > Create Tunnel. The Create
Tunnel window is displayed.
Step 2 Set the basic information about the MPLS tunnel as follows:
l Tunnel Name: The value of this parameter is automatically generated on the U2000. The
user can also enter a tunnel name based on the service plan. A tunnel name cannot
contain Chinese characters.
l Protocol Type: MPLS
l Signaling Type: Static CR
l Service Direction: The value of this parameter can be Bidirectional (recommended) or
Unidirectional. The user can also set the value to Unidirectional based on the service
plan.
l Protection Type: Protection-Free
Step 3 Configure the NEs that the MPLS tunnel traverses.
l Method 1 (recommended): select the desired NEs in the topology view. This method is
vivid and applies to the scenario where there are many NEs.
a. In the topology view on the right, double-click the desired NEs one by one. Node
Role of the NEs is Ingress, Egress, and Transit in turn.
NOTE
– Click to return to
the upper-level physical topology view.
l Method 2: select the desired NEs from the NE list. This method applies to the scenario
where there are a few NEs.
a. Click Add. Choose Node from the drop-down list that is displayed.
b. In the window that is displayed, select an NE that the MPLS tunnel traverses. The
user can hold down Shift to select multiple NEs. Click and OK.
Before using this method, ensure that 13.2.3.5 Creating L2 Links has been completed.
a. In the topology view on the right, double-click the ingress and egress NEs. Node
Role of the NEs is Ingress, Egress, and Transit respectively.
b. Click Route Constraint. In the Set Route Constraint window that is displayed,
add an NE or port, and set Explicit Restriction and Exclude Restriction for the
NE or port.
3. In the list that is displayed, select an egress port of the ingress NE and click OK. The
egress port is the NNI port of the ingress node.
4. Select the NNI ports for the transit and egress nodes by repeating the preceding steps.
For the transit node, Intbound Interface/Ring and Outbound Interface/Ring need to
be set. For the egress node, Intbound Interface/Ring needs to be set.
Step 5 Configure MPLS-TP OAM for the MPLS tunnel.
1. Click MPLS-TP OAM(Y.1731).... The Configuration MPLS-TP OAM dialog box is
displayed.
2. In the dialog box, click Add, set OAM Status of the MEP and RMEP to Enable, and
click OK.
Step 6 Optional: Set other parameters for the MPLS tunnel and MPLS-TP OAM based on network
planning.
l In general, the other parameters of MPLS-TP OAM and an MPLS tunnel use the default
values.
l For the other parameters of an MPLS tunnel, see 13.5.2.3 Parameters for Configuring
a Static Tunnel (End-to-End Mode). For the other parameters of MPLS-TP OAM, see
MPLS-TP OAM_Global OAM Parameters in the Feature Description.
Step 7 Click Apply in the lower part to apply the MPLS tunnel configurations. The Operation
Succeed dialog box is displayed.
Step 8 In the Operation Result dialog box, click Browse Trail to view the configured MPLS tunnel.
1. In the Manage Tunnel window that is displayed, ensure that Deployment Status is set
to Deployed.
2. View the information about the tunnel and sub-layers. Select the configured tunnel. Click
the Topology tab in the lower part of the Manage Tunnel window to unfold the tunnel
and all the sub-layers.
NOTE
– The tunnel contains information about the ODUk, OTUk, and OCh layers only when the tunnel was
carried on an ODUk channel.
– After connecting logical fibers and before creating the tunnel, the users must create or search for an
OCh trail.
Step 9 Test the bidirectional connectivity of the MPLS tunnel using MPLS-TP OAM.
1. In the Manage Tunnel window, right-click the MPLS tunnel and choose OAM >
MPLS-TP OAM Test. The MPLS-TP OAM Test dialog box is displayed.
2. In the Select column, select the check box corresponding to the desired MPLS tunnel
and click Run to start a loopback (LB) test. After the LB test is complete, click LB
Statistics to view the detailed test results.
3. Optional: Select LT from the drop-down list, select the check box corresponding to the
desired MPLS tunnel, and click Run to start a linktrace (LT) test. After the LT test is
complete, click LT Statistics to view the detailed test results.
----End
Prerequisites
l You are an NMS user with " NE operator" privilege or higher.
l Configuring Basic Parameters of an MPLS Tunnel has been completed.
Procedure
Step 1 From the main menu of the U2000, choose Service > Tunnel > Create Tunnel. The Create
Tunnel window is displayed.
Step 2 In the basic information configuration window, set Protection Type and Switching Mode.
For example, set Protection Type to 1:1 and Switching Mode to Dual-ended switching.
Step 3 Configure the NEs and NNI ports that the working and protection tunnels traverse and
configure MPLS-TP OAM for the working and protection tunnels.
Step 4 Use MPLS-TP OAM to test the bidirectional connectivity between the working and protection
tunnels. The test procedure is the same as that for an MPLS tunnel without tunnel APS. For
details, see Step 4 in 13.2.4.1 Configuring a single MPLS Tunnel Without Tunnel APS.
----End
Prerequisites
l You are an NMS user with " NE operator" privilege or higher.
l Configuring Basic Parameters of an MPLS Tunnel has been completed.
Procedure
Step 1 From the main menu of the U2000, choose Service > Tunnel > Batch Create Tunnel. The
Batch Create Tunnel windows is displayed.
Step 2 Set the basic information about the MPLS tunnel as follows:
l Before using this method, ensure that 13.2.3.5 Creating L2 Links has been completed.
1. In the topology view on the right, double-click the ingress and egress NEs. Node Role of
the NEs is Ingress, Egress, and Transit respectively.
2. Click Route Constraint. In the Set Route Constraint window that is displayed, add an
NE or port, and set Explicit Restriction and Exclude Restriction for the NE or port.
Prerequisites
You are an NMS user with " NE operator" privilege or higher.
Background Information
C-VLAN and S-VLAN services can share the same port only on theTN54EX8, TN55EG16,
TN54HUNQ2, and TN54HUNS3 boards.
For the TN54EX8, TN55EG16, TN54HUNQ2, and TN54HUNS3 boards on an NE, QinQ
type domain of all UNI ports must be set to the same value if it is not set to 8100.
For details about parameter description, see 13.5.1 Parameter Description: Attributes of
Ethernet Interface.
Attributes of UNI Ports for Transmission of Both C-VLAN and S-VLAN Services
1. In the NE Explorer, select the NE. In the navigation tree, choose Configuration >
Packet Configuration > Interface Management > Ethernet Interface.
2. Configure UNI port attributes based on the actual service types.
For UNI ports, set the parameters as follows:
a. On the Basic Attributes tab, set Encapsulation Type to 802.1Q.
b. On the Basic Attributes tab, set Working Mode and Max Frame Length (bytes)
based on the service plan.
c. On the Layer 2 Attributes tab, perform the following operations:
n Set TAG and Default VLAN ID.
n Set QinQ type domain based on the received services. When QinQ type
domain of an UNI port is set to A, the packets whose TPIDs are 8100 or A can
pass through the UNI port.
NOTE
For the TN54EX8, TN55EG16, TN54HUNQ2, and TN54HUNS3 boards on an NE, QinQ
type domain of all UNI ports must be set to the same value if it is not set to 8100.
n Set SVLANs.
NOTE
For details about parameter description, see 13.5.1 Parameter Description: Attributes
of Ethernet Interface.
For details about the configuration of LAGs and MC-LAGs, see the Feature Description:
l LAG
l MC-LAG
Prerequisites
l You are an NMS user with " NE operator" privilege or higher.
l Configuring Basic Parameters of an MPLS Tunnel has been completed.
l Configuring an MPLS Tunnel has been completed.
l Configuring Service-Related Basic Parameters and Features has been completed.
Procedure
Step 1 From the main menu of the U2000, choose Service > PWE3 Service > Create PWE3
Service. The Create PWE3 Service window is displayed.
Step 2 In the Create PWE3 Service window, set the basic attributes. For details, see 13.5.3.2 E-
Line Service Parameters (Configuration in End-to-End Mode).
NOTE
l Services can be configured using a service template. The user can select a template from the Service
Template drop-down list or create a template.
l Set Service Type to ETH.
Step 3 Click Configure Source and Sink to configure the source and sink nodes.
Step 4 Select the desired NE. In the pane on the right, select the board and port that accept services
and configure VLAN information for them. Click Add Node to configure the source node.
NOTE
l Setting Priority Type is optional. Set this parameter to 802.1P when packets need to be forwarded
based on port+VLAN+VLAN priority.
l When Priority Type is set, Priority Field must be set. The value of Priority Field is an integer
ranging from 0 to 7 and 7 indicates the highest priority.
l The E-Line services carried by PWs (Based on VLAN priorities) can't coexist with ETH OAM.
Step 5 Repeat Step 4 to add and configure the sink node and click OK.
NOTE
If the MPLS-TP OAM function has not been enabled when you create the PWE3 service, you can enable the
function after the service is configured. The operation procedure is as follows:
1. In the Manage PWE3 Service window, right-click the desired PWE3 service and choose PW OAM >
Configure MPLS-TP OAM from the shortcut menu.
2. In the displayed Configuration MPLS-TP OAM dialog box, click Add, set OAM Status of the MEP
and RMEP to Enable, and click OK.
3. Right-click the desired PWE3 service again and choose PW OAM > Enable MPLS-TP OAM from the
shortcut menu.
Step 7 Specify the tunnel that forwards PWs. Select the desired PW that has been created, double-
click the Forward Tunnel column and click . The Select Tunnel window is displayed.
Specify the tunnel that forwards PWs and click OK.
NOTE
Parameters such as PW ID, Forward Label, and Reverse Label can use the automatically assigned
values or be specified based on the service plan.
Step 8 Click OK or Apply on the lower right of the window to complete PWE3 service
configuration.
NOTE
Select ETH OAM CC in the lower left corner of the window to create ETH OAM.
Step 9 In the Operation Result dialog box, click Browse Trail to view the newly created PWE3
service.
Step 10 Perform a loopback (LB) test to check the bidirectional connectivity of the PWE3 service as
follows: In the PWE3 Service Management window, right-click the PWE3 service and
choose Ethernet OAM > LB Test.
Step 11 In the LB Test dialog box that is displayed, select the PWE3 service and click Run.
----End
Prerequisites
l You are an NMS user with " NE operator" privilege or higher.
l Configuring Basic Parameters of an MPLS Tunnel has been completed.
l Configuring an MPLS Tunnel has been completed.
l Configuring Service-Related Basic Parameters and Features has been completed.
Precautions
l MPLS tunnel APS and PW APS are mutually exclusively.
l The MPLS-TP OAM function must be configured and enabled for PWE3 services with
protection. Otherwise, the service will fail to be deployed.
Procedure
Step 1 From the main menu of the U2000, choose Service > PWE3 Service > Create PWE3
Service. The Create PWE3 Service window is displayed.
Step 2 Set the basic information about the PWE3 service in the same way as configuring a PWE3
service without PW APS. In addition, ensure that Protection Type has been set to PW APS
Protection.
Step 3 Specify the tunnel that forwards the working PW and the tunnel that forwards the protection
PW and click Single Source and Single Sink in the Node List area.
Step 4 The other operations are the same as those for configuring a PWE3 service without PW APS
protection. For details, see Step 3 in 13.2.6.1 Configuring a PWE3 Service Without PW
APS.
----End
Prerequisites
l You are an NMS user with " NE operator" privilege or higher.
l Configuring Basic Parameters of an MPLS Tunnel has been completed.
l Configuring an MPLS Tunnel has been completed.
l Configuring Service-Related Basic Parameters and Features has been completed.
Procedure
Step 1 From the main menu of the U2000, choose Service > VPLS Service > Create VPLS
Service. The Create VPLS Service window is displayed.
Step 2 In the Create VPLS Service window, set the basic attributes of the virtual private LAN
service (VPLS).
Step 3 In Physical Topology on the right, double-click the NE where the VPLS service needs to be
configured and set Node Role of the NE to NPE.
Step 4 Click Details in the lower left corner of the window and click the PW Configuration tab. On
the tab, select a tunnel that forwards a PW as follows: Select the PW and double-click the
Forward Tunnel column and click . The Select Tunnel window is displayed.
NOTE
Other parameters such as PWID, Forward Label, and Reverse Label can use the automatically
assigned values or be specified based on the service plan.
NOTE
Tunnels must be created between NEs that the created VPLS service traverses. If a tunnel that forwards
PWs has not been created, click Create in the lower left corner of the Select Tunnel window. In the
Create Tunnel window that is displayed, create the tunnel that forwards PWs. For details, see
Configuring an MPLS Tunnel.
Step 6 Select the associated NEs one by one, click SAI Configuration and SAI List, and click
Create.
Step 7 In the displayed Create SAI window, select the board, port, and service VLAN mounted to
each of the NEs.
Step 8 Click OK or Apply to complete VPLS service configuration.
Step 9 In the Operation Result dialog box, click Browse Trail to view the VPLS service.
Step 10 Perform a loopback (LB) test to check the bidirectional connectivity of the VPLS service as
follows: In the VPLS Service Management window, right-click the VPLS service and
choose Ethernet OAM > LB Test.
Step 11 In the LB Test dialog box that is displayed, select the VPLS service and click Run.
----End
Prerequisites
l You are an NMS user with " NE operator" privilege or higher.
l Configuring Basic Parameters of an MPLS Tunnel has been completed.
l Configuring an MPLS Tunnel has been completed.
l Configuring Service-Related Basic Parameters and Features has been completed.
Procedure
Step 1 From the main menu of the U2000, choose Sevice > Composite Sevice > Create Composite
Sevice. The Create Composite Service window is displayed.
Step 3 Click Add VPLS Node-SAI. In the Select VPLS Node window that is displayed, click the
Add Device tab. On the tab, select the NE where a virtual private LAN service (VPLS)
service needs to be configured, and select the required board, port, and service VLAN. Click
OK.
Step 4 Click Add PWE3 Node. In the Select PWE3 Node window that is displayed, select the NE
where a pseudo wire emulation edge-to-edge (PWE3) service needs to be configured, select
the required board, port, and service VLAN, and click OK.
Step 5 Click the PW Configuration tab in the lower right corner and select the tunnel that forwards
the desired PW.
Step 7 In the Operation Result dialog box, click Browse Trail to view the newly created composite
service.
Step 8 Right-click the composite service and choose Ethernet OAM > Start CC from the shortcut
menu.
Step 9 In the Start CC window that is displayed, select an MA from MA Information List and
click . The selected MA is displayed in Selected MA Information List. Click
OK.
Step 10 Right-click ETH OAM Configuration View and choose LB Test.
Step 11 In the LB Test window that is displayed, select the composite service and click Run to start a
loopback (LB) test.
----End
Prerequisites
l You are an NMS user with " NE operator" privilege or higher.
l Configuring Basic Parameters of an MPLS Tunnel has been completed.
l Configuring an MPLS Tunnel has been completed.
l Configuring Service-Related Basic Parameters and Features has been completed.
PWE3
VPLS
Working
OptiX NE
Protection
Procedure
Step 1 On the PW Configuration tab, select the tunnels of the working and protection PWs.
Step 2 On the PWE3 Protection Parameter tab, set Protection Mode, Enable Status, and
Switching Mode.
NOTE
If Protection Mode has been set to 1:1, Switching Mode must be set to Dual-ended Switching.
Step 3 The other operations are the same as those for creating a composite service without PW APS.
For details, see Step 1.
----End
Prerequisites
l You are an NMS user with " NE operator" privilege or higher.
l Configuring Basic Parameters of an MPLS Tunnel has been completed.
l Configuring an MPLS Tunnel has been completed.
l Configuring Service-Related Basic Parameters and Features has been completed.
Procedure
Step 1 Create an unterminated pseudo wire emulation edge-to-edge (PWE3) service, that is, virtual
private wire service (VPWS) or E-line service.
1. From the main menu of the U2000, choose Service > PWE3 Service > Create PWE3
Service. The Create PWE3 Service window is displayed.
2. In the Create PWE3 Service window, set the basic attributes. For details, see 13.5.3.2
E-Line Service Parameters (Configuration in End-to-End Mode).
NOTE
– Composite services can be configured using a service template. The user can select a template
from the Service Template drop-down list or create a template.
– Set Service Type to ETH.
3. Click Configure Source and Sink to configure the source and sink nodes.
4. Select the desired NE. In the pane on the right, select the board and port for service
access to configure a VLAN. Click Add Node to configure the source node.
5. Select a sink node that is not terminated. In the navigation tree on the left, click
Unterminated and set LSR ID for the sink node. Click Add Node and OK.
6. Specify the tunnel that forward a PW as follows: Double-click the Forward Tunnel
column. In the Select Tunnel window that is displayed, select the tunnel that forwards
the PW and click OK.
7. Specify the forward and reverse labels of the PWs. Reverse labels are automatically
assigned by the system but forward labels need to be manually set.
9. In the Operation Result dialog box, click Browse Trail to view the unterminated PWE3
service that is newly created.
10. Record the PW ID that is automatically generated and forward and reverse labels
because the information is required during the configuration of the unterminated PW for
a virtual private LAN service (VPLS) service. On the PW tab, click PW.
NOTE
In this example, PW ID is 39, Incoming Label is 32123, and Outgoing Label is 779.
2. Set basic attributes and add a VPLS node as follows: In the Create VPLS Service
window, set the basic attributes and click Add to select NPE. The Select NE window is
displayed.
3. In the Select NE window, select the desired NE, click , and click OK.
4. Create an unterminated PW that carries the VPLS service as follows: On the PW
Configuration tab, click Create to choose Unterminated PW. The Create PW window
is displayed.
5. In the Create PW window, set the basic attributes. Ensure that PW ID, Outgoing Label,
and IncomingLabel are the same as those set during PWE3 service creation. In the
Advanced Attribute area, specify the tunnel as follows: Double-click the blank area in
the Tunnel text box. In the window that is displayed, specify the tunnel that forward the
PW and click OK.
6. Create a service access interface (SAI) that carries the VPLS service as follows: On the
PW Configuration tab, click SAI List and click Create. The Create SAI window is
displayed.
7. In the Create SAI window, select the required board, port, and service VLAN. Click
OK.
Step 3 Create a composite service. That is, connect the unterminated PWE3 and VPLS services to
form an end-to-end composite service.
1. From the main menu of the U2000, choose Service > Composite Service > Create
Composite Service. The Create Composite Service window is displayed.
3. Click Select and choose VPLS and PWE3. In the Set Filter Criteria window that is
displayed, click Filter to search for the unterminated PWE3 and VPLS services that have
been created, and click Select to add them to Service Component.
4. Click Create to choose PW. The Create PW Connection Point window is displayed.
7. Click OK or Apply on the lower lower right of the window to create the composite
service.
----End
This topic does not describe the single-station mode. For details, see the following topics in
the Feature Description:
Table 13-4 provides the process for configuring the E-Line services carried by PWs.
NOTE
If a universal line board is used to receive and transmit packet services, configure virtual Ethernet ports
of the universal line board and ODUk mapping paths on the U2000 before configuring services
following the configuration procedure. For details, see 7.2 Configuring Virtual Ports and Mapping
Paths.
Figure 13-11 Configuration flow for the E-Line services carried by PWs
Start
1
Configure the UNI
2
Configuring the DCN
Function of a Port
3
Configure the NNI for
the services carried by
the static MPLS tunnel
4
Configure the MPLS
tunnel
5
Create the E-Line
services carried by
PWs
Required
End Optional
Table 13-4 Configuration flow for the E-Line services carried by PWs
St Operation Remarks
ep
St Operation Remarks
ep
2 Configuring the DCN (Optional) This operation is applicable only when the
Function for a Port UNI is an Ethernet port. The parameters are set as
follows:
When the UNI does not need to transmit the inband
DCN information, set Enable Port to Disabled.
Otherwise, set it to Enabled.
5 13.3.6.3 Configuring UNI- (Required) The parameters need to be set based on the
NNI E-Line Services service planning information.
Carried by PWs on a Per- NOTE
NE Basis For information to manage E-Line services carried by PWs
after they are configured, see 13.4.2 Managing PWE3
Services.
Table 13-5 provides the process for configuring the E-Line services carried by QinQ links.
NOTE
If a universal line board is used to receive and transmit packet services, configure virtual Ethernet ports
of the universal line board and ODUk mapping paths on the U2000 before configuring services
following the configuration procedure. For details, see 7.2 Configuring Virtual Ports and Mapping
Paths.
Figure 13-12 Configuration flow for the E-Line services carried by QinQ links
Start
1
Configure the UNI
2
Configuring the DCN
Function of a Port
3
Configure the NNI for
the services carried
by QinQ links
4
Configure the QinQ
links
5
Configure the QoS
6
Create the E-Line
services carried by
QinQ links
Required
End Optional
Table 13-5 Configuration flow for the E-Line services carried by QinQ links
Step Operation Remarks
3 Configuring the NNIs for (Required) The parameters need to be set based on
Ethernet Services Carried the service planning.
by QinQ Links
If a universal line board is used to receive and transmit packet services, configure virtual Ethernet ports
of the universal line board and ODUk mapping paths on the U2000 before configuring services
following the configuration procedure. For details, see 7.2 Configuring Virtual Ports and Mapping
Paths.
Figure 13-13 Configuration flow for the E-Line services carried by ports
Start
1
Configure the UNI
2
Configuring the DCN
Function of a Port
3
Configure the NNI for
the services carried by
ports
4
Configure the QoS
5
Create the E-Line
services carried by
ports
Required
End Optional
Table 13-6 Configuration flow for the E-Line services carried by ports
Step Operation Remarks
3 Configuring the NNIs for (Required) The parameters need to be set based on
Ethernet Services Carried by the service planning.
Ports
If a universal line board is used to receive and transmit packet services, configure virtual Ethernet ports
of the universal line board and ODUk mapping paths on the U2000 before configuring services
following the configuration procedure. For details, see 7.2 Configuring Virtual Ports and Mapping
Paths.
Start
1
Configure the UNI
2
Configuring the DCN
Function of a Port
3
Configure the QoS
4
Create the UNI-UNI
E-Line services
Required
End Optional
If a universal line board is used to receive and transmit packet services, configure virtual Ethernet ports
of the universal line board and ODUk mapping paths on the U2000 before configuring services
following the configuration procedure. For details, see 7.2 Configuring Virtual Ports and Mapping
Paths.
Figure 13-15 Configuration flow for the E-LAN services carried by PWs
Start
1
Configure the UNI
2
Configuring the DCN
Function of a Port
3
Configure the NNI for
the services carried
by static MPLS tunnel
4
Configure the MPLS
tunnel
5
Configure the QoS
6
Configure the E-LAN
services carried by
PWs
Required
End Optional
Table 13-8 Configuration flow for the E-LAN services carried by PWs
Step Operation Remarks
If a universal line board is used to receive and transmit packet services, configure virtual Ethernet ports
of the universal line board and ODUk mapping paths on the U2000 before configuring services
following the configuration procedure. For details, see 7.2 Configuring Virtual Ports and Mapping
Paths.
Figure 13-16 Configuration flow for the E-LAN services carried by QinQ links
Start
1
Configure the UNI
2
Configuring the DCN
Function of a Port
3
Confiure the NNI for
the services carried
by QinQ links
4
Configure the QinQ
links
5
Configure the QoS
6
Create the E-LAN
services carried by
QinQ links
Required
End Optional
Table 13-9 Configuration flow for the E-LAN services carried by QinQ links
Step Operation Remarks
3 Configuring the NNIs for (Required) The parameters need to be set based
Ethernet Services Carried by on the service planning.
QinQ Links
If a universal line board is used to receive and transmit packet services, configure virtual Ethernet ports
of the universal line board and ODUk mapping paths on the U2000 before configuring services
following the configuration procedure. For details, see 7.2 Configuring Virtual Ports and Mapping
Paths.
Figure 13-17 Configuration flow for the E-LAN services carried by ports
Start
1
Configure the UNI
2
Configuring the DCN
Function of a Port
3
Configure the NNI for
the services carried by
ports
4
Configure the QoS
5
Create the E-LAN
services carried by
ports
Required
End Optional
Table 13-10 Configuration flow for the E-LAN services carried by ports
Step Operation Remarks
2 Configuring the Inband DCN (Required) The E-LAN services carried by ports
occupy the NNIs exclusively. Therefore, you
need to set Enable State of the NNIs to
Disabled.
When the UNI does not need to transmit the
inband DCN information, set DCN Enabled
State to Disabled. Otherwise, set it to Enabled.
3 Configuring the NNIs for (Required) The parameters need to be set based
Ethernet Services Carried by on the service planning.
Ports
NOTE
When the Ethernet port is used to carry QinQ Link, the configuration procedure is similar to the
configuration procedure when the Ethernet port is used to carry Ethernet service. In this case, however,
the encapsulation types are different.
Follow the procedure shown in Figure 13-18 to set the attributes of an Ethernet port.
Start Start
Prerequisites
You must be an NM user with NE administrator authority or higher.
Legend Information
Figure 13-19 shows legend information about U2000 operations.
Procedure
Step 1 In the NE Explorer,select the board and set the Basic Attributes of Ethernet Ports,see 13.5.1.1
General Attributes.
Configuration example:
NOTE
4
:
l When Port Mode is set to Layer 2, Encapsulation Type can be set to Null, 802.1Q, or QinQ.
l When Port Mode is set to Layer 3, Encapsulation Type can be set to 802.1Q only. In this case,
the port can be used to carry the tunnel.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l In General Attributes, Port Mode must be set to Layer 2.
Legend Information
Figure 13-20 shows legend information about U2000 operations.
Procedure
Step 1 In the NE Explorer,select the port and set the parameters as required. For details about the
parameters, see 13.5.1.3 Layer 2 Attributes.
Configuration example:
NOTE
4
:
l TAG can be set only when Encapsulation Type is 802.1Q.
l Default VLAN ID and VLAN Priority can be set only when Encapsulation Type is 802.1Q.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l In General Attributes, Port Mode must be set to Layer 3.
Legend Information
Figure 13-21 shows legend information about U2000 operations.
Procedure
Step 1 In the NE Explorer,select the board and set the parameters as required. For details about the
parameters, see 13.5.1.4 Layer 3 Attributes.
Configuration example:
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
Legend Information
Figure 13-22 shows legend information about U2000 operations.
Procedure
Step 1 In the NE Explorer,select the board and set the parameters as required. For details about the
parameters, see 13.5.1.5 Advanced Attributes.
Configuration example:
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
Legend Information
Figure 13-23 shows legend information about U2000 operations.
Procedure
Step 1 In the NE Explorer,select the board and set the parameters as required. For details about the
parameters, see 13.5.1.2 Flow Control.
Configuration example:
----End
the physical-layer information, such as the port mode, encapsulation type, and maximum
frame length.
Prerequisites
You are an NMS user with " NE operator" privilege or higher.
Legend Information
Figure 13-24 shows legend information about U2000 operations.
Procedure
Step 1 In the NE Explorer,select the board and set the parameters as required.
Configuration example:
NOTE
4
:
l When Port Mode is set to Layer 2, Encapsulation Type can be set to 802.1Q, QinQ or Null.
– When Encapsulation Type is set to QinQ, the port identifies the QinQ packets.
– When Encapsulation Type is set to 802.1Q, the port identifies the 802.1Q packets.
– When Encapsulation Type is set to Null, The port transparently transmits the accessed
packets.
Step 2 Setting the Layer 2 Attributes of Ethernet Ports, select the board and set the parameters as
required. For details about the parameters, see 13.5.1.3 Layer 2 Attributes.
Configuration example:
NOTE
4
:
l Tag Aware: The port transparently transmits the data packet with a VLAN ID (that is, the data
packet is tagged). If a data packet does not have a VLAN ID (that is, the data packet is untagged),
the port discards the data packet. In this case, the Default VLAN ID and VLAN Priority are
meaningless.
l Access: The port adds the default VLAN ID to the data packet without any VLAN ID (that is, the
data packet is untagged). If the data packet has a VLAN ID (that is, the data packet is tagged), the
port discards the data packet.
l Hybrid: The port adds the default VLAN ID to the data packet without any VLAN ID (that is, the
data packet is untagged). If the data packet has a VLAN ID (that is, the data packet is tagged), the
port transparently transmits the data packet.
----End
13.3.4.2 Configuring the NNIs for Ethernet Services Carried by Static MPLS
Tunnels
The parameters are set in E2E mode.
For details, see 13.2.3.4 (Optional)Configuring NNI Port Attributes.
13.3.4.3 Configuring the NNIs for Ethernet Services Carried by QinQ Links
Before configuring Ethernet services that are carried by QinQ links, you need to set the
general attributes of the corresponding Ethernet port. The general attributes of an Ethernet
port define the physical-layer information, such as the port mode, encapsulation type, and
maximum frame length.
Prerequisites
You are an NMS user with " NE operator" privilege or higher.
Legend Information
Figure 13-25 shows legend information about U2000 operations.
Procedure
Step 1 In the NE Explorer, Select the board and set the parameters as required.
Configuration example:
NOTE
4
:
l When Port Mode is set to Layer 2, Encapsulation Type can be set to QinQ. When
Encapsulation Type is set to QinQ, he port identifies the QinQ packets.
----End
Context
NOTE
It is recommended that you configure bidirectional MPLS tunnels to facilitate tunnel management and
maintenance, and to improve OAM resource utilization efficiency.
During configuration of unidirectional MPLS tunnels, forward MPLS tunnel and reverse MPLS tunnel
are created separately. For a unidirectional forward MPLS tunnel, either its mapping reverse MPLS
tunnel or another tunnel can be configured to transmit BDI packets during MPLS-TP OAM
configuration; either its mapping reverse MPLS tunnel or another reverse MPLS tunnel can be
configured as the protection reverse tunnel during configuration of MPLS tunnel APS.
For bidirectional MPLS tunnels, a forward MPLS tunnel is bound with a specific reverse MPLS tunnel.
During configuration of MPLS-TP OAM, BDI packets are configured to be transmitted by the reverse
MPLS tunnel bound with the forward MPLS tunnel. In addition, only the reverse MPLS tunnel that is
bound with the forward MPLS tunnel can be configured as the protection reverse tunnel during
configuration of MPLS tunnel APS.
Before configuring MPLS tunnels, refer to the number of MPLS tunnels recorded in "Functions and
Features" under "Packet Boards" in the Hardware Description.
Prerequisites
You are an NMS user with " NE operator" privilege or higher.
Legend Information
Figure 13-26 shows legend information about U2000 operations.
Precautions
NOTE
Procedure
Step 1 In the NE Explorer,set LSR ID.
Configuration example:
NOTE
3
:
l When the LSR ID is specified for the first time, no warm-reset occurs on the NE. If the specified
LSR ID is then changed, a warm-reset occurs on the NE but does not affect services.
l If any tunnel exists, do not change the LSR ID.
----End
Prerequisites
l You are an NMS user with " NE operator" privilege or higher.
l You must complete the correct configuration of the port attributes.
l You must complete the correct setting of the LSR ID for each NE.
Legend Information
Figure 13-27 shows legend information about U2000 operations.
Procedure
Step 1 In the NE Explorer,select the source NE of the MPLS tunnel and set the parameters of the
forward and reverse MPLS tunnels. For details about the parameters, see 13.5.2.2 Parameters
for Configuring a Static Tunnel (on a Per-NE Basis).
Configuration example:
NOTE
7
:
l When Node Type is set to Egress, the tunnel bandwidth is the same as the bandwidth in the
Ingress direction and cannot be changed manually.
Set Next Hop Address to be the IP address of the port of the next node.
Step 2 Refer to Steps 1 - 4 to configure the static MPLS tunnels on the intermediate NEs and sink
NE.
----End
Prerequisites
l You are an NMS user with " NE operator" privilege or higher.
l You must complete the correct configuration of the port attributes.
l You must complete the correct setting of the LSR ID for each NE.
Legend Information
Figure 13-28 shows legend information about U2000 operations.
Procedure
Step 1 In the NE Explorer, select the source NE of the MPLS tunnel and set the parameters of the
bidirectional MPLS tunnels. For details about the parameters, see 13.5.2.2 Parameters for
Configuring a Static Tunnel (on a Per-NE Basis).
Configuration example:
NOTE
7
:
l When Node Type is set to Transit, the In port, Out port, Forward In Label, Forward Out
Label, Reverse In Label, Reverse Out Label, Forward Next Hop Address, Reverse Next Hop
Address, Source Node and Sink Node parameters need to be set for the tunnel.
l When Node Type is set to Egress, the In port, Forward In Label, Reverse Out Label, Reverse
Next Hop Address and Source Node parameters need to be set for the tunnel.
Step 2 Refer to Steps 1 - 4 to configure the static MPLS tunnels on the intermediate NEs and sink
NE.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l If a port needs to be occupied exclusively, disable the DCN function of the port.
Legend Information
Figure 13-29 shows legend information about U2000 operations.
Procedure
Step 1 In the NE Explorer, select an NE and set the parameters in the dialog box. For details about
the parameters, see 13.5.3.1 E-Line Service Parameters (Configuration on a Per-NE
Basis).
Configuration example:
5 3
NOTE
4
:
l When BPDU is set to Transparently Transmitted, you cannot set MTU (bytes), Source VLANs
and Sink VLANs. The transparently transmitted service does not support the configuration of the
alarms, performance events, OAM, and QoS.
l Set Direction to UNI-UNI.
l You can set several VLAN values in Source VLANs and Sink VLANs. Separate consecutive
values with "-" and separate inconsecutive values with ",". For example, The VLAN values may
be "1,3,5,8-10".
5
8 3
NOTE
6
:
If you set Bandwidth Limit to Enabled, you can set Committed Information Rate(kbit/s) and Peak
Information Rate(kbit/s). Alternatively, you can select the QoS policy directly in Policy.
Step 3 Optional: Click the Maintenance Association tab and the MEP Point tab separately to set
the OAM-related parameters.
Configuration example:
NOTE
3
:
Before setting the OAM-related parameters, you need to configure the MD first.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l If a port needs to be occupied exclusively, disable the DCN function of the port.
Legend Information
Figure 13-30 shows legend information about U2000 operations.
Procedure
Step 1 In the NE Explorer, select an NE and set the parameters in the dialog box. For details about
the parameters, see 13.5.3.1 E-Line Service Parameters (Configuration on a Per-NE
Basis).
Configuration example:
5 3
NOTE
4
:
l When BPDU is set to Transparently Transmitted, you cannot set Source VLANs. The
transparently transmitted service does not support the configuration of the alarms, performance
events, OAM and QoS.
l Set Direction to UNI-NNI.
l Set Bearer Type to Port.
l You can set several VLAN values in Source VLANs. Separate consecutive values with "-" and
separate inconsecutive values with ",". For example, The VLAN values may be "1,3,5,8-10".
5
8 3
NOTE
6
:
l If you set Bandwidth Limit to Enabled, you can set Committed Information Rate (kbit/s) and
Peak Information Rate (kbit/s). You can also select the QoS policy directly in Policy.
Step 3 Optional: Click the Maintenance Association tab and the MEP Point tab separately to set
the OAM-related parameters.
Configuration example:
NOTE
3
:Before setting the OAM-related parameters, you need to configure the MD first.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l The MPLS tunnel that carries the PWs must be configured.
l If a port needs to be occupied exclusively, disable the DCN function of the port.
Legend Information
Figure 13-31 shows legend information about U2000 operations.
Procedure
Step 1 In the NE Explorer, select an NE and set the parameters in the dialog box. For details, see
13.5.3.1 E-Line Service Parameters (Configuration on a Per-NE Basis).
Configuration example:
5 3
NOTE
4
:
l When BPDU is set to Transparently Transmitted, you cannot set Source VLANs. The
transparently transmitted service does not support the configuration of the alarms, performance
events, OAM and QoS.
l Set Direction to UNI-NNI.
l Set Bearer Type to PW.
l You can set several VLAN values in Source VLANs. Separate consecutive values with "-" and
separate inconsecutive values with ",". For example, The VLAN values may be "1,3,5,8-10".
l PRI is optional. If packets need to be forwarded based on Port+VLAN+VLAN PRI, set PRI to
an integer ranging from 0 to 7. Value 7 represents the highest priority.
l Service Tag Role can be set to User or Service.
– User: C-VLAN/S-VLAN tags of packets are used as user VLAN tags, and are processed
when the packets are forwarded.
– Service: C-VLAN/S-VLAN tags of packets are used as service VLAN tags, and are not
processed when the packets are forwarded.
l If the MPLS tunnel carrying the PWs is not configured with MPLS tunnel APS, you can set
Protection Type to PW APS. In this case, you need to configure both the service PW and
protection PW to implement MPLS PW APS protection.
5
8
3
NOTE
6
:
l You can configure the protection PW only if Protection Type is set to PW APS.
l PW Type can be set to Ethernet or Ethernet Tagged Mode.
– Ethernet: C-VLAN/S-VLAN tags of packets are encapsulated into PWs without changes,
and transparently transmitted to downstream sites.
– Ethernet Tagged Mode: A VLAN tag specified by Request VLAN is added to packets.
l Set other PW-related parameters according to the planning information.
5
8
3
Step 4 Optional: Click the Maintenance Association tab and the MEP Point tab separately to set
the OAM-related parameters.
NOTE
Before setting the OAM-related parameters, you need to configure the MD first.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l The QinQ link must be created for the NNIs.
l The services carried by the QinQ link do not support the creation of any maintenance
point (MP).
Legend Information
Figure 13-32 shows legend information about U2000 operations.
Procedure
Step 1 In the NE Explorer, select an NE and set the parameters in the dialog box. For details of the
parameters, see 13.5.3.1 E-Line Service Parameters (Configuration on a Per-NE Basis).
Configuration example:
6 4
2
3
NOTE
5
:
l When BPDU is set to Transparently Transmitted, you cannot set Source VLANs. The
transparently transmitted service does not support the configuration of the alarms, performance
events, OAM and QoS.
l Set Direction to UNI-NNI.
l Set Bearer Type to QinQ Link.
l Select a created QinQ link in QinQ Link ID.
Step 2 Click the QoS tab and click the QinQ Link tab.
Step 3 Select the QoS policy for the ingress and egress directions of the QinQ link. Click Apply.
Then, the Operation Result dialog box is displayed, indicating that the operation is
successful.
NOTE
Before selecting the policy, ensure that the policy is already created. If you set Bandwidth Limit to
Enabled, you can set Committed Information Rate (kbit/s) and Peak Information Rate (kbit/s).
----End
Prerequisites
l You are an NMS user with " NE operator" privilege or higher.
l The port attributes must be set correctly.
l If a port needs to be occupied exclusively, disable the DCN function of the port.
l If a QoS policy is required for configuring the QoS, you must create the QoS policy first.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Packet Configuration >
Ethernet Service Management > E-LAN Service from the Function Tree.
Step 2 Click New. Then, the New E-LAN Service dialog box is displayed. Set Service ID, Service
Name, and other parameters in the dialog box. For details about the parameters, see 13.5.4.1
E-LAN Service Parameters (Configuration on a Per-NE Basis).
NOTE
l Self-Learning MAC Address can be set to Enabled or Disabled. When Self-Learning MAC
Address is set to Enabled, the bridge supports MAC address self-learning and the forwarding table
items are generated through MAC address self-learning. You can also configure the static MAC
address forwarding table items manually. When Self-Learning MAC Address is set to Disabled,
the bridge does not support MAC address self-learning, and you can configure the static MAC
address forwarding table items only manually.
l MAC Address Learning Mode can be set to SVL or IVL. SVL indicates shared VLAN learning.
All VLANs share a MAC address forwarding table. Each MAC address is unique in the forwarding
table. IVL indicates the independent VLAN learning. The forwarding tables for different VLANs
are independent from each other. It is acceptable that the MAC address forwarding tables for
different VLANs have the same MAC address.
You can set MAC Address Learning Mode to IVL only when the bridge type is IEEE 802.1ad.
l Tag Type can be set to C-Awared, S-Awared, or Tag Transparent. C-Awared corresponds to the
accessed service packets with one C-VLAN tag. S-Awared corresponds to the accessed service
packets with one C-VLAN tag and one S-VLAN tag. Tag Transparent corresponds to the accessed
service packets without any VLAN tags.
Step 3 Click OK. Then, the Operation Result dialog box is displayed, indicating that the operation
is successful. Then, click Close.
Step 4 Click the UNI tab and click Configuration. Then, the Configure Port dialog box is
displayed. For details about the parameters, see 13.5.4.3 UNI Parameters.
Step 5 In the Available Ports list, select the port. Then, click to add the port to the
Selected Ports list.
Step 6 In the Selected Ports list, set VLANs of the port, and then click OK.
Step 7 Optional: Click the NNI tab. Click the Port tab. Refer to Steps Step 4- Step 6 to add and
configure the NNI port. Then, click OK. For details about the parameters, see 13.5.3.4 NNI
Parameters.
Step 8 Click the Split Horizon Group tab and click New. Then, the New Split Horizon Group
dialog box is displayed. For details about the parameters, see 13.5.4.5 Split Horizon Group.
Step 9 Set the split horizon group ID and add the port that needs to be added into the split horizon
group to the Selected Interfaces area box. Click OK. Then, the Operation Result dialog box
is displayed, indicating that the operation is successful. Then, click Close.
Step 10 Click the MAC Address Learning Parameters tab. Set Aging Ability, Aging Time(min),
Address Table Specified Capacity, Address Detection Upper Threshold(%), and Address
Detection Lower Threshold(%). For details about the parameters, see 13.5.4.6 MAC
Address Learning Parameters.
NOTE
Address Detection Upper Threshold(%) and Address Detection Lower Threshold(%) indicate the
upper threshold and lower threshold of the self-learning capacity. If the upper threshold is crossed, the
equipment reports an alarm. If the lower threshold is crossed, the alarm is cleared.
Step 11 Click Apply. Then, the Operation Result dialog box is displayed, indicating that the
operation is successful. Click Close.
Step 12 Click the Unknown Frame Processing tab. Set the processing modes for the unicast frames
and multicast frames. The default value is broadcast. For details about the parameters, see
13.5.4.7 Unknown Frame Processing.
Step 13 Click Apply. Then, the Operation Result dialog box is displayed, indicating that the
operation is successful. Click Close.
Step 14 Optional: Click the QoS tab. Set the QoS parameters.
Step 15 Click the UNI tab. Set Default Forwarding Priority and Default Packet Relabeling Color
of the port. Click Apply. Then, the Operation Result dialog box is displayed, indicating that
the operation is successful. Then, click Close.
Step 16 Optional: Click the Static MAC Address tab. You can set VLAN ID, MAC Address, and
Egress Interface. For details about the parameters, see 13.5.4.8 Static MAC Address.
Step 17 Optional: Click the Maintenance Association tab and the MEP Point tab separately to set
the OAM-related parameters. For details about the parameters, see 13.5.3.5 Maintenance
Association and 13.5.3.6 MEP Point.
NOTE
Before setting the OAM-related parameters, you need to configure the MD first.
----End
Prerequisites
l You are an NMS user with " NE operator" privilege or higher.
l The port attributes must be set correctly.
l The MPLS tunnel that carries the PWs must be created.
l If a port needs to be occupied exclusively, disable the DCN function of the port.
l If a QoS policy is required for configuring the QoS, you must create the QoS policy first.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Packet Configuration >
Ethernet Service Management > E-LAN Service from the Function Tree.
Step 2 Click New. Then, the New E-LAN Service dialog box is displayed. Set Service ID, Service
Name and other parameters in the dialog box. For details about the parameters, see 13.5.4.1
E-LAN Service Parameters (Configuration on a Per-NE Basis).
NOTE
l Self-Learning MAC Address can be set to Enabled or Disabled. When Self-Learning MAC
Address is set to Enabled, the bridge supports MAC address self-learning and the forwarding table
items are generated through MAC address self-learning. You can also configure the static MAC
address forwarding table items manually. When Self-Learning MAC Address is set to Disabled,
the bridge does not support MAC address self-learning, and you can configure the static MAC
address forwarding table items only manually.
l MAC Address Learning Mode can be set to SVL or IVL. SVL indicates shared VLAN learning.
All VLANs share a MAC address forwarding table. Each MAC address is unique in the forwarding
table. IVL indicates the independent VLAN learning. The forwarding tables for different VLANs
are independent from each other. It is acceptable that the MAC address forwarding tables for
different VLANs have the same MAC address.
You can set MAC Address Learning Mode to IVL only when the bridge type is IEEE 802.1ad.
l Tag Type can be set to C-Awared, S-Awared, or Tag Transparent. C-Awared corresponds to the
accessed service packets with one C-VLAN tag. S-Awared corresponds to the accessed service
packets with one C-VLAN tag and one S-VLAN tag. Tag Transparent corresponds to the accessed
service packets without any VLAN tags.
l If the MPLS tunnel carrying the PWs is not configured with MPLS tunnel APS, you can set
Protection Type to PW APS. In this case, you need to configure both the service PW and protection
PW to implement MPLS PW APS protection.
Step 3 Click OK. Then, the Operation Result dialog box is displayed, indicating that the operation
is successful. Click Close.
Step 4 Click the UNI tab and click Configuration. Then, the Configure Port dialog box is
displayed. For details about the parameters, see 13.5.4.3 UNI Parameters.
Step 5 In the Available Ports list, select the port. Then, click to add the port to the
Selected Ports list.
Step 6 In the Selected Ports list, set VLANs of the port, and then click OK.
Step 7 Click the NNI tab. Click the PW tab. Click New and set the parameters related to the PW.
Then, click OK. For details about the parameters, see 13.5.3.4 NNI Parameters.
Step 8 Click the Split Horizon Group tab. Click New. Then, the New Split Horizon Group dialog
box is displayed. For details about the parameters, see 13.5.4.5 Split Horizon Group.
Step 9 Set the split horizon group ID, and add the port that needs to be added into the split horizon
group to the Selected Interfaces area box. Click OK. Then, the Operation Result dialog box
is displayed, indicating that the operation is successful. Click Close.
Step 10 Click the MAC Address Learning Parameters tab. Set Aging Ability, Aging Time(min),
Address Table Specified Capacity, Address Detection Upper Threshold(%), and Address
Detection Lower Threshold(%). For details about the parameters, see 13.5.4.6 MAC
Address Learning Parameters.
NOTE
Address Detection Upper Threshold(%) and Address Detection Lower Threshold(%) indicate the
upper threshold and lower threshold of the self-learning capacity. If the upper threshold is crossed, the
equipment reports an alarm. If the lower threshold is crossed, the alarm is cleared.
Step 11 Click Apply. Then, the Operation Result dialog box is displayed, indicating that the
operation is successful. Click Close.
Step 12 Click the Unknown Frame Processing tab. Set the processing modes for the unicast frames
and multicast frames. The default value is broadcast. For details about the parameters, see
13.5.4.7 Unknown Frame Processing.
Step 13 Click Apply. Then, the Operation Result dialog box is displayed, indicating that the
operation is successful. Click Close.
Step 14 Optional: Click the QoS tab. Set the QoS parameters.
Step 15 Optional: In the QoS tab, click the PW. Set EXP and LSP Mode. Click Apply. Then, the
Operation Result dialog box is displayed, indicating that the operation is successful. Click
Close.
NOTE
If you set Bandwidth Limit to Enabled, you can set Committed Information Rate(kbit/s) and Peak
Information Rate(kbit/s). You can also select the QoS policy directly in Policy. Before selecting a
policy, you need to create the policy first.
Step 16 Optional: Click the Static MAC Address tab. You can set VLAN ID, MAC Address, and
Egress Interface. For details about the parameters, see 13.5.4.8 Static MAC Address.
Step 17 Optional: Click the Maintenance Association tab and the MEP Point tab separately to set
the OAM-related parameters. For details about the parameters, see 13.5.3.5 Maintenance
Association and 13.5.3.6 MEP Point.
NOTE
Before setting the OAM-related parameters, you need to configure the MD first.
----End
Prerequisites
l You are an NMS user with " NE operator" privilege or higher.
l The port attributes must be set correctly.
l If a port needs to be occupied exclusively, disable the DCN function of the port.
l If the services need to be carried by a QinQ link, you must configure a QinQ link first.
l If a QoS policy is required for configuring the QoS, you must create the QoS policy first.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Packet Configuration >
Ethernet Service Management > E-LAN Service from the Function Tree.
Step 2 Click New. Then, the New E-LAN Service dialog box is displayed. Set Service ID, Service
Name, and other parameters in the dialog box. For details about the parameters, see 13.5.4.1
E-LAN Service Parameters (Configuration on a Per-NE Basis).
NOTE
l Self-Learning MAC Address can be set to Enabled or Disabled. When Self-Learning MAC
Address is set to Enabled, the bridge supports MAC address self-learning and the forwarding table
items are generated through MAC address self-learning. You can also configure the static MAC
address forwarding table items manually. When Self-Learning MAC Address is set to Disabled,
the bridge does not support MAC address self-learning, and you can configure the static MAC
address forwarding table items only manually.
l MAC Address Learning Mode can be set to SVL or IVL. SVL indicates shared VLAN learning.
All VLANs share a MAC address forwarding table. Each MAC address is unique in the forwarding
table. IVL indicates the independent VLAN learning. The forwarding tables for different VLANs
are independent from each other. It is acceptable that the MAC address forwarding tables for
different VLANs have the same MAC address.
You can set MAC Address Learning Mode to IVL only when the bridge type is IEEE 802.1ad.
l Tag Type can be set to C-Awared, S-Awared, or Tag Transparent. C-Awared corresponds to the
accessed service packets with one C-VLAN tag. S-Awared corresponds to the accessed service
packets with one C-VLAN tag and one S-VLAN tag. Tag Transparent corresponds to the accessed
service packets without any VLAN tags.
Step 3 Click OK. Then, the Operation Result dialog box is displayed, indicating that the operation
is successful. Click Close.
Step 4 Click the UNI tab and click Configuration. Then, the Configure Port dialog box is
displayed. For details about the parameters, see 13.5.4.3 UNI Parameters.
Step 5 In the Available Ports list, select the port. Then, click to add the port to the
Selected Ports list.
Step 6 In the Selected Ports list, set VLANs of the port, and then click OK.
Step 8 Click the QinQ Link tab. For details about the parameters, see 13.5.5 Parameter
Description: QinQ Link.
Step 9 Click Add. Then, the QinQ Link Management window is displayed.
Step 11 Click Apply. Then, the Operation Result dialog box is displayed, indicating that the
operation is successful. Click Close,
Step 12 Click the Split Horizon Group tab and click New. Then, the New Split Horizon Group
dialog box is displayed.
Step 13 Set the split horizon group ID, and add the port that needs to be added into the split horizon
group to the Selected Interfaces area box. Click OK. Then, the Operation Result dialog box
is displayed, indicating that the operation is successful. Click Close.
Step 14 Click the MAC Address Learning Parameters tab. Set Aging Ability, Aging Time(min),
Address Table Specified Capacity, Address Detection Upper Threshold(%), and Address
Detection Lower Threshold(%). For details about the parameters, see 13.5.4.6 MAC
Address Learning Parameters.
NOTE
Address Detection Upper Threshold(%) and Address Detection Lower Threshold(%) indicate the
upper threshold and lower threshold of the self-learning capacity. If the upper threshold is crossed, the
equipment reports an alarm. If the lower threshold is crossed, the alarm is cleared.
Step 15 Click Apply. Then, the Operation Result dialog box is displayed, indicating that the
operation is successful. Click Close.
Step 16 Click the Unknown Frame Processing tab. Set the processing modes for the unicast frames
and multicast frames. The default value is broadcast. For details about the parameters, see
13.5.4.7 Unknown Frame Processing.
Step 17 Click Apply. Then, the Operation Result dialog box is displayed, indicating that the
operation is successful. Click Close.
Step 18 Optional: Click the QoS tab. Set the QoS parameters.
Step 19 Click the QinQ Link tab. Enable the bandwidth limit and select the QoS policy for the
ingress and egress directions of the QinQ link. Click Apply. The Operation Result dialog
box is displayed, indicating that the operation is successful. Click Close,
NOTE
Before selecting a policy, you need to create the policy first. If you set Bandwidth Limit to Enabled,
you can set Committed Information Rate(kbit/s) and Peak Information Rate(kbit/s).
Step 20 Optional: Click the Static MAC Address tab. You can set MAC Address and Egress
Interface. For details about the parameters, see 13.5.4.8 Static MAC Address.
Step 21 Optional: Click the Maintenance Association tab and the MEP Point tab separately to set
the OAM-related parameters. For details about the parameters, see 13.5.3.5 Maintenance
Association and 13.5.3.6 MEP Point.
NOTE
Before setting the OAM-related parameters, you need to configure the MD first.
----End
Prerequisites
l For the Ethernet service carried by ports, set Encapsulation Type to Null
(recommended) and Port Mode to Later 2.
l You must be an NM user with NE administrator authority or higher.
l The Ethernet service carried by ports exclusively occupies the NNI ports on its transit
NEs. The DCN function is disabled for the NNI ports.
Legend Information
Figure 13-33 shows legend information about U2000 operations.
Procedure
Step 1 In the NE Explorer, select the required NE and set parameters of transit NEs for an Ethernet
service. For details about the parameters, see 13.5.3.1 E-Line Service Parameters
(Configuration on a Per-NE Basis).
Configuration example:
5 3
2
NOTE
4
:
l For transit NEs for an Ethernet service, set Direction to UNI-UNI.
l For transit NEs for an Ethernet service, you do not need to set QoS parameters.
----End
Background Information
For transit NEs of an Ethernet service carried by PWs, you only need to configure MPLS
tunnels whose Node Type is Transit. For details on how to configure an MPLS tunnel, see
13.3.5 Configuring an MPLS Tunnel.
If the PW which carries Ethernet services belongs to the MS-PW, the MS-PW needs to be
configured at the Switching Provider Edge (S-PE) node through which Ethernet services pass.
This section describes how to configure the MS-PW.
Legend Information
Figure 13-34 shows legend information about U2000 operations.
Procedure
Step 1 In the NE Explorer, select the NE and set the parameters of the MS-PW.
Configuration example:
1 3
4
2
1 3
4
2
5
NOTE
----End
13.3.8.3 Configuring Transit NEs for Ethernet Services Carried by QinQ Links
This section describes how to configure transit NEs for an Ethernet service carried by QinQ
links.
Prerequisites
l For the Ethernet service carried by QinQ links, set Encapsulation Type to Null
(recommended) and Port Mode to Later 2.
l You must be an NM user with NE administrator authority or higher.
l The Ethernet service carried by QinQ links exclusively occupies the NNI ports on its
transit NEs. The DCN function is disabled for the NNI ports.
Legend Information
Figure 13-35 shows legend information about U2000 operations.
Procedure
Step 1 In the NE Explorer, select the required NE and set parameters of transit NEs for an Ethernet
service. For details about the parameters, see 13.5.3.1 E-Line Service Parameters
(Configuration on a Per-NE Basis).
Configuration example:
5 3
2
NOTE
4
:
l For transit NEs for an Ethernet service, set Direction to UNI-UNI.
l For transit NEs for an Ethernet service, you do not need to set QoS parameters.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > Packet Configuration >
Control Plane Configuration > Address Parse from the Function Tree.
Step 2 Click Create. Then, the Add Address Parse dialog box is displayed.
Step 3 Set the IP address and MAC address for each ARP table item, and then click Apply. For
details about the parameters, see 13.5.6 Parameter Description: Address Parse.
CAUTION
When configuring the MAC address of each ARP table item, ensure that the first digit of the
address is an even number.
CAUTION
Configuring the address resolution refers to creating the static ARP table items. To delete the
dynamic ARP table items, click Clear. This operation, however, clears all the contents in the
ARP table items and interrupts the services. Hence, exercise caution when performing this
operation.
NOTE
Click Delete to delete the contents of the static ARP table items.
----End
Prerequisites
You are an NMS user with " NE operator" privilege or higher.
Context
NOTE
l NE-level TPIDs configured on the OptiX OSN 8800 are effective only for PW-carried E-Line
services, and are automatically added into the request VLAN tags of the E-Line services when the
PWs work in Ethernet tagged mode.
l NE-level TPIDs configured on the OptiX OSN 8800 are ineffective for PW-carried E-LAN services.
In this case, the default value 0X88A8 is added into the request VLAN tags of the Ethernet services
when the PWs work in Ethernet tagged mode.
Procedure
Step 1 In the NE Explorer, select the required NE and then choose Configuration > Packet
Configuration > TPID Configuration from the Function Tree.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l The Layer 2 attributes of the port on the QinQ link must be set and the encapsulation
mode must be the QinQ mode.
l If the QoS parameters of the QinQ link need to be set, the QinQ policy must be
configured first.
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > Packet Configuration >
Ethernet Service Management > QinQ Link from the Function Tree.
Step 2 Click New. Then, the New QinQ Link window is displayed.
Step 3 Click the Basic Attributes tab. Set QinQ Link ID, Board, Port and S-VLAN ID.
----End
Prerequisites
l E-LAN services are configured.
l You are an NMS user with " NE operator" privilege or higher.
Legend Information
Figure 13-36 shows legend information about U2000 operations.
Procedure
Step 1 In the NE Explorer,select the created E-LAN service and set MAC Address.
Configuration example:
2
6
----End
function on the NMS helps convert a discrete MPLS tunnel to a complete tunnel, therefore
facilitating tunnel management. This section describes how to search for MPLS tunnels on the
NMS.
Prerequisites
l MPLS tunnels have been created on a per-NE basis.
l You are an NMS user with " NE operator" privilege or higher.
Procedure
Step 1 Choose Service > Search for Service from the main menu.
Step 2 In the dialog box that is displayed, set the tunnel discovery policy.
Step 4 After the search is complete, view the search results. Click Close.
----End
Prerequisites
l MPLS tunnels have been created.
NOTE
Before managing an MPLS tunnel that is created on a per-NE basis, you need to search for the
MPLS tunnel.
Legend Information
Figure 13-37 shows legend information about U2000 operations.
Procedure
Step 1 Navigation path.
Configuration example:
1
2
3
Step 3 Select the MPLS tunnel whose topology information you need to check and click the
Topology tab.
Step 4 In the MPLS tunnel topology view, right-click the NE and choose View Real-Time
Performance from the shortcut menu to check the real-time running status of the MPLS
tunnel.
----End
Prerequisites
l You are an NMS user with " NE operator" privilege or higher.
l MPLS tunnels have been created.
NOTE
Before managing an MPLS tunnel that is created on a per-NE basis, you need to search for the
MPLS tunnel.
l ODUk paths have been discovered and L2 links have been generated.
Legend Information
Figure 13-38 shows legend information about U2000 operations.
Context
l If the tunnel to be duplicated does not belong to a protection group, the U2000
automatically generates two unidirectional tunnels or a bidirectional tunnel, whose
direction is reverse and share the same source and sink nodes with the tunnel to be
duplicated.
l If the tunnel to be duplicated belongs to a protection group, the U2000 automatically
generates the tunnel who shares the same source and sink nodes with the tunnel to be
duplicated and a new protection group that contains the two tunnels.
Procedure
Step 1 Visit the following navigation path.
Configuration example:
1
2
3
Step 3 Set parameters for the duplicated MPLS tunnel, adjust the source and sink nodes of the
tunnel, and set the detailed tunnel parameters.
Configuration example:
1 2
6 5
NOTE
1
: If the tunnel to be duplicated belongs to a protection group, the U2000 automatically
generates the specified number of tunnels who share the same source and sink nodes with the tunnel to
be duplicated and a new protection group that contains the tunnels. If the Copy Protection Group check
box is cleared, a tunnel is duplicated. In this case, you can set Tunnel Number of Copying and other
relevant parameters.
----End
Prerequisites
l MPLS tunnels have been created.
NOTE
Before managing an MPLS tunnel that is created on a per-NE basis, you need to search for the
MPLS tunnel.
l You are an NMS user with " NE operator" privilege or higher.
Procedure
Step 1 Visit the following navigation path.
Configuration example:
1
Step 2 In the dialog box that is displayed, set Deployment Status to Undeployed. Click Filter to
check all undeployed MPLS tunnels.
Step 3 Select one or more MPLS tunnels to be deployed, right-click the MPLS tunnels, and choose
Deploy and Enable > Deploy from the shortcut menu.
NOTE
After an MPLS tunnel is successfully deployed, its Deployment Status is Deployed.
----End
Prerequisites
l MPLS tunnels have been created.
NOTE
Before managing an MPLS tunnel that is created on a per-NE basis, you need to search for the
MPLS tunnel.
l You are an NMS user with " NE operator" privilege or higher.
Background Information
NOTICE
Modifying an MPLS tunnel may interrupt services.
Legend Information
Figure 13-39 shows legend information about U2000 operations.
Configuration example:
1
2
3
Step 3 Select the desired tunnel information, click the tab in the lower left corner of the interface,
and change values of relevant parameters.
Step 4 Optional: If you need to modify only basic information of a tunnel, right-click the desired
tunnel and choose Details from the shortcut menu, and modify the basic information in the
displayed dialog box.
----End
Step 3 Click OK. The Warning dialog box is displayed, indicating that the operation may interrupt
services.
Step 4 Click OK. The Result dialog box is displayed, indicating that the operation is successful.
Step 6 Modify static tunnel information on intermediate and source NEs by reference to steps 1 to 5.
----End
Prerequisites
l MPLS tunnels have been created.
NOTE
Before managing an MPLS tunnel that is created on a per-NE basis, you need to search for the
MPLS tunnel.
l You are an NMS user with " NE operator" privilege or higher.
Legend Information
Figure 13-40 shows legend information about U2000 operations.
Procedure
Step 1 Visit the following navigation path.
Configuration example:
1
2
3
Step 3 Select one or more MPLS tunnels that you need to delete, and right-click the tunnels.
l Choose Delete service > Delete from the shortcut menu. Deletes the selected tunnel in
the Undeployed state, that is, deletes the tunnel from the U2000.
l Choose Delete service > Delete from Network Side from the shortcut menu. Deletes
the selected tunnel from the network. The tunnel deleted from the network is saved in the
discrete tunnel.
l Choose Deploy and Enable > Undeploy from the shortcut menu. Deletes tunnel
configurations from NEs and keeps the tunnel configurations on the U2000. After this
operation is performed, the value of Deployment Status for the tunnel changes from
Deployed or Partially Deployed to Undeployed.
NOTE
l If an MPLS tunnel has been configured in an MPLS tunnel APS protection group or has been
configured with PWE3 services, you need to delete the MPLS tunnel APS protection group or
PWE3 services before deleting the MPLS tunnel.
----End
Prerequisites
l MPLS tunnels have been created.
NOTE
Before managing an MPLS tunnel that is created on a per-NE basis, you need to search for the
MPLS tunnel.
l You are an NMS user with " NE operator" privilege or higher.
Legend Information
Figure 13-41 shows legend information about U2000 operations.
Procedure
Step 1 Choose Service > Tunnel > Manage Discrete Tunnel from the main menu.
Configuration example:
1
2
3
Step 3 Select an MPLS tunnel and click the Hops Information tab. In the tab page, check the port
information and label information about the MPLS tunnel.
Step 4 Optional: Select one or more MPLS tunnels and click Delete.
----End
Prerequisites
l PWE3 services have been created on a per-NE basis. For details on how to create PWE3
services on a per-NE basis, see Configuring UNI-NNI E-Line Services Carried by PWs
on a Per-NE Basis.
l When PWE3 services are created on a per-NE basis, ensure that the PW types are the
same; Peer IP of a local NE equals the LSR ID of the opposite NE; the PW outgoing
label of a local NE equals the PW incoming label of the opposite NE.
l You must be an NM user with NE administrator authority or higher.
Legend Information
Figure 13-42 shows legend information about U2000 operations.
Procedure
Step 1 Choose Service > Search for Service from the main menu.
Step 2 Setting the discovery policy and searching for PWE3 Services.
2
1
----End
Prerequisites
l The PWE3 service has been created.
l You must be an NM user with NE administrator authority or higher.
Legend Information
Figure 13-43 shows legend information about U2000 operations.
Procedure
Step 1 Navigation path.
Configuration example:
----End
Prerequisites
l The PWE3 service has been created.
l You must be an NM user with NE administrator authority or higher.
Legend Information
Figure 13-44 shows legend information about U2000 operations.
Procedure
Step 1 Navigation path.
Configuration example:
Step 3 Select one or more PWE3 services to be deployed, right-click the PWE3 services, and choose
Deploy and Enable > Deploy from the shortcut menu.
NOTE
After a PWE3 service is successfully deployed, its Deployment Status is Deployed.
----End
Prerequisites
l The PWE3 service has been created.
l You must be an NM user with NE administrator authority or higher.
Legend Information
Figure 13-45 shows legend information about U2000 operations.
Context
NOTICE
Modifying a PWE3 service may interrupt other services.
If the Ethernet service OAM function is used to performing performance test, after the VLAN
ID of a node is modified, the local MEP information will be deleted, which affects the
Ethernet service OAM function.
Procedure
Step 1 Navigation path.
Configuration example:
Step 3 Select the desired PWE3 service, click the tab in the lower left corner of the interface, and
change values of relevant parameters.
Step 4 Optional: If you need to modify only basic information of a PWE3 service, select the PWE3
service and click Details. In the dialog box that is displayed, change the values of the PWE3
services parameters as required.
----End
Prerequisites
l The PWE3 service has been created.
l You must be an NM user with NE administrator authority or higher.
Legend Information
Figure 13-46 shows legend information about U2000 operations.
Procedure
Step 1 Navigation path.
Configuration example:
Step 3 Select one or more PWE3 services that you need to delete, and right-click the services.
NOTE
For the service that the Deployment Status is Deployed or Partially Deployed, before deleting the service,
you need to set Deployment Status to Undeployed.
l Choose Delete Service > Delete from Network Side from the shortcut menu. Deletes
the selected service from the network. The service deleted from the network is saved in
the discrete service.
l Choose Delete Service > Delete from the shortcut menu. Deletes the selected service in
the Undeployed state, that is, deletes the service from the U2000.
l Choose Delete Service > Completely Delete from the shortcut menu. Deletes the
selected service from the U2000. The service deleted using this button cannot be restored
using Recycle Bin.
----End
Prerequisites
l The PWE3 service has been created.
l You must be an NM user with NE administrator authority or higher.
Legend Information
Figure 13-47 shows legend information about U2000 operations.
Procedure
Step 1 Navigation path.
Configuration example:
Step 3 Optional: Convert a PWE3 service to an unterminated service. Set attributes of the PWE3
service, such as the service name.
Configuration example:
NOTE
3
:After a PWE3 service is converted to an unterminated service, its service information is
displayed in Manage PWE3 Service.
----End
Prerequisites
l VPLS services have been created on a per-NE basis. For details on how to create VPLS
services on a per-NE basis, see Creating E-LAN Services Carried by PWs on a Per-NE
Basis.
l You must be an NM user with NE administrator authority or higher.
Procedure
Step 1 Choose Service > Search for Service from the main menu.
Step 2 In the dialog box that is displayed, set the discovery policy.
Step 4 After the search is complete, view the search results. Click Close.
----End
Prerequisites
l The VPLS service has been created.
l You must be an NM user with NE administrator authority or higher.
Legend Information
Figure 13-48 shows legend information about U2000 operations.
Procedure
Step 1 Navigation path.
Configuration example:
1
3
4
3
4
----End
Prerequisites
l The VPLS service has been created.
l You must be an NM user with NE administrator authority or higher.
Procedure
Step 1 Choose Service > VPLS Service > Manage VPLS Service from the main menu.
Step 2 In the dialog box that is displayed, set Deployment Status to Undeployed. Click Filter to
check all undeployed VPLS services.
Step 3 Select one or more VPLS services to be deployed, right-click the VPLS services, and choose
Deploy and Enable > Deploy from the shortcut menu.
NOTE
After a VPLS service is successfully deployed, its Deployment Status is Deployed.
----End
Prerequisites
l The VPLS service has been created.
l You must be an NM user with NE administrator authority or higher.
Legend Information
Figure 13-49 shows legend information about U2000 operations.
Background Information
NOTICE
Modifying a VPLS service may interrupt other services.
If the Ethernet service OAM function is used to performing performance test, after the VLAN
ID of a node is modified, the local MEP information will be deleted, which affects the
Ethernet service OAM function.
Procedure
Step 1 Navigation path.
Step 3 Select the desired VPLS service, modify the basic attributes of the selected VPLS service. For
details, see 13.2.7 Configuring a VPLS Service.
Configuration example:
NOTE
3
:The windows for modifying and creating a VPLS service are similar. The only difference is
that only part of the parameters can be set in the window for modifying the composite service.
Step 4 Optional: If you need to modify only basic information of a VPLS service, select the VPLS
service and change the values of the VPLS services parameters as required.
Configuration example:
----End
Prerequisites
l The VPLS service has been created.
l You must be an NM user with NE administrator authority or higher.
Legend Information
Figure 13-50 shows legend information about U2000 operations.
Procedure
Step 1 Navigation path.
Configuration example:
Step 3 Select one or more VPLS services that you need to delete, and right-click the services.
NOTE
For the service that the Deployment Status is Deployed or Partially Deployed, undeploy the VSI
before deleting it. In the Manage VPLS Service window, select VPLS services with Deployment
Status set to Deployed or Partially Deployed, and then click VSI tab. Select one or more VSIs, right-
click, and choose Undeploy.
l Choose Delete Service > Delete from the shortcut menu. Deletes the selected service in
the Undeployed state, that is, deletes the service from the U2000.
l Choose Delete Service > Delete from Network Side from the shortcut menu. Deletes
the selected service from the network. The service deleted from the network is saved in
the discrete service.
----End
Prerequisites
l The VPLS service has been created.
l You must be an NM user with NE administrator authority or higher.
Legend Information
Figure 13-51 shows legend information about U2000 operations.
Procedure
Step 1 Navigation path.
Configuration example:
1
Configuration example:
----End
Prerequisites
You are an NMS user with " NE operator" privilege or higher.
Legend Information
Figure 13-52 shows legend information about U2000 operations.
Procedure
Step 1 Navigation path.
Configuration example:
1
1
2
3 4
----End
Prerequisites
l The composite service has been created.
l You must be an NM user with NE administrator authority or higher.
Legend Information
Figure 13-53 shows legend information about U2000 operations.
Procedure
Step 1 Navigation path.
Configuration example:
1
Step 3 Select the composite service whose topology information you need to check and click the
Topology tab.
Step 4 In the topology view of the composite service, double-click to view the topology
information of the services contained in the composite service. Click the Service Component
tab to view the running status of the services.
Step 5 In the topology view of the composite service, right-click the connection point and
choose Details from the shortcut menu that is displayed to view the details about the
connection point of the composite service.
----End
Prerequisites
l The composite service has been created.
l You are an NMS user with " NE operator" privilege or higher.
Legend Information
Figure 13-54 shows legend information about U2000 operations.
Procedure
Step 1 Navigation path.
Configuration example:
Step 3 Select one or more Composite services to be deployed, right-click the Composite services,
and choose Deploy from the shortcut menu.
NOTE
After a Composite service is successfully deployed, its Deployment Status is Deployed.
----End
Prerequisites
l The composite service has been created.
l You must be an NM user with NE administrator authority or higher.
Legend Information
Figure 13-55 shows legend information about U2000 operations.
Background Information
NOTICE
If the Ethernet service OAM function is used to performing performance test, after the VLAN
ID of a node is modified, the local MEP information will be deleted, which affects the
Ethernet service OAM function.
Procedure
Step 1 Navigation path.
Configuration example:
Step 3 Select the desired composite service, right-click, and choose Modify from the shortcut menu.
In the Modify Composite Service window, modify the basic attributes, service components,
and connection points of the selected composite service. For details, see Configuring a
Composite Service.
NOTE
The windows for modifying and creating a composite service are similar. The only difference is that
only part of the parameters can be set in the window for modifying the composite service.
Step 4 Optional: To modify only the name of a composite service, select and right-click the desired
composite service, choose Rename from the shortcut menu that is displayed, and set the
service name in the dialog box that is displayed.
----End
Prerequisites
l The composite service has been created.
l You must be an NM user with NE administrator authority or higher.
Background Information
The deletion types are as follows:
l Delete Only Composite Service: In this case, only the composite services are deleted
from the U2000. Services on the NE side are not affected.
l Delete Cascaded Service: In this case, the composite services are deleted from the U2000
and the services associated with these composite services are deleted from both the
U2000 and NE side.
Legend Information
Figure 13-56 shows legend information about U2000 operations.
Procedure
Step 1 Navigation path.
Configuration example:
Step 3 Select one or more composite services that you need to delete, right-click the services, and
choose Delete from the shortcut menu.
Step 4 In the confirmation dialog box that is displayed, select Delete Composite Services Only or
Delete Cascaded Service.
NOTE
If a service component used by multiple composite services is deleted, the service component is deleted
from all these composite services after clicking the Delete Cascaded Service.
----End
Prerequisites
l You are an NMS user with "Administrators" privilege.
l End-to-end Ethernet services have been deployed.
l The license for TP-Assist function has been correctly loaded. For details about the
license, see Feature License in the Feature Description.
l The NE license authorization for the TP-Assist function has been set. For details, see
Setting License in the Commissioning Guide.
Legend Information
Figure 13-57 shows legend information about U2000 operations.
Procedure
l Search for an E-Line service path.
a. From the main menu of the U2000, choose Service > Service Path View.
c. Click Search. The service path to which the specified port and VLAN ID reside is
displayed in the right window .
c. Click Search. The service path to which the specified port and VLAN ID reside is
displayed in the right window .
----End
Prerequisites
l You are an NMS user with "Administrators" privilege.
l End-to-end Ethernet services have been deployed.
l The license for TP-Assist function has been correctly loaded. For details about the
license, see Feature License in the Feature Description.
l The NE license authorization for the TP-Assist function has been set. For details, see
Setting License in the Commissioning Guide.
Legend Information
Figure 13-58 shows legend information about U2000 operations.
Procedure
Step 1 Search for an E-LAN service path.
1. From the main menu of the U2000, choose Service > Service Path View.
3. Click Search. The service path to which the specified port and VLAN ID reside is
displayed in the right window .
2. Click Query. If the MAC address has been learned by a port, a green tick is displayed on
top right of the NE.
----End
Prerequisites
l You are an NMS user with "Administrators" privilege.
l End-to-end Ethernet services have been deployed.
l The license of the TP-Assist function has been loaded. For details about the license, see
Feature License.
l The license of the TP-Assist function has been authorized to the NE. For details, see
Setting License.
Procedure
Step 1 Search for the desired service path.
Step 2 Query the real-time and historical performance data of each statistical item on the service
path.
The following figure takes querying the real-time performance data of a PW on a service path
as an example to illustrate the query process. The process for querying the performance data
of other statistical items is similar.
1
Click the Service
Information tab.
2
右键单击需要查询的业
务3
View the historical
or real-time
performance data
of a statistical item
as required.
Performance data
display area. 6
----End
Prerequisites
l The equipment is running properly.
Legend Information
Figure 13-59 shows legend information about U2000 operations.
Procedure
Step 1 Navigation path.
Configuration example:
1
Step 2 Create the resource type for the performance monitoring function of the PWE3 Ethernet
service. The methods for other services are similar.
Configuration example:
NOTE
l Click Set Resource Type. In the dialog box that is displayed, select resource types and save the
setting. After the setting, only the selected resource types will be displayed under the Performance
Management navigation tree.
l The Is Monitored column displays the status whether a monitoring instance is created for a
resource.
l Click to add all resources in the Available Resources area to the Selected Resources
area.
Step 3 In the Available Resources area, select a resource for which you want to perform
performance monitoring and add the resource to the Selected Resources area. Create the
monitoring template.
Configuration example:
----End
Prerequisites
l You are an NMS user with "Administrators" privilege.
l The equipment is running properly.
l End-to-end Ethernet services have been deployed.
l The corresponding performance monitoring instance has been configured.
Legend Information
Figure 13-60 shows legend information about U2000 operations.
Procedure
Step 1 Navigation path.
Configuration example:
1
Step 2 Under the Performance Management navigation tree, click a resource for which you want to
query the performance data.
Step 3 Optional: Click Filter to set the filter criteria for querying.
Step 4 In the resource list, double-click a desired resource to view the service performance data.
NOTE
Click Modify in the lower right corner to change the performance monitoring template, performance
thresholds, or monitoring time policy.
----End
Enable Port Enabled, Disabled When the port is enabled, it indicates that
Default: Enabled the user uses the port and the port has
services. When the port is disabled, it
indicates that the port does not process
services.
When no service is configured, it is
recommended to disable the involved ports.
Port Mode Layer 2, Layer 3 Specifies the working mode of the Ethernet
Default: Layer 2 port.
l This parameter is set to Layer 2 when
the Ethernet port carries port-based or
QinQ-link-based Ethernet services.
l This parameter is set to Layer 3 when
the port carries tunnel services.
Encapsulation Type 802.1Q, QinQ, Null Selects the means of processing the
Default: 802.1Q accessed packets.
l This parameter is set to Null when the
port needs to transparently transmit
packets.
l This parameter is set to 802.1Q when
the port needs to identify 802.1Q
standard packets.
l This parameter is set to QinQ when the
port needs to identify QinQ standard
packets.
NOTE
The Encapsulation Type is always 802.1Q when
you set Port Mode to Layer 3.
For TN55EG16, if the port needs to identify both
C-VLAN and S-VLAN packets, Encapsulation
Type must be set to 802.1Q.
Working Mode l GE optical port: Set the Working Mode parameter to set the
1000M Full- working mode of the Ethernet port on the
Duplex, Auto- board.
Negotiation Auto-negotiation can automatically
l GE electrical determine the optimal working modes of
port: 10M Full- the connected ports. This mode is easy to
Duplex, 100M maintain and is recommended.
Full-Duplex, NOTE
1000M Full- Ensure that the working modes of the
Duplex, Auto– interconnected ports are the same, Otherwise,
Negotiation the services are not available.
l FE optical port:
100M Full-
Duplex, Auto-
Negotiation
Default: Auto-
Negotiation
Max Frame Length 1518 to 9600 This parameter specifies the maximum
(bytes) Default: 1522 length of a frame traversing a port. When
the length of a frame exceeds the specified
maximum frame length, the frame will be
discarded or the service will be interrupted.
ARP Aging Time 1 to 1440 Indicates the ARP aging time of the port.
(min.) Default: 720 After the ARP aging time expires, the
equipment automatically updates dynamic
ARP entries to prevent incorrect address
resolution.
NOTE
This parameter is valid only when Port Mode is
set to Layer 3.
Laser Interface On, Off Specifies the on/off status of the laser.
Status
Enable Port Enabled, Disabled When the port is enabled, it indicates that
Default: Enabled the user uses the port and the port has
services. When the port is disabled, it
indicates that the port does not process
services.
When no service is configured, it is
recommended to disable the involved ports.
Port Mode Layer 2, Layer 3 Specifies the working mode of the Ethernet
Default: Layer 2 port.
l Layer 2: The port can access the user-
side equipment, carry Ethernet services
that are based on the ports and use the
port exclusively or QinQ Link.
l Layer 3: The port can carry tunnels.
Encapsulation Type 802.1Q, QinQ, Null Selects the means of processing the
Default: 802.1Q accessed packets.
l Null: The port transparently transmits
the accessed packets.
l 802.1Q: The port identifies the 802.1Q
standard packets.
l QinQ: The port identifies the QinQ
standard packets.
NOTE
The Encapsulation Type is always 802.1Q when
you set Port Mode to Layer 3.
Working Mode 10G Full-Duplex Set the Working Mode parameter to set the
LAN working mode of the Ethernet port on the
Default: 10G Full- board.
Duplex LAN NOTE
l When setting this parameter, ensure that the
working modes of the interconnected ports
are the same. Otherwise, the services are not
available.
Max Frame Length 1518 to 9600 This parameter specifies the maximum
(bytes) Default: 1522 length of a frame traversing a port. When
the length of a frame exceeds the specified
maximum frame length, the frame will be
discarded or the service will be interrupted.
ARP Aging Time 1 to 1440 Indicates the ARP aging time of the port.
(min.) Default: 720 NOTE
This parameter is valid only when Port Mode is
set to Layer 3.
Laser Interface On, Off Specifies the on/off status of the laser.
Status
Enable Port Enabled, Disabled When the port is enabled, it indicates that
Default: Enabled the user uses the port and the port has
services. When the port is disabled, it
indicates that the port does not process
services.
When no service is configured, it is
recommended to disable the involved ports.
Port Mode Layer 2, Layer 3 Specifies the working mode of the Ethernet
Default: Layer 2 port.
l Layer 2: The port can access the user-
side equipment, carry Ethernet services
that are based on the ports and use the
port exclusively or QinQ Link.
l Layer 3: The port can carry tunnels.
Encapsulation Type 802.1Q, QinQ, Null Selects the means of processing the
Default: 802.1Q accessed packets.
l Null: The port transparently transmits
the accessed packets.
l 802.1Q: The port identifies the 802.1Q
standard packets.
l QinQ: The port identifies the QinQ
standard packets.
NOTE
The Encapsulation Type is always 802.1Q when
you set Port Mode to Layer 3.
If the port needs to identify both C-VLAN and
S-VLAN packets, Encapsulation Type must be
set to 802.1Q.
Working Mode Port1 to Port4: 10G Set the Working Mode parameter to set the
Full-Duplex LAN, working mode of the Ethernet port on the
10G Full-Duplex board.
WAN NOTE
Port5 to Port8: 10G When setting this parameter, ensure that the
working modes of the interconnected ports are
Full-Duplex LAN,
the same. Otherwise, the services are not
1000M Full-Duplex, available.
1000M Half-Duplex,
100M Full-Duplex,
100M Half-Duplex,
10M Full-Duplex,
10M Half-Duplex,
Auto-Negotiation
Default: 10G Full-
Duplex LAN
Max Frame Length 1518 to 9600 This parameter specifies the maximum
(bytes) Default: 1522 length of a frame traversing a port. When
the length of a frame exceeds the specified
maximum frame length, the frame will be
discarded or the service will be interrupted.
ARP Aging Time 1 to 1440 Indicates the ARP aging time of the port.
(min.) Default: 720 NOTE
This parameter is valid only when Port Mode is
set to Layer 3.
Laser Interface On, Off Specifies the on/off status of the laser.
Status
Port Mode Layer 2, Layer 3 Specifies the working mode of the Ethernet
Default: Layer 2 port.
l Layer 2: The port can access the user-
side equipment, carry Ethernet services
that are based on the ports and use the
port exclusively or QinQ Link.
l Layer 3: The port can carry tunnels.
Encapsulation Type 802.1Q, QinQ, Null Selects the means of processing the
Default: 802.1Q accessed packets.
l Null: The port transparently transmits
the accessed packets.
l 802.1Q: The port identifies the 802.1Q
standard packets.
l QinQ: The port identifies the QinQ
standard packets.
NOTE
The Encapsulation Type is always 802.1Q when
you set Port Mode to Layer 3.
ARP Aging Time 1 to 1440 Indicates the ARP aging time of the port.
(min) Default: 720 NOTE
This parameter is valid only when Port Mode is
set to Layer 3.
Port Mode Layer 2, Layer 3 Specifies the working mode of the Ethernet
Default: Layer 2 port.
l This parameter is set to Layer 2 when
the Ethernet port carries port-based or
QinQ-link-based Ethernet services.
l This parameter is set to Layer 3 when
the port carries tunnel services.
Encapsulation Type 802.1Q, QinQ, Null Selects the means of processing the
Default: 802.1Q accessed packets.
l This parameter is set to Null when the
port needs to transparently transmit
packets.
l This parameter is set to 802.1Q when
the port needs to identify 802.1Q
standard packets.
l This parameter is set to QinQ when the
port needs to identify QinQ standard
packets.
NOTE
The Encapsulation Type is always 802.1Q when
you set Port Mode to Layer 3.
If the port needs to identify both C-VLAN and
S-VLAN packets, Encapsulation Type must be
set to 802.1Q.
ARP Aging Time 1 to 1440 Indicates the ARP aging time of the port.
(min.) Default: 720 After the ARP aging time expires, the
equipment automatically updates dynamic
ARP entries to prevent incorrect address
resolution.
NOTE
This parameter is valid only when Port Mode is
set to Layer 3.
Port Mode Layer 2, Layer 3 Specifies the working mode of the Ethernet
Default: Layer 2 port.
l This parameter is set to Layer 2 when
the Ethernet port carries port-based or
QinQ-link-based Ethernet services.
l This parameter is set to Layer 3 when
the port carries tunnel services.
Encapsulation Type 802.1Q, QinQ, Null Selects the means of processing the
Default: 802.1Q accessed packets.
l This parameter is set to Null when the
port needs to transparently transmit
packets.
l This parameter is set to 802.1Q when
the port needs to identify 802.1Q
standard packets.
l This parameter is set to QinQ when the
port needs to identify QinQ standard
packets.
NOTE
The Encapsulation Type is always 802.1Q when
you set Port Mode to Layer 3.
If the port needs to identify both C-VLAN and
S-VLAN packets, Encapsulation Type must be
set to 802.1Q.
ARP Aging Time 1 to 1440 Indicates the ARP aging time of the port.
(min.) Default: 720 After the ARP aging time expires, the
equipment automatically updates dynamic
ARP entries to prevent incorrect address
resolution.
NOTE
This parameter is valid only when Port Mode is
set to Layer 3.
NOTE
QinQ Type Domain 0x0600 to 0xFFFE Indicates the customized QinQ type
Default: 0x8100 domain.
The C-VLAN port supports two QinQ type
domains, 8100 and the customized QinQ
type domain. The S-VLAN port supports
only one QinQ type domain. The default
value of the QinQ type domain is 88a8. You
can also change the value by setting QinQ
Type Domain.
NOTE
Only the TN55EG16 supports this parameter.
Tag Tag Aware, Access, Indicates the data packet processing mode.
Hybrid For details, see Table 4.
This parameter is unavailable when you set
Encapsulation Type in Basic Attributes to
QinQ or Null.
Tag Tag Aware, Access, Indicates the data packet processing mode.
Hybrid For details, see Table 4.
This parameter is unavailable when you set
Encapsulation Type in Basic Attributes to
QinQ or Null.
QinQ Type Domain 0x0600 to 0xFFFE Indicates the customized QinQ type
Default: 0x8100 domain.
The C-VLAN port supports two QinQ type
domains, 8100 and the customized QinQ
type domain. The S-VLAN port supports
only one QinQ type domain. The default
value of the QinQ type domain is 88a8. You
can also change the value by setting QinQ
Type Domain.
Tag Tag Aware, Access, Indicates the data packet processing mode.
Hybrid For details, see Table 4.
This parameter is unavailable when you set
Encapsulation Type in Basic Attributes to
QinQ or Null.
Tag Tag Aware, Access, Indicates the data packet processing mode.
Hybrid For details, see Table 5.
This parameter is unavailable when you set
Encapsulation Type in Basic Attributes to
QinQ or Null.
Tag Tag Aware, Access, Indicates the data packet processing mode.
Hybrid For details, see Table 5.
This parameter is unavailable when you set
Encapsulation Type in Basic Attributes to
QinQ or Null.
Tag Tag Aware, Access, Indicates the data packet processing mode.
Hybrid For details, see Table 5.
This parameter is unavailable when you set
Encapsulation Type in Basic Attributes to
QinQ or Null.
Enable Tunnel Enabled, Disabled After this parameter is set to Enabled for a
port, the port can identify and process
MPLS labels.
NOTE
The parameter value Disabled is invalid.
Therefore, this parameter can be set only to
Enabled.
Enable Tunnel Enabled, Disabled After this parameter is set to Enabled for a
port, the port can identify and process
MPLS labels.
NOTE
The parameter value Disabled is invalid.
Therefore, this parameter can be set only to
Enabled.
Enable Tunnel Enabled, Disabled After this parameter is set to Enabled for a
port, the port can identify and process
MPLS labels.
NOTE
The parameter value Disabled is invalid.
Therefore, this parameter can be set only to
Enabled.
Enable Tunnel Enabled, Disabled After this parameter is set to Enabled for a
port, the port can identify and process
MPLS labels.
Enable Tunnel Enabled, Disabled After this parameter is set to Enabled for a
port, the port can identify and process
MPLS labels.
NOTE
The parameter value Disabled is invalid.
Therefore, this parameter can be set only to
Enabled.
Enable Tunnel Enabled, Disabled After this parameter is set to Enabled for a
port, the port can identify and process
MPLS labels.
NOTE
The parameter value Disabled is invalid.
Therefore, this parameter can be set only to
Enabled.
Start of Global Label Space For example: 0 Set and display the start of
the global label space.
The start of the global label
space is the minimum value
of the ingress and egress
labels of the unicast tunnel.
When Start of Global
Label Space is 0, the
minimum value of the
ingress and egress labels of
the unicast tunnel is 16.
"0-15" values are reserved
and are unavailable.
Global Label Space Size For example: 32768 Set and display the size of
the global label space.
The global label space size
is the number of unicast
tunnel labels.
Start of Multicast Label The value of Start of Display the start of the
Space Global Label Space plus multicast label space.
the value of Global Label The start of the multicast
Space Size Example: 0 label space is the minimum
+ 32768 = 32768 value of the ingress and
egress labels of the multicast
tunnel.
Forward Next Hop Address For example, 192.168.0.3 Displays or specifies the
address of the next hop of
the tunnel.
This function is supported
only when the equipment is
configured with a
bidirectional tunnel.
Reverse Next Hop Address For example, 192.168.0.4 Displays or specifies the
address of the next hop of
the tunnel.
NOTE
When a bidirectional tunnel is
configured on the device,
Forward Next Hop Address
can be set at the ingress node,
and Reverse Next Hop
Address can be set at the
egress node.
Reverse Tunnel Name For example, Tunnel1_RVS Specifies the name of the
reverse tunnel.
Protection Tunnel Name For example, Tunnel1_PRT Specifies the name of the
protection tunnel.
This parameter is available
only when Signaling Type
is set to Static CR and
Protection Type is set to
1+1 or 1:1.
Signaling Type RSVP TE, LDP, Static CR, Specifies the signaling type
Static of the tunnel.
Default: Static CR This parameter is
configurable only when you
set Protocol Type to
MPLS.
l RSVP TE: You need to
specify only the ingress
and egress nodes for an
RSVP TE tunnel. The
MPLS protocol
automatically calculates
a route for the tunnel. In
addition, you can specify
constraint nodes to plan a
specific route for the
tunnel. You can
configure FRR
protection and the QoS
function for an RSVP TE
tunnel. Therefore, an
RSVP tunnel is more
flexible and safer than an
LDP tunnel.
l LDP: You need to
specify only the source
and sink nodes. The LDP
protocol automatically
calculates a route for the
tunnel. An LDP tunnel is
more flexible than a
static tunnel.
l Static CR: A static CR
tunnel is created with
certain constraints. The
mechanism for creating
and managing those
constraints is CR. Every
site that a static CR
tunnel passes through
must be manually
specified too. Different
from a static tunnel that
requires only routing
information, creating a
CR tunnel has other
configurations, such as
the bandwidth, route, and
QoS parameters.
Protection Group Name For example, Protection Set the name of protection
Group 1 group of tunnel.
This parameter is available
only when Signaling Type
is set to Static CR and
Protection Type is set to
1+1 or 1:1.
Auto Calculate Route Sets the value by clicking If Auto Calculate Route is
the check box. checked, the system
Checked, Unchecked automatically computes the
route after you select the
Default: Checked source node and sink node
and specify the NEs as
explicit/inexplicit nodes in
the physical topology.
Service ID For example, 11 Sets and queries the ID of the Ethernet service.
Service Name For example, test Sets and queries the name of the Ethernet
service.
Source Node For example, Displays the source node of the E-Line service.
21-54EG16-1(PORT-1 The format is Slot number - Board name - Port
)(14) name (VLAN ID).
Sink Node For example, PW-0 Displays the sink node of the E-Line service.
The sink node can be a port, PW or QinQ link.
Source Port For example, Sets and queries the user-side port or network-
21-54EG16-1(PORT-1 side port.
)(1-2)
Source VLANs 1-4094 Sets one or several VLAN IDs, or does not set
any VLAN ID.
Bearer Type Port, PW, QinQ Link Specifies the bearer type for different types of
Default: / Ethernet services. The value of this parameter
can be set to Port, PW, or QinQ Link.
l The bearer is the PW, and the PW ID needs
to be specified.
l The bearer is the physical port, and the slot
ID and port number needs to be specified.
l The bearer is the QinQ link, and the QinQ
link ID needs to be specified.
QinQ Link ID For example, 5 Selects and displays the QinQ link ID.
Control Channel Type None, CW, Alert Label Specifies the type of
Default: CW channels for transmitting
VCCV packets.
l None: Indicates that the
control word is not used
to indicate the VCCV
control channel
information.
l CW: Indicates that the
control word is used to
indicate the VCCV
control channel
information.
l Alert Label: Indicates
that VCCV packets in
Alert Label
encapsulation mode are
used.
Control Channel Type None, CW, Alert Label Specifies the type of
Default: CW channels for transmitting
VCCV packets.
l None: Indicates that the
control word is not used
to indicate the VCCV
control channel
information.
l CW: Indicates that the
control word is used to
indicate the VCCV
control channel
information.
l Alert Label: Indicates
that VCCV packets in
Alert Label
encapsulation mode are
used.
Role For example, Working Displays and specifies the role of a service
Source access port.
Based on different protection types, service
access ports can function as different roles,
for example, working source, working sink,
protection source, protection sink, FRR
source, and FRR sink.
Local QoS Policy - Displays the QoS policy at the local end.
Default CS6, CS7, EF, AF1, Displays the service forwarding priority.
Forwarding AF2, AF3, AF4, BE, Different values represent different service
Priority NONE classes.
l CS6-CS7: indicate the highest service
class, mainly applicable to signaling
transmission.
l EF: indicates expedited forwarding,
applicable to services (for example,
voice services) with low transmission
delay and low packet loss rate.
l AF1-AF4: indicate assured forwarding,
applicable to services that require an
assured rate rather than restricted delay
or jitter.
l BE: applicable to services that do not
need special processing.
Default Packet Red, Yellow, Green, Displays the default packet marking color.
Marking Color None Based on the labels carried by packets,
different colors are configured for marking
the packets. Red packets have the highest
priority.
Processing Mode Discard, Pass, Remark Specifies the processing mode of packets.
of Green Packet l Discard: The packets are discarded.
l Pass: The packets are forwarded.
CoS of Green CS6, CS7, EF, AF1, Displays the service class of the packets
Packet AF2, AF3, AF4, BE, marked green.
NONE CoS of packets defines different service
classes.
l CS6-CS7: indicate the highest service
class, mainly applicable to signaling
transmission.
l EF: indicates expedited forwarding,
applicable to services (for example,
voice and video services) with low
transmission delay and low packet loss
rate.
l AF1-AF4: indicate assured forwarding,
applicable to services that require an
assured rate rather than restricted delay
or jitter.
l BE: applicable to services that do not
need special processing.
Processing Mode Discard, Pass, Remark Specifies the processing mode of packets.
of Yellow Packet l Discard: The packets are discarded.
l Pass: The packets are forwarded.
CoS of Yellow CS6, CS7, EF, AF1, Displays the service class of the packets
Packet AF2, AF3, AF4, BE, marked yellow.
NONE CoS of packets defines different service
classes.
l CS6-CS7: indicate the highest service
class, mainly applicable to signaling
transmission.
l EF: indicates expedited forwarding,
applicable to services (for example,
voice and video services) with low
transmission delay and low packet loss
rate.
l AF1-AF4: indicate assured forwarding,
applicable to services that require an
assured rate rather than restricted delay
or jitter.
l BE: applicable to services that do not
need special processing.
Processing Mode Discard, Pass, Remark Specifies the processing mode of packets.
of Red Packet l Discard: The packets are discarded.
l Pass: The packets are forwarded.
CoS of Red CS6, CS7, EF, AF1, Displays the service class of the packets
Packet AF2, AF3, AF4, BE, marked red.
NONE CoS of packets defines different service
classes.
l CS6-CS7: indicate the highest service
class, mainly applicable to signaling
transmission.
l EF: indicates expedited forwarding,
applicable to services (for example,
voice and video services) with low
transmission delay and low packet loss
rate.
l AF1-AF4: indicate assured forwarding,
applicable to services that require an
assured rate rather than restricted delay
or jitter.
l BE: applicable to services that do not
need special processing.
Default BE, AF1, AF2, AF3, Indicates the forwarding priority that the NE
Forwarding AF4, EF, CS6, CS7, sets to the user packets on the V-UNI side by
Priority NONE default.
Default: BE l CS7: Indicates the highest forwarding
priority, for delivering the control packets
(very important protocol packets) in the
network.
l CS6: Indicates the priority that is lower
than CS7, for delivering the control packets
(important protocol packets) in the
network.
l EF: Indicates the expedited forwarding
priority that is lower than CS6, for the low
delay services (for example, voice
services).
l AF4: Indicates the assured forwarding
priority 4, whose forwarding priority is
lower than EF.
l AF3: Indicates the assured forwarding
priority 3, whose forwarding priority is
lower than AF4.
l AF2: Indicates the assured forwarding
priority 2, whose forwarding priority is
lower than AF3.
l AF1: Indicates the assured forwarding
priority 1, whose forwarding priority is
lower than AF2.
l BE: Indicates the best effort forwarding
priority that is the lowest forwarding
priority, for the services without QoS in the
network.
Default Packet Red, Yellow, Green, Indicates the color that the NE sets to the user
Relabeling None packets on the V-UNI side by default.
Color Default: Green The user packets of a higher priority should be
marked green. The user packets of a lower
priority should be marked red. The user
packets of a medium priority should be marked
yellow.
Tunnel Type MPLS Displays the type of the tunnel that carries the
PW.
Control Word No Use, Used First Specifies the policy for using the PW control
Default: / word. That is, this parameter determines
whether a PW uses the control word field. A
control word is a 4-byte encapsulated packet
header, which can be used to identify the
packet sequence or used for bit stuffing.
l If the ping or traceroute test needs to be
performed on a PW, set this parameter to
Used First.
l If the ping or traceroute test does not need
to be performed on a PW, set this parameter
to No Use to save NNI-side bandwidth.
Control None, CW, Alert Label Specifies the type of channels for transmitting
Channel Type Default: CW VCCV packets.
l None: Indicates that the control word is not
used to indicate the VCCV control channel
information.
l CW: Indicates that the control word is used
to indicate the VCCV control channel
information.
l Alert Label: Indicates that VCCV packets
in Alert Label encapsulation mode are used.
CC Test 3.33ms, 10ms, 100ms, The source end MEP constructs the CC
Transmit Period 1s, 10s, 1m, 10m frames, and then transmits them periodically to
Default: 1s the destination MEP. Within a certain period
(3.5 times of the transmission period), if the
destination MEP does not receive the CC
packets from the source end, an alarm is
automatically reported. The CC Test
Transmit Period parameter indicates the
transmission period of the unidirectional
connectivity check.
It is recommended that you use three period
values, that is, 3.33 ms for protection
switching, 100 ms for performance check, and
1 s for connectivity check. The configuration
should comply with user requirements. If the
fast check is required, set to 3.33 ms. Hence,
the fault can be detected quickly. The
bandwidth used, however, descends with the
period value.
Board For example, Displays the board where the MEP point is
21-54EG16 located. The format is Slot number - Board
name.
Port For example, Displays the port where the MEP point is
21-54EG16-1(PORT-1 located. The format is Slot number - Board
) name - Port information.
Node For example, Sets the node as an MEP point. The format is
21-54EG16-1(PORT-1 Slot number - Board name - Port information.
)
Service ID For example, 11 Sets and queries the ID of the Ethernet service.
Service Name For example, test Sets and queries the name of the Ethernet
service.
Tag Type C-Awared, S-Awared, C-Awared indicates that the learning is based
Tag-Transparent on the C-TAG (client-side VLAN tag).
S-Awared indicates that the learning is based
on the S-TAG (operator service-layer VLAN
tag). S-Awared is valid only when
Encapsulation Type is set to QinQ for a port.
Tag-Transparent indicates that all Ethernet
packets can be transmitted transparently when
Encapsulation Type is set to Null for a port.
MAC Address SVL, IVL SVL indicates the shared VLAN learning. All
Learning Mode VLANs share a MAC address forwarding
table. Any MAC address is unique in the
forwarding table.
IVL indicates the independent VLAN
learning. The forwarding tables for different
VLANs are independent from each other. It is
acceptable that the MAC address forwarding
tables for different VLANs have the same
MAC address.
When Tag Type is set to Tag-Transparent,
the parameter value is SVL by default and is
not configurable.
NOTE
You can set MAC Address Learning Mode to IVL
only when the bridge type is IEEE 802.1ad.
MTU (bytes) - The OptiX OSN 8800 does not support the
setting of this parameter.
Service Tag User, Service The Service Tag Role is used to indicate the
Role Default: User user access mode, that is, the encapsulation
mode when the Ethernet service is received by
the AC.
l User: If the service-delimiting tag is User,
the user access mode is Ethernet. In this
case, the Ethernet frame that the CE sends
to the PE does not carry a provider-tag (P-
Tag). If the frame header contains the
VLAN tag, the VLAN tag is the inner
VLAN tag of the user packet, which is
called user-tag (U-Tag). The PE does not
identify or process a U-Tag.
l If the service-delimiting tag is Service, the
user access mode is VLAN. In this case,
the Ethernet frame that the CE sends to the
PE carries a provider-tag (P-Tag), which is
provided for the carrier to differentiate
users. The PE identifies and processes a P-
Tag based on the PW encapsulation mode.
MAC Address Aging Time 1 min - 640 min Specifies the aging time of
Default: 5 min MAC addresses.
If the MAC address aging
function is enabled, the
system deletes a MAC
address if no packets that
contain the MAC address
are received after the aging
time expires.
If the MAC address aging
function is disabled, this
parameter is unavailable.
Control Channel Type None, CW, Alert Label Specifies the type of
Default: CW channels for transmitting
VCCV packets.
l None: Indicates that the
control word is not used
to indicate the VCCV
control channel
information.
l CW: Indicates that the
control word is used to
indicate the VCCV
control channel
information.
l Alert Label: Indicates
that VCCV packets in
Alert Label
encapsulation mode are
used.
Enabled Enabled and Disabled Sets whether to enable the broadcast packet
Broadcast suppression. Enabling the broadcast packet
Packet suppression efficiently prevents the broadcast
Suppression storm and network congestion, and ensures the
normal running of services. The E-LAN
service supports this parameter.
Default BE, AF1, AF2, AF3, The Default Forwarding Priority parameter
Forwarding AF4, EF, CS6, CS7, indicates the forwarding priority that the NE
Priority NONE sets to the user packets on the V-UNI side by
Default: BE default.
Default Packet Red, Yellow, Green, The Default Packet Relabeling Color indicates
Relabeling None the color that the NE sets to the user packets
Color Default: Green on the V-UNI side by default.
Tunnel Type MPLS Displays the type of the tunnel that carries the
PW.
Control Word No Use, Used First Specifies the policy for using the PW control
Default: / word. That is, this parameter determines
whether a PW uses the control word field. A
control word is a 4-byte encapsulated packet
header, which can be used to identify the
packet sequence or used for bit stuffing.
l If the ping or traceroute test needs to be
performed on a PW, set this parameter to
Used First.
l If the ping or traceroute test does not need
to be performed on a PW, set this parameter
to No Use to save NNI-side bandwidth.
Control None, CW, Alert Label Specifies the type of channels for transmitting
Channel Type Default: CW VCCV packets.
l None: Indicates that the control word is not
used to indicate the VCCV control channel
information.
l CW: Indicates that the control word is used
to indicate the VCCV control channel
information.
l Alert Label: Indicates that VCCV packets
in Alert Label encapsulation mode are used.
Split Horizon For example, PW-100, The Split Horizon Group Member parameter
Group Member PORT1[90, 100] indicates the logical port member in a split
horizon group.
Aging Time 1-640 Set the Aging Time (min) parameter to set the
(min) Default: 5 aging time of the learnt MAC address. The
Aging Time (min) parameter indicates that the
MAC address is automatically aged after the
timing is set.
Address Table 0-65534 Sets the capacity of the MAC address table.
Specified Default: 512
Capacity
Frame Type Unicast, Multicast Displays the type of the received unknown
frames.
Handing Mode Discard, Broadcast Selects the mode for handling the unknown
Default: Broadcast frames. Discard indicates that unknown
frames are directly discarded. Broadcast
indicates that unknown frames are broadcast at
the forwarding port.
Egress Interface For example, PW-100 Sets the egress interface, which can be a PW,
port or QinQ link.
CC Test 3.33ms, 10ms, 100ms, The source end MEP constructs the CC
Transmit Period 1s, 10s, 1m, 10m frames, and then transmits them periodically to
Default: 1s the destination MEP. Within a certain period
(3.5 times of the transmission period), if the
destination MEP does not receive the CC
packets from the source end, an alarm is
automatically reported. The CC Test
Transmit Period parameter indicates the
transmission period of the unidirectional
connectivity check.
It is recommended that you use three period
values, that is, 3.33 ms for protection
switching, 100 ms for performance check, and
1 s for connectivity check. The configuration
should comply with user requirements. If the
fast check is required, set to 3.33 ms. Hence,
the fault can be detected quickly. The
bandwidth used, however, descends with the
period value.
Board For example, Displays the board where the MEP point is
21-54EG16 located. The format is Slot number - Board
name.
Port For example, Displays the port where the MEP point is
21-54EG16-1(PORT-1 located. The format is Slot number - Board
) name - Port information.
Node For example, Sets the node as an MEP point. The format is
21-54EG16-1(PORT-1 Slot number - Board name - Port information.
)
QinQ Link For example, 5 Displays or specifies the ID of the QinQ link.
ID
14 Configuration Tasks
This chapter describes basic operations that may be used when you configure services. For
example, configure the service type and WDM-side port attributes of the board. You can see
this topic if required.
Prerequisites
You are an NMS user with " NE operator" privilege or higher.
Before changing the working mode or port working mode of a board, delete the cross-
connections on the board and logical fiber connections at the optical ports.
l You need to configure working modes for the following boards: TN11TOM, TN52TOM,
THA, TOA, LOA, TN53TDX, TN55TQX and TEM28.
l You need to configure only Port Working Mode for the following boards: THA, TOA,
LOA, TN53TDX, and TN55TQX.
l For the TN52TOM board, you need to configure not only Board Working Mode but
also Port Working Mode (such as ODU0/ODU1 mapping and tributary-line integration)
to achieve different service signal flows.
l If you set Board Working Mode to Non-Cascading mode for the TN52TOM board,
you need to set Port Working Mode only for optical ports ClicentLP1, ClicentLP3,
ClicentLP5, and ClicentLP7.
Legend Information
Figure 14-1 shows legend information about U2000 operations.
Procedure
Step 1 In the NE Explorer, select the board that you want to configure and choose Configuration >
Working Mode from the Function Tree.
Step 2 In the Board Working Mode pane, set Board Working Mode to Cascading mode or Non-
Cascading mode.
NOTE
Step 3 In the Port Working Mode pane, select the desired optical port. Click the Port Working
Mode field and select the corresponding mode from the drop-down list.
Step 4 Click Apply.
Step 5 Click Query. Confirm that the query results are the same as the values that are set.
----End
Prerequisite
You are an NMS user with " NE operator" privilege or higher.
Precautions
NOTICE
Modifying the service mode interrupts the existing services.
NOTE
Legend Information
Figure 14-2 shows legend information about U2000 operations.
Step 2 Click By Board/Port(Channel), and then choose Channel from the drop-down list.
Step 3 Select the Basic Attributes tab, and then select the desired optical port.
Step 4 Double-click the Service Mode field, and then choose the desired service mode from the
drop-down list. For details, see Service Mode (WDM Interface).
Step 6 Click Query. Confirm that the query results are the same as the values that are set.
----End
Prerequisite
You must be an NMS user with "NE operator" authority or higher.
Precautions
NOTICE
Caution
l Modifying the service type will lead to service interruption. For ASON services, this
operation may trigger service rerouting.
l When configuring a GE or 10GE service, make sure that the service encapsulation types
specified for the transmitter and receiver are the same.
Legend Information
Figure 14-3 shows legend information about U2000 operations.
Step 2 Select By Board/Port(Channel) and choose Channel from the drop-down list.
Step 3 In the Basic Attributes tab, select the desired optical port. Double-click the Service Type
field and select the required service type.
NOTE
l If you set Service Type to Any, you must set the service rate in Client Service Bearer Rate
(Mbit/s).
l If you set Service Type to 10GE LAN, you must set the Port Mapping .
Step 5 Click Query, and the Operation Result dialog box is displayed. Click Close. Confirm that
the query results are the same as the values that are set.
----End
Prerequisite
You are an NMS user with " NE operator" privilege or higher.
Background Information
l For the OptiX OSN 6800, the available cross-connection capacity of a board is related to
the slot where the board is installed. For example, when the TQX or NQ2 board is
installed in slots 1, 4, 11 or 14, the available cross-connection capacity of the board is 40
Gbit/s; when the TQX or NQ2 board is installed in any other slots, the available cross-
connection capacity of the board is 20 Gbit/s. Different boards have different cross-
connection capacities.
l If the capacity of the configured services is greater than the available cross-connection
capacity, the service configuration fails.
l When configuring the cross-connection services, first configure the service type of the
WDM interface of the OTU. For detailed configuration method, see Configuring the
Service Type.
Legend Information
Figure 14-4 shows legend information about U2000 operations.
4
1
1
4
4
1
1
4
NOTE
3
: For details about the standard mode and ODUflex, see 2.1.2 Standard Mode and
Compatible Mode and 2.1.3 ODUflex.
----End
Step 2 In the NE Explorer, select the NE and choose Configuration > Electrical Cross-Connection
Service Management from the Function Tree.
Step 3 Click the Electrical Cross-Connection Configuration tab. Click New and the Create Cross-
Connection Service dialog box is displayed. For parameter descriptions, see 2.8.1 WDM
Cross-Connection Configuration.
Step 4 Select corresponding values for Service Level and Service Type and set other parameters for
the service.
Step 5 Click OK and the created cross-connection is displayed in the user interface.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Applies to the TQM, TOM, LQM, LQMD, LOM, LQMS, LDMD, LDM, LDMS, TOA, THA.
Step 2 Click Query to query the status of configured services for each port on the board.
Step 3 Choose the port, double-click Timeslot Configuration Mode and select Automatically
Assign.
NOTE
TOA and THA boards support the compatible mode and standard mode. The compatible mode supports
Automatically Assign and Manual. The standard mode does not support Manual. Therefore, set
Timeslot Configuration Mode to Automatically Assign when a TOA board in the compatible mode
interconnects with a TOA board in the standard mode or a THA board in the compatible mode
interconnects with a THA board in the standard mode.
NOTE
When Timeslot Configuration Mode is set as Automatically Assign, Timeslot Configuration Mode
of the receive end and transmit end in the same direction of the service must be set as Automatically
Assign, and Send Timeslots and Receive Timeslots do not need to be set.
When Timeslot Configuration Mode is set as Manual, you can set parameters, such as Send
Timeslots and Receive Timeslots.
l The format of timeslots can be one of the following two:
– 1, 2, 3, 4: Indicates that four (1-4) timeslots are used.
– 1-4: Indicates that four (1-4) timeslots are used.
l Please obey the following rules during service configuration:
– The transmit and receive timeslots should be specified for each board.
– For each board, the same timeslot in the same direction cannot be shared by multiple
services.
– In one direction of one service, the timeslot of the receive end must be the same as that of
the transmit end.
– Timeslots must be set again after the service type is changed.
For details, see Service Timeslot (WDM Services).
Step 5 Click Query. The configured timeslots of the board are displayed in the interface.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Legend Information
Figure 14-5 shows legend information about U2000 operations.
Operation Example:
1
3
5
6
NOTE
4
If a cross-connection is configured on the board, delete the cross-connection on the board
before setting Board Mode.
----End
Prerequisites
l You are an NMS user with " NE operator" privilege or higher.
l Service Type of the board has been set to the SDH or SONET service.
Parameter Description
Input in Text For example: A The text entry field is used to input the
Format desired byte.
Byte Mode Single-Byte Mode, 16- Before inputting the text, you need to select
Byte Mode (First Byte the byte mode. Different services support
Created different modes.
Automatically), Disable
Input Mode Text Mode, Selects an input mode before entering texts.
Hexadecimal Text Mode means you can enter characters
directly; Hexadecimal means you enter
texts in hexadecimal mode.
Prerequisites
You are an NMS user with " NE operator" privilege or higher.
Background Information
When the WDM-side signal of the line board is OTU2e or OTU3e, or when the client-side
signal of the tributary board is 10GE LAN and Port Mapping is set to Bit Transparent
Mapping (11.1 G) for the client-side port, set Line Rate of the line board to Speedup Mode.
In any other cases, set it to Standard Mode.
Legend Information
Figure 14-6 shows legend information about U2000 operations.
Procedure
Step 1 In the NE Explorer, configure Line Rate of the line board .
Operation Example:
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Background Information
l Only the TOM board supports interchange of line-side ports and client-side ports. When
a TOM board is created, the ports on the TOM board are created automatically and are
defined as client-side ports by default.
l When a board is created, the ports on the board are created automatically and the client-
side ports are defined as Client Side Grey Optical Port by default.
l For 100G tributary boards, the port type is CFP4*25G by default. If CFP10*10G optical
modules are used on 100G tributary boards, services will be unavailable and a
LASER_MODULE_MISMATCH alarm will be reported. Therefore, ensure that the
client-side optical module type is the same as the practical optical module type before
service configuration.
Legend Information
Figure 14-7 shows legend information about U2000 operations.
ProcedureU2000
Step 1 Configure the port type based on the practical SFP optical modules used on the client-side and
WDM-side ports of the OTU boards inPath View.
Operation Example:
3 4
2
5
NOTE
If you need to modify Type to Client Side Color Optical Port, Line Side Color Optical Port or
Electrical Port, you must first delete the port, and then add the port. Otherwise the port cannot be
modified successfully.
Configure the port type based on the practical client-side optical modules of 100G tributary
boards.
2
1
----End
Step 2 Right-click the port for which you want to modify the port type and choose Modify Port from
the shortcut menu. The Modify Port dialog box is displayed. Set Type and click OK to apply
the configuration.
NOTE
If you need to modify Type to Client Side Color Optical Port, Line Side Color Optical Port or
Electrical Port, you must first delete the port, and then add the port. Otherwise the port cannot be
modified successfully.
Step 3 Optional: In Path View, right-click the desired port, and click Delete Port.
Step 4 Optional: In Path View, right-click a blank space and select Add Port. In the Add Port
dialog box displayed, set the Type of the port. Click OK to apply the configuration.
----End
Prerequisite
You are an NMS user with " NE operator" privilege or higher.
The Cross-Connection Service must be created and the activated state of the service should be
activated.
Precautions
NOTICE
The deactivation operation may interrupt services.
Legend Information
Figure 14-8 shows legend information about U2000 operations.
NOTE
1
If the Web LCT is used, the navigation path is as follows: in the NE Explorer, select the NE
and choose Configuration > Electrical Cross-Connection Service Management from the Function
Tree.
2
If the Web LCT is used, the navigation path is as follows: click the Electrical Cross-
Connection Configuration tab
----End
Prerequisite
You are an NMS user with " NE operator" privilege or higher.
The cross-connections must be created and inactive.
Precautions
NOTICE
Deleting cross-connections may interrupt services.
Legend Information
Figure 14-9 shows legend information about U2000 operations.
Operation Example:
2
4
Step 2 In the two Confirm dialog box that is displayed , click OKand then click Close. In the
Operation Result dialog box.
----End
----End
A Parameters Description
This chapter describes the parameters of all the WDM products of Huawei. Each parameter is
described in terms of description, impact on the system, values, configuration guidelines, and
relationship with other parameters in detail.
A.1 Enable Port
A.2 Port (Ethernet Port Attribute)
A.3 Broadcast Packet Suppression Threshold
A.4 Enabling Broadcast Packet Suppression
A.5 Default VLAN ID
A.6 VLAN Priority
A.7 Entry Detection
A.8 Tag Identifier
A.9 Source Channel (WDM Cross-Connection)
A.10 Sink Channel (WDM Cross-Connection Configuration)
A.11 Activation Status (WDM Cross-Connection Configuration)
A.12 Level (WDM Cross-Connection Configuration)
A.13 Direction (WDM Cross-Connection Configuration)
A.14 Service Timeslot (WDM Services)
A.15 Service Mode (WDM Interface)
A.16 Board Mode (WDM Interface)
A.17 Explicit Link
A.18 Explicit Node
A.19 Excluded Node
A.20 Auto-Calculation
A.21 Copy after Creation
Values
Value Range Default Value
Value Description
Enabled Enables a port. In this case, the attributes configured for the
port take effect.
Disabled Disables a port. In this case, the attributes configured for the
port becomes invalid and the service at the port is
interrupted.
Configuration Guidelines
None.
Values
Value Range Default Value
Value Description
Configuration Guidelines
None.
Values
Value Range Default Value
10%-100% 30%
Configuration Guidelines
Value Description
Values
Value Range Default Value
Value Description
Configuration Guidelines
Set this parameter only when you need to limit the traffic of broadcast services.
Values
Value Range Default Value
1 to 4095 1
Configuration Guidelines
None.
Values
Value Range Default Value
0 to 7 0
Configuration Guidelines
None.
Values
Value Range Default Value
Value Description
Configuration Guidelines
None.
Values
Value Range Default Value
Value Description
Configuration Guidelines
None.
Values
Value Range Default Value
Value Description
Slot ID-Board Name- Slot ID: The ID of the slot on the local NE where the cross-
Optical Interface ID-Optical connect board is located.
Channel ID Board Name: The name of the cross-connect board.
Optical Interface ID: The ID of the optical interface where
the cross-connect services are configured.
Optical Channel ID: The ID of the optical channel where
the cross-connect services are configured.
Configuration Guidelines
None.
Values
Value Range Default Value
Value Description
Slot ID-Board Name - Slot ID: The ID of the slot on the local NE where the cross-
Optical Interface ID - connect board is located.
Optical Channel ID Board Name: The name of the cross-connect board.
Optical Interface ID: The ID of the optical interface where
the cross-connect services are configured.
Optical Channel ID: The ID of the optical channel where
the cross-connect services are configured.
Configuration Guidelines
None.
Values
Value Range Default Value
Value Description
Inactive Indicates that the configuration is not activated. The service cross-
connection configuration will not be delivered to the NE software.
Configuration Guidelines
When creating service cross-connections, determine whether to deliver the configuration
immediately to the NE software.
Values
Value Range Default Value
Value Description
NOTE
For the services listed in the table above, the ODU5G service is used only for intra-board fixed cross-
connections. For new cross-connections, only GE, Any, ODU0, ODU1, ODU2, ODU3 and OTU1
services can be used.
The LSX, LSXR, TMX, LOM, LSXL, and LSXLR boards do not support electrical cross-connections
but fixed cross-connections.
Configuration Guidelines
The value of the parameter varies according to boards. For details, see the Hardware
Description.
When you configure electrical cross-connections by using the cross-connect board, the
services at the source and sink nodes configured with cross-connections must be consistent.
The fixed cross-connection within a board does not need to be configured manually. It is
configured automatically by the U2000.
Values
Value Range Default Value
Value Description
Configuration Guidelines
The values of the parameter are different according to the boards. For details, see the
Hardware Description.
Values
Value Range Default Value
Configuration Guidelines
The following table lists the required timeslots of each board for the OptiX OSN 6800, the
OptiX OSN 3800 and OptiX OSN 8800.
LDM/LDMD/ FE 1
LDMS/LQM/LQMD/
LQMS/TOM/TQM GE 7
OTU-1 16
STM-1 1
STM-4 4
STM-16 16
OC-3 1
OC-12 4
OC-48 16
FC100 6
FC200 12
FICON 6
FICON Express 12
HD-SDI 11
DVB-ASI 2
SDI 3
ESCON 2
FDDI 1
LOM GE 1
FC100 1
FC200 2
FC400 4
FICON 1
FICON4G 4
FICON Express 2
ISC 1G 1
ISC 2G 2
Values
See the NMS parameter descriptions of corresponding boards.
Configuration Guidelines
l For the L4G, LDGS, LDGD, and LQG boards: Set the line-side service modes of the
local and remote boards to the same value. When the local board is connected to an SDH
service board on non-WDM equipment, set the line-side service mode to SDH.
l For the LQM, LQMD, LQMS, TOM, and TQM boards: When the board is enabled to
receive an OTN service on the client side, set this parameter to OTN Mode. For any
other client service types, set this parameter to Client Mode.
Values
The following table provides the parameter values of the ECOM board.
The following table describes the parameter values of the ECOM board.
Service Mode In this mode, the ECOM board can aggregate eight FE
services into one GE service.
HUB Mode In this mode, the ECOM board can aggregate eight FE
services into one FE service.
The following table provides the parameter values of the TN12LQMS board.
The following table describes the parameter values of the TN12LQMS board.
NS1 Mode In this mode, the TN12LQMS board serves as a line board
and adds/drops OTU1 signals in conjunction with a
tributary board.
NOTE
The NS1 Mode value is valid only when the TN12LQMS board is deployed in an OptiX OSN 6800
subrack or OptiX OSN 3800 subrack.
The following table provides the parameter values of the TN11TOM board.
The following table describes the parameter values of the TN11TOM board.
Cascading Mode In this mode, only the RX7/TX7 and RX8/TX8 port pairs
on the board can be used as WDM side optical port pairs.
The board can multiplex up to six Any-rate signals into one
OTU1 signal.
Electrical Relay Mode When optical-layer and electrical-layer ASON are enabled,
it does not matter whether the Board Mode parameter is set
Optical Relay Mode to Optical Relay Mode or Electrical Relay mode. The
parameter must be set to Optical Relay Mode for the line
board in a non-ASON system; otherwise, end-to-end
management of ASON services is not available.
Configuration Guidelines
Set the board mode depending on the actual service application scenario.
Values
Value Range Default Value
Value Description
Configuration Guidelines
In general, only one explicit link is available on an NE. In addition, the explicit link can be set
only at the egress port on the link that a service traverses.
Values
Value Range Default Value
Value Parameter
Configuration Guidelines
Check whether the number of nodes that an ASON service traverses exceeds the maximum
number of nodes. In the process of creating an ASON service, the ASON software by default
considers that the maximum hops of the ASON service is . That is, the maximum number of
nodes that an ASON service travels is . In general, only one explicit node is available on an
NE.
Values
Value Range Default Value
Value Parameter
Configuration Guidelines
Set this parameter according to customer requirements.
A.20 Auto-Calculation
Description
The Auto-Calculation parameter enables auto-calculation of the trails that comply with the
specified level, direction, rate, source, sink, and route constraints.
Values
Value Range Default Value
None None
Configuration Guidelines
None.
Users can create services in batches if the services have the same source node and the same
sink node and comply with the same specified route constraints.
Values
Value Range Default Value
Value Description
Sink Lists all nodes that can function as the sink of a service
complying with the specified constraints.
Values
Value Range Default Value
Value Description
Configuration Guidelines
None.
Values
Value Range Default Value
Value Description
Unidirectional Indicates that the source can transmit services, and the sink can
receive services.
Bidirectional Indicates that the source and sink can receive and transmit
services.
Configuration Guidelines
Ensure that a created ASON service is bidirectional.
Values
Value Range Default Value
GE, 10GE, 10GELAN, 10GEWAN, The default rate varies according to service
OTU1, OTU5G, OTU2, OTU3, ANY, levels.
FC25, FC50, FC100, FC200, OC-3,
OC-12, OC-48, OC-192, OC-768,
STM-1, STM-4, STM-16, STM-64...
Configuration Guidelines
l Ensure that the service rates for upstream and downstream boards are the same.
l Set this parameter according to the actual service mapping mode and signal rate. The
parameter value varies according to boards. For details, see the Hardware Description.
Values
Value Range Default Value
Configuration Guidelines
l Only one source port can be set for one board-level optical cross-connection.
l A MON port cannot be used as the source port for a board-level optical cross-
connection.
Values
Value Range Default Value
Value Description
Configuration Guidelines
l Only one sink port can be set for one board-level optical cross-connection.
l A MON port cannot be used as a sink port for a board-level optical cross-connection.
B Glossary
Numerics
3G See Third Generation.
3R reshaping, retiming, regenerating
802.1Q in 802.1Q A VLAN feature that allows the equipment to add a VLAN tag to a tagged frame. The
(QinQ) implementation of QinQ is to add a public VLAN tag to a frame with a private VLAN
tag to allow the frame with double VLAN tags to be transmitted over the service
provider's backbone network based on the public VLAN tag. This provides a layer 2
VPN tunnel for customers and enables transparent transmission of packets over
private VLANs.
A
A/D analog/digit
AA authentication authorization
AAA See Authentication, Authorization and Accounting.
AC alternating current
ACH associated channel header
ACK See acknowledgement.
ACL See Access Control List.
ACR allowed cell rate
ACS See Application Control Server.
ADC analog to digital converter
ADM add/drop multiplexer
ADSL See asymmetric digital subscriber line.
AF See assured forwarding.
AH See Authentication Header.
AIN advanced intelligent network
AIS alarm indication signal
automatic power A function to automatically equalize channel optical power at the transmitter end,
equilibrium (APE) ensuring a required optical power flatness and OSNR at the receiver end.
autonomous system A network set that uses the same routing policy and is managed by the same
(AS) technology administration department. Each AS has a unique identifier that is an
integer ranging from 1 to 65535. The identifier is assigned by IANA. An AS can be
divided into areas.
avalanche photodiode A semiconductor photodetector with integral detection and amplification stages.
(APD) Electrons generated at a p/n junction are accelerated in a region where they free an
avalanche of other electrons. APDs can detect faint signals but require higher voltages
than other semiconductor electronics.
B
B/S Browser/Server
BA booster amplifier
BBC See battery backup cabinet.
BBER background block error ratio
BC boundary clock
BDI See backward defect indication.
BE See best effort.
BEI backward error indication
BER bit error rate
BFD See Bidirectional Forwarding Detection.
BGP Border Gateway Protocol
BIAE backward incoming alignment error
BIOS See basic input/output system.
BIP-8 See bit interleaved parity-8.
BITS See building integrated timing supply.
BMC best master clock
BPDU See bridge protocol data unit.
BPS board protection switching
BRA See basic rate access.
BRAS See broadband remote access server.
BTS base transceiver station
Bidirectional A fast and independent hello protocol that delivers millisecond-level link failure
Forwarding Detection detection and provides carrier-class availability. After sessions are established between
(BFD) neighboring systems, the systems can periodically send BFD packets to each other. If
one system fails to receive a BFD packet within the negotiated period, the system
regards that the bidirectional link fails and instructs the upper layer protocol to take
actions to recover the faulty link.
backplane An electronic circuit board containing circuits and sockets into which additional
electronic devices on other circuit boards or cards can be plugged.
backward defect A function that the sink node of a LSP, when detecting a defect, uses to inform the
indication (BDI) upstream end of the LSP of a downstream defect along the return path.
basic input/output Firmware stored on the computer motherboard that contains basic input/output control
system (BIOS) programs, power-on self test (POST) programs, bootstraps, and system setting
information. The BIOS provides hardware setting and control functions for the
computer.
basic rate access An ISDN interface typically used by smaller sites and customers. This interface
(BRA) consists of a single 16 kbit/s data (or "D") channel plus two bearer (or "B") channels
for voice and/or data. Also known as Basic Rate Access, or BRI.
battery backup cabinet A cabinet that contains a built-in battery group to back up -48 V DC power and to
(BBC) supply power to the base station when there is no power input. It is a component of a
base station.
best effort (BE) 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.
bit interleaved parity-8 Consists of a parity byte calculated bit-wise across a large number of bytes in a
(BIP-8) transmission transport frame. Divide a frame is into several blocks with 8 bits (one
byte) in a parity unit and then arrange the blocks in matrix. Compute the number of
"1" or "0" over each column. Then fill a 1 in the corresponding bit for the result if the
number is odd, otherwise fill a 0.
bridge A device that connects two or more networks and forwards packets among them.
Bridges operate at the physical network level. Bridges differ from repeaters because
bridges store and forward complete packets, while repeaters forward all electrical
signals. Bridges differ from routers because bridges use physical addresses, while
routers use IP addresses.
bridge protocol data Data messages exchanged across switches within an extended LAN that uses a
unit (BPDU) spanning tree protocol (STP) topology. BPDU packets contain information on ports,
addresses, priorities, and costs, and they ensure that the data reaches its intended
destination. BPDU messages are exchanged across bridges to detect loops in a
network topology. These loops are then removed by shutting down selected bridge
interfaces and placing redundant switch ports in a backup, or blocked, state.
broadband remote A new type of access gateway for broadband networks. As a bridge between backbone
access server (BRAS) networks and broadband access networks, BRAS provides methods for fundamental
access and manages the broadband access network. It is deployed at the edge of
network to provide broadband access services, convergence, and forwarding of
multiple services, meeting the demands for transmission capacity and bandwidth
utilization of different users. BRAS is a core device for the broadband users' access to
a broadband network.
broadcast domain A group of network stations that receives broadcast packets originating from any
device within the group. The broadcast domain also refers to the set of ports between
which a device forwards a multicast, broadcast, or unknown destination frame.
building integrated In the situation of multiple synchronous nodes or communication devices, one can use
timing supply (BITS) a device to set up a clock system on the hinge of telecom network to connect the
synchronous network as a whole, and provide satisfactory synchronous base signals to
the building integrated device. This device is called BITS.
burst A process of forming data into a block of the proper size, uninterruptedly sending the
block in a fast operation, waiting for a long time, and preparing for the next fast
sending.
byte A unit of computer information equal to eight bits.
C
CAD See router.
CAR committed access rate
CBS See committed burst size.
CC See continuity check.
CCM continuity check message
CD chromatic dispersion
CDR See call detail record.
CE See customer edge.
CENELEC European Committee for Electrotechnical Standardization
CES See circuit emulation service.
CGMP Cisco Group Management Protocol
CIR committed information rate
CIST See Common and Internal Spanning Tree.
CLI command-line interface
CLNP connectionless network protocol
CMEP connection monitoring end point
CMI coded mark inversion
CNP connection-not-possible signal
CORBA See Common Object Request Broker Architecture.
COS chip operating system
CP cyclic prefix
CPLD complex programmable logic device
CPRI See common public radio interface.
CPU See central processing unit.
CR carriage return
CR-LDP Constraint-based Routed Label Distribution Protocol
CS class selector
coarse wavelength A signal transmission technology that multiplexes widely-spaced optical channels into
division multiplexing the same fiber. CWDM spaces wavelengths at a distance of several nm. CWDM does
(CWDM) not support optical amplifiers and is applied in short-distance chain networking.
comma separated A CSV file is a text file that stores data, generally used as an electronic table or by the
values (CSV) database software.
committed burst size A parameter used to define the capacity of token bucket C, that is, the maximum burst
(CBS) IP packet size when information is transferred at the committed information rate. This
parameter must be greater than 0 but should be not less than the maximum length of
an IP packet to be forwarded.
common public radio A common standard of the key internal interface between the REC and the RE of the
interface (CPRI) wireless base station. This standard was established by Huawei, Ericsson, NEC,
Siemens, and Nortel in June 2003. It aims at standardizing the baseband and RF
interface. The CPRI has a set of mature standards, which advance the standard and
equipment. The major feature of the CPRI is that baseband is separated from RF to
reduce the cost of engineering, equipment room, and equipment.
common spanning tree A single spanning tree that connects all the MST regions in a network. Every MST
(CST) region is considered as a switch; therefore, the CST can be considered as their
spanning tree generated with STP/RSTP.
composite service An aggregation of a series of services relevant to each other.
configuration data A command file defining hardware configurations of an NE. With this file, an NE can
collaborate with other NEs in a network. Therefore, configuration data is the key
factor that determines the operation of an entire network.
consistency check A function that is used to check the consistency of service data and resource data
between two softswitches that have the dual homing relation. This ensures the
consistency of service data and resource data between the softswitches.
continuity check (CC) An Ethernet connectivity fault management (CFM) method used to detect the
connectivity between MEPs by having each MEP periodically transmit a Continuity
Check Message (CCM).
control VLAN A VLAN that transmits only protocol packets.
crossover cable A twisted pair patch cable wired in such a way as to route the transmit signals from
one piece of equipment to the receive signals of another piece of equipment, and vice
versa.
customer edge (CE) A part of the BGP/MPLS IP VPN model that provides interfaces for directly
connecting to the Service Provider (SP) network. A CE can be a router, switch, or
host.
D
DAPI destination access point identifier
DB database
DBPS distributed board protect system
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 ground) (DC-C) with 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
ground) (DC-I) with 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.
DCE See data circuit-terminating equipment.
DCF See dispersion compensation fiber.
DCM See dispersion compensation module.
DCN See data communication network.
DDF digital distribution frame
DEI device emulation interrupt
DHCP See Dynamic Host Configuration Protocol.
DIP switch dual in-line package switch
DLAG See distributed link aggregation group.
DM See delay measurement.
DMUX demultiplexer
DPSK differential phase shift keying
DRDB dynamic random database
DRZ differential phase return to zero
DS See Data source.
DS node A DS-compliant node, which is subdivided into DS boundary node and ID interior
node.
DSCP See differentiated services code point.
DSCR dispersion slope compensation rate
DSE dispersion slope equalizer
DSF See distributed service framework.
DSLAM See digital subscriber line access multiplexer.
DSP See digital signal processor.
DSS door status switch
DTE See data terminal equipment.
DTMF See dual tone multiple frequency.
DVB digital video broadcasting
DVB-ASI digital video broadcast-asynchronous serial interface
DVMRP See Distance Vector Multicast Routing Protocol.
DWDM See dense wavelength division multiplexing.
Data source (DS) A system, database (database user; database instance), or file that can make BOs
persistent.
DiffServ See differentiated service.
Distance Vector An Internet gateway protocol based primarily on the RIP. The DVMRP protocol
Multicast Routing implements a typical dense mode IP multicast solution and uses IGMP to exchange
Protocol (DVMRP) routing datagrams with its neighbors.
DoS denial of service
Dynamic Host A client-server networking protocol. A DHCP server provides configuration
Configuration Protocol parameters specific to the DHCP client host requesting information the host requires
(DHCP) to participate on the Internet network. DHCP also provides a mechanism for allocating
IP addresses to hosts.
data circuit- The equipment that provides the signal conversion and coding between the data
terminating equipment terminal equipment (DTE) and the line. A DCE is located at a data station. The DCE
(DCE) may be separate equipment, or an integral part of the DTE or intermediate equipment.
The DCE may perform other functions that are normally performed at the network end
of the line.
data communication A communication network used in a TMN or between TMNs to support the data
network (DCN) communication function.
data terminal A user device composing the UNI. The DTE accesses the data network through the
equipment (DTE) DCE equipment (for example, a modem) and usually uses the clock signals produced
by DCE.
delay measurement The time elapsed since the start of transmission of the first bit of the frame by a source
(DM) node until the reception of the last bit of the loopbacked frame by the same source
node, when the loopback is performed at the frame's destination node.
dense wavelength The technology that utilizes the characteristics of broad bandwidth and low
division multiplexing attenuation of single mode optical fiber, employs multiple wavelengths with specific
(DWDM) frequency spacing as carriers, and allows multiple channels to transmit simultaneously
in the same fiber.
designated switch A designated switch of a device is a switch that is directly connected to the device and
forwards BPDUs to the device.
detection sensitivity The capability for a detector to respond to an exception.
differentiated service An IETF standard that defines a mechanism for controlling and forwarding traffic in a
(DiffServ) differentiated manner based on CoS settings to handle network congestion.
differentiated services According to the QoS classification standard of the Differentiated Service (Diff-Serv),
code point (DSCP) the type of services (ToS) field in the IP header consists of six most significant bits
and two currently unused bits, which are used to form codes for priority marking.
Differentiated services code point (DSCP) is the six most important bits in the ToS. It
is the combination of IP precedence and types of service. The DSCP value is used to
ensure that routers supporting only IP precedence can be used because the DSCP
value is compatible with IP precedence. Each DSCP maps a per-hop behavior (PHB).
Therefore, terminal devices can identify traffic using the DSCP value.
digital signal processor A microprocessor designed specifically for digital signal processing, generally in real
(DSP) time.
digital subscriber line A network device, usually situated in the main office of a telephone company, that
access multiplexer receives signals from multiple customer Digital Subscriber Line (DSL) connections
(DSLAM) and uses multiplexing techniques to put these signals on a high-speed backbone line.
dispersion A type of fiber that uses negative dispersion to compensate for the positive dispersion
compensation fiber of the transmitting fiber to maintain the original shape of the signal pulse.
(DCF)
dispersion A type of module that contains dispersion compensation fibers to compensate for the
compensation module dispersion of the transmitting fiber.
(DCM)
distributed link A board-level port protection technology that detects unidirectional fiber cuts and
aggregation group negotiates with the opposite port. In the case of a link down failure on a port or
(DLAG) hardware failure on a board, services are automatically switched to the slave board,
thereby achieving 1+1 protection for the inter-board ports.
distributed service A distributed service development and running framework, in which services comply
framework (DSF) with standard specifications, and can be loaded and run by containers. This framework
provides a range of services including registration, detection, routing, and distributed
access.
dotted decimal A format of IP address. IP addresses in this format are separated into four parts by a
notation dot "." with each part is in the decimal numeral.
downlink traffic The network traffic transferred into an internal carrier network. Noticeably, downlink
refers to sending traffic to user-end link nodes.
downstream In an access network, the direction of transmission toward the subscriber end of the
link. A direction of message forwarding within a transaction that refers to the direction
that requests flow from the user agent client to user agent server.
dual feed and selective A channel used to transmit monitoring data on an optical transmission network. The
receiving monitoring data is transmitted on the data communications channel as part of the
overhead of the service signal.
dual tone multiple Multi-frequency signaling technology for telephone systems. According to this
frequency (DTMF) technology, standard set combinations of two specific voice band frequencies, one
from a group of four low frequencies and the other from a group of four high
frequencies, are used.
E
E-LAN See Ethernet local area network.
E-Line See Ethernet line.
E1 An European standard for high-speed data transmission at 2.048 Mbit/s. It provides
thirty-two 64 kbit/s channels. A time division multiplexing frame is divided in to 32
timeslots numbered from 0 to 31. Timeslot 0 is reserved for frame synchronization,
and timeslot 16 is reserved for signaling transmission. The rest 30 timeslots are use as
speech channels. Each timeslot sends or receives an 8-bit data per second. Each frame
sends or receives 256-bit data per second. 8000 frames will be sent or received per
second. Therefore the line data rate is 2.048 Mbit/s.
EAPE enhanced automatic power pre-equilibrium
EBS See excess burst size.
ECC See embedded control channel.
Ethernet private line A type of Ethernet service provided by SDH, PDH, ATM, or MPLS server layer
(EPL) networks. This service is carried over dedicated bandwidth between point-to-point
connections.
Ethernet virtual A type of Ethernet service provided by SDH, PDH, ATM, or MPLS server layer
private LAN service networks. This service is carried over shared bandwidth between multipoint-to-
(EVPLAN) multipoint connections.
Ethernet virtual A type of Ethernet service provided by SDH, PDH, ATM, or MPLS server layer
private line (EVPL) networks. This service is carried over shared bandwidth between point-to-point
connections.
European ETSI is a multinational standardization body with regulatory and standardization
Telecommunications authority over much of Europe. GSM standardization took place under the auspices of
Standards Institute ETSI.
(ETSI)
eDQPSK enhanced differential quadrature phase shift keying
eSFP enhanced small form-factor pluggable
egress The egress LER. The group is transferred along the LSP consisting of a series of LSRs
after the group is labeled.
electric supervisory A technology that implements communication among all the nodes and transmission
channel (ESC) of monitoring data in an optical transmission network. The monitoring data of ESC is
introduced into DCC service overhead and is transmitted with service signals.
electrically erasable A type of EPROM that can be erased with an electrical signal. It is useful for stable
programmable read- storage for long periods without electricity while still allowing reprograming.
only memory EEPROMs contain less memory than RAM, take longer to reprogram, and can be
(EEPROM) reprogramed only a limited number of times before wearing out.
electromagnetic A condition which prevails when telecommunications equipment is performing its
compatibility (EMC) 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.
embedded control A logical channel that uses a data communications channel (DCC) as its physical layer
channel (ECC) to enable the transmission of operation, administration, and maintenance (OAM)
information between NEs.
encapsulation A technology for layered protocols, in which a lower-level protocol accepts a message
from a higher-level protocol and places it in the data portion of the lower-level frame.
Protocol A's packets have complete header information, and are carried by protocol B
as data. Packets that encapsulate protocol A have a B header, an A header, followed by
the information that protocol A is carrying. Note that A could equal to B, as in IP
inside IP.
enterprise system A path protocol that connects the host to various control units in a storage system.
connection (ESCON) Enterprise system connection is a serial bit stream transmission protocol that operates
a rate of 200 Mbit/s.
erasable A logic array device which can be used to implement the required functions by
programmable logic programming the array. In addition, a user can modify and program the array
device (EPLD) repeatedly until the program meets the requirement.
erbium-doped fiber An optical device that amplifies optical signals. This device uses a short optical fiber
amplifier (EDFA) doped with the rare-earth element, Erbium. The signal to be amplified and a pump
laser are multiplexed into the doped fiber, and the signal is amplified by interacting
with doping ions. When the amplifier passes an external light source pump, it
amplifies the optical signals in a specific wavelength range.
excess burst size (EBS) A parameter related to traffic. In the single rate three color marker (srTCM) mode,
traffic control is achieved by token buckets C and E. The excess burst size parameter
defines 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 greater than 0 but should be not less than the maximum length of an IP packet to be
forwarded.
excess information rate The bandwidth for excessive or burst traffic above the CIR; it equals the result of the
(EIR) actual transmission rate without the safety rate.
expedited forwarding The highest order QoS in the Diff-Serv network. EF PHB is suitable for services that
(EF) 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".
experimental bits A field in the MPLS packet header, three bits long. This field is always used to
(EXP) identify the CoS of the MPLS packet.
eye pattern An oscilloscope display in which a digital data signal from a receiver is repetitively
sampled and applied to the vertical input, while the data rate is used to trigger the
horizontal sweep. It is so called because, for several types of coding, the pattern looks
like a series of eyes between a pair of rails.
F
FBG fiber Bragg grating
FC See Fibre Channel.
FDB flash database
FDD See frequency division duplex.
FDDI See fiber distributed data interface.
FDI See forward defect indication.
FDV See frame delay variation.
FE fast Ethernet
FEC See forward error correction.
FICON See Fibre Connect.
FIFO See first in first out.
FLR See frame loss ratio.
FMC See fixed mobile convergence.
FMT See fiber management tray.
FOA fixed optical attenuator
FOADM fixed optical add/drop multiplexer
forward error A bit error correction technology that adds correction information to the payload at the
correction (FEC) transmit end. Based on the correction information, the bit errors generated during
transmission can be corrected at the receive end.
frame delay variation A measurement of the variations in the frame delay between a pair of service frames,
(FDV) where the service frames belong to the same CoS instance on a point to point ETH
connection.
frame loss ratio (FLR) A ratio, is expressed as a percentage, of the number of service frames not delivered
divided by the total number of service frames during time interval T, where the
number of service frames not delivered is the difference between the number of
service frames arriving at the ingress ETH flow point and the number of service
frames delivered at the egress ETH flow point in a point-to-point ETH connection.
frame relay (FR) A packet-switching protocol used for WANs. Frame relay transmits variable-length
packets at up to 2 Mbit/s over predetermined, set paths known as PVCs (permanent
virtual circuits). It is a variant of X.25 but sacrifices X.25's error detection for the sake
of speed.
frequency division An application in which channels are divided by frequency. In an FDD system, the
duplex (FDD) uplink and downlink use different frequencies. Downlink data is sent through bursts.
Both uplink and downlink transmission use frames with fixed time length.
G
G-ACH generic associated channel header
GAL generic associated channel header label
GCC general communication channel
GE Gigabit Ethernet
GE ADM A technique that improves the transmission of GE services on a metropolitan area
network. Using this technique, equipment configured with a high-speed backplane can
separately transmit, aggregate, or divert GE services over electrical-layer wavelengths
or sub-wavelengths. This achieves cross-connections of wavelengths and end-to-end
management of sub-wavelengths over a single device. GE ADM enables GE
convergence and cross-connections at the same time, thereby ensuring that network
resources are used effectively.
GFF gain flattening filter
GFP See Generic Framing Procedure.
GMPLS generalized multiprotocol label switching
GNE See gateway network element.
GPON gigabit-capable passive optical network
GPS See Global Positioning System.
GSM See Global system for mobile communications.
GSSP General Snooping and Selection Protocol
GTS See generic traffic shaping.
GUI graphical user interface
Generic Framing A framing and encapsulated method that can be applied to any data type. GFP is
Procedure (GFP) defined by ITU-T G.7041.
Global Positioning A global navigation satellite system that provides reliable positioning, navigation, and
System (GPS) timing services to users worldwide.
Global system for The second-generation mobile networking standard defined by the European
mobile Telecommunications Standards Institute (ETSI). It is aimed at designing a standard for
communications global mobile phone networks. GSM consists of three main parts: mobile switching
(GSM) subsystem (MSS), base station subsystem (BSS), and mobile station (MS).
gateway IP address The IP address of a gateway. A gateway is a node that forwards packets between
networks. Packets are sent to the gateway IP address when the destination network
address resides in a different network to the sender.
gateway network An NE that serves as a gateway for other NEs to communicate with a network
element (GNE) management system.
generic traffic shaping A traffic control measure that proactively adjusts the output speed of the traffic. This
(GTS) is to adapt the traffic to network resources that can be provided by the downstream
router to avoid packet discarding and congestion.
granularity The extent to which a system is broken down into small parts, either the system itself
or its description or observation. It is the extent to which a larger entity is subdivided.
If a system has more granularity for you to choose, that is, there are more granules in
the system for you to choose, then you can customize the system more flexibly.
H
HA system high availability system
HCS higher order connection supervision
HD-SDI high definition serial digital interface
HDB3 See High Density Bipolar of Order 3.
HDTV See high-definition television.
HP higher order path
HPT higher order path termination
HSDPA See High Speed Downlink Packet Access.
HSI high-speed Internet
HSL See high-level script language.
HTML Hypertext Markup Language
HUAWEI Electronic The software used to view, search for, and upgrade electronic documentation of
Document Explorer Huawei products. HedEx, pronounced as [hediks], has two editions, HedEx Lite and
(HedEx) HedEx Server.
HedEx See HUAWEI Electronic Document Explorer.
High Density Bipolar A code used for baseband transmissions between telecommunications devices. The
of Order 3 (HDB3) HDB3 code has the following feature: high capability of clock extraction, no direct
current component, error-checking capability, and a maximum of three consecutive
zeros.
High Speed Downlink A modulating-demodulating algorithm put forward in 3GPP R5 to meet the
Packet Access requirement for asymmetric uplink and downlink transmission of data services. It
(HSDPA) enables the maximum downlink data service rate to reach 14.4 Mbit/s without
changing the WCDMA network topology.
high-definition High-definition television (HDTV) is a television system providing an image
television (HDTV) resolution that is substantially higher than that of standard-definition television.
HDTV may be transmitted in various formats: 1080p: 1920×1080p: 2,073,600 pixels
(~2.07 megapixels) per frame 1080i: 1920×1080i: 1,036,800 pixels (~1.04 MP) per
field or 2,073,600 pixels (~2.07 MP) per frame Some countries also use a non-
standard CEA resolution, such as 1440×1080i: 777,600 pixels (~0.78 MP) per field or
1,555,200 pixels (~1.56 MP) per frame 720p: 1280×720p: 921,600 pixels (~0.92 MP)
per frame The letter "p" here stands for progressive scan, while "i" indicates
interlaced.
high-level script A script language. Based on python, the HSL syntax is simple, clear, and extendable.
language (HSL)
I
IANA See Internet Assigned Numbers Authority.
IC See integrated circuit.
ICMP See Internet Control Message Protocol.
IEC International Electrotechnical Commission
IEEE See Institute of Electrical and Electronics Engineers.
IETF Internet Engineering Task Force
IF See intermediate frequency.
IGMP See Internet Group Management Protocol.
IGRP Interior Gateway Routing Protocol
ILM incoming label map
IM See instant messaging.
IMP Instant Message Platform
IP Internet Protocol
IP address A 32-bit (4-byte) binary number that uniquely identifies a host connected to the
Internet. An IP address is expressed in dotted decimal notation, consisting of the
decimal values of its 4 bytes, separated with periods; for example, 127.0.0.1. The first
three bytes of the IP address identify the network to which the host is connected, and
the last byte identifies the host itself.
IP subnet A special submap used to identify an IP network segment. It is displayed as the
submap icon in the topological view.
IPA See intelligent power adjustment.
IPTV See Internet Protocol television.
IPv4 See Internet Protocol version 4.
IPv6 See Internet Protocol version 6.
instant messaging (IM) A form of real-time communication between two or more people based on typed text.
The text is conveyed via devices connected over a network such as the Internet.
integrated circuit (IC) A combination of inseparable associated circuit elements that are formed in place and
interconnected on or within a single base material to perform a microcircuit function.
intelligent power A technology that reduces the optical power of all the amplifiers in an adjacent
adjustment (IPA) regeneration section in the upstream to a safe level if the system detects the loss of
optical signals on the link. IPA helps ensure that maintenance engineers are not injured
by the laser escaping from a broken fiber or a connector that is not plugged in
properly.
intermediate frequency The transitional frequency between the frequencies of a modulated signal and an RF
(IF) signal.
J
jitter The measure of short waveform variations caused by vibration, voltage fluctuations,
and control system instability.
L
L2VPN Layer 2 virtual private network
L3VPN Layer 3 virtual private network
LACP See Link Aggregation Control Protocol.
LACPDU Link Aggregation Control Protocol data unit
LAG See link aggregation group.
LAN See local area network.
LAPS Link Access Protocol-SDH
LAS line assurance system
LB See loopback.
LBM See loopback message.
LBR See loopback reply.
LC Lucent connector
LCAS See link capacity adjustment scheme.
LCK See Locked signal function.
LCT local craft terminal
LER See label edge router.
LHP long hop
LLC See logical link control.
LLID local loopback ID
LM See loss measurement.
LMP link management protocol
LOP loss of pointer
linktrace reply (LTR) For 802.1ag MAC Trace, the destination MEP replies with a response message to the
source MEP after the destination MEP receives the LTM, and the response message is
called LTR. LTR also includes the TTL that equals the result of the TTL of LTM
minus 1.
local area network A network formed by the computers and workstations within the coverage of a few
(LAN) square kilometers or within a single building, featuring high speed and low error rate.
Current LANs are generally based on switched Ethernet or Wi-Fi technology and run
at 1,000 Mbit/s (that is, 1 Gbit/s).
logical link control According to the IEEE 802 family of standards, Logical Link Control (LLC) is the
(LLC) upper sublayer of the OSI data link layer. The LLC is the same for the various
physical media (such as Ethernet, token ring, WLAN).
loopback (LB) A troubleshooting technique that returns a transmitted signal to its source so that the
signal or message can be analyzed for errors. The loopback can be a inloop or outloop.
loopback message The loopback packet sent by the node that supports 802.2ag MAC Ping to the
(LBM) destination node. LBM message carries its own sending time.
loopback reply (LBR) A response message involved in the 802.1ag MAC Ping function, with which the
destination MEP replies to the source MEP after the destination MEP receives the
LBM. The LBR carries the sending time of LBM, the receiving time of LBM and the
sending time of LBR.
loss measurement A method used to collect counter values applicable for ingress and egress service
(LM) frames where the counters maintain a count of transmitted and received data frames
between a pair of MEPs.
loss of signal (LOS) No transitions occurring in the received signal.
M
MA maintenance association
MAC See Media Access Control.
MAC address A link layer address or physical address. It is six bytes long.
MAC address aging A function that deletes MAC address entries of a device when no packets are received
from this device within a specified time period.
MADM multiple add/drop multiplexer
MBB mobile broadband
MD See maintenance domain.
MD5 See message digest algorithm 5.
MDF See main distribution frame.
ME See maintenance entity.
MEG See maintenance entity group.
MEP maintenance association end point
MFAS See multiframe alignment signal.
MGC media gateway controller
MIB See management information base.
Media Access Control A protocol at the media access control sublayer. The protocol is at the lower part of
(MAC) 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.
Multicast Source A protocol that is applicable only to the PIM-SM domain and meaningful only for the
Discovery Protocol Any-Source Multicast (ASM) model. After the MSDP peer relationship is set up
(MSDP) between RPs of different PIM-SM domains, multicast source information can be
shared between PIM-SM domains, and the inter-domain multicast can be
implemented. After the MSDP peer relationship is set up between RPs of the same
PIM-SM domain, multicast source information can be shared in the PIM-SM domain,
and anycast RP can be implemented.
Multiple Spanning A protocol that can be used in a loop network. Using an algorithm, the MSTP blocks
Tree Protocol (MSTP) 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.
Multiple Spanning A region that consists of switches that support the MSTP in the LAN and links among
Tree region (MST them. Switches physically and directly connected and configured with the same MST
region) region attributes belong to the same MST region.
Multiprotocol Label A technology that uses short tags of fixed length to encapsulate packets in different
Switching (MPLS) link layers, and provides connection-oriented switching for the network layer on the
basis of IP routing and control protocols.
main distribution A device at a central office, on which all local loops are terminated.
frame (MDF)
maintenance domain The network or the part of the network for which connectivity is managed by
(MD) connectivity fault management (CFM). The devices in a maintenance domain are
managed by a single Internet service provider (ISP).
maintenance entity An ME consists of a pair of maintenance entity group end points (MEPs), two ends of
(ME) a transport trail, and maintenance association intermediate points (MIPs) on the trail.
maintenance entity A MEG consists of MEs that meet the following criteria: 1. Exist within the same
group (MEG) management edges. 2. Have the same MEG hierarchy. 3. Belong to the same P2P or
P2MP connection.
maintenance entity An intermediate point in a MEG, which is able to forward OAM packets and respond
group intermediate to some OAM packets, but unable to initiate the transmission of OAM packets or
point (MIP) perform any operations on network connections.
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
(MIB) as routers and switches) in a network.
maximum The largest packet of data that can be transmitted on a network. MTU size varies,
transmission unit depending on the network—576 bytes on X.25 networks, for example, 1500 bytes on
(MTU) Ethernet, and 17,914 bytes on 16 Mbit/s 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.
measurement result Percentage of the number of the actually reported measurement results to the number
integrity (MRI) of the measurement results that should be reported.
message digest A hash function that is used in a variety of security applications to check message
algorithm 5 (MD5) integrity. MD5 processes a variable-length message into a fixed-length output of 128
bits. It breaks up an input message into 512-bit blocks (sixteen 32-bit little-endian
integers). After a series of processing, the output consists of four 32-bit words, which
are then cascaded into a 128-bit hash number.
method of procedure A document that describes the process of executing a specific task. It facilitates the
(MOP) mutual understanding of and cooperation between a service provider and a carrier.
Before executing a task, the representatives from both parties confirm this document
and reach an agreement on it. This document describes who, when, where, why, and
how to execute a task and what to do.
mobile network A company that has a network infrastructure, sells large network capacities, and
operator (MNO) provides transparent network channels.
multi-segment pseudo A collection of multiple adjacent PW segments. Each PW segment is a point-to-point
wire (MS-PW) PW. The use of MS-PWs to bear services saves tunnel resources and can transport
services over different networks.
multicast A process of transmitting data packets 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.
multicast listener A protocol used by an IPv6 router to discover the multicast listeners on their directly
discovery (MLD) connected network segments, and to set up and maintain member relationships. On
IPv6 networks, after MLD is configured on the receiver hosts and the multicast router
to which the hosts are directly connected, the hosts can dynamically join related
groups and the multicast router can manage members on the local network.
multiframe alignment A distinctive signal inserted into every multiframe or once into every n multiframes,
signal (MFAS) always occupying the same relative position within the multiframe, and used to
establish and maintain multiframe alignment.
multiple spanning tree A type of spanning trees calculated by MSTP within an MST Region, to provide a
instance (MSTI) simply and fully connected active topology for frames classified as belonging to a
VLAN that is mapped to the MSTI by the MST Configuration. A VLAN cannot be
assigned to multiple MSTIs.
multiplex section An all-ONES characteristic or adapted information signal. It's generated to replace the
alarm indication signal normal traffic signal when it signal contains a defect condition in order to prevent
(MS-AIS) consequential downstream failures being declared or alarms being raised. AIS can be
identified as multiplex section alarm indication signal.
multiplex section A function, which is performed to provide capability for switching a signal between
protection (MSP) and including two multiplex section termination (MST) functions, from a "working" to
a "protection" channel.
multiplex section A function that generates the multiplex section overhead (MSOH) during the
termination (MST) formation of an SDH frame signal and that terminates the MSOH in the reverse
direction.
multiplexer (MUX) Equipment that combines a number of tributary channels onto a fewer number of
aggregate bearer channels, the relationship between the tributary and aggregate
channels being fixed.
multiplexing A procedure by which multiple lower order path layer signals are adapted into a higher
order path or the multiple higher order path layer signals are adapted into a multiplex
section.
multiprotocol label An Internet Protocol (IP) virtual private network (VPN) based on the multiprotocol
switching virtual label switching (MPLS) technology. It applies the MPLS technology for network
private network routers and switches, simplifies the routing mode of core routers, and combines
(MPLS VPN) traditional routing technology and label switching technology. It can be used to
construct the broadband Intranet and Extranet to meet various service requirements.
N
NAS network access server
NBI See northbound interface.
NDF new data flag
NE network element
NE Explorer The main operation interface of the NMS, which is used to manage the
telecommunication equipment. In the NE Explorer, a user can query, manage, and
maintain NEs, boards, and ports.
NE ID An ID that indicates a managed device in the network. In the network, each NE has a
unique NE ID.
NE Panel A graphical user interface, of the network management system, which displays
subracks, boards, and ports on an NE. On the NE Panel, the user can complete most of
the configuration, management and maintenance functions for an NE.
NHLFE next hop label forwarding entry
NM network management
NMC network management center
NNI network-to-network interface
NOC network operations center
NOS network operating system
NP See network processor.
NPE network provider edge
NRZ non-return to zero
NRZ code non-return-to-zero code
NS network system
NSAP See network service access point.
NTP Network Time Protocol
network layer Layer 3 of the seven-layer OSI model of computer networking. The network layer
provides routing and addressing so that two terminal systems are interconnected. In
addition, the network layer provides congestion control and traffic control. In the
TCP/IP protocol suite, the functions of the network layer are specified and
implemented by IP protocols. Therefore, the network layer is also called IP layer.
network processor An integrated circuit which has a feature set specifically targeted at the networking
(NP) application domain. Network Processors are typically software programmable devices
and would have generic characteristics similar to general purpose CPUs that are
commonly used in many different types of equipment and products.
network segment Part of a network on which all message traffic is common to all nodes; that is, a
message broadcast from one node on the segment is received by all other nodes on the
segment.
network service access A network address defined by ISO, at which the OSI Network Service is made
point (NSAP) available to a Network service user by the Network service provider.
network storm A phenomenon that occurs during data communication. To be specific, mass broadcast
packets are transmitted in a short time; the network is congested; transmission quality
and availability of the network decrease rapidly. The network storm is caused by
network connection or configuration problems.
noise figure A measure of degradation of the signal-to-noise ratio (SNR), caused by components in
a radio frequency (RF) signal chain. The noise figure is defined as the ratio of the
output noise power of a device to the portion thereof attributable to thermal noise in
the input termination at standard noise temperature T0 (usually 290 K). The noise
figure is thus the ratio of actual output noise to that which would remain if the device
itself did not introduce noise. It is a number by which the performance of a radio
receiver can be specified.
non-GNE See non-gateway network element.
non-gateway network A network element that communicates with the NM application layer through the
element (non-GNE) gateway NE application layer.
northbound interface An interface that connects to the upper-layer device to provision services and report
(NBI) alarms and performance statistics.
O
O&M operation and maintenance
OA optical amplifier
OADM See optical add/drop multiplexer.
OAM See operation, administration and maintenance.
OAMPDU operation, administration and maintenance protocol data unit
OAMS Optical fiber line Automatic Monitoring System
OC ordinary clock
OCI open connection indication
OCP optical channel protection
OCS optical core switching
OCh optical channel with full functionality
OD optical demultiplexing
ODB optical duobinary
ODF optical distribution frame
ODUk optical channel data unit - k
OEQ optical equalizer
OFC optical fiber communication conference and exhibit
OIF See Optical Internetworking Forum.
OLP See optical line protection.
OM optical multiplexing
OMS optical multiplexing section
OMU optical multiplexer unit
ONE See optical network element.
ONT See optical network terminal.
ONU See optical network unit.
OOS out of service
OPEX operating expense
OPS optical physical section
OPU See optical channel payload unit.
OPUk optical channel payload unit - k
ORT See operation response time.
OSC See optical supervisory channel.
OSI reference model See Open Systems Interconnection reference model.
OSN optical switch node
OSNR See optical signal-to-noise ratio.
OSPF See Open Shortest Path First.
OSS operations support system
OTDR See optical time domain reflectometer.
OTN optical transport network
OTS See optical transmission section.
OTU See optical transponder unit.
OTUk optical channel transport unit - k
OUI organizationally unique identifier
OWSP optical wavelength shared protection
Open Shortest Path A link-state, hierarchical interior gateway protocol (IGP) for network routing that uses
First (OSPF) 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 An open network architecture model developed by the International Organization for
Interconnection Standardization (ISO) and the ITU-T. This module consists of 7 layers. Each layer has
reference model (OSI special network functions, such as addressing, flow control, error control,
reference model) encapsulation, and reliable message transmission. The lowest layer (physical layer) is
closest to media technologies. The lower two layers are implemented in hardware and
software, and the upper five layers are implemented only in software. The highest
layer (application layer) is closest to users. The OSI reference model is a widely used
method of understanding network functions.
Optical A worldwide non-profit organization with membership open to any organization
Internetworking interested in shaping the future of optical internetworking.
Forum (OIF)
operation response The average time taken by a storage device to respond to each request. It is a critical
time (ORT) storage performance indicator.
operation, A set of network management functions that cover fault detection, notification,
administration and location, and repair.
maintenance (OAM)
optical add/drop A device that can be used to add the optical signals of various wavelengths to one
multiplexer (OADM) channel and drop the optical signals of various wavelengths from one channel.
optical attenuator A passive device that increases the attenuation in a fiber link. An optical attenuator is
used to ensure that the optical power of a signal at the receive end is not excessively
high.
optical channel A protection architecture that allows one wavelength to provide protection for
payload unit (OPU) multiple services between different stations, saving wavelength resources and
lowering costs.
optical line protection Optical line protection is implemented using the dual feeding and selective receiving
(OLP) function. Two pairs of fibers (that is, four fibers) are used. One pair of fibers function
as the working trail and is used to transmit service signals of a line when the line is
normal. The other pair of fibers function as the protection trail and is used to carry
protection switching signals when a fiber cut occurs or the signal attenuation is
excessively large.
optical network A transport entity that implements the NE functions (terminal multiplexing, add/drop
element (ONE) multiplexing, cross-connection and regeneration) in a DWDM layer network. The
types of ONEs include OTM, OADM, OLA, REG and OXC.
optical network A device that terminates the fiber optical network at the customer premises.
terminal (ONT)
optical network unit A form of Access Node that converts optical signals transmitted via fiber to electrical
(ONU) signals that can be transmitted via coaxial cable or twisted pair copper wiring to
individual subscribers.
optical signal-to-noise The ratio of signal power to noise power in a transmission link. OSNR is the most
ratio (OSNR) important index for measuring the performance of a DWDM system.
optical supervisory A technology that uses specific optical wavelengths to realize communication among
channel (OSC) nodes in optical transmission network and transmit the monitoring data in a certain
channel.
optical time domain A device that sends a series of short pulses of light down a fiber-optic cable and
reflectometer (OTDR) measures the strength of the return pulses. An OTDR is used to measure fiber length
and light loss, and to locate fiber faults.
optical transmission A section in the logical structure of an optical transport network (OTN). The OTS
section (OTS) allows the network operator to perform monitoring and maintenance tasks between
NEs.
optical transponder A device or subsystem that converts accessed client signals into a G.694.1/G.694.2-
unit (OTU) compliant WDM wavelength.
orderwire A channel that provides voice communication between operation engineers or
maintenance engineers of different stations.
P
P2MP point-to-multipoint
P2P See point-to-point service.
PCB See printed circuit board.
PCC protection communication channel
PCS physical coding sublayer
PDG polarization-dependent gain
PDH See plesiochronous digital hierarchy.
PDL See polarization-dependent loss.
PDM pulse duration modulation
PDU See power distribution unit.
PE See provider edge.
PER packet error rate
PET polyester
PFI packet forward interface
PGA program global area
PHB See per-hop behavior.
PID photonics integrated device
PIM-DM Protocol Independent Multicast - Dense Mode
PIM-SM Protocol Independent Multicast - Sparse Mode
PLC See packet loss compensation.
PLL See phase-locked loop.
PM performance monitoring
PMD polarization mode dispersion
PMI payload missing indication
PMS Product Management System
PMU power monitoring unit
PON passive optical network
POS See packet over SDH/SONET.
per-hop behavior IETF Diff-Serv workgroup defines forwarding behaviors of network nodes as per-hop
(PHB) 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).
performance threshold A limit for generating an alarm for a selected entity. When the measurement result
reaches or exceeds the preset alarm threshold, the performance management system
generates a performance alarm.
permanent virtual Virtual path that consists of PVCs.
path (PVP)
phase-locked loop A circuit that consists essentially of a phase detector that compares the frequency of a
(PLL) voltage-controlled oscillator with that of an incoming carrier signal or reference-
frequency generator. The output of the phase detector, after passing through a loop
filter, is fed back to the voltage-controlled oscillator to keep it exactly in phase with
the incoming or reference frequency.
ping A method used to test whether a device in the IP network is reachable according to the
sent ICMP Echo messages and received response messages.
plain old telephone The basic telephone service provided through the traditional cabling such as twisted
service (POTS) pair cables.
plesiochronous digital A multiplexing scheme of bit stuffing and byte interleaving. It multiplexes the
hierarchy (PDH) minimum rate 64 kit/s into rates of 2 Mbit/s, 34 Mbit/s, 140 Mbit/s, and 565 Mbit/s.
point-to-point service A service between two terminal users. In P2P services, senders and recipients are
(P2P) terminal users.
pointer An indicator whose value defines the frame offset of a virtual container with respect to
the frame reference of the transport entity on which this pointer is supported.
polarization-dependent A measure of the peak-to-peak insertion loss or gain variation caused by a component
loss (PDL) when stimulated by all possible polarization states. PDL is specified in dB.
power distribution unit A unit that performs AC or DC power distribution.
(PDU)
printed circuit board A board used to mechanically support and electrically connect electronic components
(PCB) using conductive pathways, tracks, or traces, etched from copper sheets laminated
onto a non-conductive substrate.
private line A line, such as a subscriber cable and trunk cable, which are leased by the
telecommunication carrier and are used to meet the special user requirements.
protection path A path in a protection group that transports services when a fault occurs on the
working path.
provider edge (PE) A device that is located in the backbone network of the MPLS VPN structure. A PE is
responsible for managing VPN users, establishing LSPs between PEs, and exchanging
routing information between sites of the same VPN. 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 the sense that the value of each element is independent
sequence (PRBS) of the values of any of the other elements, similar to a real random sequence.
pseudo wire (PW) 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 An end-to-end Layer 2 transmission technology. It emulates the essential attributes of
edge-to-edge (PWE3) 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 multiplexing (TDM) circuit and SONET/SDH. The simulation approximates
to the real situation.
public switched A telecommunications network established to perform telephone services for the
telephone network public subscribers. Sometimes it is called POTS.
(PSTN)
Q
QPSK See quadrature phase shift keying.
QinQ See 802.1Q in 802.1Q.
QoS See quality of service.
quadrature phase shift A modulation method of data transmission through the conversion or modulation and
keying (QPSK) 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.
quality of service A commonly-used performance indicator of a telecommunication system or channel.
(QoS) Depending on the specific system and service, it may relate to jitter, delay, packet loss
ratio, bit error ratio, and signal-to-noise ratio. It functions to measure the quality of the
transmission system and the effectiveness of the services, as well as the capability of a
service provider to meet the demands of users.
R
RADIUS See Remote Authentication Dial In User Service.
RAN See radio access network.
RBW reverse-band working
RDI remote defect indication
RED See random early detection.
REG See regenerator.
RFC See Request For Comments.
RIP See Routing Information Protocol.
RJ45 registered jack45
RMEP remote maintenance association end point
RMON remote network monitoring
RMS resource management system
RMU rack monitoring unit
Routing Information A simple routing protocol that is part of the TCP/IP protocol suite. It determines a
Protocol (RIP) route based on the smallest hop count between the source and destination. RIP is a
distance vector protocol that routinely broadcasts routing information to its
neighboring routers and is known to waste bandwidth.
radio access network The network that provides the connection between CPEs and the CN. It isolates the
(RAN) CN from wireless network.
radio network A device in a radio network subsystem that is in charge of controlling the usage and
controller (RNC) integrity of radio resources.
random early detection A packet loss algorithm used in congestion avoidance. It discards the packet according
(RED) to the specified higher limit and lower limit of a queue so that global TCP
synchronization resulting from traditional tail drop can be prevented.
receiver sensitivity The minimum acceptable value of mean received power at point Rn (a reference point
at an input to a receiver optical connector) to achieve a 1x10-12 BER when the FEC is
enabled.
recognition Consumer awareness of having seen or heard an advertising message.
reference clock A stable and high-precision autonomous clock that provides frequencies as a reference
for other clocks.
regeneration The process of receiving and reconstructing a digital signal so that the amplitudes,
waveforms and timing of its signal elements are constrained within specified limits.
regenerator (REG) A piece of equipment or device that regenerates electrical signals.
regional root The root of the Internal Spanning Tree (IST) and Multiple Spanning Tree Instance
(MSTI) in the MST region. The regional root differs with the topology of the spanning
tree in the MST region.
remote optical A remote optical amplifier subsystem designed for applications where power supply
pumping amplifier and monitoring systems are unavailable. The ROPA subsystem is a power
(ROPA) compensation solution to the ultra-long distance long hop (LHP) transmission.
reservation An action that the charging module performs to freeze a subscriber's balance amount,
free resources, credits, or quotas before the subscriber uses services. This action
ensures that the subscriber has sufficient balance to pay for services.
ring network A network topology in which each node connects to exactly two other nodes, forming
a circular pathway for signals.
router (CAD) A device on the network layer that selects routes in the network. The router selects the
optimal route according to the destination address of the received packet through a
network and forwards the packet to the next router. The last router is responsible for
sending the packet to the destination host. Can be used to connect a LAN to a LAN, a
WAN to a WAN, or a LAN to the Internet.
S
S-VLAN service virtual local area network
Simple Network An IETF protocol for monitoring and managing systems and devices in a network.
Management Protocol The data being monitored and managed is defined by a MIB. The functions supported
(SNMP) by the protocol are the request and retrieval of data, the setting or writing of data, and
traps that signal the occurrence of events."
Synchronization Status A message that carries the quality levels of timing signals on a synchronous timing
Message (SSM) link. SSM messages provide upstream clock information to nodes on an SDH network
or synchronization network.
security object (SO) A main part of the information security. It is not related with the communication mode
or terminal. It does not only focus on the security of the information exchange but also
provides feasible solutions of security for the user information, including the user
identity authentication, user password, and encryption.
segment A subset of an identity type. This is a different subset from a trust level including but
is not limited to the following examples: A subset based on customer age, a subset
based on where the identity was registered or based, a subset based on the customer's
gender, and a subset based on an association that the identity may have. For example,
an organization is confirmed as a supermarket or a customer is a member of a society.
serial digital interface An interface that transmits data in a single channel in sequence.
(SDI)
service creation A service generation tool that provides a graphical user interface (GUI) for
environment (SCE) programming.
service support data An identifier that defines data parameters of specific service feature descriptions in the
(SSD) global functional plane.
shaping A process of delaying packets within a traffic stream to cause it to conform to specific
defined traffic profile.
shared risk group A group of resources that share a common risk component whose failure can cause the
(SRG) failure of all the resources in the group.
signal degrade (SD) A signal indicating that associated data has degraded in the sense that a degraded
defect condition is active.
signal fail (SF) A signal indicating that 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
(SNR) given point in time. SNR is expressed as 10 times the logarithm of the power ratio and
is usually expressed in dB.
single-mode fiber A type of optical fiber through which only one type of optical signal with a fixed wave
(SMF) length can travel at a time. The inner diameter of the single-mode fiber is less than 10
microns. This type of fiber can transmit data over a long distance.
single-pair high-speed A symmetric digital subscriber line technology developed from HDSL, SDSL, and
digital subscriber line HDSL2, which is defined in ITU-T G.991.2. The SHDSL port is connected to the user
(SHDSL) terminal through the plain telephone subscriber line and uses trellis coded pulse
amplitude modulation (TC-PAM) technology to transmit high-speed data and provide
the broadband access service.
split ratio The ratio of the number one to the number of optical signal channels that are split
from a channel of downstream optical signals in a GPON network. A larger split ratio
implies greater optical splitting which creates the need for an increased power budget
to support the physical reach.
standard definition- Standard definition video signal transported by serial digital interface.
serial digital interface
signal (SD-SDI)
storage area network A storage area network (SAN) is a dedicated network that provides access to
(SAN) consolidated, block level data storage. SANs are primarily used to make storage
devices, such as disk arrays, tape libraries, and optical jukeboxes, accessible to servers
so that the devices appear like locally attached devices to the operating system. A
SAN does not provide file abstraction, only block-level operations. However, file
systems built on top of SANs do provide file-level access, and are known as SAN
filesystems or shared disk file systems. An architecture to attach remote computer
storage devices such as disk array controllers, tape libraries and CD arrays to servers
in such a way that to the operating system the devices appear as locally attached
devices.An architecture to attach remote computer storage devices such as disk array
controllers, tape libraries and CD arrays to servers in such a way that to the operating
system the devices appear as locally attached devices.
structured query A programming language widely used for accessing, updating, managing, and
language (SQL) querying data in a relational database.
subnet mask The subnet mask is a binary pattern that is stored in the device and is matched with the
IP address. A subnet mask is used by the IP protocol to determine to which network
segment packets are destined.
synchronous digital A transmission scheme that follows ITU-T G.707, G.708, and G.709. SDH defines the
hierarchy (SDH) 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.
synchronous optical A high-speed network that provides a standard interface for communications carriers
network (SONET) to connect networks based on fiber optical cable. SONET is designed to handle
multiple data types (voice, video, and so on). It transmits at a base rate of 51.84
Mbit/s, but multiples of this base rate go as high as 2.488 Gbit/s.
synchronous transport An information structure used to support section layer connections in the SDH. It
module (STM) 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.
T
T1 A North American standard for high-speed data transmission at 1.544Mbps. It
provides 24 x 64 kbit/s channels.
TCM tandem connection monitor
TCN topology change notification
TCP See Transmission Control Protocol.
TCP/IP Transmission Control Protocol/Internet Protocol
TD-SCDMA See Time Division-Synchronous Code Division Multiple Access.
TDD time division duplex
telecommunications A protocol model defined by ITU-T for managing open systems in a communications
management network network. TMN manages the planning, provisioning, installation, and OAM of
(TMN) equipment, networks, and services.
terminal multiplexer A device used at a network terminal either to multiplex multiple channels of low rate
(TM) signals into one channel of high rate signals, or to demultiplex one channel of high
rate signals into multiple channels of low rate signals.
time division A multiplexing technology. TDM divides the sampling cycle of a channel into time
multiplexing (TDM) slots (TSn, n=0, 1, 2, 3…), and the sampling value codes of multiple signals engross
time slots in a certain order, forming multiple multiplexing digital signals to be
transmitted over one channel.
time to live (TTL) A specified period of time for best-effort delivery systems to prevent packets from
looping endlessly.
token bucket The token bucket is a container for tokens. The capacity of a token bucket is limited,
algorithm and the number of tokens determines the traffic rate of permitted packets. The token
bucket polices the traffic. Users place the tokens into the bucket regularly according to
the preset rate. If the tokens in the bucket exceed the capacity, no tokens can be put in.
Packets can be forwarded when the bucket has tokens, otherwise they cannot be
transferred till there are new tokens in the bucket. This scheme adjusts the rate of
packet input.
trTCM See two rate three color marker.
traffic classification A function that enables you to classify traffic into different classes with different
priorities according to some criteria. Each class of traffic has a specified QoS in the
entire network. In this way, different traffic packets can be treated differently.
traffic shaping A way of controlling the network traffic from a computer to optimize or guarantee the
performance and minimize the delay. It actively adjusts the output speed of traffic in
the scenario that the traffic matches network resources provided by the lower layer
devices, avoiding packet loss and congestion.
traffic statistics An activity of measuring and collecting statistics of various data on devices and
telecommunications networks. With the statistics, operators can be aware of the
operating status, signaling, users, system resource usage of the devices or networks.
The statistics also help the operators manage the device operating, locate problems,
monitor and maintain the networks, and plan the networks.
transparent mode A method of binary synchronous text transmission in which only transmission control
characters preceded by the data link escape (DLE) character are processed as
transmission control characters.
transparent A process during which the signaling protocol or data is not processed in the content
transmission but encapsulated in the format for the processing of the next phase.
trunk Physical communications line between two offices. It transports media signals such as
speech, data and video signals.
tunnel A channel on the packet switching network that transmits service traffic between PEs.
In VPN, a tunnel is an information transmission channel between two entities. The
tunnel ensures secure and transparent transmission of VPN information. In most cases,
a tunnel is an MPLS tunnel.
two rate three color An algorithm that meters an IP packet stream and marks its packets based on two
marker (trTCM) rates, Peak 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 does not exceed the CIR.
type-length-value An encoding type that features high efficiency and expansibility. It is also called
(TLV) Code-Length-Value (CLV). T indicates that different types can be defined through
different values. L indicates the total length of the value field. V indicates the actual
data of the TLV and is most important. TLV encoding features high expansibility. New
TLVs can be added to support new features, which is flexible in describing
information loaded in packets.
U
UDP See User datagram protocol.
UI User interface
UNI See user-to-network interface.
UPE user-end provider edge
UPI user payload identifier
UPM uninterruptible power module
UTC Coordinated Universal Time
User datagram An Internet protocol that provides connectionless datagram delivery service to
protocol (UDP) applications. UDP over IP adds the ability to address multiple endpoints within a
single network node."
upstream In an access network, the direction that is far from the subscriber end of the link. A
direction of message forwarding within a transaction that refers to the direction that
responses flow from the user agent server back to the user agent client.
upstream board A board that provides the upstream transmission function. Through an upstream
board, services can be transmitted upstream to the upper-layer device.
user-to-network The interface between user equipment and private or public network equipment (for
interface (UNI) example, ATM switches).
V
V-NNI virtual network-network interface
V-UNI See virtual user-network interface.
VA value assurance
VAS See value-added service.
VB virtual bridge
VBR See variable bit rate.
VC See virtual channel.
VC trunk See virtual container trunk.
VCC See virtual channel connection.
virtual channel (VC) Any logical connection in the ATM network. A VC is the basic unit of switching in
the ATM network and is uniquely identified by a virtual path identifier (VPI)/virtual
channel identifier (VCI) value. It is the channel on which ATM cells are transmitted
by a switch.
virtual channel A VC logical trail that carries data between two end points in an ATM network. A
connection (VCC) point-to-multipoint VCC is a set of ATM virtual connections between two or multiple
end points.
virtual circuit A channel or circuit established between two points on a data communications
network with packet switching. Virtual circuits can be permanent virtual circuits
(PVCs) or switched virtual circuits (SVCs) .
virtual concatenation A group of co-located member trail termination functions that are connected to the
group (VCG) same virtual concatenation link.
virtual connection A logical tunnel built in a non-backbone area between two ABRs in a same OSPF
routing domain. It is used to maintain the logical connections between physical
division areas. The two ends of the virtual connection must be ABRs. In addition, to
make a virtual connection effective, the ABRs must be configured at the same time.
The virtual connection is identified by the ID of the peer router.
virtual container trunk The logical path formed by some cascaded VCs.
(VC trunk)
virtual private wire A technology that bears Layer 2 services. VPWS emulates services such as ATM, FR,
service (VPWS) Ethernet, low-speed TDM circuit, and SONET/SDH in a PSN.
virtual switching An instance through which the physical access links of VPLS can be mapped to the
instance (VSI) virtual links. Each VSI provides independent VPLS service. VSI has Ethernet bridge
function and can terminate PW.
virtual user-network A virtual user-network interface, works as an action point to perform service
interface (V-UNI) classification and traffic control in HQoS.
W
WAN wide area network
WCDMA See Wideband Code Division Multiple Access.
WDM wavelength division multiplexing
WFQ See weighted fair queuing.
WLAN See wireless local area network.
WRR weighted round robin
WSS wavelength selective switching
WTR See wait to restore.
WXCP See wavelength cross-connection protection.
Web LCT The local maintenance terminal of a transport network, which is located at the NE
management layer of the transport network.
Wideband Code A standard defined by the ITU-T for the third-generation wireless technology derived
Division Multiple from the Code Division Multiple Access (CDMA) technology.
Access (WCDMA)
wait to restore (WTR) The number of minutes to wait before services are switched back to the working line.
wavelength cross- A type of channel protection based on ring network topology. WXCP employs the
connection protection dual feed and selective receiving principle and uses the cross-connection function to
(WXCP) implement service switching between the working and protection channels.
weighted fair queuing A fair queue scheduling algorithm based on bandwidth allocation weights. This
(WFQ) 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.
wireless local area A hybrid of the computer network and the wireless communication technology. It uses
network (WLAN) wireless multiple address channels as transmission media and carriers out data
interaction through electromagnetic wave to implement the functions of the traditional
LAN.
X
X.25 A data link layer protocol. It defines the communication in the Public Data Network
(PDN) between a host and a remote terminal.
xDSL x digital subscriber line