This read-only Counter64 counts messages the router-side logic discarded because a join arrived on a port that is configured as a router port. This specifically flags a join coming in from the "wrong side" of the network — where the multicast router itself should be — which is usually a topology or port-role misconfiguration rather than a subscriber issue; 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 an access port serving a multi-dwelling unit, a count of 258 over the 99 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.