Questo sito utilizza cookie di profilazione (propri e di terze parti) per ottimizzare la tua esperienza online e per inviarti pubblicità in linea con le tue preferenze. Continuando a utilizzare questo sito senza modificare le tue preferenze acconsenti all’uso dei cookie. Se vuoi saperne di più o negare il consenso a tutti o ad alcuni cookie clicca qui>
The website that you are visiting also provides Arabian language. Do you wish to switch language version?
يوفر موقع الويب الذي تزوره المحتوى باللغة العربية أيضًا. هل ترغب في تبديل إصدار اللغة؟
The website that you are visiting also provides Russia language Do you wish to switch language version?
Данный сайт есть в английской версии. Желаете ли Вы перейти на английскую версию?
1.Configures cross-connections in the NE Explorer.
2.Searches for trails based on the cross-connections on the network.
3.Deactivates the trails.The services are interrupted.
4.Activates the trails. The services are still interrupted. In normal conditions, services are restored after trails are activated.
5.Queries cross-connections on NEs.The selective receiving cross-connections of trails do not exist on NEs
Create cross-connections on NE Explorers and apply services by trail search.
When a problem occurred, restart the NMS and activate the service on the NE Explorer.
Cause analysis based on the NMS
1.The NMS needs to reallocate protection group IDs when the NMS activates trails for ASON NEs.
2.When SNCP and MSP 1+1 are configured, the NMS needs to reallocate protection relationship to differentiate working services from protection services.
3.Two protection groups (one working group and one protection group) associate with each other by using the working group ID as the associated protection group ID.
4.Cross-connections applied to NEs are generated by the sink and source information of the protection group in the working trail.The NMS reallocates protection group IDs when trails are activated. However, the associated protection group ID in the database rather than in the memory is refreshed due to refreshing data failures. Therefore, the working and protection groups cannot associate with each other during service activation without the correct associated protection group ID. As a result, the working service is considered the protection service by mistake. The working services are not applied to NEs.
Cause analysis based on user operationsFailure to create E2E protection groups and restore services after reactivation