Why CES Service Cant be Created In the P-OTN Network

Hi,
Today I want to share a case with you, when I couldn’t create CES
services in our new P-OTN network.
 
 Introduction
P-OTN is a Transmission system and technology that allows networks to
operate multi Transmission services at the same time using one NE and
one pair of fiber, P-OTN used when operator needs to transmit native
TDM, Packet and OTN in the same network.
We have new P-OTN network that consist of Huawei OSN9800-U32E,
OSN1800V, OSN1800II-E, OSN1800I-E.
 
Description
we usually need to transmit TDM over packet using CES(Circuit
Emulation Services), to provide E1 for 3G mobile provider.

CES service creation 

Today when I come to create PW-CES service from OSN1800II to

another OSN1800II using trail, The PW creating succeeded but related
operation failed.
In the details the reason is (PW type is incorrect)
 creation succeded partially

The PW-CES service got created but partially deployed and partially
enabled.

partially deployed, partially enabled

Also with major alarms in both source and sink MD1 boards
( CES_LOSPKT_EXC ).

CES_LOSPKT_EXC

Analyzing and solution

After reviewing the service type, Boards, path and tunnels, we found that
everything is normal and no problem.
Checking the NEs along the path, the service generated and ended in
OSN1800II-E, passed through OSN1800V, OSN9800-U32E.
Referring to the Hedex for further NE capabilities and details, we found
that OSN9800-U32E doesn’t support CES as it intended for a very high
capacity and services.
The CES services wasn’t generated or ended in the OSN9800-U32E but
the service was passing through it and PW needed to change the tunnel
in the OSN9800-U32E using MS-PW.
So we just excluded the OSN9800-U32E of the path of the service and
tried again, then service got created normally with no problem.

exclude OSN9800-U32E 

Note :-
OSN9800-U32E is a core node where slot have 1Tera capacity and not
intended to be used for low traffic services.
 
 
Welcome to feedback

This is a valuable case. I had a similar service scenario before, the core site is OptiX OSN 9800 U32,
and the branch site is OptiX OSN 1800V. The core site is a large-scale router that uses the 622M C-
POS interface to connect to the STM-4 interface of the OptiX OSN 9800 U32. A branch site is a small-
sized router that uses E1 interfaces to connect to the E1 interfaces of the OptiX OSN 1800V.