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 instance's running statistics bin, it behaves like a long-running total rather than a rotating window, so admins baseline against it instead of expecting it to reset daily. On an access port serving a multi-dwelling unit, a count of 3,727 over the current statistics 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.