Before changing the Huawei network configuration, an engineer investigates: A route-imported prefix unexpectedly loses a BGP tie break to an IGP-originated candidate with equal earlier attributes. Which diagnostic check should be performed first?
Inspect candidate origin codes, LOCAL_PREF, AS_PATH and decision order. This check isolates the suspected cause before an unsafe change. If confirmed, the targeted action is: Check earlier best-path attributes and prefer the supported origin order IGP, then EGP, then Incomplete where reached. Successful verification is: The chosen route matches the documented origin tie-break sequence and other path attributes.
Inspect adjacency graph, route source type and advertisement history on the transit router. This check would diagnose iBGP split-horizon route propagation, but would not first isolate the described BGP origin attribute tie break. Begin with: Inspect candidate origin codes, LOCAL_PREF, AS_PATH and decision order.
Review advertised-route output, prefix-list matches and outbound route-policy order. This check would diagnose BGP prefix export-filter leak, but would not first isolate the described BGP origin attribute tie break. Begin with: Inspect candidate origin codes, LOCAL_PREF, AS_PATH and decision order.
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 origin attribute tie break. Begin with: Inspect candidate origin codes, LOCAL_PREF, AS_PATH and decision order.
A Huawei Datacom engineer is investigating the following situation: A partner route tagged NO_EXPORT is unintentionally forwarded to an external transit AS after its community is stripped. Which corrective action best resolves the specified issue?
Preserve and enforce relevant BGP community propagation and NO_EXPORT behavior under the export policy. Technical basis: BGP NO_EXPORT community constrains external AS propagation when carried and honored. The measurable acceptance criterion is: The prefix remains usable internally where authorized and is not advertised to prohibited external peers.
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 policy community NO_EXPORT condition reported. The relevant technical distinction is: BGP NO_EXPORT community constrains external AS propagation when carried and honored.
Design intended reflector cluster IDs and client relationships with loop-prevention attributes intact. This is a legitimate response to the different issue of BGP route reflector cluster loop prevention, but it does not correct the specific BGP route policy community NO_EXPORT condition reported. The relevant technical distinction is: BGP NO_EXPORT community constrains external AS propagation when carried and honored.
Apply supported next-hop handling such as next-hop-local where appropriate and provide underlay reachability. This is a legitimate response to the different issue of iBGP next-hop reachability, but it does not correct the specific BGP route policy community NO_EXPORT condition reported. The relevant technical distinction is: BGP NO_EXPORT community constrains external AS propagation when carried and honored.
A team is validating a Huawei network repair: A partner route tagged NO_EXPORT is unintentionally forwarded to an external transit AS after its community is stripped. Which observable result provides the clearest evidence of success?
The prefix remains usable internally where authorized and is not advertised to prohibited external peers. This result directly tests whether the correct action worked: Preserve and enforce relevant BGP community propagation and NO_EXPORT behavior under the export policy. This is explained by: BGP NO_EXPORT community constrains external AS propagation when carried and honored.
The EVPN table shows appropriate host MAC/IP mapping and separately advertised intended IP prefixes. That observation would support a separate case of EVPN Type-2 MAC/IP route interpretation, not verification of the reported BGP route policy community NO_EXPORT. The relevant observable outcome here is: The prefix remains usable internally where authorized and is not advertised to prohibited external peers.
The leaf follows the intended default path and its LSDB lacks the suppressed detailed inter-area summaries. That observation would support a separate case of OSPF totally stub area inter-area constraint, not verification of the reported BGP route policy community NO_EXPORT. The relevant observable outcome here is: The prefix remains usable internally where authorized and is not advertised to prohibited external peers.
Traffic captures show intended markings and low-delay queue behavior during representative congestion. That observation would support a separate case of QoS DSCP remarking and trust, not verification of the reported BGP route policy community NO_EXPORT. The relevant observable outcome here is: The prefix remains usable internally where authorized and is not advertised to prohibited external peers.
Consider the following Huawei Datacom deployment: A partner route tagged NO_EXPORT is unintentionally forwarded to an external transit AS after its community is stripped. Which technical principle best explains the observed behavior?
BGP NO_EXPORT community constrains external AS propagation when carried and honored. This mechanism explains the case-specific corrective step: Preserve and enforce relevant BGP community propagation and NO_EXPORT behavior under the export policy. Confirm the mechanism by verifying: The prefix remains usable internally where authorized and is not advertised to prohibited external peers.
BGP export routing policies determine which eligible local and learned prefixes a peer receives. This explains BGP prefix export-filter leak, but not why the issue in this scenario occurs. The specific mechanism is: BGP NO_EXPORT community constrains external AS propagation when carried and honored.
Policy-based routing can select forwarding based on packet attributes before conventional destination routing. This explains Policy-based routing for approved application, but not why the issue in this scenario occurs. The specific mechanism is: BGP NO_EXPORT community constrains external AS propagation when carried and honored.
BGP route reflectors use ORIGINATOR_ID and CLUSTER_LIST to prevent reflection loops. This explains BGP route reflector cluster loop prevention, but not why the issue in this scenario occurs. The specific mechanism is: BGP NO_EXPORT community constrains external AS propagation when carried and honored.
A Huawei network is left in this condition: A partner route tagged NO_EXPORT is unintentionally forwarded to an external transit AS after its community is stripped. What direct operational or security risk is most relevant if it is not corrected?
Stripping a no-export marker can leak intended internal reachability to other networks. This is the direct exposure created by BGP route policy community NO_EXPORT. Mitigate it through: Preserve and enforce relevant BGP community propagation and NO_EXPORT behavior under the export policy. Then test: The prefix remains usable internally where authorized and is not advertised to prohibited external peers.
Incorrect client designation can create route visibility gaps despite healthy TCP sessions. This consequence is associated more directly with BGP route-reflector client scoping. For the stated conditions the immediate exposure is: Stripping a no-export marker can leak intended internal reachability to other networks.
A healthy adjacency without a consistent LSDB may produce transient wrong paths. This consequence is associated more directly with IS-IS CSNP and PSNP database sync. For the stated conditions the immediate exposure is: Stripping a no-export marker can leak intended internal reachability to other networks.
Changing inbound MED may not correct the enterprise's outbound egress preference. This consequence is associated more directly with BGP local preference internal egress. For the stated conditions the immediate exposure is: Stripping a no-export marker can leak intended internal reachability to other networks.
Before changing the Huawei network configuration, an engineer investigates: A partner route tagged NO_EXPORT is unintentionally forwarded to an external transit AS after its community is stripped. Which diagnostic check should be performed first?
Inspect BGP communities on receipt and advertisement, send-community settings and outbound policy. This check isolates the suspected cause before an unsafe change. If confirmed, the targeted action is: Preserve and enforce relevant BGP community propagation and NO_EXPORT behavior under the export policy. Successful verification is: The prefix remains usable internally where authorized and is not advertised to prohibited external peers.
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 policy community NO_EXPORT. Begin with: Inspect BGP communities on receipt and advertisement, send-community settings and outbound policy.
Inspect OSPF interface network type, DR/BDR identity, priority and per-peer state. This check would diagnose Broadcast OSPF DR and BDR election, but would not first isolate the described BGP route policy community NO_EXPORT. Begin with: Inspect BGP communities on receipt and advertisement, send-community settings and outbound policy.
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 BGP route policy community NO_EXPORT. Begin with: Inspect BGP communities on receipt and advertisement, send-community settings and outbound policy.
A Huawei Datacom engineer is investigating the following situation: An engineer applies a community policy on a Huawei edge router but fails to send communities to the intended iBGP peer. Which corrective action best resolves the specified issue?
Preserve and enforce relevant BGP community propagation and NO_EXPORT behavior under the export policy. Technical basis: BGP NO_EXPORT community constrains external AS propagation when carried and honored. The measurable acceptance criterion is: The prefix remains usable internally where authorized and is not advertised to prohibited external peers.
Use MED as a lower-is-better hint only under the supported path-comparison policy and verify competing attributes. This is a legitimate response to the different issue of BGP MED same-neighbor-AS comparison, but it does not correct the specific BGP route policy community NO_EXPORT condition reported. The relevant technical distinction is: BGP NO_EXPORT community constrains external AS propagation when carried and honored.
Use an ordered narrow ACL with the correct interface and traffic direction for the required filter. This is a legitimate response to the different issue of ACL packet filter rule order and direction, but it does not correct the specific BGP route policy community NO_EXPORT condition reported. The relevant technical distinction is: BGP NO_EXPORT community constrains external AS propagation when carried and honored.
Evaluate eligible candidate paths and select the shorter AS_PATH when earlier BGP preference criteria do not decide. This is a legitimate response to the different issue of BGP AS_PATH length egress choice, but it does not correct the specific BGP route policy community NO_EXPORT condition reported. The relevant technical distinction is: BGP NO_EXPORT community constrains external AS propagation when carried and honored.
A team is validating a Huawei network repair: An engineer applies a community policy on a Huawei edge router but fails to send communities to the intended iBGP peer. Which observable result provides the clearest evidence of success?
The prefix remains usable internally where authorized and is not advertised to prohibited external peers. This result directly tests whether the correct action worked: Preserve and enforce relevant BGP community propagation and NO_EXPORT behavior under the export policy. This is explained by: BGP NO_EXPORT community constrains external AS propagation when carried and honored.
Clients form valid global addresses and default-router entries for the authorized prefix. That observation would support a separate case of IPv6 SLAAC router advertisement, not verification of the reported BGP route policy community NO_EXPORT. The relevant observable outcome here is: The prefix remains usable internally where authorized and is not advertised to prohibited external peers.
All intended iBGP peers learn the eligible prefix without loops or unintended repeated announcements. That observation would support a separate case of iBGP split-horizon route propagation, not verification of the reported BGP route policy community NO_EXPORT. The relevant observable outcome here is: The prefix remains usable internally where authorized and is not advertised to prohibited external peers.
TCP 179 establishes to the configured peer and BGP progresses toward Established. That observation would support a separate case of BGP TCP reachability and port, not verification of the reported BGP route policy community NO_EXPORT. The relevant observable outcome here is: The prefix remains usable internally where authorized and is not advertised to prohibited external peers.
Consider the following Huawei Datacom deployment: An engineer applies a community policy on a Huawei edge router but fails to send communities to the intended iBGP peer. Which technical principle best explains the observed behavior?
BGP NO_EXPORT community constrains external AS propagation when carried and honored. This mechanism explains the case-specific corrective step: Preserve and enforce relevant BGP community propagation and NO_EXPORT behavior under the export policy. Confirm the mechanism by verifying: The prefix remains usable internally where authorized and is not advertised to prohibited external peers.
MP-BGP carries address-family-specific routes only when corresponding capabilities and peers are configured. This explains MP-BGP address-family activation, but not why the issue in this scenario occurs. The specific mechanism is: BGP NO_EXPORT community constrains external AS propagation when carried and honored.
An RR's advertisement rules depend on whether the source and target peers are clients. This explains BGP route-reflector client scoping, but not why the issue in this scenario occurs. The specific mechanism is: BGP NO_EXPORT community constrains external AS propagation when carried and honored.
Routing policy can alter selection attributes, but route installation still depends on next-hop reachability. This explains Route-policy next-hop and preference application, but not why the issue in this scenario occurs. The specific mechanism is: BGP NO_EXPORT community constrains external AS propagation when carried and honored.
A Huawei network is left in this condition: An engineer applies a community policy on a Huawei edge router but fails to send communities to the intended iBGP peer. What direct operational or security risk is most relevant if it is not corrected?
Stripping a no-export marker can leak intended internal reachability to other networks. This is the direct exposure created by BGP route policy community NO_EXPORT. Mitigate it through: Preserve and enforce relevant BGP community propagation and NO_EXPORT behavior under the export policy. Then test: The prefix remains usable internally where authorized and is not advertised to prohibited external peers.
Blindly altering IP prefixes cannot repair an ISO NET area mismatch. This consequence is associated more directly with IS-IS level-1 area adjacency. For the stated conditions the immediate exposure is: Stripping a no-export marker can leak intended internal reachability to other networks.
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: Stripping a no-export marker can leak intended internal reachability to other networks.
A link-up interface can still hide a failed downstream forwarding path for too long. This consequence is associated more directly with BFD fast failure detection tied to route. For the stated conditions the immediate exposure is: Stripping a no-export marker can leak intended internal reachability to other networks.
Before changing the Huawei network configuration, an engineer investigates: An engineer applies a community policy on a Huawei edge router but fails to send communities to the intended iBGP peer. Which diagnostic check should be performed first?
Inspect BGP communities on receipt and advertisement, send-community settings and outbound policy. This check isolates the suspected cause before an unsafe change. If confirmed, the targeted action is: Preserve and enforce relevant BGP community propagation and NO_EXPORT behavior under the export policy. Successful verification is: The prefix remains usable internally where authorized and is not advertised to prohibited external peers.
Inspect adjacency graph, route source type and advertisement history on the transit router. This check would diagnose iBGP split-horizon route propagation, but would not first isolate the described BGP route policy community NO_EXPORT. Begin with: Inspect BGP communities on receipt and advertisement, send-community settings and outbound policy.
Compare OSPF router IDs, neighbor tables and LSA advertising-router fields. This check would diagnose OSPF duplicate router IDs, but would not first isolate the described BGP route policy community NO_EXPORT. Begin with: Inspect BGP communities on receipt and advertisement, send-community settings and outbound policy.
Inspect candidate AS origins, MED values, higher-priority attributes and effective route-selection rules. This check would diagnose BGP MED same-neighbor-AS comparison, but would not first isolate the described BGP route policy community NO_EXPORT. Begin with: Inspect BGP communities on receipt and advertisement, send-community settings and outbound policy.
Please check your mailbox for a message from support@examlabs.com and follow the directions.
