To have a better experience, please upgrade your IE browser.upgrade
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.The optical interface frequently reports the start and end of the R_LOS alarm only when the manual alarm inversion mode is set and the alarm inversion is set to Enabled for the optical interface on which the services are available or the self-loop is performed on the fiber. This R_LOS alarm, however, is a fake R_LOS alarm generated when the alarm module is in manual inversion mode. That is, the R_LOS alarm does not actually exist on the board.
2.The R_LOS alarm occurs periodically and lasts about three minutes. In addition, the alarm is immediately reported again after it ends. The reason is that the alarm module verifies the alarms on the board. If the NE software fails to receive the start or end of the same alarm reported from the board in continuous three minutes, the NE software deems that the alarm ends on the board, and the alarm module actively terminates the alarm.
3.The implementation of the alarm verification function on the board is as follows: The alarm module has a task (TBAV) of verifying the alarms on the board. The task increases the verification count of the board alarms received on the NE software by 1 about every one minute. Another task (TBAC) of collecting alarms on the board clears the verification count of an alarm each time the NE software receives the start of the alarm from the board. If the accumulated verification count reaches 3 (within about three minutes) and if the NE software fails to receive the start or end of the same alarm from the board, the NE software deems that the alarm ends on the board. In this case, the alarm module ends the alarm actively. Then, the start of the R_LOS alarm is reported again because the alarm module has one scheduled task to continuously insert the R_LOS alarm to the NE software. This is the phenomenon that you see.
4.The problem occurs on the NE software of only this version instead of the earlier versions because the alarm module fails to clear the verification count in time owing to the rectification of another problem.