The EFT board of the Metro 1000 is interconnected with the data board of the S200 of vendor Z. After the overhead settings are modified, the service interconnection fails but no alarm is reported at both ends. The NE software version of the Metro 1000 is 5.42.03.12.
1. The Metro 1000 generates alarms such as LP_TIM_VC12, LP_SLM_VC12, LP_RDI_VC12, HP_TIM, J0_MM, and VCAT_LOA.2. The equipment of vendor Z generates alarms such as the VCG loss alarm.
1. Modify the outgoing and expected bytes of Huawei Metro 1000 so as to remove the LP_TIM_VC12, LP_SLM_VC12, and LP_RDI_VC12 alarms.
2. Change the V5 byte of Huawei Metro 1000 to GFP mapping, and enable LCAS on the equipment of vendor Z. The VCG loss alarm generated by the equipment of vendor Z is removed and the VCAT_LOA alarm generated by Huawei Metro 1000 is removed.
3. The two ends do not generate any alarm, but the service interconnection still fails.
4. Check the settings: EFT > Internal interface > Encapsulation and Mapping. Change the default check field length parameter FCS32 to None. The services become normal.
1. The LP_TIM_VC12, LP_SLM_VC12, and LP_RDI_VC12 alarms are caused by the inconsistency of J0, J1, and J2 bytes during the interconnection.
2. The VCG loss alarm generated by the equipment of vendor Z is caused by the inconsistency of V5 and K4 bytes during the interconnection.
1. This case provides supplementary information for the original case SC0000451758 about the interconnection failure between the Metro 1000 and the data board of vendor Z.
2. For the interconnection between the Metro 1000 and the data board of vendor Z, you need to set the V5 byte on the Metro 1000 and set the LCAS function on the equipment of vendor Z. You also need to set the check field length parameter used for encapsulation and mapping on the Metro 1000. For details on the settings, refer to the attachment.