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>

Reminder

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

upgrade

FAQ-Status Display of the OWSP and the ODUk SPRing Protection Protocol

Publication Date:  2012-07-25 Views:  53 Downloads:  0
Issue Description
Q:
In the ODUSP or the OWSP protection, an SF_RP failure is detected at end A of a service section. In the same service section, an SF_W failure is detected at end B. At this time, SF_R switching is performed in this section. When the SF_W failure is cleared at end B, the SF_R switching is still performed in this section. Why?
Note: This problem does not affect the switching, but it affects the status display of the protection group. 
 
Alarm Information
Null 
Handling Process
A:
To understand the current implementation mode of the OWSP and the ODUk SPRing protection protocol:
The current implementation mode is partial recovery. When the SF occurs in both the working and protection channels, if the SF in only the working channel is cleared, the section still performs the SF_R switching. This is called partial recovery for the SF in only one channel is cleared.
As the short path of end B still receives the SF_P request from end A, end B keeps performing the SF_R switching. When the SF_R switching is performed at end B, regardless of the failure (SF_P or SF_RP) at end A, the short path of end A keeps sending the SF_P request. Therefore, when end B clears the SF_W, it maintains the SF_R, because it cannot determine whether the failure at end A is SF_P or SF_RP. 
 
Root Cause
Null 
Suggestions
Null 

END