When using the command "show subscribers client-type pppoe count agent-circuit-identifier XXX-XXX*" to provide a count of subscribers for a specific ACI wildcard
For eg:- DN9-BLT is the site code. So the command "show subscribers client-type pppoe count agent-circuit-identifier DN9-BLT*" would be expected to return the count of subscribers where the first part of the string matches. The matching excludes the last character of the string. Another code DN9-BLA so the same command actually matches DN9-BL and aggregates BLA and BLT.
For example:
{master}
user@MX-re0> show subscribers client-type pppoe count agent-circuit-identifier DN9-BLA*
Total subscribers: 301, Active Subscribers: 301
user@MX-re0> show subscribers client-type pppoe count agent-circuit-identifier DN9-BLT*
This can be further confirmed by using DN9-BLX, a site code that does not exist and is not present in any ACI
user@MX-re0> show subscribers client-type pppoe count agent-circuit-identifier DN9-BLX*
user@MXre0> show subscribers client-type pppoe count agent-circuit-identifier DN9-BLAX*
Total subscribers: 277, Active Subscribers: 277
user@MX-re0> show subscribers client-type pppoe count agent-circuit-identifier DN9-BLTX*
Total subscribers: 24, Active Subscribers: 24
user@MX-re0> show subscribers client-type pppoe count agent-circuit-identifier DN9-BLXX*
Total subscribers: 0, Active Subscribers: 0
These commands return the correct count despite the last X really being a hyphen
The issue is being tracked by a known PR - 1949605
Workaround :Fictional character (X) can be appended to the end of the site code before the wildcard then the command correctly evaluates all characters except the final character immediately preceding the wildcard (*).
This is fixed in the following releases.
junos:25.2R2-S1 junos:25.4R2 junos:26.2R1 junos:26.3R1