Cant Create PWE3 Service Through

OSN1800I-E Highlighted
Created:  Oct 26, 2021 08:34:43Latest reply: Feb 8, 2022 16:03:39 1324 48 25 0 2
View the author 1#

Cant Create PWE3 Service Through OSN1800I-E

Hi ,

Today, I want to share with you a case, about a problem happened while
Creating PWE3 Service in OSN1800I-E PTN in our network.

 Description

We build our new PTN network based on Huawei MS-OTN OSN-1800

-  

series , we use OSN1800V and OSN1800II-E as aggregation and OSN1800I-

E as access. After creating a tunnel between every adjacent NEs successfully ,
We start creating a new PWE3 ethernet service that source in OSN1800I-E
then passes through another OSN1800I-E and the sink in OSN1800II-E , a
message indicating that ( The Transaction is empty ) and the trail state is
(partially deployed).
 The Transaction is empty

The Problem Cause

-we tried to create the same service in another link has only OSN1800II-
E(Type2) NEs and it worked so, we realized that the problem exist only in the
OSN1800I-E(Type1), the limitation is related of creating a PW transiting in
NEs in the middle , or what called MS-PW (Multi- Segment PW).

- According to the HedEX in the version of our NEs V100R019C10 the

OSN1800I-E doesn’t support MS-PW.

Demonstration
- An MS-PW consists of multiple adjacent PW segments, and each PW
segment is a point-to-point PW , when NE support MS-PW the PWs can
transit in the NE and travel across several Tunnels.

-The Transit NE called ((PW Switching Provider Edge (S-PE)) , The S-PE
can terminate the tunnel labels of the tunnel packet, and switch the PW labels,
An MS-PW must transit an S-PE.

- MS-PW is so useful to decrease the number of needed tunnels , aggregate

services going to the same destination and enhance protection through
making services going through diverse tunnels ,therefore have more potential
routes to the destination.

                                                                                                 MS-PW

Solution

-The only way to let the PW travel through several NEs which don’t support
MS-PW , is by creating Static Tunnel from source NE to Sink NE, or from
source NE to an NE supports MS-PW like OSN1800V or
OSN1800II(Type2).
 Direct PW through Static tunnel

-After creating StaticTunnel from the source NE OSN1800-I (Type1), passing

through another NE OSN1800-I then to the sink NE OSN1800-II (Type2).

the PW passes through the NEs that doesn’t support the MS-PW, and the
service worked normally.

Welcome to feedback