Malformed packets cause Cisco Catalyst OS (CatOS) 7.x code to display %SYS-4-SUPERVISOR_ERR:Forwarding engine IP errors.
These error message counters are recorded in the syslog:
%SYS-4-SUPERVISOR_ERR:Forwarding engine IP length error counter =4
%SYS-4-SUPERVISOR_ERR:Forwarding engine IP too short error counter =1
%SYS-4-SUPERVISOR_ERR:Forwarding engine IP check sum error counter = 38
These messages indicate the switch forwarding engine has received an IP packet which is below the minimum length of the allowed IP packets, and the forwarding engine is dropping it. In older CatOS code, the packet was silently dropped with no corresponding error messages and counted in the forwarding engine statistics. In newer supervisor codes (CatOS 7.x and later), this message error is recorded in the syslog once every 30 minutes.
The switch normally drops malformed packets. The root cause is not the switch itself, but a device connected to it. A connected device sends the malformed packets. The causes of this issue include a bad Network Interface Card (NIC) driver, a NIC driver bug, or a misbehaving application.
Note: Use a network sniffer to track down the source address.
To disable these error messages, issue the set errordetection portcounters disable command on the switch. This action does not fix the root cause; to fix the cause, the offending device must be discovered.
I have set up my DHCP Pool to bind by Interfaces' as the Client ID for example:Pool Marquees :
Utilization mark (high/low) : 100 / 0
Subnet size (first/next) : 0 / 0
Total addresses : 254
Leased addresses : 0...
Inviting all network professionals in operations! We'd like to understand what would be valuable for you in a mobile application. Your response will help Cisco improve a product feature that could benefit you. Thanks!
Click here to take the sur...
hi everybody!I've issue with load balancing mechanism on asr1001xChassis type: ASR1001-X
Slot Type State Insert time (ago)
--------- ------------------- --------------------- -----------------
0 ASR1001-X ...
At below, it's the message I found in syslog, and this "junk" fills up the syslog. The source ip is Cisco Prime Infrastructure. I checked the switch login credential in CPI and it's correct. Can anyone tell me why the user name is empty and CPI tries to l...
Hello, I'm having troubles getting NAT to work with two WAN interfaces dynamically. We don't have a range of IP's to create a pool from each ISP, so was just doing a NAT overload on the individual interface. Below is our configuration with any public IP's...