In the MX960 DPCE model 4x 10GE X EQ, customers may observe the following recurring syslog messages, which may impact traffic on the installed Physical Interface Cards (PICs) on the device. This article explains what must be done when this syslog message is seen on the specified router model.
The following messages may be seen in syslog on a recurring basis, with consequent traffic impact on the installed PICs:
user@mx960>show log messages | match fpc7 Apr 27 20:45:01.657 mx960 fpc7 ICHIP(2) Queue Wedge detected in physical queue 7 : mu 1315862 out_pkt_hi 518502 out_pkt_lo 253 dramq empty:false tnq empty:false hnq empty:true Apr 27 20:45:39.657 mx960 fpc7 ICHIP(2) Queue Wedge detected in physical queue 7 : mu 1315862 out_pkt_hi 518502 out_pkt_lo 253 dramq empty:false tnq empty:false hnq empty:true Apr 27 20:45:57.657 mx960 fpc7 ICHIP(2) Queue Wedge detected in physical queue 7 : mu 1315862 out_pkt_hi 518502 out_pkt_lo 253 dramq empty:false tnq empty:false hnq empty:true Apr 27 20:46:03.657 mx960 fpc7 ICHIP(2) Queue Wedge detected in physical queue 7 : mu 1315862 out_pkt_hi 518502 out_pkt_lo 253 dramq empty:false tnq empty:false hnq empty:true Apr 27 20:46:35.658 mx960 fpc7 ICHIP(2) Queue Wedge detected in physical queue 7 : mu 1315862 out_pkt_hi 518502 out_pkt_lo 253 dramq empty:false tnq empty:false hnq empty:true Apr 27 20:46:37.658 mx960 fpc7 ICHIP(2) Queue Wedge detected in physical queue 7 : mu 1315862 out_pkt_hi 518502 out_pkt_lo 253 dramq empty:false tnq empty:false hnq empty:true
The following Major Errors - Error code: 0x4f3 may also be logged:
user@mx960> show log chassisd Apr 27 08:24:27 send: red alarm set, device FPC 7, reason FPC 7 Major Errors - Error code: 0x4f3 <<<<
To resolve the above error, you need to determine whether traffic is impacted or not when the above ICHIP Queue Wedge is detected in physical queue.
If there is no traffic impact, schedule a Maintenance Window to reboot the DPC/MPC that is reporting the alarm. After reboot, ensure that the same alarm is not seen by monitoring the device for 24 hours.
If there is traffic impact, note down the exact time when traffic loss is detected. Check if an error with "Error code: 0x4f3" is seen in the chassisd log for that particular DPC slot number.
Check whether the following "Major Errors - Error code: 0x4f3" error is seen and matches with timestamp of traffic loss:
.... Apr 27 08:24:44 reconnect expired: fpc 7 reconnected Apr 27 08:24:44 FM: fm_is_fec_supported FPC 7 do not support FEC Apr 27 08:24:44 FM: fm_is_fec_supported FPC 7 do not support FEC Apr 27 08:24:44 FM: fm_is_fec_supported FPC 7 do not support FEC Apr 27 08:24:44 FM: fm_is_fec_supported FPC 7 do not support FEC Apr 27 08:24:44 FM: fm_is_fec_supported FPC 7 do not support FEC Apr 27 08:24:44 FM: fm_is_fec_supported FPC 7 do not support FEC
The 0x4f3 problem is a form of hardware problem. Because this may be a transient issue, the first recommendation is to reboot the Dense Port Concentrator (DPC) in a Maintenance Window. If the issue recurs, contact Support for additional assistance. Note: An alternative workaround to recover from this issue is to reconfigure the affected services to a different PIC in the router.
The 0x4f3 problem is a form of hardware problem. Because this may be a transient issue, the first recommendation is to reboot the Dense Port Concentrator (DPC) in a Maintenance Window.
If the issue recurs, contact Support for additional assistance.
Note: An alternative workaround to recover from this issue is to reconfigure the affected services to a different PIC in the router.