The Speed of Inspection of OSN3500II Type Equipment is Slow

The inspection of OSN3500II equipment is slow. It takes 1-2 days to inspect a set of OSN3500II equipment.

Processing process

1. there are two OSN3500II devices in the existing network, which all have this problem and can basically eliminate the main board problem.

2. due to the shortage of existing OSN3500II network stock, it is doubtful whether it is equipment specification.

3. recommend the on-site feedback log of the OSN3500II device, because the network element that has not completed the inspection does not generate a log, and the command line tool is used manually to view the result of the return.

4. the inspection use case of the current inspection tool, "check whether the 485 communication between the cross board and the business single board is normal" to check the OSN3500II subframe, the script does have the optp:[format%x $bid], 0,96,1,30,06, [format%x $xcsbid], 1,0,0,0, F, 0,1 and so on, but the power board does not support the above command, It will wait until the command execution timeout results in slow progress.

5. all current versions have this problem (the latest V2R9C00SPC206), which will be resolved in the later version of the inspection tool. The version is not yet confirmed. The current circumvention measures can not use the use case of "check whether the 485 communication between the cross board and the business board is normal" in the inspection tool.

Root cause

Inspection use case of inspection tool, "check whether the 485 communication between the cross and business single board is normal" to check the OSN3500II subframe, the script does go down the power board 1 slot: optp:[format%x$bid], 0,96,1,30,06, [format%x $xcsbid], 1,0,0,0, F, 0,1 and other related optp commands, but the power board does not support the above command, will be one Wait until the command execution timeout results in slow progress in the inspection process.

Solution

1. recommend the on-site feedback log of the OSN3500II device, because the network element that has not completed the inspection does not generate a log, and the command line tool is used manually to view the result of the return.

2. research and development confirm the inspection use case of the current inspection tool, "check whether the 485 communication between the cross board and the business single board is normal" to check the OSN3500II subframe. The script does have the optp:[format%x $bid], 0,96,1,30,06, [format%x $xcsbid], 1,0,0,0, F, 0,1 and other related optp commands, but the power board is not supported by the power board The command will wait until the command execution timeout results in slow progress.

3. R & D validation will solve this problem in the latest version of the inspection tool. The version is not yet confirmed. The current circumvention measures can not use the use case of "check whether the 485 communication between the cross board and the business board is normal" in the inspection tool.

More informaiton about Huawei OSN3500, welcome to contact us.