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?
Данный сайт есть в английской версии. Желаете ли Вы перейти на английскую версию?
EVDO signaling link interrupted from BTS to BSC and after giving reset to BCIM, link came up.
218 HSIA sites are down for delhi (Kindly support packet capture and NE40 logs collection required for end to end tracing of the issue from BSC to BTS.)
During the outage time we observed that there was alram occured at BTS and BSC end and there was no alram found on the router end.
But at same time we are able to ping the BTS and BSC end IP's and learnig the MAC address of the equipment also.
Ping result is attached below with file name "Site 644 in testing 01-46 AM" .
There after we decided to capture the TCP packets at our NE40E end port .
During the MUX switchover, and the TCP request was sent by BTS, received by BTS END MUX, but not received BSC, and it also not received by NE40 during , thus we can say the TCP request was lost somewhere between NE40 AND BTS END MUX.
Base on the analysis of BTS110 AND BTS103, we found that BSC cannot receive the BTS TCP request after switching over MUX, so DO signaling link interrupted. BTS has sent the TCP request and received by BTS END MUX, but NE40 and BSC cannot receive it, only after giving reset to BCIM, TCP request was received by BSC, DO signaling link re-connected. So we are strongly suspecting the transmission between NE40 and BTS end MUX are abnormal, which will lead to DO link interruption and it cannot restored automatically.
Change the TX device
Need to check the Third part TX equipment why it is droping the TCP packets