Ingress exception counters

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Ingress exception counters

L1 Bithead

Hey, all!

Does anyone know something about FPGA Exception global counters? Especially these counters:

flow_fpga_rcv_igr_INTFNF
flow_fpga_rcv_igr_IPFRAGMENT
flow_fpga_rcv_igr_PROTO

 

I see packet drops on FPGA showed by counter flow_fpga_ingress_exception_err. Also the counter has the same rate as flow_fpga_rcv_igr_INTFNF. I'd like to understand what kind of traffic hits such behavior.

 

Thanks

1 accepted solution

Accepted Solutions

Community Team Member

Hi @m0tash ,

 

The FPGA handles processes like VLAN tagging, routing lookups, and certain Layer 2/3 operations.

 

flow_fpga_rcv_igr_INTFNF = Interface not found. Increments when the fpga receives a packet and cannot find a corresponding interface. 
flow_fpga_rcv_igr_IPFRAGMENT = IP fragmentation. Increments when MTU is exceeded and packets are fragmented.
flow_fpga_rcv_igr_PROTO = Protocol. Increments when unsupported protocols are passed through. 

 

Your "flow_fpga_ingress_exception_err" is an aggregation of the various counters of the fpga. So if the value of "flow_fpga_rcv_igr_INTFNF" is almost exactly the same then its likely the "flow_fpga_rcv_igr_INTFNF" is the reason for your "flow_fpga_ingress_exception_err errors".

 

There could be issues with VLAN tagging like if you are sending traffic with a 802.1q tag for which there is no corresponding sub-interface on firewall, you will see this counter. 

 

Do you notice any specific issues or were you just poking around the counter logs? 

 

 

LIVEcommunity team member
Stay Secure,
Jay
Don't forget to Like items if a post is helpful to you!

Please help out other users and “Accept as Solution” if a post helps solve your problem !

Read more about how and why to accept solutions.

View solution in original post

1 REPLY 1

Community Team Member

Hi @m0tash ,

 

The FPGA handles processes like VLAN tagging, routing lookups, and certain Layer 2/3 operations.

 

flow_fpga_rcv_igr_INTFNF = Interface not found. Increments when the fpga receives a packet and cannot find a corresponding interface. 
flow_fpga_rcv_igr_IPFRAGMENT = IP fragmentation. Increments when MTU is exceeded and packets are fragmented.
flow_fpga_rcv_igr_PROTO = Protocol. Increments when unsupported protocols are passed through. 

 

Your "flow_fpga_ingress_exception_err" is an aggregation of the various counters of the fpga. So if the value of "flow_fpga_rcv_igr_INTFNF" is almost exactly the same then its likely the "flow_fpga_rcv_igr_INTFNF" is the reason for your "flow_fpga_ingress_exception_err errors".

 

There could be issues with VLAN tagging like if you are sending traffic with a 802.1q tag for which there is no corresponding sub-interface on firewall, you will see this counter. 

 

Do you notice any specific issues or were you just poking around the counter logs? 

 

 

LIVEcommunity team member
Stay Secure,
Jay
Don't forget to Like items if a post is helpful to you!

Please help out other users and “Accept as Solution” if a post helps solve your problem !

Read more about how and why to accept solutions.
  • 1 accepted solution
  • 308 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!