This read-only Counter64 counts IGMP packets dropped because the switch ran out of internal resources to process them. This is the counter that shows real control-plane overload — sustained increases mean the incoming IGMP message rate on this instance is outrunning the snooping/proxy engine's capacity, the first symptom of an IGMP flood; because it is drawn from the current, still-open 24-hour bin for today, the number keeps climbing until midnight rollover, so it should be read as "so far today" rather than a finished daily total. On an access port serving a multi-dwelling unit, a count of 1,190 over today so far is the kind of number an admin would trend against the join/leave rate on the same port to judge whether it's normal channel-surfing or an anomaly worth a closer look.