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 short-interval historical bin, it is a closed record of the interval right before the current one, useful for checking whether a problem seen right now had already started in the previous window. On a metro aggregation uplink carrying several video EVCs, a count of 737 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.