Inspect tracked uplinks, priority changes, VRRP master transition and end-to-end reachability. This check would diagnose VRRP uplink tracking and priority decrement, but would not first isolate the described MP-BGP address-family activation. Begin with: Inspect AFI/SAFI negotiation, peer AF activation and received EVPN routes.

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 MP-BGP address-family activation. Begin with: Inspect AFI/SAFI negotiation, peer AF activation and received EVPN routes.

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 MP-BGP address-family activation. Begin with: Inspect AFI/SAFI negotiation, peer AF activation and received EVPN routes.

Preserve and enforce relevant BGP community propagation and NO_EXPORT behavior under the export policy. This is a legitimate response to the different issue of BGP route policy community NO_EXPORT, but it does not correct the specific EVPN Type-2 MAC/IP route interpretation condition reported. The relevant technical distinction is: EVPN Type 2 carries MAC or MAC/IP reachability; Type 5 is used for IP-prefix reachability.

Apply an explicit allowlist of authorized public prefixes with a default deny export policy. This is a legitimate response to the different issue of BGP prefix export-filter leak, but it does not correct the specific EVPN Type-2 MAC/IP route interpretation condition reported. The relevant technical distinction is: EVPN Type 2 carries MAC or MAC/IP reachability; Type 5 is used for IP-prefix reachability.

Correct the IS-IS area identities or redesign the intended Level-2 boundary before forming the peer. This is a legitimate response to the different issue of IS-IS level-1 area adjacency, but it does not correct the specific EVPN Type-2 MAC/IP route interpretation condition reported. The relevant technical distinction is: EVPN Type 2 carries MAC or MAC/IP reachability; Type 5 is used for IP-prefix reachability.

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 EVPN Type-2 MAC/IP route interpretation. The relevant observable outcome here is: The EVPN table shows appropriate host MAC/IP mapping and separately advertised intended IP prefixes.

One appropriate DIS per active level advertises the LAN pseudonode and the LSDB remains consistent. That observation would support a separate case of IS-IS DIS and pseudonode on broadcast LAN, not verification of the reported EVPN Type-2 MAC/IP route interpretation. The relevant observable outcome here is: The EVPN table shows appropriate host MAC/IP mapping and separately advertised intended IP prefixes.

The valid corrected route is accepted and routes still containing the receiver AS are denied. That observation would support a separate case of BGP AS_PATH loop detection, not verification of the reported EVPN Type-2 MAC/IP route interpretation. The relevant observable outcome here is: The EVPN table shows appropriate host MAC/IP mapping and separately advertised intended IP prefixes.

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: EVPN Type 2 carries MAC or MAC/IP reachability; Type 5 is used for IP-prefix reachability.

BGP NO_EXPORT community constrains external AS propagation when carried and honored. This explains BGP route policy community NO_EXPORT, but not why the issue in this scenario occurs. The specific mechanism is: EVPN Type 2 carries MAC or MAC/IP reachability; Type 5 is used for IP-prefix reachability.

An ordinary iBGP speaker does not re-advertise iBGP-learned routes to other iBGP peers. This explains iBGP split-horizon route propagation, but not why the issue in this scenario occurs. The specific mechanism is: EVPN Type 2 carries MAC or MAC/IP reachability; Type 5 is used for IP-prefix reachability.

Misunderstanding origin can lead to misleading troubleshooting changes to later attributes. This consequence is associated more directly with BGP origin attribute tie break. For the stated conditions the immediate exposure is: Confusing route types can leave inter-subnet overlay connectivity missing or misconfigured.

An Established session with received prefixes can still leave routes unusable if next hops are unresolved. This consequence is associated more directly with iBGP next-hop reachability. For the stated conditions the immediate exposure is: Confusing route types can leave inter-subnet overlay connectivity missing or misconfigured.

Absent or misleading attached exits can strand a local area or direct it into an invalid path. This consequence is associated more directly with IS-IS L1 default to nearest attached L1L2. For the stated conditions the immediate exposure is: Confusing route types can leave inter-subnet overlay connectivity missing or misconfigured.

Check metric-style configuration, TLVs, interface costs and selected SPF paths. This check would diagnose IS-IS metric-style consistency, but would not first isolate the described EVPN Type-2 MAC/IP route interpretation. Begin with: Inspect EVPN NLRI route types, MAC/IP attributes, VNI bindings and desired prefix routes.

Inspect VLANIF relay configuration, DHCPDISCOVER/OFFER packets and server scope. This check would diagnose DHCP relay to remote server, but would not first isolate the described EVPN Type-2 MAC/IP route interpretation. Begin with: Inspect EVPN NLRI route types, MAC/IP attributes, VNI bindings and desired prefix routes.

Test bidirectional peer IP routing, TCP port 179 and BGP neighbor socket state. This check would diagnose BGP TCP reachability and port, but would not first isolate the described EVPN Type-2 MAC/IP route interpretation. Begin with: Inspect EVPN NLRI route types, MAC/IP attributes, VNI bindings and desired prefix routes.

Check earlier best-path attributes and prefer the supported origin order IGP, then EGP, then Incomplete where reached. This is a legitimate response to the different issue of BGP origin attribute tie break, but it does not correct the specific EVPN Type-2 MAC/IP route interpretation condition reported. The relevant technical distinction is: EVPN Type 2 carries MAC or MAC/IP reachability; Type 5 is used for IP-prefix reachability.

Validate Level-1 and Level-2 DIS election behavior, eligible priorities and generated pseudonode LSPs. This is a legitimate response to the different issue of IS-IS DIS and pseudonode on broadcast LAN, but it does not correct the specific EVPN Type-2 MAC/IP route interpretation condition reported. The relevant technical distinction is: EVPN Type 2 carries MAC or MAC/IP reachability; Type 5 is used for IP-prefix reachability.

Apply an explicit allowlist of authorized public prefixes with a default deny export policy. This is a legitimate response to the different issue of BGP prefix export-filter leak, but it does not correct the specific EVPN Type-2 MAC/IP route interpretation condition reported. The relevant technical distinction is: EVPN Type 2 carries MAC or MAC/IP reachability; Type 5 is used for IP-prefix reachability.

The valid corrected route is accepted and routes still containing the receiver AS are denied. That observation would support a separate case of BGP AS_PATH loop detection, not verification of the reported EVPN Type-2 MAC/IP route interpretation. The relevant observable outcome here is: The EVPN table shows appropriate host MAC/IP mapping and separately advertised intended IP prefixes.

A mobile client preserves approved session continuity while roaming across intended coverage and subnets. That observation would support a separate case of Campus WLAN layer-3 roaming, not verification of the reported EVPN Type-2 MAC/IP route interpretation. The relevant observable outcome here is: The EVPN table shows appropriate host MAC/IP mapping and separately advertised intended IP prefixes.

Newer LSPs supersede outdated versions and a stable LSDB yields the intended routing path. That observation would support a separate case of IS-IS LSP sequence and aging, not verification of the reported EVPN Type-2 MAC/IP route interpretation. The relevant observable outcome here is: The EVPN table shows appropriate host MAC/IP mapping and separately advertised intended IP prefixes.

Packet filtering depends on first relevant ACL matches and the direction of filter application. This explains ACL packet filter rule order and direction, but not why the issue in this scenario occurs. The specific mechanism is: EVPN Type 2 carries MAC or MAC/IP reachability; Type 5 is used for IP-prefix reachability.

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: EVPN Type 2 carries MAC or MAC/IP reachability; Type 5 is used for IP-prefix reachability.

BGP best-path and route installation require reachable NEXT_HOP; iBGP advertising does not always rewrite it. This explains iBGP next-hop reachability, but not why the issue in this scenario occurs. The specific mechanism is: EVPN Type 2 carries MAC or MAC/IP reachability; Type 5 is used for IP-prefix reachability.

Misordered or misplaced ACLs can allow forbidden flows or deny legitimate services. This consequence is associated more directly with ACL packet filter rule order and direction. For the stated conditions the immediate exposure is: Confusing route types can leave inter-subnet overlay connectivity missing or misconfigured.

Defining a classifier without applying the intended policy gives a false impression of active QoS. This consequence is associated more directly with MQC classifier and behavior association. For the stated conditions the immediate exposure is: Confusing route types can leave inter-subnet overlay connectivity missing or misconfigured.

Treating an iBGP authentication issue as pure reachability can mask an unexpected transport source. This consequence is associated more directly with Loopback-based iBGP update source. For the stated conditions the immediate exposure is: Confusing route types can leave inter-subnet overlay connectivity missing or misconfigured.

Check route tags, source protocol, import-route statements and re-advertisement history. This check would diagnose Redistribution route tag loop avoidance, but would not first isolate the described EVPN Type-2 MAC/IP route interpretation. Begin with: Inspect EVPN NLRI route types, MAC/IP attributes, VNI bindings and desired prefix routes.

Test bidirectional peer IP routing, TCP port 179 and BGP neighbor socket state. This check would diagnose BGP TCP reachability and port, but would not first isolate the described EVPN Type-2 MAC/IP route interpretation. Begin with: Inspect EVPN NLRI route types, MAC/IP attributes, VNI bindings and desired prefix routes.

Compare external route type, advertised metric, internal ASBR reachability cost and route selection. This check would diagnose OSPF E1 versus E2 external metric, but would not first isolate the described EVPN Type-2 MAC/IP route interpretation. Begin with: Inspect EVPN NLRI route types, MAC/IP attributes, VNI bindings and desired prefix routes.