No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


FAQ-ETH-loss due to different MTU between Huawei and third party

Publication Date:  2012-07-25 Views:  124 Downloads:  3
Issue Description
In X project we have Huawei equipment RTN 980 including EM6F card and third party which is connected to the RNC ,in order to generate our 3G date through Huawei equipment we detect alarm Eth_los and cleared after 2 Sec appearance and for the third party they lost the data and did not received the all of frames required ,so after investigation we found that the maximum frame length from our side and the third party is different .  

Alarm Information

Handling Process
1-We detect the Maximum frame length in huawei is different than third party which is in huawei which is connected to the NodeB 1522 and the other party which is connected to the RNC is 1500 so adjust the both sides as the same 1522 to be the Maximum Frame Length in both Sides is the same.

Root Cause
"1"- The negotiation fails because the transmit port and receive port work in different modes.
"2"- The cable is faulty.
"3"- The local NE is faulty.
"4"- The opposite NE is faulty.
"5"- Change the EM6F card.

 But after all this trials the alarm still appear so we check he Maximum frame length at Both Sides and we detect that   it is different than each other.

"1"-Check the cable and the card.
"2"-Check the maximum speed auto negotiation is the same.
"3"-The Maximum transfer unit is the same.