This read-only Counter64 counts queries discarded because there was no server-side logical interface configured to relay them. A running count on a subscriber-facing port usually points to an incomplete multicast/IGMP-proxy configuration on that logical interface rather than an actual traffic problem; because it is drawn from the most recently completed 24-hour bin, frozen once the day rolled over, it is frozen and safe to use for day-over-day comparison, since no further traffic will ever be added to it. On a residential VLAN used for multicast video delivery, a count of 3,402 over the last completed collection window 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.