Osn 8800 Tom Toa Tha

Configuring WDM Services
(Manually by Station)
Contents
6.2 Configuring WDM Services (Manually by Station)
6.2.1 Basic Concepts
6.2.1.1 General Principles for Configuring Electrical Cross-Connections
6.2.1.1.1 Inter-board Electrical Cross-Connections
6.2.1.1.2 Intra-board Electrical Cross-Connections
6.2.1.2 Standard Mode and Compatible Mode
6.2.1.3 ODUflex
6.2.2 WDM Service Configuration Flow
6.2.3 Configuring WDM Services for OTU Boards Without Cross-Connect Capability
6.2.3.1 Configuration Networking Diagram
6.2.3.2 Service Signal Flow
6.2.3.3 Configuration Process
6.2.4 Configuring WDM Services for OTU Boards with Cross-Connect Capability
6.2.5 Configuring WDM Services for Tributary Boards and Line Boards
6.2.6 Configuring 10GE LAN Services by Using the TDX and NS2 Boards
6.2.7 Configuring 10GE LAN Services Through the TQX and NS3 Boards
6.2.8 Parameters
6.2.8.1 WDM Cross-Connection Configuration
6.2.8.2 WDM Timeslot Configuration
6.3 Manually Configuring Services Carried by the TOM Board by Station
6.3.1 Configuring the TN11TOM Board (Manually by Station)
6.3.1.1 Overview of the Working Modes
6.3.1.2 Scenario 1: ODU1 tributary mode (cascading)
6.3.1.3 Scenario 2: ODU1 tributary-line mode (cascading)
6.3.1.4 Scenario 3: ODU1 tributary mode (non-cascading)
6.3.1.5 Scenario 4: ODU1 tributary-line mode (non-cascading)
6.3.1.6 Scenario 5: ODU1 tributary-line mode (electrical regeneration board)
6.3.2 Configuring the TN52TOM Board (by Station)
6.3.2.2 Configuration Principles
6.3.2.3 Configuration Flow
6.3.2.4 Scenario 1: ODU0 mode (cascading)
6.3.2.8 Scenario 5: ODU0 mode (non-cascading)
6.3.2.10 Scenario 7: ODU1 mode (non-cascading)
6.3.2.11 Scenario 8: ODU1_ANY_ODU0_ODU1 re-encapsulation mode (non-cascading)
6.3.2.12 Scenario 9: ODU1_ANY_ODU0_ODU1 re-encapsulation tributary-line mode
(non-cascading)
6.3.2.14 Scenario 11: ODU1_ODU0 mode (non-cascading)
6.3.2.15 Scenario 12: ODU1_ANY_ODU0 re-encapsulation mode (non-cascading)
6.3.3 Multimedia Documentation: TN52TOM Board Configuration Guide
6.4 Configuring the THA/TOA Board (Manually by Station)
6.4.1 Overview of the Working Mode
6.4.2 Configuration Procedures
6.4.3 Scenario 1: ODU0 non-convergence mode (Any->ODU0)
6.4.4 Scenario 2: ODU1 non-convergence mode (Any->ODU1)
6.4.5 Scenario 3: ODU1 convergence mode (n*Any->ODU1)
6.4.6 Scenario 4: ODU1_ODU0 mode (OTU1->ODU1->ODU0)
6.4.7 Scenario 5: ODUflex non-convergence mode (Any->ODUflex)
6.2 Configuring WDM Services (Manually

by Station)
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 Concepts
The basic concepts involved in WDM service configuration include electrical cross-
connections, WDM service types, and board models. Understanding the basic concepts
helps you successfully configure services.
 WDM Service Configuration Flow

This section describes the configuration process of boards and services. Before
configuring WDM services according to the configuration flow, complete the basic
configuration of NEs according to the configuration flow of creating a network.
 Configuring WDM Services for OTU Boards Without Cross-Connect Capability

This section describes how to configure the 10GE LAN services by using the LDX
board, which is a type of OTU board that does not require cross-connection
configuration.
 Configuring WDM Services for OTU Boards with Cross-Connect Capability
This section describes how to configure GE services by using the LQMS board.
 Configuring WDM Services for Tributary Boards and Line Boards

This section describes how to configure GE services by using the TQM and NQ2
boards.
 Configuring 10GE LAN Services by Using the TDX and NS2 Boards
This section describes how to configure 10GE LAN services by using the TDX and
NS2 boards.
 Configuring 10GE LAN Services Through the TQX and NS3 Boards
This section describes how to configure 10GE LAN services through TN52TQX boards
and cross-connect ODU2 or ODU2e signals to TN54NS3 boards in one station. The
other station is configured exactly the same.
 Parameters
Describes the parameters involved in the WDM services configuration.
Parent topic: Configuration
6.2.1 Basic Concepts

The basic concepts involved in WDM service configuration include electrical cross-
connections, WDM service types, and board models. Understanding the basic concepts
helps you successfully configure services.
 General Principles for Configuring Electrical Cross-Connections

Electrical cross-connections include inter-board cross-connections (namely, cross-
connections between boards) and intra-board cross-connections (namely, cross-
connections inside a board). This topic describes the concepts, port types, configuration
principles, and applications of the two types of electrical cross-connections.
 Standard Mode and Compatible Mode

Starting from V100R006C01, some boards support new board models. To distinguish
new models from existing models, the new board models are marked as standard mode
and the existing board models are marked as compatible mode. For boards in standard
mode, only channels or physical ports are presented in the models and NMS, with
service mapping paths displayed for the channels or physical ports. All ODU layers are
allocated to the physical ports. When configuring cross-connections, users do not need
to know the internal ports on the boards. Compared with the compatible mode, the
standard mode makes operations easier and has fewer end-to-end trail layers, reducing
maintenance costs.
 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.
Parent topic: Configuring WDM Services (Manually by Station)
6.2.1.1 General Principles for Configuring

Electrical Cross-Connections
Electrical cross-connections include inter-board cross-connections (namely, cross-
connections between boards) and intra-board cross-connections (namely, cross-
connections inside a board). This topic describes the concepts, port types, configuration
principles, and applications of the two types of electrical cross-connections.
 Inter-board Electrical Cross-Connections

This topic describes the concept, port types, configuration principles, and two
applications of inter-board electrical cross-connections. In addition, this topic provides
an example of configuring inter-board electrical cross-connections using the U2000.
 Intra-board Electrical Cross-Connections

This topic describes the concept and port types of intra-board electrical cross-
connections. This topic provides a schematic diagram of intra-board cross-connections.
Parent topic: Basic Concepts
6.2.1.1.1 Inter-board Electrical Cross-

Connections
This topic describes the concept, port types, configuration principles, and two
applications of inter-board electrical cross-connections. In addition, this topic provides
an example of configuring inter-board electrical cross-connections using the U2000.
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.
Specifically, inter-board electrical cross-connections can be configured either between
OTN tributary and line boards (include PID boards) or between line boards (include
PID boards). The line boards include OTN line boards, universal line boards.
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:
 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.
 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
 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.
 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.
 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 in the figure.
 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 in the figure.
NOTE:
 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 Standard Mode and Compatible
Mode.
 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
 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 1illustrates 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 1 Adding/dropping of client-side services on the WDM side at sites A and C
 Local service pass-through on the WDM side

The cross-connect board cross-connects the ODUk services between OTN line
boards or universal line boards.
When a PID network interconnects with a non-PID network, only centralized
electrical cross-connections are supported. For the tangent node between the two
networks, cross-connections must be configured between the PID and OTN/universal
line boards so that the ODUk services can be sent from the PID network to the non-
PID network.
Figure 2illustrates how pass-through of a local service is achieved on the WDM side
in a non-PID network using the ODU0 cross-connections between the ND2
(standard) and ND2 (compatible) boards.
illustrates how pass-through of a local service is achieved on the WDM side
Figure 3
from the PID network to the non-PID network.
Figure 2 Local service pass-through on the WDM side at site B (non-PID network)
Figure 3 Local service pass-through on the WDM side (interconnection of PID network and
non-PID network)
Configuring Cross-Connections on the U2000

Figure 4shows the U2000 GUI for configuring cross-connections on the U2000. In the
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 4 GUI for configuring cross-connections (using the ODU0 cross-connection between
TOA and ND2 boards as an example)
NOTE:
Direction shown in the figure can be set to Unidirectional or Bidirectional.
 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.
 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.
Parent topic: General Principles for Configuring Electrical Cross-Connections

6.2.1.1.2 Intra-board Electrical Cross-
Connections
This topic describes the concept and port types of intra-board electrical cross-
connections. This topic provides a schematic diagram of intra-board cross-connections.
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:
 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
 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
 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.
 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 1illustrates 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.
Figure 1 Schematic diagram of intra-board cross-connection (multiple Any-rate services into
one ODU1 signal)
Intra-board cross-connections are configured on the U2000 in the same way as inter-
board cross-connections. For details, see Inter-board Electrical Cross-Connections.
Parent topic: General Principles for Configuring Electrical Cross-Connections
6.2.1.2 Standard Mode and Compatible

Mode
Starting from V100R006C01, some boards support new board models. To distinguish
new models from existing models, the new board models are marked as standard mode
and the existing board models are marked as compatible mode. For boards in standard
mode, only channels or physical ports are presented in the models and NMS, with
service mapping paths displayed for the channels or physical ports. All ODU layers are
allocated to the physical ports. When configuring cross-connections, users do not need
to know the internal ports on the boards. Compared with the compatible mode, the
standard mode makes operations easier and has fewer end-to-end trail layers, reducing
maintenance costs.
Boards Supporting the Standard Mode

Table 1 lists the boards that support standard mode, the names of the boards on the NMS.
Table 1 Board names displayed on the NMS
Name of Board in Standard Name of Board in Board Name (Displayed in

Mode (Displayed Only Compatible Mode the NE Panel)
When the Logical Board Is (Displayed Only When the
Added) Logical Board Is Added)
53TDX(STND) 53TDX 53TDX
54THA(STND) 54THA 54THA
54TOA(STND) 54TOA 54TOA
55TOX - 55TOX
55TQX(STND) 55TQX 55TQX
54TSC - 54TSC
54TSXL - 54TSXL
54TTX - 54TTX
52ND2(STND) 52ND2 52ND2
53ND2 53ND2(COMP) 53ND2
55NO2 - 55NO2
53NQ2 53NQ2(COMP) 53NQ2
52NS2(STND) 52NS2 52NS2
53NS2 53NS2(COMP) 53NS2
54NS3(STND) 54NS3 54NS3
55NS3 - 55NS3
Table 1 Board names displayed on the NMS
Name of Board in Standard Name of Board in Board Name (Displayed in

Mode (Displayed Only Compatible Mode the NE Panel)
When the Logical Board Is (Displayed Only When the
Added) Logical Board Is Added)
56NS3 - 56NS3
54NS4 - 54NS4
56NS4 - 56NS4
57NS4 - 57NS4
58NS4 - 58NS4
54NS4M - 54NS4M
54HUNQ2 - 54HUNQ2
54HUNS3 - 54HUNS3
54ENQ2(STND) 54ENQ2 54ENQ2
55NPO2(STND) 55NPO2 55NPO2
55NPO2E - 55NPO2E
The hyphen (-) indicates that the compatible mode is not supported.
When electrical-layer ASON is deployed, there are the following restrictions:

 Boards in standard mode cannot connect with those in compatible mode on the
WDM side. They can be interconnect only on the backplane side.
 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 1 shows the board model of the TN53NS2 board in standard mode.
Figure 1 Board model of the TN53NS2 board in standard mode
Cross-connect module ODU1 mapping path
Multiplexing module ODU2 mapping path
Service processing ODUflex mapping path

module
ODU0 mapping path Cross-connection that must be

(ODU0–>ODU1– configured on the NMS to receive ODUk
>ODU2) signals from other boards
ODU0 mapping path
(ODU0–>ODU2)
Table 2 Meaning of ports of the TN53NS2 board
Port Name Meaning
IN/OUT-OCh:1-ODU2:1- Mapping path for ODU0 signals received from the

ODU1:(1-4)-ODU0:(1-2) backplane (ODU0->ODU1->ODU2)

ODU0:(1-8) backplane (ODU0->ODU2)

ODU1:(1-4) backplane
IN/OUT-OCh:1 Mapping path for ODU2/ODU2e signals received from

the backplane
IN/OUT-OCh:1-ODU2:1- Mapping path for ODUflex signals received from the

ODUflex:(1-2) backplane
IN/OUT WDM-side optical ports
Compatible Mode
Figure 2 shows the board model of the TN53NS2 board in compatible mode.
Figure 2 Board model of the TN53NS2 board in compatible mode
Cross-connect ODU1 mapping path
module
Multiplexing ODU2 mapping path

module
Service Automatic cross-connection, which does not need

processing to be configured on the NMS. For example, if
module ODU0 signals are required, users only need to
configure cross-connections from other boards to
the ODU0LP port on the board using the NMS. The
board's internal structure enables transmission of
the multiplexed signal to the ODU2LP port. Users
do not need to configure a cross-connection for
transmitting the multiplexed signal.
ODU0 Cross-connection that must be configured on the

mapping path NMS to receive ODUk signals from other boards
Table 3 Meaning of ports of the TN53NS2 board
Port Name Description Automatic Cross-Connection
ODU0LP1- Internal logical ports of the board. Automatic cross-connections are

ODU0LP4 Each of the ports provides optical established between these ports and
channels 1 and 2. the ODU1LP port.
ODU1LP1 Internal logical ports. Each of the Automatic cross-connections are

port provides optical channels 1, 2, 3, established between these ports and
and 4. the ODU2LP port
ODU2LP1 Internal logical ports of the board. Automatic cross-connections are

Each of the ports provides optical established between these ports and
channel 1. the IN/OUT port
IN/OUT WDM-side optical ports. -
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.
Comparison of NMS GUIs for Different Modes

Service creation operations on the NMS vary according to board models. Table 4 uses the
TN53NS2 board as an example to illustrate the differences in the board operation GUIs.
Table 4 GUIs on the NMS
GUI on the Navigation Path Compatible Mode Standard Mode

NMS
Path View In the NE panel, select a board, See Figure 3. See Figure 4.
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 5. See Figure 6.

Interface required board and choose
Configuration > WDM
Interface from the Function
Tree. tab.
Create Cross- In the NE Explorer, select the See Figure 7. See Figure 8.
Connection required NE and choose
Service Configuration > WDM
Service Management from
the Function Tree.
Figure 3 Path View (compatible mode)

Figure 4 Path View (standard mode)
Figure 5 WDM Interface (compatible mode)

Figure 6 WDM Interface (standard mode)
Figure 7 Create Cross-Connection Service (compatible mode)

Figure 8 Create Cross-Connection Service (standard mode)
6.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:
 Tributary boards: TN53TDX, TN57TDX, TN55TQX, TN57TQX, TN54TOA,
TN57TOA, and TEM28
 Line boards: TN52ND2, TN53ND2, TN57ND2, TN52NS2, TN53NS2, TN53NQ2,
TN57NQ2, TN54NS4, TN54HUNS3, TN54HUNQ2, TN56NS3
 Tributary-line integrated board: LOA
NOTE:
 The TN11LOA board supports ODUflex only when ODU Timeslot Configuration Mode is set to
Assign random.
 The TN52ND2, TN53ND2, TN57ND2, TN53NQ2, TN57NQ2, TN52NS2, and TN53NS2 boards
support ODUflex only when they work in Standard Mode and ODU Timeslot Configuration Mode
is set to Assign random.
ODUflex Involved Operations

The following describes the GUIs for creating services involving ODUflex on the NMS
and the navigation paths.
Table 1 GUIs and navigation paths
GUI on the NMS Description Navigation Path
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:
 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).
 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).
ODUflex Configuration Procedure

Figure 1 shows the ODUflex configuration flowchart.
Figure 1 ODUflex configuration flowchart
Table 2 describes the ODUflex configuration procedure.
Table 2 Configuration procedure
No. Action Involved Board Description
Configure the Tributary board or  Parameter settings: Set Port Working Mode
port working tributary-line to ODUflex non-convergence mode.
mode. integrated board  Operation description: In the NE Explorer,
select the required board and choose
Configuration > Working Mode from the
Function Tree. In the displayed window.
Configure the Line board or  Parameter settings: Set ODU Timeslot

timeslot tributary-line Configuration Mode to Assign random for
configuration integrated board the required ports.
mode.  Operation description: In the NE Explorer,
select the required board and choose
Configuration > WDM Interface >
Advanced Attributes from the Function
Tree.
Configure the Tributary board or  Parameter settings: Set the service type
service type. tributary-line based on the service plan.
integrated board  Operation description: Choose
Configuration > WDM Interface from the
Function Tree.
(Optional) Line board or  Parameter settings: Specifies the tolerance of

Configure tributary-line deviation between the actual client-side
integrated board service rate and the specified rate when the
No. Action Involved Board Description
ODUflex client-side service type is ODUflex. This

tolerance parameter is reserved and optional in
configuring the services currently supported.
When the tributary board receives
3GSDI/3GSDIRBR services from client
equipment, set this parameter to 10. If the
tributary board receives other services, set it
to 100.
 Operation description: Choose
Configuration > WDM Interface >
Advanced Attributes from the Function
Tree.
Configure  Tributary board  Parameter settings:

cross- or line board:  Set Level to ODUflex and select the
connections. inter-board source slot, sink slot, source optical port,
cross- sink optical port, source optical channel,
connections and sink optical channel.
between  Set Service Type to the actual client-side
tributary and signals.
line boards
 Operation description: In the NE Explorer,
 Tributary-line select the required NE and choose
integrated Configuration > WDM Service
board: cross- Management from the Function Tree. In the
connections displayed window, click New.
from LP ports to
the WDM side
6.2.2 WDM Service Configuration Flow

This section describes the configuration process of boards and services. Before
configuring WDM services according to the configuration flow, complete the basic
configuration of NEs according to the configuration flow of creating a network.
WDM service configuration flow refer to Table 1.
Table 1 WDM Service Configuration Flow
No. OTU Boards OTU Boards Line Boards and Task Description
Without With Grooming Tributary Boards
Grooming Functions
Functions
1 - Configuring the Configuring the Optional

Board Mode Board Mode
2 - Configuring the Configuring the Optional

Service Mode Service Mode
3 Configuring the Configuring the Configuring the Mandatory

Service Type Service Type Service Type
The type of client-
side services on
boards needs to be
set according to
the type of
services
transmitted over
the network.
Different boards
access different
types of services.
For details, see the
client-side
specifications of
the OTU board
and tributary
board in the
Hardware
Description.
4 Configuring the J0 Configuring the J0 Configuring the J0 Optional

Byte Byte Byte
When the service
type is SDH or
SONET service,
you must set the
J0 byte.
5 - - Configuring the Line Optional

Rate
 When ODU2e
or ODU3e
signals are
cross-
connected to
the line board,
you need to set
Line Rate to
Speedup
Mode for the
line board.
Grooming Functions
Functions
 In other
scenarios, you
need to set
Line Rate to
Standard
Mode for the
line board.
6 - Creating cross- Creating cross- Optional

connect services connect services
(intra-board) (intra-board) There is no need
to configure cross-
connections for
the OTU board
without grooming
functions. Cross-
connections must
be configured for
tributary boards
and other OTU
boards. For details
on how to choose
ports of a board
for cross-
connections, see
service
configuration
descriptions of the
board in the
Hardware
Description.
7 - - Creating cross- Optional

connect services
(inter-board) When tributary
boards work with
line boards, the
inter-board cross-
connections must
be configured. For
details on how to
choose ports of a
board for cross-
connections, see
service
configuration
descriptions of the
Grooming Functions
Functions
board in the
Hardware
Description.
8 Configuring Service Configuring Service Configuring Service Optional

Timeslots Timeslots Timeslots
When the timeslot
configuration
mode is set to
manual, Send
Timeslots and
Receive
Timeslots need to
be set for certain
boards.
9 - Creating WDM Creating WDM trails Optional

trails by using the by using the trail
trail search function search function Create WDM
trails by using the
trail search
function and
check whether
service
configurations are
correct. If the end-
to-end services on
the client side are
correctly
configured, the
client trails of the
corresponding
level can be
searched out.
Configuration Configuring WDM Configuring WDM Configuring WDM -

Example Services for OTU Services for OTU Services for
Boards Without Boards with Cross- Tributary Boards
Cross-Connect Connect Capability and Line Boards is
Capability is is provided. provided.
provided.

6.2.3 Configuring WDM Services for OTU
Boards Without Cross-Connect Capability
This section describes how to configure the 10GE LAN services by using the LDX
board, which is a type of OTU board that does not require cross-connection
configuration.
 Configuration Networking Diagram

This section describes how to configure a 10GE LAN service on a ring network.
 Service Signal Flow

This section describes how to configure the transparent transmission signal flow of a
10GE LAN service.
 Configuration Process
This section describes how to configure a bidirectional 10GE LAN service at stations A
and B.

Service Requirement
See Figure 1. 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.
Figure 1 Configuration networking diagram of the 10GE LAN service
Board Configuration Information

In this example, a 12LDX board must be configured at station A and station B.
Parent topic: Configuring WDM Services for OTU Boards Without Cross-Connect Capability

10GE LAN service.
There is one bidirectional 10GE LAN service between stations A and B.
NOTE:
You do not need to configure cross-connections on the LDX board.

This section describes how to configure a bidirectional 10GE LAN service at stations A
and B.
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.
Tools, Equipment, and Materials

U2000/Web LCT (U2000 is recommended)
Procedure on the U2000/Web LCT

1. Set Service Type of the client-side ports on the TN12LDX boards at stations A and
B to 10GETH. For details, see Configuring the Service Type.
2. Optional: Configure service timeslots of the logical port of the TN12LDX board at
station A. For details, see Configuring Service Timeslots.
3. Optional: Configure service timeslots of the logical port of the TN12LDX board at
station B. For details, see Configuring Service Timeslots.
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.
6.2.4 Configuring WDM Services for OTU

Boards with Cross-Connect Capability
This section describes how to configure GE services by using the LQMS board.

This section describes how to configure a GE service on a ring network.

GE service.
This section describes how to configure a bidirectional GE service at stations A and B.

Service Requirement
On the network shown in Figure 1, 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.
Figure 1 Configuration networking diagram of the GE service

In this example, two 12LQMS boards must be configured at each station.
Parent topic: Configuring WDM Services for OTU Boards with Cross-Connect Capability

GE service.
One bidirectional GE service is available between station A and station B.
Figure 1 shows the service signal flow between station A and station B.
Figure 1 Unidirectional service at each station
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
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.

1. Set Board Mode of the TN12LQMS boards at stations A and B to LQM Mode.
For details, see Configuring the Board Mode.
NOTE:
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.
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.
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.
4. Configure the service to be added or dropped at station A.
a. Configure a GE service from the RX/TX port of the LQMS 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
GE
Level
NOTE:
On the Web LCT, this parameter is Service Level.
Service Type -
Direction Bidirectional
Source Slot Shelf0(subrack)-13-12LQMS
Source Optical Port 3(RX1/TX1)
NOTE:
On the Web LCT, this parameter is Source Port.
Source Optical Channel 1
NOTE:
On the Web LCT, this parameter is Source
Optical Path.
Sink Slot Shelf0(subrack)-13-12LQMS

Sink Optical Port 201(ClientLP/ClientLP)
NOTE:
On the Web LCT, this parameter is Sink Port.
Sink Optical Channel 1

Field Value
NOTE:
On the Web LCT, this parameter is Sink Optical
Path.
Activate Immediately Active
NOTE:
This parameter is valid only on the U2000. It is not
applicable to the Web LCT.
NOTE:
For details on how to select a port for electrical cross-connection services, see Service Signal
Flow.
5. Click Query. Ensure that the query result is consistent with the configuration.
6. Optional: Configure service timeslots of the logical port of the TN12LQMS board
at station A. For details, see Configuring Service Timeslots.
7. Configure the service to be added or dropped at station B.
a. Configure a GE service from the ClientLP port of the LQMS board to the
RX/TX port. For details, see Creating Cross-Connections.
The following table lists the values of the parameters for station B.
Field Value
GE
Level
NOTE:
Service Type -
Source Slot Shelf0(subrack)-13-12LQMS
NOTE:
Field Value
NOTE:
Optical Path.
Sink Slot Shelf0(subrack)-13-12LQMS

NOTE:
NOTE:
Path.
NOTE:
NOTE:
Flow.
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 Configuring Service
Timeslots.
client side are correctly configured, the client trails of GE levels can be searched out.
For details, see Searching for Trails.
6.2.5 Configuring WDM Services for
Tributary Boards and Line Boards
This section describes how to configure GE services by using the TQM and NQ2
boards.


GE service.

Service Requirement
See Figure 1. 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.

In this example, a 12TQM board and a 52NQ2 board must be configured at station A
and station B.
Parent topic: Configuring WDM Services for Tributary Boards and Line Boards

GE service.
One bidirectional GE service is available between station A and station B.
Figure 1 shows the service signal flow between station A and station B.
Figure 1 Unidirectional service at each station
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
Check parameters of the OTU board and ensure that no error is found.


1. Set Service Mode of the client-side ports on the TN12TQM 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 TN12TQM board can access services other than
OTN services.
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.
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.
4. Configure the internal cross-connections for the wavelengths that are added or
dropped from the TN12TQM board at station A.
a. Configure a GE service from the RX/TX port of the TN12TQM board to the
Field Value
GE
Level
NOTE:
Service Type -
Source Slot Shelf0(subrack)-13-12TQM
NOTE:
NOTE:
Optical Path.
Sink Slot Shelf0(subrack)-13-12TQM

NOTE:
NOTE:
Path.
NOTE:
NOTE:
Flow.
6. Configure ODU1 services between the TN52NQ2 board and the TN12TQM board
at station A.
a. 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.
Field Value
ODU1
Level
NOTE:
Service Type -
Source Optical Port 201(ClientLP/ClientLP)
NOTE:
NOTE:
Optical Path.
Sink Slot Shelf0(subrack)-12-52NQ2

Sink Optical Port 51(ODU1LP/ODU1LP)
NOTE:
NOTE:
Path.

Field Value
NOTE:
NOTE:
Flow.
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 Configuring Service
Timeslots.
9. Configure the internal cross-connections for the wavelengths that are added or
dropped from the TN12TQM board at station B.
a. Configure a GE service from the RX/TX port of the TN12TQM board to the
Field Value
GE
Level
NOTE:
Service Type -
NOTE:
NOTE:
Field Value

Optical Path.
Sink Slot Shelf0(subrack)-13-12TQM

NOTE:
NOTE:
Path.
NOTE:
NOTE:
For details on how to select a port for electrical cross-connection services, see Service Signal Flow.
11. Configure ODU1 cross-connections between the TN52NQ2 board and the
TN12TQM board at station B.
a. 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.
Field Value
ODU1
Level
NOTE:
Field Value
Service Type -
NOTE:
NOTE:
Optical Path.
Sink Slot Shelf0(subrack)-12-52NQ2

NOTE:
NOTE:
Path.
NOTE:
NOTE:
Flow.
13. Optional: Configure service timeslots of the logical port of the TN12TQM board at
NE B. For details, see Configuring Service Timeslots.
client side are correctly configured, the client trails of GE levels can be searched out.
For details, see Searching for WDM Trails.
6.2.6 Configuring 10GE LAN Services by

Using the TDX and NS2 Boards
This section describes how to configure 10GE LAN services by using the TDX and
NS2 boards.


This topic describes how to configure the transmission signal flow of a 10GE LAN
service.
This section describes how to configure a bidirectional 10GE LAN service at stations A,
B, and C.

Service Requirement
See Figure 1. 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.

In this example, the TN52TDX board and TN52NS2 boards must be configured at
stations A and C. Two TN52NS2 boards must be configured at station B.
Parent topic: Configuring 10GE LAN Services by Using the TDX and NS2 Boards

This topic describes how to configure the transmission signal flow of a 10GE LAN
service.
One bidirectional GE service is available among stations A, B, and C.
Figure 1 shows the service signal flow among stations A, B, and C.
Figure 1 Service at each station
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.

This section describes how to configure a bidirectional 10GE LAN service at stations A,
B, and C.
Prerequisite
You are an NMS user with "Operator Group" privilege or higher.
Context
Legend Information
Figure 1 shows legend information about U2000 operations.

Figure 1 Legend Information

Background Information
 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.
 The port mapping modes of the upstream and downstream board must be the same.
NOTICE:
 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.
 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.
 The Service Mode must be set to ODU2 or Automatic.
1. Configure attributes of client-side ports on the TN52TDX board of station A.
a. In the NE Explorer, select the TN52TDX board that you want to configure, and
then choose Configuration > WDM Interface from the Function Tree.
b. Click By Board/Port (Channel), and select Channel from the drop-down list.
c. Select the Basic Attributes tab.
d. 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)
Configuration example:
NOTE:
:
 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.
e. Click Apply. In the dialog box that is displayed, click OK.

f. Click Query. Ensure that the query result is consistent with the configuration.
2. Configure attributes of client-side ports on the TN52NS2 board of station A.
a. In the NE Explorer, select the TN52NS2 board and choose Configuration >
WDM Interface from the Function Tree.
b. Click By Board/Port (Channel), and then choose Channel from the drop-
down list.
d. Select the ODU2LP port. Double-click the Service Mode parameter and then
select ODU2 or Automatic.
e. On the Advanced Attributes tab, select the ODU2LP port and then double-
click the Line Rate parameter and select Speedup Mode.
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.
3. Repeat step 2 to configure attributes of ports on the TN52NS2 board at station B.

4. Repeat steps 1 and 2 to configure attributes of ports on the TN52TDX and
TN52NS2 boards of station C.
5. Configure ODU2 services between the TN52NS2 board and the TN52TDX board at
station A.
a. 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.
The following table lists the values of the parameters.
Field Value
Level ODU2
Service Type -
Source Slot Shelf0(subrack)-13-52TDX
Sink Slot Shelf0(subrack)-12-52NS2
NOTE:
Flow.
7. Configure ODU2 services between the TN52NS2 boards at station B.
Field Value
Level ODU2
Field Value
Service Type -
Source Slot Shelf0(subrack)-07-52NS2
Source Optical Port 71(ODU2LP/ODU2LP)
NOTE:
For details on how to select a port for electrical cross-connection services, see Service Signal Flow.
9. Configure ODU2 services between the TN52NS2 board and the TN52TDX board at
station C.
a. 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
Field Value
Service Type -
NOTE:
Flow.
6.2.7 Configuring 10GE LAN Services

Through the TQX and NS3 Boards
This section describes how to configure 10GE LAN services through TN52TQX boards
and cross-connect ODU2 or ODU2e signals to TN54NS3 boards in one station. The
other station is configured exactly the same.
Prerequisites
You are an NMS user with "Operator Group" privilege or higher.
Legend Information
Application Diagram
Figure 2 Position of the TQX and NS3 boards in the WDM system
Cross-Connection Diagram
NOTE:
In this configuring process, a TN54NS3 board in compatible mode is used as an example in Figure 3.
Figure 3 Cross-connection diagram of the TQX and NS3 boards
Procedure
1. Configure attributes of client-side ports on the TN52TQX board of station A.
a. In the NE Explorer, select the TN52TQX board that you want to configure, and
then choose Configuration > WDM Interface from the Function Tree.
b. Click By Board/Port (Channel), and select Channel from the drop-down list.
d. 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)
NOTE:
: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.
e. Click Apply. In the dialog box that is displayed, click OK.
f. Click Query, In the dialog box that is displayed, click Close. Ensure that the
query result is consistent with the configuration.
2. Configure attributes of client-side ports on the TN54NS3 board of station A.
a. In the NE Explorer, select the TN54NS3 board and choose Configuration >
WDM Interface from the Function Tree.
b. Click By Board/Port (Channel) and choose Channel from the drop-down list.
d. Select the ODU2 port. Double-click the Service Mode parameter and then
select ODU2 or Automatic.
e. Select the ODU3 port. Double-click the Service Mode parameter and then
select Automatic or MIX.
f. On the Advanced Attributes tab, select the ODU2 port and ODU3 port and
double-click the Line Rate parameter and set to Speedup Mode.
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.
g. Click Apply. In the dialog box that is displayed, click OK.
h. Click Query. Ensure that the query result is consistent with the configuration.
3. In the NE Explorer,configure ODU2 services from the ClientLP port of the

TN52TQX board to the ODU2LP port of the TN54NS3 board.
6.2.8 Parameters
Describes the parameters involved in the WDM services configuration.
 WDM Cross-Connection Configuration

In this user interface, you can configure the cross-connections of various WDM
services.
 WDM Timeslot Configuration

In this user interface, you can configure WDM services. You can specify ports and
timeslots for transmitting and receiving services, and set the client-side service protocol.
6.2.8.1 WDM Cross-Connection

Configuration
In this user interface, you can configure the cross-connections of various WDM
services.
Table 1 WDM Cross-Connection Configuration
Field Value Description
Level Values of parameters vary The Level parameter is used

with different boards and to differentiate the service
products. types configured when
electrical cross-connections
are configured.
Click Level (WDM Cross-
Connection Configuration) for
more information.
Service Type For example, FE, STM-1, When Level of a new service
FICON is set to Any, you can select a
specific service type.
Occupied ODTUk Timeslots  When Level is ODUflex The number of ODUflex

and Service Type is set to timeslots for received
Custom: 1-8 services. This parameter is set
Default: 8 based on the type and rate of
 It cannot be set manually. the service received by the

 When Level is ODUflex port. The parameter value
and Service Type is set to ranges from 1 to 8.
FC400: this parameter is 4
 When Level is ODUflex NOTE:
and Service Type is set to Set this parameter when Level of
FC800: this parameter is 7 a WDM cross-connection is
ODUflex and Service Type is
 When Level is ODUflex
Custom or PACKET.
and Service Type is set to
3GSDI or InfiniBand
2.5G: this parameter is 3
Service Rate(bit/s) 1-9993964557 The parameter value varies

according to the value of
Occupied ODTUk Timeslots
in the range of 1 to
9993964557.
NOTE:
Set this parameter when Level of
a WDM cross-connection is
ODUflex and Service Type is
Custom.
Direction Unidirectional, Bidirectional. The Direction parameter

Default: Unidirectional indicates the service direction
mode when the service cross-
connection is configured. It
can be set to either
Unidirectional or
Bidirectional.
Click Direction (WDM Cross-
Connection Configuration) for
more information.
Source Channel Slot ID-Board Name-Optical The Source Channel

Interface ID-Optical Channel parameter is used to query the
ID transmit channel of a certain
Default: Null electrical cross-connect
service (unidirectional service
flow).
Click Source Channel (WDM
Cross-Connection) for more
information.
Sink Channel Slot ID - Board Name - The Sink Channel parameter

Optical Interface ID - Optical is used to query the receive
Channel ID channel of a certain electrical
Default: Null cross-connect service
(unidirectional service flow).
Click Sink Channel (WDM
Cross-Connection Configuration)
for more information.
Activation Status Active, Inactive The Activation Status

Default: Active parameter is used to display
whether the service cross-
connection configuration is
activated.
Click Activation Status (WDM
Cross-Connection Configuration)
for more information.
Service Origin Create Manually, Intelligently Displays the mode of creating

Generate WDM cross-connections.
Lock Status Unknown, Locked, Unlocked Indicates the lockout status of

Default: Unlocked an electrical cross-connection.
Parent topic: Parameters
6.2.8.2 WDM Timeslot Configuration

In this user interface, you can configure WDM services. You can specify ports and
timeslots for transmitting and receiving services, and set the client-side service protocol.
Table 1 Parameters of WDM services
Parameters Value Description
Port NE-Slot-Board-Optical The Port parameter indicates

Interface-Channel the location of the service
timeslots, including the
channel, optical interface,
board, slot, and NE where the
timeslots reside.
Table 1 Parameters of WDM services
Parameters Value Description
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.
Transmit Timeslot 1 to 16 The Transmit Timeslot
parameter is used to select the
service timeslots in the
transmit direction.
The Send Timeslot parameter
is used to select the service
timeslots in the transmit
direction.
Click Service Timeslot (WDM
Services) for more
information.
Receive Timeslot 1 to 16 The Receive Timeslot

parameter is used to select the
service timeslots on the
receive direction.
Click Service Timeslot (WDM
Services) for more
information.
Parent topic: Parameters
6.3 Manually Configuring Services Carried

by the TOM Board by Station
This section describes how to manually configure services carried by the TOM board by
station.
 Configuring the TN11TOM Board (Manually by Station)

A TN11TOM board can work in cascading or non-cascading mode and be configured
with different port working modes. Based on different working modes, the TN11TOM
board is applicable to five scenarios. You need to manually configure the TN11TOM
board by station on the NMS for the five application scenarios.
 Configuring the TN52TOM Board (by Station)
board is applicable to 12 scenarios. You need to manually configure the TN52TOM
board by station on the NMS for the 12 application scenarios.
 Multimedia Documentation: TN52TOM Board Configuration Guide
6.3.1 Configuring the TN11TOM Board

board is applicable to five scenarios. You need to manually configure the TN11TOM
board by station on the NMS for the five application scenarios.
 Overview of the Working Modes

This section describes the board working mode and port working mode. A specific
service signal flow of a board is available when the board working mode and port
working mode are set to specific values.
 Scenario 1: ODU1 tributary mode (cascading)

This section describes the configuration process for the TN11TOM board that works in
cascading mode with its ports working in ODU1 tributary mode.
 Scenario 2: ODU1 tributary-line mode (cascading)

cascading ODU1 mode with its ports working in tributary-line mode.
 Scenario 3: ODU1 tributary mode (non-cascading)

non-cascading mode with its ports working in ODU1 tributary mode.
 Scenario 4: ODU1 tributary-line mode (non-cascading)

non-cascading mode with its ports working in ODU1 tributary-line mode.
 Scenario 5: ODU1 tributary-line mode (electrical regeneration board)

This section describes the configuration process for the TN11TOM board that works as
an electrical regeneration board with its ports working in ODU1 tributary-line mode.
Parent topic: Manually Configuring Services Carried by the TOM Board by Station
This section describes the board working mode and port working mode. A specific
service signal flow of a board is available when the board working mode and port
working mode are set to specific values.
Board mode
As shown in Table 1, the TN11TOM boards support the cascading and non-cascading
modes.
Table 1 Board mode of the TN11TOM board
Board mode Description
Cascading mode  A maximum of eight multi-rate (< 2.5 Gbit/s) client-side services can be
input to the TN11TOM board through the SFP module on the client side.
 The services are then multiplexed into different timeslots of one or two
ODU0 services or one ODU1 service.
 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  A maximum of eight multi-rate (< 2.5 Gbit/s) client-side services can be
mode input to the TN11TOM board through the SFP module on the client side.
 The services are then multiplexed into different timeslots of one to eight
ODU0 services or one to four ODU1 services.
to 201(ClientLP1/ClientLP1)-4 ports, can access a maximum of four
Port Working Mode

The TOA board supports five working modes listed in Table 2. You can set the port
working modes on the NMS.
Table 2 Mappings between the working modes and the service mapping paths
Board Working Configuration Port Working Mapping Path

Mode Scenario Mode
Cascading mode Scenario 1: ODU1 N/A OTU1/Anya->ODU1

tributary mode
(cascading)
Scenario 2: ODU1 N/A OTU1/Any->ODU1->OTU1
tributary-line mode
(cascading)
Table 2 Mappings between the working modes and the service mapping paths
Board Working Configuration Port Working Mapping Path

Mode Scenario Mode
Non-cascading Scenario 3: ODU1 N/A OTU1/Any->ODU1

mode tributary mode (non-
cascading)
Scenario 4: ODU1 N/A Any->ODU1->OTU1
tributary-line mode
(non-cascading)
Scenario 5: ODU1 N/A OTU1->ODU1->OTU1
tributary-line mode
(electrical
regeneration board)
a: "Any" in the table indicates the client-side service supported in the corresponding
application scenario.
Parent topic: Configuring the TN11TOM Board (Manually by Station)
6.3.1.2 Scenario 1: ODU1 tributary mode

(cascading)
cascading mode with its ports working in ODU1 tributary mode.
Application Diagram
shows the position of the TN11TOM board in a WDM system where the
Figure 1
TN11TOM board works in cascading ODU1 tributary mode.
Figure 1 Position of the TN11TOM board in a WDM system (scenario 1: ODU1 tributary mode
(cascading))
OptiX OSN 6800: From/To paired slot
OptiX OSN 3800: From/To the mesh group slots
OptiX OSN 6800: N/A

OptiX OSN 3800: From/To the mesh group slots
Figure 2 shows the cross-connection diagram of the TN11TOM board.
Figure 2 Cross-connection diagram of the TN11TOM board (scenario 1: ODU1 tributary mode
(cascading))
Other board TN52ND2 / TN52NQ2 / TN54NQ2 / TN52NS2 / TN52NS3 /

(Compatible TN54NS3 / TN54NPO2 / TN54ENQ2
mode)
Other board TN53NS2 / TN53ND2 / TN53NQ2

(Standard mode)
NOTE:
A cross-connection can be configured between any client-side port and any ClientLP port.
Legend Information
Procedure
1. Setthe Board Modeof the TN11TOM boardtoCascading mode.
Operation Example:
2. Optional: When the client service type is ,Service Mode must be set to OTN
Mode.
Operation Example:
3. Configure the service type for the ports on the TN11TOM board.
Operation Example:
NOTICE:
 Modifying the service type leads to a service interruption.
 When configuring a GE service, make sure that the service encapsulation types
specified for the transmitter and receiver are the same.
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:
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.
5. Configure the cross-connections for the ODU1 services between the TN11TOM
and TN12NS2 boards.
Operation Example:
NOTE:
This step uses the compatible mode board as an example.
6.3.1.3 Scenario 2: ODU1 tributary-line

mode (cascading)
cascading ODU1 mode with its ports working in tributary-line mode.
Application Diagram
Figure 1lists 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.
 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.
 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 1 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:
Single transmitting and single receiving on the WDM side:

OptiX OSN 3800: From/To the mesh
group slots
Figure 2 Cross-connection diagram of the TN11TOM board (scenario 2: ODU1 tributary-line
mode (cascading))
NOTE:
 Only the RX7/TX7 and RX8/TX8 optical ports can be used as WDM-side optical ports.
 A cross-connection can be configured between any client-side port and any ClientLP port.
Legend Information
Procedure
1. Setthe Board Modeof the TN11TOM boardtoCascading mode.
Operation Example:
2. Configure the WDM-side optical ports.Operation Example
NOTE:
In cascading mode, only RX7/TX7 and RX8/TX8 can be used as the WDM-side optical ports.
a. 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.
b. 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.
c. 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.
Mode.
Operation Example:
Operation Example:
NOTICE:
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:
Repeat 5 to configure the remaining Any services.
TN11TOM board.
n 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.
6. Configure ODU1 cross-connections from the ClientLP ports to the ODU1LP ports
on the TN11TOM board.Operation Example:
NOTE:
Repeat 6 to configure the remaining ODU1 services.
7. Configure OTU1 cross-connections between the ODU1LP ports and WDM-side

ports.Parameters of the working channel,Operation Example:
Parameters of the protection channel,Operation Example:
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.
8. Optional: Configure selective receiving at the WDM side of the TN11TOM
board.Operation Example:
NOTE:
For the application of dual-fed and selectively receiving on the WDM side, this step is mandatory.
6.3.1.4 Scenario 3: ODU1 tributary mode

(non-cascading)
non-cascading mode with its ports working in ODU1 tributary mode.
Application Diagram
Figure 1
TN11TOM board works in non-cascading ODU1 tributary mode.
Figure 1 Position of the TN11TOM board in a WDM system (scenario 3: ODU1 tributary mode
(non-cascading))

group slots
OptiX OSN 6800: N/A

group slots
Figure 2 Cross-connection diagram of the TN11TOM board (scenario 3: ODU1 tributary mode
(non-cascading))
Other board TN11ND2 / TN12ND2 / TN52ND2 / TN51NQ2 / TN52NQ2 /

(Compatible TN11NS2 / TN12NS2 / TN52NS2 / TN52NS3 / TN12LQMS(NS1
mode) Mode)
Other board TN53NS2 / TN53ND2 / TN53NQ2

(Standard mode)
NOTE:
A cross-connection can be configured between any client-side port and any ClientLP port.
Legend Information
Procedure
1. Set Board Mode to Non-cascading mode.Operation Example:
Mode.
Operation Example:
Operation Example:
NOTICE:
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.
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.
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.

mode (non-cascading)
non-cascading mode with its ports working in ODU1 tributary-line mode.
Application Diagram
Figure 1
TN11TOM board works in non-cascading ODU1 tributary-line mode.
mode (non-cascading))

group slots
mode (non-cascading))
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.
 A cross-connection can be configured between any ODU1LP port and any WDM-side port.
Legend Information
Procedure
2. Configure the WDM-side optical ports.Operation Example:
NOTE:
All RX/TX optical ports can be used as 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.
Mode.
Operation Example:
Operation Example:
NOTICE:
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:
TN11TOM board.
n 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.
6. Configure ODU1 cross-connections from the ClientLP ports to the ODU1LP ports
NOTE:
7. Configure a cross-connection between the ODU1LP port and any WDM-side port
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 2.
Repeat to configure the remaining OTU1 services.

mode (electrical regeneration board)
This section describes the configuration process for the TN11TOM board that works as
an electrical regeneration board with its ports working in ODU1 tributary-line mode.
Application Diagram
Figure 1shows 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.
mode (electrical regeneration board))
mode (electrical regeneration board))
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.
 A cross-connection can be configured between any client-side port and any ClientLP port.
 A cross-connection can be configured between any ODU1LP port and any WDM-side port.
Legend Information
Procedure
2. Configure the WDM-side optical ports.Operation Example:
NOTE:
3. Configure the service mode for the ports on the TN11TOM board.Operation
Example:
NOTE:
Because the service type is OTU-1, set Service Mode of ports to OTN Mode.
4. Set the service type to OTU-1 for the port. Operation Example:
TN11TOM board for the OTU1 services that are input to the board.Operation
Example:
NOTE:
6. Configure the cross-connections from the ClientLP ports to the ODU1LP ports on
the TN11TOM board for the ODU1 services.Operation Example:
NOTE:
7. Configure a cross-connection between the ODU1LP port and any WDM-side
port.Operation Example:
NOTE:
Selected in the WDM-side optical ports2to modefy the Port type of port
6.3.2 Configuring the TN52TOM Board (by

Station)
board is applicable to 12 scenarios. You need to manually configure the TN52TOM
board by station on the NMS for the 12 application scenarios.
 Overview of the Working Modes
Each port on the TN52TOM board can work in different modes so that services can be
processed on different paths.
 Configuration Principles
This section describes the principles for configuring the TN52TOM board.
 Configuration Flow
Twelve port working modes are available for the TN52TOM board on the NMS. All of
these modes require configurations.
 Scenario 1: ODU0 mode (cascading)

cascading mode with its ports working in ODU0 tributary mode (Any->ODU0(-
>ODU1)). Note that "(->ODU1)" in the mapping path means the ODU1 procedure is
optional.

cascading mode with its ports working in ODU0 tributary-line mode (Any->ODU0-
>ODU1->OTU1).
 Scenario 3: ODU1 mode (cascading)

cascading mode with its ports working in ODU1 tributary mode (Any->ODU1).

>OTU1).
 Scenario 5: ODU0 mode (non-cascading)

non-cascading mode with its ports working in ODU0 tributary mode (Any->ODU0[-
>ODU1]).

non-cascading mode with its ports working in ODU0 tributary-line mode (Any-
>ODU0->ODU1->OTU1).
 Scenario 7: ODU1 mode (non-cascading)

non-cascading mode with its ports working in ODU1 tributary mode (OTU1/Any-
>ODU1).
 Scenario 8: ODU1_ANY_ODU0_ODU1 re-encapsulation mode (non-cascading)

non-cascading mode with its ports working in ODU1 tributary mode (OTU1->ODU1-
>Any->ODU0->ODU1).
 Scenario 9: ODU1_ANY_ODU0_ODU1 re-encapsulation tributary-line mode (non-cascading)

non-cascading mode with its ports working in ODU1 tributary-line mode (OTU1-
>ODU1->Any->ODU0->ODU1->OTU1).

non-cascading mode with its ports working in ODU1 tributary-line mode (OTU1/Any-
>ODU1->OTU1).
 Scenario 11: ODU1_ODU0 mode (non-cascading)

non-cascading mode with its ports working in ODU1 Tributary Mode (OTU1->ODU1-
>ODU0).
 Scenario 12: ODU1_ANY_ODU0 re-encapsulation mode (non-cascading)

>Any->ODU0).

Each port on the TN52TOM board can work in different modes so that services can be
Board Working mode

As shown in Table 1, the TN52TOM boards support the cascading and non-cascading
modes.
Table 1 Board Working mode of the TN52TOM board
Board Working Description

mode
Cascading mode  A maximum of eight multi-rate (< 2.5 Gbit/s) client-side services can be
input to the TN52TOM board through the SFP module on the client side.
 The services are then multiplexed into different timeslots of one or two
ODU0 services or one ODU1 service.
to 201(ClientLP1/ClientLP1)-8 ports, can access a maximum of eight
Non-cascading  A maximum of eight multi-rate (< 2.5 Gbit/s) client-side services can be
mode input to the TN52TOM board through the SFP module on the client side.
Table 1 Board Working mode of the TN52TOM board
Board Working Description

mode
 The services are then multiplexed into different timeslots of one to eight
ODU0 services or one to four ODU1 services.
to 201(ClientLP1/ClientLP1)-4 ports, can access a maximum of four
Port Working Mode

The TN52TOM board should be set to the cascading or non-cascading mode. In
addition, you are advised to set the application scenarios, such as the ODU0 or ODU1
mapping mode and tributary-line mode, of the ports on the board. As shown in Table 2,
the TN52TOM board supports 14 different working modes.
Table 2 Mapping between the working modes and the mapping path of the
TN52TOM board
Board Configuration Scenario Port Working Mode Mapping Path

Working
mode
Scenario 1: ODU0 mode ODU0 mode Any->ODU0[->ODU1]

(cascading)
Scenario 2: ODU0 ODU0 Tributary-Line mode Any->ODU0->ODU1-
tributary-line mode
(cascading) >OTU1
Cascading Scenario 3: ODU1 mode ODU1 mode Any->ODU1

(cascading)
Scenario 4: ODU1 ODU1 Tributary-Line mode Any->ODU1->OTU1
tributary-line mode
(cascading)
- None (not for ports) -

Scenario 5: ODU0 mode ODU0 mode Any->ODU0[->ODU1]
(non-cascading)
Scenario 6: ODU0 ODU0 Tributary-Line Mode Any->ODU0->ODU1-
tributary-line mode (non-
cascading) >OTU1
Non-
Cascading Scenario 7: ODU1 mode ODU1 mode OTU1/Any->ODU1
(non-cascading)
Scenario 8: ODU1_ANY_ODU0_ODU1 OTU1->ODU1->Any-
ODU1_ANY_ODU0_ODU1
re-encapsulation mode re-encapsulation mode >ODU0->ODU1
(non-cascading)
Table 2 Mapping between the working modes and the mapping path of the
TN52TOM board
Board Configuration Scenario Port Working Mode Mapping Path

Working
mode
Scenario 9: ODU1_ANY_ODU0_ODU1 OTU1->ODU1->Any-

ODU1_ANY_ODU0_ODU1
re-encapsulation tributary- re-encapsulation tributary- >ODU0->ODU1-
line mode (non-cascading) line mode >OTU1
Scenario 10: ODU1 ODU1 tributary-line mode OTU1/Any->ODU1-
tributary-line mode (non-
cascading) >OTU1
Scenario 11: ODU1_ODU0 ODU1_ODU0 mode OTU1->ODU1-
>ODU0
Scenario 12: ODU1_ANY_ODU0 re- OTU1->ODU1->Any-
ODU1_ANY_ODU0 re-
encapsulation mode (non- encapsulation mode >ODU0
cascading)
a: "Any" in the table indicates the client-side service supported in the corresponding
application scenario.
NOTE:
 [->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.
 None (not for ports): indicates that the resources at this port are not used and are released to other
ports.
Parent topic: Configuring the TN52TOM Board (by Station)
6.3.2.2 Configuration Principles

This section describes the principles for configuring the TN52TOM board.
Table 1 Rules for configuring the TN52TOM board
Item Description
Slots For the OptiX OSN 3800:

Item Description
 When two TN52TOM boards are used to configure GE service and Any
service cross-connections, the TN52TOM boards must be installed in the
following slots:
 IU2 and IU3
 IU4 and IU5
 When two TN52TOM boards are used to configure ODU1 cross-connections,
the TN52TOM boards must be installed in the following slots:
 IU2 and IU4
 IU2 and IU5
 IU3 and IU4
 IU3 and IU5
Application The following port working mode scenarios are only supported by the OptiX
scenarios OSN 8800.
 Application Scenario 11: Non-cascading ODU1_ODU0 mode (OTU1-
>ODU1->ODU0)
 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.
 Application Scenario 8: Non-cascading ODU1_ANY_ODU0_ODU1 re-
encapsulation mode (OTU1->ODU1->Any->ODU0->ODU1)
Cross-  The OptiX OSN 8800 does not support distributed cross-connection.
connect  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.
 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.
WDM-side In the cascading tributary-line mode, only RX7/TX7 and RX8/TX8 can be used
optical as the WDM-side optical ports.
ports In the non-cascading tributary-line mode, all RX/TX optical ports can be used as
WDM-side optical ports.
Item Description
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
Channel In the cascading ODU0 mode (Any->ODU0(->ODU1)) and ODU0 tributary-
line mode (Any->ODU0->ODU1->OTU1):
 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.
In the non-cascading ODU0 mode (Any->ODU0[->ODU1]) and ODU0
tributary-line mode (Any->ODU0->ODU1->OTU1):
 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.
When the board works in any mode, the source and sink channel IDs for services
must be consistent. For example, if a client-side service is configured at
ClientLPX.1, the service must also be configured at ClientLPY.1 on the
interconnected board. If a client-side service is configured at ClientLPX.2, the
service must also be configured at ClientLPY.2 on the interconnected board. In
other words, service interconnection must be implemented at channels with the
same ID, although the port numbers may be different.
6.3.2.3 Configuration Flow

Twelve port working modes are available for the TN52TOM board on the NMS. All of
these modes require configurations.
shows the general configuration flow for the port working modes on the
Figure 1
TN52TOM board.
Figure 1 Configuration flow
The actions that are labeled "optional" in the preceding figure are required only in
specific scenarios. The following provides the details:
 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.
 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.
 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.

cascading mode with its ports working in ODU0 tributary mode (Any->ODU0(-
>ODU1)). Note that "(->ODU1)" in the mapping path means the ODU1 procedure is
optional.
Application Diagram
and Figure 2 show the position of the TN52TOM board in a WDM system in
Figure 1
which the TN52TOM board works in cascading ODU0 tributary mode (Any->ODU0(-
>ODU1)).
Figure 1 Position of the TN52TOM in a WDM system (scenario 1: Any->ODU0->ODU1)
(OptiX OSN 6800/OptiX OSN 3800)
OptiX OSN 8800: N/A

OptiX OSN 3800: From/To paired slot of the mesh group
OptiX OSN 8800: N/A

OptiX OSN 6800: N/A
OptiX OSN 3800: From/To non-paired slots of the mesh
group
Figure 2 Position of the TN52TOM in a WDM system (scenario 1: Any->ODU0) (OptiX OSN
8800)
Figure 3 and Figure 4 show the cross-connection diagram of the TN52TOM board.
Figure 3 Cross-connection diagram of the TN52TOM board (scenario 1: Any->ODU0->ODU1)
(OptiX OSN 6800/OptiX OSN 3800)
mode)
Other board TN53ND2 / TN53NQ2 / TN53NS2 / TN55NPO2 / TN55NPO2E /

(Standard mode) TN54ENQ2
Figure 4 Cross-connection diagram of the TN52TOM board (scenario 1: Any->ODU0) (OptiX

OSN 8800)

mode)

Legend Information
Procedure
1. ConfigureBoard Working ModeandPort Working Modefor the TN52TOM
NOTE:
Port Working Modeis ODU0 mode (Any->ODU0(->ODU1)).
2. Configure Service Type of the TN52TOM board according to the service planning.
Operation Example:
NOTICE:
NOTE:
 If you set Service Type to Any, you must set the service rate in Client Service Bearer Rate
(Mbit/s).
 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.
 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.
 Only one GE service can be input through each group of ClientLP ports.
 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.
TN52TOM board for the Any services that are input to the board.Operation
Example:
NOTE:
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 3 to configure the remaining services.
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 OptiX OSN 3800.
When ODU1 cross-connections are created, ODU0 cross-connections from the ClientLP port to the
ODU0LP port on the TN52TOM board are automatically created.
5. Configure electrical cross-connections for the two ODU0 services between the
NOTE:
This configuration is only supported by the OptiX OSN 8800.
When creating the cross-connection of the ODU0 signal, only the first channel can be selected, for
example, 201(ClientLP1/ClientLP1)-1.
Repeat to configure a cross-connection for the other ODU0 service between the TN52TOM and
TN52NS2 boards.

mode (cascading)
>ODU1->OTU1).
Application Diagram
Figure 1lists two conditions in which the TN52TOM board works in cascading ODU0
tributary-line mode. Perform the configurations according to the network plan.
 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.
receives a maximum of seven services on the client side. The other client-side port
works as a WDM-side port.
Figure 1 Position of the TN52TOM in a WDM system (scenario 2: Any->ODU0->ODU1-
>OTU1)
OptiX OSN 8800: N/A


OptiX OSN 8800: N/A
Figure 2 Cross-connection diagram of the TN52TOM board (scenario 2: Any->ODU0->ODU1-
>OTU1)
The dual-fed and selectively receiving on the WDM side:
The single transmitting and single receiving on the WDM side:
Legend Information
Procedure
NOTE:
Port Working Modeis ODU0 mode (Any->ODU0(->ODU1)).
2. Configure the working mode for the TN52TOM board.Operation Example:
NOTE:
 For the application of the single transmitting and single receiving on the WDM side, set
 For the application of the dual-fed and selectively receiving on the WDM side, set both
port.
Operation Example:
NOTICE:
NOTE:
(Mbit/s).
Example:
NOTE:
TN52TOM board.
5. Configure an intra-board WDM-side cross-connection.

Configure a bidirectional OTU1 cross-connection between the
51(ODU1LP1/ODU1LP1) and 10(RX8/TX8) ports.
For the application of dual-fed and selectively receiving on the WDM side,
configure a unidirectional OTU1 cross-connection between the
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:
6. Configure selective receiving at the WDM side of the TN52TOM board.Operation
Example:

cascading mode with its ports working in ODU1 tributary mode (Any->ODU1).
Application Diagram
Figure 1
TN52TOM board works in cascading ODU1 tributary mode.
Figure 1 Position of the TN52TOM in a WDM system (scenario 3: Any->ODU1)
OptiX OSN 8800: N/A

OptiX OSN 8800: N/A

OptiX OSN 6800: N/A
group
Figure 2 Cross-connection diagram of the TN52TOM board (scenario 3: Any->ODU1)
mode)

(Standard TN54ENQ2
mode)
Legend Information
Procedure
1. ConfigureBoard Working ModeandPort Working Modeof the TN52TOM
NOTE:
Port Working Modemust beODU1 mode (Any->ODU1).
2. Configure Service Type of the TN52TOM board according to the service plan.
Operation Example:
NOTICE:
 Modifying the service type will lead to service interruption.
NOTE:
(Mbit/s).
 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.
 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.
 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.
TN52TOM board for the Any services that are input to the board. Operation
Example:
NOTE:
TN52TOM board.
NOTE:

mode (cascading)
>OTU1).
Application Diagram
Figure 1shows two applications where the TN52TOM board works in cascading ODU1
tributary-line mode. Perform configurations according to the network design.
 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.
receives a maximum of seven channels of services on the client side and the other
client-side port works as a WDM-side port.
Figure 1 Position of the TN52TOM in a WDM system (scenario 4: Any->ODU1->OTU1)
Dual-fed selectively receiving on the WDM side:
OptiX OSN 8800: N/A

OptiX OSN 8800: N/A

Figure 2 Cross-connection diagram of the TN52TOM board (scenario 4: Any->ODU1->OTU1)
Legend Information
Procedure
1. ConfigureBoard Working ModeandPort Working Mode of the TN52TOM
2. Configure the working mode for the TN52TOM board.Operation Example:
NOTE:
 For the application of the single transmitting and single receiving on the WDM side, set
 For the application of the dual-fed and selectively receiving on the WDM side, set both
port.
3. Configure Service Type of the TN52TOM board according to the service
plan.Operation Example:
NOTICE:
NOTE:
(Mbit/s).
 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.
 Services can be input at the six or seven pairs of client-side optical ports at a maximum rate of
2.5 Gbit/s.
 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.
Example:
NOTE:
TN52TOM board.

NOTE:
Example:
6.3.2.8 Scenario 5: ODU0 mode (non-

cascading)
non-cascading mode with its ports working in ODU0 tributary mode (Any->ODU0[-
>ODU1]).
Application Diagram
and Figure 2 show the position of the TN52TOM board in a WDM system where
Figure 1
the TN52TOM board works in non-cascading ODU0 tributary mode (Any->ODU0[-
>ODU1]).
Figure 1 Position of the TN52TOM in a WDM system (scenario 5: Any->ODU0-
>ODU1)(OptiX OSN 6800/OptiX OSN 3800)
OptiX OSN 8800: N/A

OptiX OSN 8800: N/A

OptiX OSN 6800: N/A
group
Figure 2 Position of the TN52TOM in a WDM system (scenario 5: Any->ODU0)(OptiX OSN

8800)
Figure 3 Cross-connection diagram of the TN52TOM board (scenario 5: Any->ODU0-
>ODU1)(OptiX OSN 6800/OptiX OSN 3800)

mode)

(Standard TN54ENQ2
mode)
Figure 4 Cross-connection diagram of the TN52TOM board (scenario 5: Any->ODU0)(OptiX
OSN 8800)

mode)

Legend Information
Procedure
NOTE:
Port Working Modemust beODU0 mode (Any->ODU0[->ODU1]).
Operation Example:
NOTICE:
NOTE:
(Mbit/s).
Example:
NOTE:
TN52TOM board.
NOTE:
This configuration is only supported by the OptiX OSN 6800 and 3800.
When ODU1 cross-connections are created, ODU0 cross-connections from the ClientLP port to
ODU0LP on the TN52TOM board are automatically created.
5. Configure electrical cross-connections for the two ODU0 services between the
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.

non-cascading mode with its ports working in ODU0 tributary-line mode (Any-
>ODU0->ODU1->OTU1).
Application Diagram
shows two conditions where the TN52TOM board works in non-cascading
Figure 1
ODU0 tributary-line mode. Perform configurations according to the network plan.
 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.
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 1 Position of the TN52TOM board in a WDM system (scenario 6: Any->ODU0-
>ODU1->OTU1)
OptiX OSN 8800: N/A

OptiX OSN 8800: N/A

Figure 2 Cross-connection diagram of the TN52TOM board (scenario 6: Any->ODU0->ODU1-
>OTU1)
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
Procedure
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).
 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).
 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).
2. Set the port type.Operation Example:
NOTE:
port.
3. Configure Service Type of the TN52TOM board according to the service
plan.Operation Example:
NOTICE:
NOTE:
 If you set Service Type to Any, you must set the Service Rate(Mbit/s).
same time, but the total rate of the services must be less than or equal to 5 Gbit/s.
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.
 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.
Example:
NOTE:
TN52TOM board.

NOTE:
Example:
6.3.2.10 Scenario 7: ODU1 mode (non-

cascading)
non-cascading mode with its ports working in ODU1 tributary mode (OTU1/Any-
>ODU1).
Application Diagram
Figure 1
the TN52TOM board works in non-cascading ODU1 tributary mode (OTU1/Any-
>ODU1).
Figure 1 Position of the TN52TOM board in a WDM system (scenario 7: OTU1->ODU1)
OptiX OSN 8800: N/A

OptiX OSN 6800: N/A
OptiX OSN 3800: From/To non-paired slots of the mesh group
Figure 2 Position of the TN52TOM board in a WDM system (scenario 7:Any->ODU1)
OptiX OSN 8800: N/A

OptiX OSN 8800: N/A

OptiX OSN 6800: N/A
Figure 3 Cross-connection diagram of the TN52TOM board (scenario 7: OTU1/Any->ODU1)

mode)

Legend Information
Procedure
Set Board Working Mode to Non-cascading mode and Port Working Mode to
ODU1 mode (OTU1/Any->ODU1).
2. Optional: Configure the service mode for the ports on the TN52TOM
NOTE:
 If the service type is OTU-1, set Service Mode to OTN Mode for the port.
 If the service type is another service, retain the default value Client Modefor the port.
3. Set the service type of the TN52TOM board according to the service plan.
Operation Example:
NOTICE:
NOTE:
 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).
 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.
 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.
Example:
NOTE:
TN52TOM board.
The inter-board ODU1 cross-connections between the TN52TOM and TN52NS2

boards must be configured as shown below.
TN52TOM board TN52NS2 board

Product
OptiX OSN 3800 201(ClientLP1/ClientLP1) 51(ODU1LP/ODU1LP)-1

205(ClientLP5/ClientLP5) 51(ODU1LP/ODU1LP)-2
OptiX OSN 8800/6800 A cross-connection can be configured between any port on the
TN52TOM board and any port on the TN52NS2 board.
NOTE:
6.3.2.11 Scenario 8:
ODU1_ANY_ODU0_ODU1 re-encapsulation
>Any->ODU0->ODU1).
Application Diagram
Figure 1
TN52TOM board works in non-cascading ODU1 tributary mode (OTU1->ODU1-
>Any->ODU0->ODU1).
Figure 1 Position of the TN52TOM board in a WDM system (scenario 8: OTU1->ODU1-
>Any->ODU0->ODU1)

OptiX OSN 6800: N/A

Figure 2 Cross-connection diagram of the TN52TOM board (scenario 8: OTU1->ODU1->Any-
>ODU0->ODU1)
Other board TN52ND2 / TN52NQ2 / TN54NQ2 / TN52NS2 / TN52NS3 / TN54NS3

(Compatible / TN54NPO2 / TN54ENQ2
mode)

(Standard TN54ENQ2
mode)
Legend Information
Procedure
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).
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.
3. Set the service type of the TN52TOM board toOTU-1.Operation Example:
NOTE:
 The board can receive a maximum of four OTU1 services at the same time.
 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.
 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.
 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.
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 2 and
3.
Repeat 4 to configure the remaining OTU1 services.

5. Configure internal cross-connections for Any services on the TN52TOM
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 5to configure the remaining Any services.
6. Configure ODU1 cross-connections between the TN52TOM and TN52NS2
boardsOperation Example:
NOTE:
Repeat to configure the remaining ODU1 services.
6.3.2.12 Scenario 9:
ODU1_ANY_ODU0_ODU1 re-encapsulation
tributary-line mode (non-cascading)
non-cascading mode with its ports working in ODU1 tributary-line mode (OTU1-
>ODU1->Any->ODU0->ODU1->OTU1).
Application Diagram
Figure 1
TN52TOM board works in non-cascading ODU1 tributary-line mode (OTU1->ODU1-
>Any->ODU0->ODU1->OTU1).
>Any->ODU0->ODU1->OTU1)
Figure 2 Cross-connection diagram of the TN52TOM board (scenario 9: OTU1->ODU1->Any-
>ODU0->ODU1->OTU1)
NOTE:
example.
Legend Information
Procedure
NOTE:
 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).
 The ClientLP5 and ClientLP7 ports do not support the non-cascading
>ODU0->ODU1->OTU1) mode.
 Before the working modes of the ClientLP1 and ClientLP3 ports are set to
>ODU0->ODU1->OTU1), the working modes of the ClientLP5 and ClientLP7 ports must be set
to None (not for ports).
2. Set the port type.Operation Example:
NOTE:
When the service type is OTU-1, Service Mode must be set to OTN Mode for
ports.
4. Configure the service mode for the ports on the TN52TOM board toOTU-
1.Operation Example:
TN52TOM board for the OTU1 services that are input to the board.Operation
Example:
NOTE:
Repeat 6to configure the remaining Any services.

Parameters of the working channel,Operation Example
Parameters of the protection channel,Operation Example
51(ODU1LP1/ODU1LP1) and 7(RX5/TX5), 52(ODU1LP2/ODU1LP2) and
10(RX8/TX8) ports.
For the application of dual-fed selectively receiving on the WDM side, configure a
unidirectional OTU1 cross-connection between the 51(ODU1LP1/ODU1LP1) and
8(RX6/TX6)ports, and between the 52(ODU1LP2/ODU1LP2) and 9(RX7/TX7)
ports.
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.
8. Configure the realization of the dual-fed and selectively receiving on the WDM side
of the TN11TOM board.Operation Example:
NOTE:
For the application of "the dual-fed and selectively receiving on the WDM side", the steps above.

non-cascading mode with its ports working in ODU1 tributary-line mode (OTU1/Any-
>ODU1->OTU1).
Application Diagram
Figure 1
the TN52TOM board works in non-cascading ODU1 tributary-line mode (OTU1/Any-
>ODU1->OTU1). Perform configurations according to the network design.
 Figure 1 shows a scenario where OTU1 signals are electrically regenerated.
 shows a scenario where the TN52TOM board works in tributary-line mode
Figure 2
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.
>OTU1)
Electrical regeneration of four OTU1 optical signals:
Figure 2 Position of the TN52TOM board in a WDM system (scenario 10: Any->ODU1-
>OTU1)
OptiX OSN 8800: N/A

OptiX OSN 8800: N/A

Figure 3 Cross-connection diagram of the TN52TOM board (scenario 10: OTU1->ODU1-
>OTU1)
OTU1/Any->ODU1->OTU1 mode. The dual-fed selectively receiving on the WDM
side.
Figure 4 Cross-connection diagram of the TN52TOM board (scenario 10: Any->ODU1-

>OTU1)
OTU1/Any->ODU1->OTU1 mode. Single transmitting and single receiving
NOTE:
example.
Legend Information
Procedure
NOTE:
 Set Board Working Mode to Non-cascading mode and Port Working Mode to ODU1
tributary-line mode (OTU1/Any->ODU1->OTU1).
 For the 201(ClientLP1/ClientLP1)-207(ClientLP7/ClientLP7) ports, set Port Working Mode to
ODU1 tributary-line mode (OTU1/Any->ODU1->OTU1).
2. Optional: Set the port type.Operation Example:
NOTE:
 All RX/TX optical ports can be used as WDM-side optical ports.
 For the application of "Electrical regeneration of four OTU1 optical signals", set four RX/TX
ports as WDM-side optical ports.
 For the application of "Dual-fed selectively receiving on the WDM side", set four RX/TX ports
as WDM-side optical ports.
 For the application of "Single transmitting and single receiving on the WDM side", set two
RX/TX ports as WDM-side optical ports.
3. Optional: Configure the service mode toOTN Modefor the ports on the
TN52TOM board.Operation Example:
NOTE:
 For the application of "Electrical regeneration of four OTU1 optical signals", set Service Mode
of the four RX/TX ports to OTN Mode.
 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.
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.
Example:
NOTE:
TN52TOM board.

Parameters of the working channel,Operation Example
Parameters of the protection channel,Operation Example
NOTE:
Configure a bidirectional OTU1 cross-connection between the 51(ODU1LP1/ODU1LP1) and
7(RX5/TX5), 52(ODU1LP2/ODU1LP2) and 10(RX8/TX8) ports.
For the application of dual-fed selectively receiving on the WDM side, configure a unidirectional
OTU1 cross-connection between the 51(ODU1LP1/ODU1LP1) and 8(RX6/TX6),
7. Optional: Configure the realization of the dual-fed and selectively receiving on the
WDM side of the TN11TOM board.Operation Example:
NOTE:
For the application of "the dual-fed and selectively receiving on the WDM side", the steps above.
6.3.2.14 Scenario 11: ODU1_ODU0 mode

(non-cascading)
non-cascading mode with its ports working in ODU1 Tributary Mode (OTU1->ODU1-
>ODU0).
Application Diagram
Figure 1
>ODU0)
>ODU0)

mode)
Legend Information
Procedure
NOTE:
 Set Board Working Mode to Non-cascading mode and Port Working Mode to ODU1_ODU0
mode (OTU1->ODU1->ODU0).
3. Set the service type of the TN52TOM board to OTU-1.Operation Example:

TN52TOM board.Operation Example:

boards.Operation Example:
Repeat to configure the remaining ODU0 cross-connections.
NOTE:
6.3.2.15 Scenario 12: ODU1_ANY_ODU0 re-

encapsulation mode (non-cascading)
>Any->ODU0).
Application Diagram
Figure 1
>Any->ODU0)
Figure 2 shows the port configuration of the TN52TOM board.
>Any->ODU0)

mode)

Legend Information
Procedure
NOTE:
 Set Board Working Mode to Non-cascading mode and Port Working Mode to
ODU1_ANY_ODU0 re-encapsulation mode (OTU1->ODU1->Any->ODU0).
3. Set the service type of the TN52TOM board toOTU-1.Operation Example:
NOTE:
 The board can receive a maximum of four OTU1 services at the same time.
 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.
 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.
 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.
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 2 and
3.
Repeat 4 to configure the remaining OTU1 services.
NOTE:
boards.Operation Example:
Repeat to configure the remaining ODU0 cross-connections.
NOTE:
6.3.3 Multimedia Documentation: TN52TOM

Board Configuration Guide
6.4 Configuring the THA/TOA Board

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:
 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.
 The THA board cannot receive SDI, HD-SDI and HDSDIRBR services on the client
side.
 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.
 Overview of the Working Mode

Each port on the TOA board can work in different modes so that services can be
 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.
 Scenario 1: ODU0 non-convergence mode (Any->ODU0)

This section describes the configuration process of the TOA board works in ODU0 non-
convergence mode.
 Scenario 2: ODU1 non-convergence mode (Any->ODU1)

convergence mode.
 Scenario 3: ODU1 convergence mode (n*Any->ODU1)

This section describes the configuration process of the TOA board works in ODU1
convergence mode.
 Scenario 4: ODU1_ODU0 mode (OTU1->ODU1->ODU0)

This section describes the configuration process of the TOA board works in
ODU1_ODU0 mode.
 Scenario 5: ODUflex non-convergence mode (Any->ODUflex)

This section describes the configuration process of the TOA board works in ODUflex
non-convergence mode.

6.4.1 Overview of the Working Mode
Each port on the TOA board can work in different modes so that services can be
The TOA board supports six port working modes listed in Table 1. You can set the port
working modes on the NMS.
Table 1 Port working modes on the TOA board
Configuration Scenario Port Working Mode Mapping Path
Scenario 1: ODU0 non- ODU0 non-convergence Any->ODU0

convergence mode (Any-
>ODU0) mode
Scenario 2: ODU1 non- ODU1 non-convergence OTU1/Any->ODU1
>ODU1) mode
Scenario 3: ODU1 convergence ODU1 convergence mode n x Any->ODU1 (1 ≤ n ≤ 8)
mode (n*Any->ODU1)
Scenario 4: ODU1_ODU0 mode ODU1_ODU0 mode OTU1->ODU1->ODU0
(OTU1->ODU1->ODU0)
Scenario 5: ODUflex non- ODUflex non-convergence Any->ODUflex
>ODUflex) mode
NOTE:
None (not for ports): indicates that the resources at the port in this mode are not used and are released to
other ports.
Parent topic: Configuring the THA/TOA Board (Manually by Station)
6.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.
General Configuration Procedure

shows the general configuration procedure for the port working modes on the
Figure 1
TOA board.
Figure 1 General configuration procedure
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:
 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.
 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.
 Configure the service mode: When Service Type is set to OTU1, Service Mode
must be set to OTN Mode first.
 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.
 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.
 Table 1 describes the configuration procedure for the ODU0 non-convergence mode.
 Table 2 describes the configuration procedure for the ODU1 non-convergence mode.
 Table 3 describes the configuration procedure for the ODU1 convergence mode.
 Table 4 describes the configuration procedure for the ODU1_ODU0 mode.
 Table 5 describes the configuration procedure for the ODUflex non-convergence
mode.
Configuration Procedure for the ODU0 Non-Convergence Mode
No. Action Description
1 Configure the port Optional

working mode.  Parameter settings: The default value of Port Working
Mode is ODU0 non-convergence mode (Any->ODU0).
If the default value is used, skip this step.
 Operation description: For details about the configuration
procedure, see Configuring the Working Mode.

type.  Parameter settings: The default value of Port Type is
Client Side Grey Optical Port. If colored optical signals
are received on the client side, set Port Type to Client
Side Color Optical Port.
procedure, see Modifying Port.
3 Configure the service Mandatory

type.  Parameter settings: The available values for Service Type
are FE, FDDI, GE(GFP-T), GE(TTT-GMP), STM-1,
STM-4, OC-3, OC-12, FC100, FICON, DVB-ASI,
ESCON, and SDI.
 Operation description: Configure the service type based on
the service plan. For details about the configuration
procedure, see Configuring the Service Type.
NOTE:
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.
This note is only for the compatible mode. Services in standard
mode are configured at RX/TX ports.
4 Configure cross- When services are in compatible mode, it is mandatory to

connections from the configure this parameter. But when services are in standard
client side to ClientLP mode, this parameter does not need to be configured.
ports on the TOA  Parameter settings:
board.
 Level and Service Type:
 If you set Service Type to GE(GFP-T) or
GE(TTT-GMP) in step 3, retain the default value
(GE) for Level.
 If you set Service Type to a value other than GE in
step 3, set Level to Any and then set Service Type
to the same value that you set in step 3.
 Direction: Set it to Bidirectional.
 Source Slot/Sink Slot: Set the two parameters to the
ID of the slot where the TOA board is housed.
 Source Optical Port: Set it to a port in the range of
3(RX1/TX1) to 10(RX8/TX8).
 Source Optical Channel: Set it to 1.
 Sink Optical Port: Set it to a port in the range of
201(ClientLP1/ClientLP1) to
208(ClientLP8/ClientLP8). Ensure that the client-side
port matches an ClientLP port. That is, if you set the
source optical port to RXi/TXi, set the sink optical port
to ClientLPi.
 Sink Optical Channel: 1 or 2. Set it to the channel for
which you configure the service type in step 3.
 Operation description: Configure cross-connections from
the client side to each ClientLP port. For details about the
configuration procedure, see Creating Cross-Connections.
NOTE:
Set Port Working Mode to ODU0 non-convergence mode (Any-
>ODU0) for each sink optical port.
5 Configure inter-board Mandatory

cross-connections.  Parameter settings: See Table 6.
each ClientLP port on the TOA board to other boards. For
details about the configuration procedure, see Creating
Cross-Connections.
Configuration Procedure for the ODU1 Non-Convergence Mode
1 Configure the port Mandatory

working mode.  Parameter settings: Set Port Working Mode to ODU1
non-convergence mode (OTU1/Any->ODU1).

3 Configure the service Optional

mode.  Parameter settings: The default value of Service Mode is
Client Mode. When you set Service Type to OTU1, set
Service Mode to OTN Mode.
procedure, see Configuring the Service Mode.

are HD-SDI, STM-16, OC-48, FC200, FICON Express,
and OTU1. The total received service bandwidth cannot
exceed 20 Gbit/s.

Cross-Connections.
Configuration Procedure for the ODU1 Convergence Mode

working mode.  Parameter settings: Set Port Working Mode to ODU1
convergence mode (n*Any->ODU1).


are ANY, FE, FDDI, GE(GFP-T), FC100, FC200, DVB-
ASI, ESCON, STM-1, STM-4, STM-16, OC-3, OC-12,
SDI, HDSDI, HDSDIRBR, FICON, and FICON Express.
NOTE:
 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.
 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.
 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.
The preceding ClientLP ports are only for configuring service types
in compatible mode. in standard mode, RX/TX ports are configured.
201(ClientLP1/ClientLP1)-1 in compatible mode corresponds to
3(RX1/TX1) in standard mode. The rest follows the same principle.
4 Configure cross- Mandatory

connections from the  Parameter settings:
client side to ClientLP
 Level and Service Type:
ports on the TOA
board.  If you set Service Type to GE(GFP-T) in step 3,
retain the default value (GE) for Level.
 If you set Service Type to a value other than GE in
step 3, set Level to Any and then set Service Type
to the same value that you set in step 3.
 Direction: Set it to Bidirectional.
 Source Slot/Sink Slot: Set the two parameters to the
ID of the slot where the TOA board is housed.
 Source Optical Port: Set it to a port in the range of
3(RX1/TX1) to 10(RX8/TX8).
 Source Optical Channel: Set it to 1.
 Sink Optical Port:
 Compatible Mode: 201(ClientLP1/ClientLP1) to
208(ClientLP8/ClientLP8)
 Standard Mode: 201(ConvGroup1/ConvGroup1) to
208(ConvGroup8/ConvGroup8)
 Sink Optical Channel: Set it to a value in the range of
1 to 8, which is the ID of the channel for which you
configure the service type in step 3.
 Configuration principles: There is no mapping between
client-side ports and ClientLP ports. For example, if you
set the source optical port to 3(RX1/TX1), you can set the
sink optical port to any of the ports from 201 to 208.
NOTE:
However, for a board in compatible mode, 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.

the client side to each ClientLP port. For details about the
configuration procedure, see Creating Cross-Connections.
NOTE:
Set Port Working Mode to ODU1 convergence mode (n*Any-
>ODU1) for each sink optical port.

Cross-Connections.
Configuration Procedure for the ODU1_ODU0 Mode

working mode.  Parameter settings: Set Port Working Mode to
ODU1_ODU0 mode (OTU1->ODU1->ODU0).


mode.  Parameter settings: Set Service Mode to OTN Mode.
procedure, see Configuring the Service Mode.

type.  Parameter settings: Set Service Type to OTU1.


each ODU0LP port on the TOA board to other boards. For
Cross-Connections.
Configuration Procedure for the ODUflex Non-Convergence Mode

working mode.  Parameter settings: Set Port Working Mode to ODUflex
non-convergence mode (Any->ODUflex).

3 Configure the timeslot Mandatory

configuration mode for  Parameter settings: The default value of ODU Timeslot
the line board that is Configuration Mode is Assign random. If the default
interconnected with the value is used, skip this step.
TOA board.
 Operation description: In the NE Explorer, select the line
board that is interconnected with the TOA board and
choose Configuration > WDM Interface from the
Function Tree. Click By Function and choose ODU
Timeslot Configuration Mode from the dropdown list.
Set ODU Timeslot Configuration Mode to Assign
random for the required ports.

are 3GSDI, 3GSDIRBR and FC400.
5 Configure the Optional

ODUflex  Parameter settings: For the transmission of 3GSDI or
tolerance(ppm) for the 3GSDIRBR services, set this parameter to 10; for the
line board that is transmission of other services, set this parameter to 100.
interconnected with the
 Operation description: In the NE Explorer, select the line
TOA board.
board that is interconnected with the TOA board and
choose Configuration > WDM Interface > Advanced
Attributes from the Function Tree. In the displayed
window, set ODUflex tolerance(ppm) for the required
ports.

Cross-Connections.
Table 6 Parameters for configuring inter-board cross-connections
Parameter ODU0 Non-Convergence ODU1 Non-Convergence ODU1 Convergence Mode

Mode Mode
Level ODU0 ODU1 ODU1 OD
Service - - - -
Type
Direction Bidirectional Bidirectional Bidirectional Bid

Source ID of the slot where the TOA ID of the slot where the TOA ID of the slot where the TOA ID
Slot board is housed board is housed board is housed bo
Table 6 Parameters for configuring inter-board cross-connections
Parameter ODU0 Non-Convergence ODU1 Non-Convergence ODU1 Convergence Mode

Mode Mode
Source  Compatible Mode:  Compatible Mode:  Compatible Mode: 

Optical 201(ClientLP1/ClientLP1) 201(ClientLP1/ClientLP1) 201(ClientLP1/ClientLP1) to
Port to to 208(ClientLP8/ClientLP8)
208(ClientLP8/ClientLP8) 208(ClientLP8/ClientLP8)  Standard Mode:
 Standard Mode:  Standard Mode: 201(ConvGroup1/ConvGroup1) 
3(RX1/TX1) to 3(RX1/TX1) to to
10(RX8/TX8) 10(RX8/TX8) 208(ConvGroup8/ConvGroup8)
Source 1 1 1 1o
Optical
Channel
Sink Slot ID of the slot where the ID of the slot where the ID of the slot where the ID
interconnected board is interconnected board is interconnected board is houseda int
houseda houseda ho
Sink Example: Example: Example: Ex
Optical 161(ODU0LP1/ODU0LP1) 51(ODU1LP1/ODU1LP1) 51(ODU1LP1/ODU1LP1) 16
Port
Sink 1 or 2 1 to 4 1 to 4 1o
Optical
Channel
Occupied - - - -
ODUTUk
Timeslots
Service - - - -
Rate(bit/s)
 There is no mapping between source optical ports and sink optical ports. For example, if you set the source optic
optical port to 161(ODU0LP1/ODU0LP1) or any other ODU0LP port on the board in the sink slot.
 a: The interconnected board can be
 Standard mode:
TN53ND2 / TN53NQ2 / TN53NS2 / TN55NPO2 / TN55NPO2E / TN54ENQ2
 Compatible mode:
TN52ND2 / TN52NQ2 / TN54NQ2 / TN52NS2 / TN52NS3 / TN54NS3 / TN54NPO2 / TN54ENQ2

6.4.3 Scenario 1: ODU0 non-convergence
mode (Any->ODU0)
convergence mode.
Legend Information
Application Diagram
Figure 2 lists the condition where the TOA board works in ODU0 non-convergence
mode.
Figure 2 Position of the TOA in a WDM system (Scenario 1: ODU0 non-convergence mode
(Any->ODU0))
Figure 3 and Figure 4 shows the port configuration of the TOA board.
Figure 3 Cross-connection diagram of the TOA board (Scenario 1: ODU0 non-convergence
mode (Any->ODU0))(compatible mode)
Other TN53ND2 / TN53NQ2 / TN53NS2 / TN55NPO2 / TN55NPO2E /

board a TN54ENQ2
(standard
mode)
Other TN52ND2 / TN52NQ2 / TN54NQ2 / TN52NS2 / TN52NS3 / TN54NS3
board b / TN54NPO2 / TN54ENQ2
(compatible
mode)
mode (Any->ODU0)) (standard mode)

board a TN54ENQ2
(standard
mode)
(compatible
mode)
Procedure
Expand All
1. Configure the working mode for the TOA board.Set Port Working Mode to
ODU0 non-convergence mode (Any->ODU0)
Operation Example:
2. Optional:
According to the network plan, set the port type in Path View.
Operation Example:
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:
 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.
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 5.
Operation Example:
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.
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:
 Retain the same values for the other parameters except Source Optical Port and Sink Optical
Port.
 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.
 Set Sink Optical Channel to 1 or 2. Set it to the channel for which you configure the service
type in 3.
5. Configure ODU0-level cross-connections from ClientLP port on the TOA board to

other boards.
Operation Example:
 When the TOA board is in compatible mode, set the cross-connection
parameters as follows.
 When the TOA board is in standard mode, set the cross-connection parameters
as follows.
NOTE:
to ODU0 non-convergence mode (Any->ODU0), note the following difference in cross-connection
configuration:
 Retain the same values for the other parameters except Source Optical Port.
 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.
6.4.4 Scenario 2: ODU1 non-convergence

mode (Any->ODU1)
convergence mode.
Legend Information
Application Diagram
Figure 2 lists the condition where the TOA board works in ODU1 non-convergence
mode.
Figure 2 Position of the TOA in a WDM system (Scenario 2: ODU1 non-convergence mode
(Any->ODU1))
mode (Any->ODU1))(compatible mode)

board a TN54ENQ2
(standard
mode)
(compatible
mode)
mode (Any->ODU1)) (standard mode)

board a TN54ENQ2
(standard
mode)
(compatible
mode)
Procedure
Expand All
1. Configure the working mode for the TOA board.Set Port Working Mode to
ODU1 non-convergence mode (OTU1/Any->ODU1)
Operation Example:
.
2. Optional:
Operation Example:
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:
: The default value of Service Mode is Client Mode. When you set Service Type to OTU-1,
set Service Mode to OTN Mode
Operation Example:
NOTICE:
5. Configure ODU1-level cross-connections from TOA board to other boards.
Operation Example:
as follows.
NOTE:
to ODU1 non-convergence mode (OTU1/Any->ODU1), note the following difference in cross-
connection configuration:
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.

6.4.5 Scenario 3: ODU1 convergence mode
(n*Any->ODU1)
This section describes the configuration process of the TOA board works in ODU1
convergence mode.
Legend Information
Application Diagram
Figure 2 lists the condition where the TOA board works in ODU1 convergence mode.
Figure 2 Position of the TOA in a WDM system (Scenario 3: ODU1 convergence mode
(n*Any->ODU1))
Figure 3 shows the port configuration of the TOA board.
Figure 3 Cross-connection diagram of the TOA board (Scenario 3: ODU1 convergence mode
(n*Any->ODU1))(compatible mode)

board a TN54ENQ2
(standard
mode)
(compatible
mode)
Figure 4 Cross-connection diagram of the TOA board (Scenario 3: ODU1 convergence mode
(n*Any->ODU1)) (standard mode)

board a TN54ENQ2
(standard
mode)
(compatible
mode)
Procedure
Expand All
1. Configure the working mode for the TOA board. Set Port Working Mode to
ODU1 convergence mode (n*Any->ODU1).
Operation Example:
2. Optional:
Operation Example:
Operation Example:
NOTICE:
NOTE:
 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.
 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.
 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.
4. Configure cross-connections from the client side to ClientLP or ConvGroup ports

on the TOA board.
Operation Example:
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.
as follows.
NOTE:
The service type must be the same as Service Type in the WDM Interface window of the TOA
board.
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:
 Retain the same values for the other parameters except Source Optical Port and
Sink Optical Port.
 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.
5. Configure ODU1-level cross-connections from ClientLP ports to the WDM side on
the TOA board.
Operation Example:
as follows.
NOTE:
to ODU1 convergence mode (n*Any->ODU1), note the following difference in cross-connection
configuration:
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.

6.4.6 Scenario 4: ODU1_ODU0 mode
(OTU1->ODU1->ODU0)
This section describes the configuration process of the TOA board works in
ODU1_ODU0 mode.
Legend Information
Application Diagram
Figure 2 lists the condition where the TOA board works in ODU1 convergence mode.
Figure 2 Position of the TOA in a WDM system (Scenario 4: ODU1_ODU0 mode (OTU1-
>ODU1->ODU0))
Figure 3 shows the port configuration of the TOA board.
Figure 3 Cross-connection diagram of the TOA board (Scenario 4: ODU1_ODU0 mode
(OTU1->ODU1->ODU0))(compatible mode)

board a TN54ENQ2
(standard
mode)
(compatible
mode)
Figure 4 Cross-connection diagram of the TOA board (Scenario 4: ODU1_ODU0 mode
(OTU1->ODU1->ODU0)) (standard mode)

board a TN54ENQ2
(standard
mode)
(compatible
mode)
Procedure
Expand All
ODU1_ODU0 mode (OTU1->ODU1->ODU0).
Operation Example:
2. Optional:
Operation Example:
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:
4. The available values for Service Type is OTU-1 only.

Operation Example:
NOTICE:
5. Configure ODU0-level cross-connections from the TOA board to other boards.
Operation Example:
as follows.
NOTE:
to ODU1_ODU0 mode (OTU1->ODU1->ODU0), note the following difference in cross-
162(ODU0LP2/ODU0LP2) to 168(ODU0LP8/ODU0LP8). When the TOA board is in standard
sink optical port channel does not need to match the source optical port number.

6.4.7 Scenario 5: ODUflex non-
convergence mode (Any->ODUflex)
This section describes the configuration process of the TOA board works in ODUflex
non-convergence mode.
Legend Information
Application Diagram
Figure 2 lists the condition where the TOA board works in ODUflex non-convergence
mode.
Figure 2 Position of the TOA in a WDM system (Scenario 5: ODUflex non-convergence mode
(Any->ODUflex))
 3G-SDI<->ODUflex
 FC400/FICON4G<->ODUflex
Figure 3 Cross-connection diagram of the TOA board (Scenario 5: ODUflex non-convergence
mode (Any->ODUflex))(compatible mode)
Other TN53ND2 / TN53NQ2 / TN53NS2

board
Figure 4 Cross-connection diagram of the TOA board (Scenario 5: ODUflex non-convergence
mode (Any->ODUflex)) (standard mode)
Other TN53ND2 / TN53NQ2 / TN53NS2

board
Procedure
Expand All
ODUflex non-convergence mode (Any->ODUflex).
Operation Example:
2. Optional:
Operation Example:
3. Optional:
The available values for ODU Timeslot Configuration Mode is Assign random
only.
Operation Example:
Operation Example:
NOTICE:
5. Configure ODUflex-level cross-connections from ClientLP port on the TOA board

to other boards.
Operation Example:
as follows.
NOTE:
: 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.
to ODUflex non-convergence mode (Any->ODUflex), note the following difference in cross-
202(ClientLP2/ClientLP2) to 208(ClientLP8/ClientLP8). When the TOA board is in standard
value of Sink Optical Channel is automatically generated by the system.

Osn 8800 Tom Toa Tha

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Osn 8800 Tom Toa Tha

Uploaded by

Copyright:

Available Formats

Configuring WDM Services

6.2 Configuring WDM Services (Manually

 WDM Service Configuration Flow

 Configuring WDM Services for OTU Boards Without Cross-Connect Capability

 Configuring WDM Services for Tributary Boards and Line Boards

Parent topic: Configuration

6.2.1 Basic Concepts

 General Principles for Configuring Electrical Cross-Connections

 Standard Mode and Compatible Mode

6.2.1.1 General Principles for Configuring

 Inter-board Electrical Cross-Connections

 Intra-board Electrical Cross-Connections

Parent topic: Basic Concepts

6.2.1.1.1 Inter-board Electrical Cross-

 Local service pass-through on the WDM side

Configuring Cross-Connections on the U2000

Parent topic: General Principles for Configuring Electrical Cross-Connections

Parent topic: General Principles for Configuring Electrical Cross-Connections

6.2.1.2 Standard Mode and Compatible

Boards Supporting the Standard Mode

Table 1 Board names displayed on the NMS

Name of Board in Standard Name of Board in Board Name (Displayed in

53TDX(STND) 53TDX 53TDX

54THA(STND) 54THA 54THA

54TOA(STND) 54TOA 54TOA

55TQX(STND) 55TQX 55TQX

52ND2(STND) 52ND2 52ND2

53ND2 53ND2(COMP) 53ND2

53NQ2 53NQ2(COMP) 53NQ2

52NS2(STND) 52NS2 52NS2

53NS2 53NS2(COMP) 53NS2

54NS3(STND) 54NS3 54NS3

Name of Board in Standard Name of Board in Board Name (Displayed in

54ENQ2(STND) 54ENQ2 54ENQ2

55NPO2(STND) 55NPO2 55NPO2

When electrical-layer ASON is deployed, there are the following restrictions:

Cross-connect module ODU1 mapping path

Multiplexing module ODU2 mapping path

Service processing ODUflex mapping path

ODU0 mapping path Cross-connection that must be

Table 2 Meaning of ports of the TN53NS2 board

Port Name Meaning

IN/OUT-OCh:1-ODU2:1- Mapping path for ODU0 signals received from the

IN/OUT-OCh:1-ODU2:1- Mapping path for ODU0 signals received from the

IN/OUT-OCh:1-ODU2:1- Mapping path for ODU1 signals received from the

IN/OUT-OCh:1 Mapping path for ODU2/ODU2e signals received from

IN/OUT-OCh:1-ODU2:1- Mapping path for ODUflex signals received from the

IN/OUT WDM-side optical ports

Multiplexing ODU2 mapping path

Service Automatic cross-connection, which does not need

ODU0 Cross-connection that must be configured on the

Table 3 Meaning of ports of the TN53NS2 board

Port Name Description Automatic Cross-Connection

ODU0LP1- Internal logical ports of the board. Automatic cross-connections are

ODU1LP1 Internal logical ports. Each of the Automatic cross-connections are

ODU2LP1 Internal logical ports of the board. Automatic cross-connections are

IN/OUT WDM-side optical ports. -

Comparison of NMS GUIs for Different Modes

GUI on the Navigation Path Compatible Mode Standard Mode

WDM In the NE Explorer, select the See Figure 5. See Figure 6.

Figure 3 Path View (compatible mode)

Figure 5 WDM Interface (compatible mode)

Figure 7 Create Cross-Connection Service (compatible mode)