The
ipv4_input_set_proto_and_ports
message indicates that a trap occurred when the microcode attempted to interpret data past the end of the packet.
When an ipv4_input_set_proto_and_ports event occurs, a message similar to the following is reported:
fpc1 PPE PPE HW Fault Trap: Count 1, PC 56, 0x0056: ipv4_input_set_proto_and_ports tfeb0 PPE PPE HW Fault Trap: %PFE-3: Count 3, PC 62, 0x0062: ipv4_input_set_proto_and_ports
This can also be seen in connection with this syslog message:
fpc1 LU 1 PPE_12 Errors lmem addr error
The error occurs at the microcode instruction label ipv4_input_set_proto_and_ports. These instructions extract Layer 4 ports from a packet and place them in an internal context. However, a malformed packet is causing the microcode to read past valid lmem memory, thereby causing a hardware (HW) fault. This can occur when a packet Authentication Header length field points past the end of the packet.
Perform these steps to determine the cause and resolve the problem (if any):
1. Collect the show command output to help determine the cause of this message.
Capture the output to a file (in case you have to open a technical support case). To do this, configure each SSH client/terminal emulator to log your session.
show log messages show log chassisd request pfe execute command "show syslog messages" target (fpc/tfeb)# request pfe execute command "show nvram" target (fpc/tfeb)#
2. Analyze the show command output. Look for any related events that occurred at or just before the ipv4_input_set_proto_and_ports message in the syslog or chassisd outputs.
3. If the message only occurs sporadically, infrequently, or both, the PFE is behaving normally and discarding malformed packets. The log message is cosmetic in this case.
4. If the messages continue regularly, then, during a maintenance window (as it will impact transit traffic), try rebooting the associated FPC with the command
request chassis fpc restart slot #, where #
, where # is the number of the FPC referenced in the log message.
5. If these efforts do not resolve the problem, contact your technical support representative to investigate the issue further.