Description

This article describes about the logs PECHIP_CMERROR_IPW_MISC_INT_EVENTS_OVERSIZE_DROP and NPOA in case of occurrence.

Symptoms

Below logs are reported from customer's device-

 

Nov 23 17:05:51.168 PTX10k2 fpc0 Error: /fpc/0/pfe/0/cm/0/PE_Chip/5/PECHIP_CMERROR_IPW_MISC_INT_EVENTS_OVERSIZE_DROP (0x21002d), scope: pfe, category: processing, severity: minor, module: PE Chip, type: Description for PECHIP_CMERROR_IPW_MISC_INT_EVENTS_OVERSIZE_DROP

Nov 23 17:05:51.185 PTX10k2 fpc0 Cmerror Op Set: PE Chip: PE5[5]: IPW: oversize_drop error

Nov 23 17:05:51.194 PTX10k2 fpc0 T6E(0/0) link[55 0] UP, phy_link_ok: 1 mac_local_fault:0 mac_remote_fault: 0 asic_fault: 0

Nov 23 17:07:22.153 PTX10k2 fpc0 Performing action log for error /fpc/0/pfe/0/cm/0/PE_Chip/5/PECHIP_CMERROR_IPW_MISC_INT_EVENTS_OVERSIZE_DROP (0x21002d) in module: PE Chip with scope: pfe category: processing level: minor

Solution

“Oversize packets: IPW provides a configurable maximum-size limit (in units of 128-byte cells). A received packet which is larger than this maximum is truncated and marked as errored in the notification sent to IngressQueueManager. This is provided to protect the data-path from illegal or out-of-bounds conditions, not to enforce requirements of particular protocols.

 

IPW is ingress packet writer responsible for writing packets into memory while sending notifications to Ingress Queue manager. This error means that an oversize packet was encountered by IPW.”

 

>> This is a transient error and can be ignored. The error should be cleared on its own as part of self healing mechanism.

 

>> If the logs persist over long time with high frequency, please with reboot of FPC in a MW.

 

Modification History

2023-12-04 : Initial Draft