NPO2 Board Service Configuration

On the U2000 Web LCT, each optical interface on the NPO2 board has a serial number, and the logical ports of the board are provided.

Display of Optical Interfaces

Table 1 lists the serial numbers of the optical interfaces on the front panel of the board displayed on the NMS.

**Table 1** Serial numbers of the interfaces on the NPO2 displayed on the NMS
Interface on the Front Panel	Interface on the NMS
IN/OUT	1

NOTE:

The number of an interface displayed on the U2000 Web LCT indicates a pair of physical optical interfaces, of which one is used to transmit signals and the other is used to receive signals.

Port Description

The TN55NPO2 board can work in standard or compatible mode, and the TN54NPO2 board can work only in compatible mode.

NOTE:

For information about the standard and compatible modes of the board, see the Product Description.

Figure 1 shows the board model of the TN55NPO2/TN54NPO2 board in compatible mode. Table 2 lists the descriptions of the ports on the board.
Figure 2 shows the board model of the T55NPO2 board in standard mode. Table 3 Lists the descriptions of the ports on the board.

Figure 1 Diagram of ports on the TN55NPO2/TN54NPO2 (compatible mode)

NOTE:

There are cross-connections between ports 141 (OCHLP9/OCHLP9)-1 to 144 (OCHLP12/OCHLP12)-1 on the NPO2 board and ports 71 (ODU2LP1/ODU2LP1)-1 to 74 (ODU2LP4/ODU2LP4)-1 on the ENQ2 board. You do not need to configure these cross-connections on the U2000 Web LCT.

	Cross-connect module		ODU1 mapping path
	Multiplexing module		ODU2 mapping path
	Service processing module		Automatic cross-connection, which does not need to be configured on the NMS. For example, if 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 mapping path		Cross-connection that must be configured on the NMS to receive ODUk signals from other boards

**Table 2** Meaning of ports on the TN55NPO2/TN54NPO2 (compatible mode)
Port Name	Meaning
ODU0LP1-ODU0LP32	Internal logical ports. The optical paths are numbered 1 and 2.
ODU1LP1-ODU1LP8	Internal logical ports. The optical paths are numbered 1, 2, 3 and 4.
ODU2LP1-ODU2LP8	Internal logical ports. The optical paths are numbered 1.
OCHLP1-OCHLP12	Internal logical ports. The optical paths are numbered 1.
IN/OUT	This port corresponds to the WDM-side optical interface.

Figure 2 Diagram of ports on the TN55NPO2 (standard mode)

NOTE:

ODU0, ODU1, ODU2, and ODU2e signals carried over the NPO2 board's OCH9 to OCH12 channels are processed on the TN54ENQ2 board.

The OCH9 to OCH12 optical channels only receive the signals coming from the TN54ENQ2 board.

If an ODUk channel has been used, cross-connections cannot be configured on any other channels that correspond to the ODUk channel, regardless of the rate level. For example, if channel 1(IN/OUT)-OCH:1-ODU2:1-ODU1:1 has been used, cross-connections cannot be configured on channel 1(IN/OUT)-OCH:1ODU2:1 or 1(IN/OUT)-OCH:1-ODU2:1-ODU1:1-ODU0:1.

The NPO2 board's OCH5 to OCH8 optical channels are available only when the board works with the TN54PQ2 service processing board.

	Cross-connect module		ODU1 mapping path
	Multiplexing module		ODU2 mapping path
	Service processing module		Cross-connection that must be configured on the NMS to receive ODUk signals from other boards
	ODU0 mapping path

**Table 3** Meaning of ports on the TN55NPO2 (standard mode)
Port Name	Meaning
1(IN/OUT)-OCH:(1-12)-ODU2:(1-12)-ODU1:(1-4)-ODU0:(1-2)	Indicates the mapping path for the ODU0 signals that are received through the backplane.
1(IN/OUT)-OCH:(1-12)-ODU2:(1-12)-ODU1:(1-4)	Indicates the mapping path for the ODU1 signals that are received through the backplane.
1(IN/OUT)-OCH:(1-12)-ODU2:(1-12)	Indicates the mapping path for the ODU2/ODU2E signals that are received through the backplane.
1(IN/OUT)	Indicates the WDM-side port.

Cross-Connection Configuration of Services

When the NPO2 is used to transmit services, cross-connections must be configured on the U2000 Web LCT. For information on how to create ODU0 cross-connections, see Figure 3 and Figure 4. For information on how to create ODU1 cross-connections, see Figure 5 and Figure 6. For information on how to create ODU2 cross-connections, see Figure 7 and Figure 8.

shows configuration of cross-connections from other boards to the NPO2 board. The configuration enables add/drop of client-side services on the line at the local site.
shows configuration of cross-connections from other boards to the NPO2 board. The configuration enables line-side services to pass through the local site.

NOTE:

Cross-connections can be configured between the boards working in standard mode and the boards working in compatible mode.

Figure 3 Diagram of cross-connections of the TN55NPO2 (ODU0 level)

Other board a	TN52TOG/TN52TOM/TN54THA/TN54TOA
Other board b	TN52ND2/TN53ND2/TN52NQ2/TN54NQ2/TN53NQ2/TN53NS2/TN52NS2/TN52NS3/TN54NS3/TN55NPO2/TN54ENQ2
Other board c	TN53NS2/TN53ND2/TN53NQ2/TN55NPO2/TN55NPO2E/TN54ENQ2

Figure 4 Diagram of cross-connections of the TN54NPO2 (ODU0 level)

Other board a	TN52TOG/TN52TOM/TN54THA/TN54TOA
Other board b	TN52ND2/TN53ND2/TN52NQ2/TN54NQ2/TN53NQ2/TN53NS2/TN52NS2/TN52NS3/TN54NS3/TN55NPO2/TN54ENQ2
Other board c	TN53NS2/TN53ND2/TN53NQ2/TN55NPO2/TN55NPO2E/TN54ENQ2

Figure 5 Diagram of cross-connections of the TN55NPO2 (ODU1 level)

Other board a	TN52TOG/TN52TOM/TN54THA/TN54TOA
Other board b	TN52ND2/TN53ND2/TN53NQ2/TN52NQ2/TN54NQ2/TN53NS2/TN52NS2 /TN52NS3/TN54NS3/TN55NPO2/TN54ENQ2
Other board c	TN53NS2/TN53ND2/TN53NQ2/TN55NPO2/TN55NPO2E/TN54ENQ2

Figure 6 Diagram of cross-connections of the TN54NPO2 (ODU1 level)

Other board a	TN52TOG/TN52TOM/TN54THA/TN54TOA
Other board b	TN52ND2/TN53ND2/TN53NQ2/TN52NQ2/TN54NQ2/TN53NS2/TN52NS2 /TN52NS3/TN54NS3/TN55NPO2/TN54ENQ2
Other board c	TN53NS2/TN53ND2/TN53NQ2/TN55NPO2/TN55NPO2E/TN54ENQ2

Figure 7 Diagram of cross-connections of the TN55NPO2 (ODU2 level)

Other board a	TN52TDX/TN53TDX/TN55TQX/TN52TQX/TN53TQX
Other board b	TN52ND2/TN53ND2/TN53NQ2/TN52NQ2/TN54NQ2/TN53NS2/TN52NS2/TN52NS3/TN54NS3/TN55NPO2/TN54ENQ2
Other board c	TN53NS2/TN53ND2/TN53NQ2/TN55NPO2/TN55NPO2E/TN54ENQ2

Figure 8 Diagram of cross-connections of the TN54NPO2 (ODU2 level)

Other board a	TN52TDX/TN53TDX/TN55TQX/TN52TQX/TN53TQX
Other board b	TN52ND2/TN53ND2/TN53NQ2/TN52NQ2/TN54NQ2/TN53NS2/TN52NS2/TN52NS3/TN54NS3/TN55NPO2/TN54ENQ2
Other board c	TN53NS2/TN53ND2/TN53NQ2/TN55NPO2/TN55NPO2E/TN54ENQ2

Figure 9 Diagram of cross-connections between the TN55NPO2 and ENQ2

Figure 10 Diagram of cross-connections between the TN54NPO2 and ENQ2

Example of Service Cross-Connections

Figure 11 shows an example of service cross-connections on the NPO2 board. One board can transmit a hybrid of ODU0, ODU1, ODU2 and ODU2e signals.

Figure 11 Example of service cross-connections on the NPO2 board