Problem description

OSN3500 device EFT8 single board, the 4thVC4 is configured with 3VC3 services, the 8thVC4 is configured with VC12 service, when the VC12 service in the 8thVC4 is deleted from the binding, the 3VC3 services of the 4thVC4 bound to the EFT8 single board are interrupted, and TUAIS alarms are reported both at the local end and the peer end. Host version 5.21.13.47, single-board software matching.

Alarm information

TU_AIS is reported on both local and peer side , andW_R_FAILURE alarm is reported on EFT8 single board when service interruption occurs.

Processing

Delete and re-add the VCTRUNK port that was interrupted, and the service is resumed.

Root cause

1, SSN2EFT8 single board has two SD579 chips, the first fourVC4s correspond to the first SD579 and the last four VC4s correspond to the second SD579, the last VC4 of each SD579 can support VC3 or VC12 level of binding, i.e., the fourth and eighthVC4s can support VC3 or VC12 level of binding. Also the working mode of the chip ( VC3 mode or VC12 mode) must be the same as the binding level, otherwise the service cannot be opened normally.

2、When deleting the binding of the last VC4 of SD579 chip, the software will reset the working mode of the corresponding SD579 chip according to the deleted binding level. However, when deleting the time slot of the 8thVC4, the working mode of the second SD579 chip should be set, but the software doesn't judge how many chips it is through the time slot, and it defaults to setting VC12 working mode for the 4th VC4 of the first SD579, and the second SD579 chip will not support VC3 or VC12 mode. VC12 operating mode is set for the fourth VC4 of the first SD579 chip by default, and the second chip is not reset, because the second chip is originally VC12 mode, and it does not affect the business if it is not set, while the first chip is VC3 mode which is mistakenly set to VC12 mode, and so the business is interrupted.

3、When deleting the VC12 or VC3 service binding in the fourthVC4, it will not affect the service of the eighthVC4, because when deleting it, the software will reconfigure the fourth VC mode of the first piece of SD579 by default, so it will not affect the service on the second piece of SD579.

4, there is no such problem when new service is created, because when new service is created, there is a time slot, according to the time slot to determine the first SD579, so the mode is sent correctly, and it will not be under the wrong chip.

Suggestions and Summary

OSN3500 SSN2EFT8 single board, when the time slot level of the configuration of the 4th VC4 and the configuration of the 8th VC4 are not the same, only when deleting one or more VCTRUNKs in the 8thVC4 will affect the service in the 4thVC4, and the operation of the 4thVC4 will not affect the 8thVC4, so you need to pay attention to this issue when deleting the service bindings of the 8thVC4 of the EFT8 single board. Therefore, you need to be careful when deleting the 8th VC4 service binding on the EFT8 board.

Solution:

1. Before the corresponding EFT8 single-board version is released, note that the 4thVC4 and the 8thVC4 are bound to the same time slot level.

2, R & D is expected to release the single board software 7.55 and later ( R9C04SPC200B01k ) version of the solution, this version and R9 supporting, other R version of the matching situation to be evaluated, please provide the host version and the company to confirm the matching situation before use.

END