Inspect candidate origin codes, LOCAL_PREF, AS_PATH and decision order. This check would diagnose BGP origin attribute tie break, but would not first isolate the described BGP route reflector cluster loop prevention. Begin with: Inspect reflector cluster ID, reflected path attributes and RR-client membership.

Inspect AFI/SAFI negotiation, peer AF activation and received EVPN routes. This check would diagnose MP-BGP address-family activation, but would not first isolate the described BGP route reflector cluster loop prevention. Begin with: Inspect reflector cluster ID, reflected path attributes and RR-client membership.

Inspect session NAT fields, original and translated addresses, egress interface and upstream replies. This check would diagnose Source NAT for outbound clients, but would not first isolate the described BGP route reflector cluster loop prevention. Begin with: Inspect reflector cluster ID, reflected path attributes and RR-client membership.

Bind the correct MQC classifier, behavior, and traffic-policy in the intended interface direction. This is a legitimate response to the different issue of MQC classifier and behavior association, but it does not correct the specific BGP route-reflector client scoping condition reported. The relevant technical distinction is: An RR's advertisement rules depend on whether the source and target peers are clients.

Set reviewed RSTP bridge priorities so an appropriate resilient core device remains root. This is a legitimate response to the different issue of RSTP root bridge location, but it does not correct the specific BGP route-reflector client scoping condition reported. The relevant technical distinction is: An RR's advertisement rules depend on whether the source and target peers are clients.

Set reviewed LOCAL_PREF values for the intended egress and confirm internal propagation. This is a legitimate response to the different issue of BGP local preference internal egress, but it does not correct the specific BGP route-reflector client scoping condition reported. The relevant technical distinction is: An RR's advertisement rules depend on whether the source and target peers are clients.

The restricted destination is denied and authorized comparison traffic succeeds in a controlled test. That observation would support a separate case of ACL packet filter rule order and direction, not verification of the reported BGP route-reflector client scoping. The relevant observable outcome here is: Eligible routes are reflected according to design while unauthorized peerings stay restricted.

The selected route follows the expected shorter path unless an explicitly higher-priority attribute overrides it. That observation would support a separate case of BGP AS_PATH length egress choice, not verification of the reported BGP route-reflector client scoping. The relevant observable outcome here is: Eligible routes are reflected according to design while unauthorized peerings stay restricted.

The Level-1 area learns its required specifics while unrelated Level-2 routes stay outside its LSDB. That observation would support a separate case of IS-IS selective L2-to-L1 route leaking, not verification of the reported BGP route-reflector client scoping. The relevant observable outcome here is: Eligible routes are reflected according to design while unauthorized peerings stay restricted.

BGP aggregation reduces advertised prefix count but must preserve valid forwarding for component destinations. This explains BGP prefix aggregation and specifics, but not why the issue in this scenario occurs. The specific mechanism is: An RR's advertisement rules depend on whether the source and target peers are clients.

CSNP and PSNP exchanges help IS-IS identify and request missing or stale link-state packets. This explains IS-IS CSNP and PSNP database sync, but not why the issue in this scenario occurs. The specific mechanism is: An RR's advertisement rules depend on whether the source and target peers are clients.

BGP peer addressing and actual TCP source must correspond, and loopback peering needs a reachable underlay. This explains Loopback-based iBGP update source, but not why the issue in this scenario occurs. The specific mechanism is: An RR's advertisement rules depend on whether the source and target peers are clients.

Overbroad aggregation can hide loss of component reachability and blackhole traffic. This consequence is associated more directly with BGP prefix aggregation and specifics. For the stated conditions the immediate exposure is: Incorrect client designation can create route visibility gaps despite healthy TCP sessions.

Disabling AS loop detection to hide a policy error risks persistent routing loops. This consequence is associated more directly with BGP AS_PATH loop detection. For the stated conditions the immediate exposure is: Incorrect client designation can create route visibility gaps despite healthy TCP sessions.

Unnecessary RP dependence or an invalid source RPF path can block SSM delivery. This consequence is associated more directly with Multicast SSM and RPF source path. For the stated conditions the immediate exposure is: Incorrect client designation can create route visibility gaps despite healthy TCP sessions.

Inspect rejected UPDATE attributes, local AS number and AS_PATH on each advertised prefix. This check would diagnose BGP AS_PATH loop detection, but would not first isolate the described BGP route-reflector client scoping. Begin with: Inspect peer reflect-client settings, received and advertised routes and RR topology.

Check BGP NEXT_HOP, recursive route resolution and underlay reachability on the receiver. This check would diagnose iBGP next-hop reachability, but would not first isolate the described BGP route-reflector client scoping. Begin with: Inspect peer reflect-client settings, received and advertised routes and RR topology.

Inspect import policy, level-specific LSP advertisements and the Level-1 route table. This check would diagnose IS-IS selective L2-to-L1 route leaking, but would not first isolate the described BGP route-reflector client scoping. Begin with: Inspect peer reflect-client settings, received and advertised routes and RR topology.

Apply a reviewed community-filter match in the relevant import or export route-policy. This is a legitimate response to the different issue of BGP community filtering in routing control, but it does not correct the specific BGP route-reflector client scoping condition reported. The relevant technical distinction is: An RR's advertisement rules depend on whether the source and target peers are clients.

Set reviewed RSTP bridge priorities so an appropriate resilient core device remains root. This is a legitimate response to the different issue of RSTP root bridge location, but it does not correct the specific BGP route-reflector client scoping condition reported. The relevant technical distinction is: An RR's advertisement rules depend on whether the source and target peers are clients.

Enable and verify the supported L2VPN EVPN MP-BGP address family for intended peers. This is a legitimate response to the different issue of MP-BGP address-family activation, but it does not correct the specific BGP route-reflector client scoping condition reported. The relevant technical distinction is: An RR's advertisement rules depend on whether the source and target peers are clients.

The selected route follows the expected shorter path unless an explicitly higher-priority attribute overrides it. That observation would support a separate case of BGP AS_PATH length egress choice, not verification of the reported BGP route-reflector client scoping. The relevant observable outcome here is: Eligible routes are reflected according to design while unauthorized peerings stay restricted.

The prefix remains usable internally where authorized and is not advertised to prohibited external peers. That observation would support a separate case of BGP route policy community NO_EXPORT, not verification of the reported BGP route-reflector client scoping. The relevant observable outcome here is: Eligible routes are reflected according to design while unauthorized peerings stay restricted.

Reflected routes reach intended clients without repeated originator or cluster loops. That observation would support a separate case of BGP route reflector cluster loop prevention, not verification of the reported BGP route-reflector client scoping. The relevant observable outcome here is: Eligible routes are reflected according to design while unauthorized peerings stay restricted.

Huawei MQC separates class identification, traffic behavior and applied traffic-policy binding. This explains MQC classifier and behavior association, but not why the issue in this scenario occurs. The specific mechanism is: An RR's advertisement rules depend on whether the source and target peers are clients.

BGP MED is a nontransitive hint often compared among paths learned from the same neighboring AS. This explains BGP MED same-neighbor-AS comparison, but not why the issue in this scenario occurs. The specific mechanism is: An RR's advertisement rules depend on whether the source and target peers are clients.

BGP exchanges routing control messages over an established TCP transport connection. This explains BGP TCP reachability and port, but not why the issue in this scenario occurs. The specific mechanism is: An RR's advertisement rules depend on whether the source and target peers are clients.

Incorrect DIS assumptions can cause inconsistent troubleshooting and churn in shared-segment LSPs. This consequence is associated more directly with IS-IS DIS and pseudonode on broadcast LAN. For the stated conditions the immediate exposure is: Incorrect client designation can create route visibility gaps despite healthy TCP sessions.

A permissive export filter can leak confidential topology and disrupt other routing domains. This consequence is associated more directly with BGP prefix export-filter leak. For the stated conditions the immediate exposure is: Incorrect client designation can create route visibility gaps despite healthy TCP sessions.

Using AS_PATH padding without understanding precedence can fail to shift traffic. This consequence is associated more directly with BGP AS_PATH length egress choice. For the stated conditions the immediate exposure is: Incorrect client designation can create route visibility gaps despite healthy TCP sessions.

Inspect matching rule, applied attributes, selected route and resolved FIB next hop. This check would diagnose Route-policy next-hop and preference application, but would not first isolate the described BGP route-reflector client scoping. Begin with: Inspect peer reflect-client settings, received and advertised routes and RR topology.

Inspect EVPN NLRI route types, MAC/IP attributes, VNI bindings and desired prefix routes. This check would diagnose EVPN Type-2 MAC/IP route interpretation, but would not first isolate the described BGP route-reflector client scoping. Begin with: Inspect peer reflect-client settings, received and advertised routes and RR topology.

Inspect configured peer AS, received OPEN messages and BGP neighbor reset reasons. This check would diagnose BGP peer autonomous-system mismatch, but would not first isolate the described BGP route-reflector client scoping. Begin with: Inspect peer reflect-client settings, received and advertised routes and RR topology.