This read-only Counter64 counts messages the host-side logic discarded when a join or leave arrived on a port that has no established router port to forward toward. A climbing count on an access port means subscribers are trying to join multicast groups but the switch has no upstream path configured yet — a deployment gap rather than a subscriber fault; 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 residential VLAN used for multicast video delivery, a count of 3,202 over the 100 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.