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?
Данный сайт есть в английской версии. Желаете ли Вы перейти на английскую версию?
The OptiX OSN 8800 equipment is installed at stations A, B, and C to form an ODU2 SNCP SPRing. Two NQ2 boards and one TQX board are configured at each of stations A and C. The NQ2 board in slot 2 is the working board, the NQ2 board in slot 13 is the protection board, and the TQX board in slot 22 is used as a tributary board. Configuration of a service with SNC/N protection fails and the system displays a message indicating mismatch between the settings of the working channel overheads and the protection levels of the protection group and the error code is 41907.The NE software version is 126.96.36.199.
1. After the SNC/N protection group is configured, you must set non-intrusive monitoring of the PM overhead on the working and protection channels of the NQ2 board to Enable. In this manner, the SNC/N protection group can monitor the PM section and the ODU2 SNC/N protection switching can be triggered properly.2. The ODU2 SNC/N protection detects service signals according to states of the ODU2 overheads in the PM section. The NE considers enabling of the ODU2 non-intrusive monitoring as a monitoring condition of the protection group. Therefore, you need to enable the non-intrusive monitoring of the PM overhead on the corresponding working/protection channel before configuring the service with SNC/N protection. Otherwise, configuring the service with SNC/N protection fails.