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 this table's currently-accumulating, short-interval bin, it reflects only the last few minutes of activity, so it's the value to watch for a fast-forming problem rather than a long-term trend. On an uplink toward the multicast-enabled core router, a count of 3,087 over the last 15 minutes 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.