A problem with EOS (Ethernet over SDH)

expansion Highlighted
Created:  Aug 6, 2022 14:25:33Latest reply: Aug 15, 2022 10:35:59 312 59 35 0 0
View the author 1#

Hi, 

- Today I want to share a case with you when a customer complained that he
can’t expand the EOS link between 2 NEs OSN7500 using N4EGS4 board.
 

Description
- The costumer have 2 * SDH OSN7500 in 2 sites. they are connected
through leased DWDM channel, the customer is responsible of his services
configuration in the 2 sites.

-  As he complained that he can’t expand his EOS services with 10Mb
(5xvc12) , we moved to his site to check.

- The OSN7500 version is VI00R010C03 and the board is N4EGS4 version is

(1.17), it is well known that N3EGS4 and N4EGS4 boards can use 16XVC4
the VC4 no.1-4 & 9-12 can be used for binding services in the level of VC12,
VC3 and VC4 while VC-4s  5-8 & 13-16 support the binding of VC-4 and
VC-3 paths only.

- And it is unallowed to use both VC12 and VC3 paths in the same VCTrunck
to get the needed bandwidth.
 Board type and version

-In our case the VCtrunk no. 24 has 40 x VC12 taken from VC4 no.1,2,4 as
the VC4 (1,2,4) are full so the customer tried to add vc12 from the available
VC4 no.9, but the following message appeared.
 before expand

alarm message

-The same alarm message appeared when try to add VC12 from VC4
no.10,11 or 12.

By trying the configuration of adding VC12 from VC4 no.9,10,11,12 with

other VCTrunck, the configuration worked and was totally normal.

The case was clear that there is a kind of limitation in the using of VC12 from
several (VC4)s.
After referring to HedEX the same NE version, we found that VC-4s
numbered 1-4 and VC-4s numbered 9-12 of the N3EGS4, N4EGS4 belong to
two areas. VC-12 binding must not span the two areas.

hedex

Acording to the previous ,we needed to evacuate some VC12s from the VC4
no.1-4 then use it for our expansion.

so we swapped some VC12s of another service using only the VC4 no.1 to
VC4 no.9 and then used these VC12 in VC4 no.1 for our service expansion.

After Expansion

Welcome to feedback