Problem description

1、OSN3500 equipment host version is V100R010C03, OSN7500 equipment host version is V100R010C03,

2、Dual-fiber bidirectional multiplexing segment protection ring networking: A-B-C-D-E-F-a trunk ASON-BeijingH network elements, A for the OSN3500, B, C, D, E network elements for the OSN7500 composed of dual-fiber bidirectional multiplexing segment protection environment, E and F composed of 1 +1 linear multiplexing segment ( STM-16 ), F for the DXC equipment, A network elements docking business-side routers, the business through the A-B composed of 1 +1 linear multiplexing segment ( STM-16 ) via B-C-D-E via DXC equipment, A network elements to the business-side router, business via A-B composed of 1 +1 linear multiplexing segment ( STM-16 ) via B-C - D-E through the DXC equipment F network element uplink a trunk ASON network across the provinces to the local network in Beijing.

3, A network element of the 14-slot, 5-slotN4EGS4 single board to open a 400M service to the Beijing local network , a day5-slot to Beijing service is normal, 14-slot to Beijing service interruption , the port to receive packets is normal , no packets sent , no alarms.

Alarm information

No alarm

Processing

1、Beijing local network element H does physical hard loopback to A. A network element's EGS4 single board port in slot 14 receives packets normally , no packets are sent , and there is no alarm .

2、Suspecting that the trunk line in the province to the local fault , from theDXC equipment F network element 8 slot SLQ16-2 port (docking a trunk ASON network element) to the business side of the direction of the optical port and VC4 internal loopback , 14-slotEGS4 single-board port port packet collection is normal , no packets sent , no alarms .

3、Preliminary judgment is local network failure in the province , hang Ethernet tester on the router port on the business side of Network Element A, and do VC4 external loopback from SLQ16-2 in slot 8 of Network Element B to the business side , and the packet collection is normal on the single board port of EGS4, no packet is sent , and there is no any alarm ; 4、Perform EGS4 internal loopback and VC4 internal loopback on slot 14 of EGS4, the packet collection is normal , no packet is sent and there is no any alarm .

4. Configure unidirectional time slot crossover for EGS4 in slot 14(exclude the failure of optical board and crossover in this station ), and packet collection is normal on the port of EGS4 single board , no packet is sent , and there is no alarm .

5. Judging that the port of EGS4 single board in slot 14 is faulty , change the service to the port of EGS4 single board in slot 14, and the port of EGS4 single board in slot 14 receives packets normally , no packets are sent , and there are no alarms .

6、Since there is no other service on the 14-slot EGS4 board, after resetting the 14-slot EGS4 board, the packet collection is normal , no packet is sent , and no alarm is generated .

7. Positioned as hardware failure of EGS4 board in slot 14, change the service to port 2 of EGS4 board in slot 5, and the packets received and sent by EGS4 board ports are normal. The service side test service is back to normal.

8、Troubleshooting is completed , and the reason is caused by hardware failure of EGS4 single board.

Root cause

Hardware failure of EGS4 single board

Solution

Replace the EGS4 board with the same model.

Recommendation and Summary

Hardware failure of EGS4 single board causes the port to send too few packets. When the single-board port receives packets normally and does not send packets, it is recommended to reset the single-board directly.