No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Activating path failed due to cross connect is not deleted from NE level

Publication Date:  2012-07-25 Views:  108 Downloads:  0
Issue Description
While trail creation on OSN2500 equipment the following information was reported “Trail creation succeeded but related operation failed, Error Code: 81940” and “The SNCP protection group object already exists, Error Code:38687” and “Activating path failed, Error Code:82152”
Although in SDH Service configuration there is no such existing service. The necessary VC12 timeslots are not occupied.
Alarm Information
“Trail creation succeeded but related operation failed, Error Code: 81940” 
“The SNCP protection group object already exists, Error Code:38687” 
“Activating path failed, Error Code:82152”
Handling Process
In Order to get this lost cross connect and delete discrete service do as follows:
- upload NE configuration from NE level to T2000 level
- Query SDH Service configuration
- Trail Search
- Delete discrete service
- Configure trail again
Root Cause
This kind of problem can be met on OSN1500/2500/3500 equipment. Sometimes after deleting trails some cross-connect are deleted from T2000 level and are not deleted form NE level. The possible reason  is that customer often use T2000 Server and Client on different PC and in different places. After a command is issued it takes some time to transfer it from T2000 Client PC to T2000 Server PC and then to hardware. Sometimes another operation is issued while the previous operation is not finished on hardware level.  Another possible reason is that customer did not  delete the trail from end to end, for example just delete some part of trail,  it could cause discrete service.
To handle the problem refer to the previous chapter.