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 lifetime bin, which keeps accumulating until an operator explicitly clears it, a sudden plateau on an otherwise busy instance is itself a signal — most likely that someone cleared the stats rather than that traffic actually stopped. On a subscriber-facing IPTV access port, a count of 2,325 over the 76 days since the counters were last cleared 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.