You may encounter the following errors on the FPC :  

- Minor Errors - XQSS Error code: 0x2300d1

- Major Errors - EA Error code: 0x2400c1

Router1 chassisd[5644]: %DAEMON-3: FPC 16 sent action 0x44 that is not configured 0x2 

Router1 alarmd[10260]: %DAEMON-4: Alarm set: FPC color=RED, class=CHASSIS, reason=FPC 16 Major Errors - EA Error code: 0x2400c1

Router1 craftd[5647]: %DAEMON-4: Major alarm set, FPC 16 Major Errors - EA Error code: 0x2400c1

Router1 : %PFE-3: fpc2 mqss_stream_out_wait_to_drain: Waiting for PHY stream to drain for DSTAT failed - status 29, phy_stream 78 

Router1 : %PFE-3: fpc2 mqss_stream_out_disable: Waiting for PHY stream to drain failed - status 29, phy_stream 78 

Router1 : %PFE-3: fpc2 mqss_fo_stream_port_enable: Disabling PHY stream for egress side failed - status 29, instance 3, phy_stream 78 

Router1 : %PFE-3: fpc2 Error: failed incmtfpc_fm_fo_stream_port_enable: (pfe 3, fab_stream 78 phy_port 2)   

Router1 : %PFE-3: fpc2 cmtfpc_fm_process_fe_cmd: fo_stream_port_enable(3, 78, 23, ...) status:29  

Router1 : %PFE-3: fpc2 mqss_bcmf_icm_recfg_stat_wait_to_set_for_stream: Timeout occured while waiting for reconfiguration status to be set - fab_stream 79 

Router1 : %PFE-3: fpc2 mqss_bcmf_stream_enable: Waiting for reconfiguration status to be set failed - status 29, fab_stream 79 

Router1 : %PFE-3: fpc2 mqss_stream_in_disable: Performing stream disable operations for BCMF failed - status 29, fab_stream 79 

Router1 : %PFE-3: fpc2 mqss_stream_disable: Disabling PHY stream for ingress side failed - status 29, instance 3, phy_stream 79 

Router1 : %PFE-3: fpc2 jnh_ucast_free(3351): Expected BufMod but found JNH 0x23257a380000002e on inst 3, ingress:0 

Router1 : %PFE-3: fpc2 jnh_ucast_free(3351): Expected BufMod but found JNH 0x23257c5c0000002e on inst 3, ingress:0 

Router1 : %PFE-3: fpc2 mqss_bcmf_icm_recfg_stat_wait_to_set_for_stream: Timeout occured while waiting for reconfiguration status to be set - fab_stream 207 

Router1 : %PFE-3: fpc2 mqss_bcmf_stream_enable: Waiting for reconfiguration status to be set failed - status 29, fab_stream 207 

Router1 : %PFE-3: fpc2 mqss_stream_in_disable: Performing stream disable operations for BCMF failed - status 29, fab_stream 207 

Router1 : %PFE-3: fpc2 mqss_stream_disable: Disabling PHY stream for ingress side failed - status 29, instance 3, phy_stream 207 

Router1 rpd[5912]: %DAEMON-3: bgp_recv: read from peer 2001:504:0:2::6447:1 (External AS 6447) failed: Connection reset by peer

Router1 : %PFE-3: fpc2 mqss_dstat_stream_wait_to_drain: Timeout while waiting for the PHY stream 207 to drain - Queue 207 (Invalid: False, Timeout: False, Timestamp: False, Queue Depth: 6602 bytes) 

Router1 : %PFE-3: fpc2 mqss_stream_out_wait_to_drain: Waiting for PHY stream to drain for DSTAT failed - status 29, phy_stream 207 

Router1 chassisd[5644]: %DAEMON-3: <FPC 16> ASIC Error detected errorno 0x002300d1 

Router1 alarmd[10260]: %DAEMON-4: Alarm set: FPC color=YELLOW, class=CHASSIS, reason=FPC 16 Minor Errors - XQSS Error code: 0x2300d1

Router1 craftd[5647]: %DAEMON-4: Minor alarm set, FPC 16 Minor Errors - XQSS Error code: 0x2300d1

Router1 : %PFE-3: fpc2 mqss_stream_out_disable: Waiting for PHY stream to drain failed - status 29, phy_stream 207 

Router1 : %PFE-3: fpc2 mqss_fo_stream_port_enable: Disabling PHY stream for egress side failed - status 29, instance 3, phy_stream 207 

Router1 : %PFE-3: fpc2 Error: failed incmtfpc_fm_fo_stream_port_enable: (pfe 3, fab_stream 207 phy_port 2)   

Router1 : %PFE-3: fpc2 cmtfpc_fm_process_fe_cmd: fo_stream_port_enable(3, 207, 23, ...) status:29  

Router1 : %PFE-3: fpc2 Cmerror Op Set: XQSS(3): XQ-SS[3]: RATE program has fallen behind and exceeded threshold

Cause  
These errors are typically associated with issues in the FPC hardware or a chipset-related fault. In most cases, restarting the FPC can resolve these alarms.

---

Workaround and Resolution  

Follow these steps to troubleshoot and resolve the issue:

1. Verify the FPC Type  
   Ensure that you are working with the correct FPC type by running the following command:  
  > show chassis hardware details

2. Check the FPC Reboot Status and Uptime  
   Confirm if the FPC has been rebooted and review its uptime. This will help determine if there are any recent hardware issues. Use the command:  
   >show chassis FPC details

3. Review Logs for Chipset Errors  
   Examine the system logs for any error messages related to the chipset when the issue occurred. This can help identify if the issue is hardware-related. Run the following commands:  
    >show log messages  
    >show log chassis  
   >start shell pfe network fpc<slot>  
   #show syslog messages
   

4. Clear Alarms by Restarting the FPC  
   If the issue is related to a temporary hardware or software glitch, restarting the FPC will clear the errors. To restart the FPC, use the command:  
     > request chassis FPC slot <X> restart
   

5. No RMA Required  
   In most cases, these alarms can be cleared by restarting the FPC. If the issue persists after restarting, further investigation may be required. However, an RMA (Return Merchandise Authorization) is not needed unless the FPC hardware fails completely.