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?
Данный сайт есть в английской версии. Желаете ли Вы перейти на английскую версию?
After analysis i found that protocol was unstarted in Protection Group. I tried to start that protocol from T2000, but it failed to start the protocol. I deleted that ring from NM layer and then created again, but still protocol was unstarted for this particular NE. Protocol of other NEs in this ring were started and normal.
After anlysed the cause deeply, we found the issue was caused by the inconsistent software. When the slave XCS board which is used the lower version than that of working board, it will make the data synchronization from the working board automatically in case of hard reset or power on. But the slave XCS board which is used the later version than that of working board will not make the activity in that case.
Because the vesions between the active board and the standby board are different and the format of files partition are also different, so the data synchronization will be out-of-order and leads to the abnormal state of MSP.