Reasons for IfInDiscards

There are several common causes for IfInDiscards events:

■

Each frame arriving at a network port that is not logically connected using a map, or map-passall command is counted as an IfInDiscard.

■

When a destination tool port’s link status is down, frames destined only for that tool port are discarded at the network port interfaces for map, map-passall, and tool-mirror commands and counted as IfInDiscards.

■

Frames that do not match any allow type map rule are discarded and counted as IfInDiscards.

■

When a drop type map rule is applied to a port, all frames that meet the map rule criteria are discarded and counted as IfInDiscards.

■

All pause frames received at a network port are discarded and counted as IfInDiscards.