Channel Model of Line-side Ports (OTU, Line or PID Board)

This topic describes differences between the standard and compatibility modes, and impacts of the standard mode upon the Web LCT. Standard mode is brought up to simplify operations and reduce costs, since service configurations are more complex and maintenance is more difficult in the steady compatibility mode, as services grow rapidly.

Availability of the Standard Mode

Standard Mode	Compatibility Mode	OptiX OSN 8800 series	OptiX OSN 6800	OptiX OSN 3800
53ND2	53ND2(COMP)	√	√	x
53NQ2	53NQ2(COMP)	√	√	x
53NS2	53NS2(COMP)	√	√	√
11LOA	-	√	√	√
54ENQ2(STND)	54ENQ2	√	x	x
55NPO2(STND)	55NPO2	√	x	x
55NPO2E	-	√	x	x

NOTE:

Standard mode is supported since the V100R006C01 version of the product that works with the Web LCT V100R005C01.
11LOA board and NPO2E board only support the standard mode.
√ means that the board supports the mode and x means that the board does not support the mode.

Differences Between Board Channels in the Compatible and Standard Modes

Item	Compatible Modes	Standard Mode
OTU channel	The OTU channel is named with a channel ID.	The OTU channel is in encapsulation format of signals.
Internal logical port	The internal logical port are remained.	Internal logical ports are discarded. All ODUk trails are allocated to physical ports.
Number of timeslots	Each service occupies a fixed number of timeslots during service configuration.	Timeslots can be inconsecutive, but must be sufficient for service transmission.

This topic describes differences between NS2 board channels in the standard and compatibility modes using NS2 boards as an example.

Compatibility mode
The board model of 53NS2 boards is shown in Figure 1.
Figure 1 53NS2 board model
- In the compatibility mode, channel numbers are defined to 1, 2, ... The channel number does not show whether the channel is an ODU layer channel or an OTU layer channel. Add internal optical ports and cross-connections of the same level when adding services of a level.
- Ensure that the number of timeslots used by a service is fixed.
- LP port supports the ODUk and ODUk+1 functions. As shown in Figure 1, (ODU0LP1/ODU0LP1)-1 port supports the ODU0 and ODU1 functions. Therefore, alarms cannot be identified as ODU0 or ODU1 alarms if no alarm ID is rooted.
Standard mode
The board model of 53NS2 boards is shown in Figure 2.
Figure 2 53NS2 board model

NOTE:
If an ODUk channel is used, cross-connections cannot be configured on channels of levels involved. For example, if IN/OUT-OCH:1-OTU2:1-ODU2:1-ODU1:1 is used, cross-connections cannot be configured on the IN/OUT-OCH:1-OTU2:1-ODU2:1 and OCH:1-OTU2:1-ODU2:1-ODU1:1-ODU0:1; if cross-connections are configured on IN/OUT-OCH:1-OTU2:1-ODU2:1-ODU1:1-ODU0:1, cross-connections cannot be configured on IN/OUT-OCH:1-OTU2:1-ODU2:1-ODU0:1.
- The channel name shows the encapsulation format, excluding the channel number of the ODUk level. NS2 boards are used as an example. The second ODU0 of the third ODU1 of the first ODU2 on the board is displayed as 53NS2-1(IN1/OUT1)-OCH:1-OTU2:1-ODU1:3-ODU0:2.
- Timeslots can be inconsecutive. Services can be transmitted if the number of timeslots is sufficient. If the maximum bandwidth of the optical port is OTU2, there are three ODU1s remained after an ODU1 service is accessed. The rest bandwidth can be used by any ODU0, ODUFlex or ODU1 services.
- Internal logic ports are discarded and all ODUk trails are allocated to physical ports. Alarms and performance are mapped to specific physical ports. Boards can be located according to alarms for fault detection and maintenance.

Impacts of the Standard Mode on the Web LCT

The change of board models has impacts on operations on the Web LCT. This topic describes how the change of board models affects the Web LCT using NS2 boards as an example.

Path View:
In the NE panel, select a board, double-click or right-click the board icon and choose Path View from the shortcut menu.
SM Overhead:
In the NE Explorer, click the desired NE and choose Configuration > OTN Overhead Management > SM Overhead from the Function Tree.
TCM Overhead:
In the NE Explorer, click the desired NE and choose Configuration > OTN Overhead Management > TCM Overhead from the Function Tree.
Create Cross-Connection and Create SNCP Service:
Create Cross-Connection:
1. In the NE Explorer, click an NE and choose Configuration > WDM Service Management from the Function Tree.
2. On the WDM Cross-connection Configuration tab, click New to create a cross-connection.
Create SNCP Service:
1. In the NE Explorer, click an NE and choose Configuration > WDM Service Management from the Function Tree.
2. On the WDM Cross-connection Configuration tab, click Create SNCP Service in the lower pane.
WDM Interface, ODUk SPRing, PM Overhead, Performance and Alarm:
- WDM Interface:
  In the NE Explorer, select a board and choose Configuration > WDM Interface from the Function Tree.
- ODUk SPRing:
  In the NE Explorer, click an NE and choose Configuration > ODUk SPRing from the Function Tree.
- PM Overhead:
  In the NE Explorer, click the desired NE and choose Configuration > OTN Overhead Management > PM Overhead from the Function Tree.
- Performance:
  In the NE Explorer, click a board and choose Performance from the Function Tree.
- Alarm:
  In the NE Explorer, click a board and choose Alarm from the Function Tree.