Before changing the Huawei network configuration, an engineer investigates: A data center changes BGP local preference for one class of prefixes and shifts all internal client traffic to the expensive link. Which diagnostic check should be performed first?
Compare received candidate paths, LOCAL_PREF values, route policy and installed best path. This check isolates the suspected cause before an unsafe change. If confirmed, the targeted action is: Set reviewed LOCAL_PREF values for the intended egress and confirm internal propagation. Successful verification is: Internal BGP route decisions prefer the intended provider for matched prefixes and fail over if unavailable.
Inspect ip-prefix sequence, mask-length qualifiers and test candidate routes. This check would diagnose Prefix-list network and mask matching, but would not first isolate the described BGP local preference internal egress. Begin with: Compare received candidate paths, LOCAL_PREF values, route policy and installed best path.
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 local preference internal egress. Begin with: Compare received candidate paths, LOCAL_PREF values, route policy and installed best path.
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 local preference internal egress. Begin with: Compare received candidate paths, LOCAL_PREF values, route policy and installed best path.
A Huawei Datacom engineer is investigating the following situation: Two links to the same neighboring AS announce equal-length paths and engineers expect the higher MED to be preferred. Which corrective action best resolves the specified issue?
Use MED as a lower-is-better hint only under the supported path-comparison policy and verify competing attributes. Technical basis: BGP MED is a nontransitive hint often compared among paths learned from the same neighboring AS. The measurable acceptance criterion is: The neighboring AS picks the intended ingress where the MED comparison is applicable.
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 BGP MED same-neighbor-AS comparison condition reported. The relevant technical distinction is: BGP MED is a nontransitive hint often compared among paths learned from the same neighboring AS.
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 BGP MED same-neighbor-AS comparison condition reported. The relevant technical distinction is: BGP MED is a nontransitive hint often compared among paths learned from the same neighboring AS.
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 MED same-neighbor-AS comparison condition reported. The relevant technical distinction is: BGP MED is a nontransitive hint often compared among paths learned from the same neighboring AS.
A team is validating a Huawei network repair: Two links to the same neighboring AS announce equal-length paths and engineers expect the higher MED to be preferred. Which observable result provides the clearest evidence of success?
The neighboring AS picks the intended ingress where the MED comparison is applicable. This result directly tests whether the correct action worked: Use MED as a lower-is-better hint only under the supported path-comparison policy and verify competing attributes. This is explained by: BGP MED is a nontransitive hint often compared among paths learned from the same neighboring AS.
The route-policy accepts the intended subnet lengths and rejects a specifically tested unauthorized length. That observation would support a separate case of Prefix-list network and mask matching, not verification of the reported BGP MED same-neighbor-AS comparison. The relevant observable outcome here is: The neighboring AS picks the intended ingress where the MED comparison is applicable.
Internal BGP route decisions prefer the intended provider for matched prefixes and fail over if unavailable. That observation would support a separate case of BGP local preference internal egress, not verification of the reported BGP MED same-neighbor-AS comparison. The relevant observable outcome here is: The neighboring AS picks the intended ingress where the MED comparison is applicable.
Receiving iBGP routers resolve the BGP next hop and install the approved destination. That observation would support a separate case of iBGP next-hop reachability, not verification of the reported BGP MED same-neighbor-AS comparison. The relevant observable outcome here is: The neighboring AS picks the intended ingress where the MED comparison is applicable.
Consider the following Huawei Datacom deployment: Two links to the same neighboring AS announce equal-length paths and engineers expect the higher MED to be preferred. Which technical principle best explains the observed behavior?
BGP MED is a nontransitive hint often compared among paths learned from the same neighboring AS. This mechanism explains the case-specific corrective step: Use MED as a lower-is-better hint only under the supported path-comparison policy and verify competing attributes. Confirm the mechanism by verifying: The neighboring AS picks the intended ingress where the MED comparison is applicable.
Campus design separates edge access, aggregation and core responsibilities and applies policy at appropriate boundaries. This explains Enterprise campus layered design, but not why the issue in this scenario occurs. The specific mechanism is: BGP MED is a nontransitive hint often compared among paths learned from the same neighboring AS.
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 MED is a nontransitive hint often compared among paths learned from the same neighboring AS.
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 MED is a nontransitive hint often compared among paths learned from the same neighboring AS.
A Huawei network is left in this condition: Two links to the same neighboring AS announce equal-length paths and engineers expect the higher MED to be preferred. What direct operational or security risk is most relevant if it is not corrected?
Assuming MED always overrides LOCAL_PREF or applies across every AS can misroute traffic. This is the direct exposure created by BGP MED same-neighbor-AS comparison. Mitigate it through: Use MED as a lower-is-better hint only under the supported path-comparison policy and verify competing attributes. Then test: The neighboring AS picks the intended ingress where the MED comparison is applicable.
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: Assuming MED always overrides LOCAL_PREF or applies across every AS can misroute traffic.
An attribute-only change without forwarding checks can create a silent blackhole. This consequence is associated more directly with Route-policy next-hop and preference application. For the stated conditions the immediate exposure is: Assuming MED always overrides LOCAL_PREF or applies across every AS can misroute traffic.
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: Assuming MED always overrides LOCAL_PREF or applies across every AS can misroute traffic.
Before changing the Huawei network configuration, an engineer investigates: Two links to the same neighboring AS announce equal-length paths and engineers expect the higher MED to be preferred. Which diagnostic check should be performed first?
Inspect candidate AS origins, MED values, higher-priority attributes and effective route-selection rules. This check isolates the suspected cause before an unsafe change. If confirmed, the targeted action is: Use MED as a lower-is-better hint only under the supported path-comparison policy and verify competing attributes. Successful verification is: The neighboring AS picks the intended ingress where the MED comparison is applicable.
Inspect roaming history, AC mobility peers, station IP before and after move and voice packet loss. This check would diagnose Campus WLAN layer-3 roaming, but would not first isolate the described BGP MED same-neighbor-AS comparison. Begin with: Inspect candidate AS origins, MED values, higher-priority attributes and effective route-selection rules.
Inspect peer addresses, source interfaces, loopback routes and TCP endpoint addresses. This check would diagnose Loopback-based iBGP update source, but would not first isolate the described BGP MED same-neighbor-AS comparison. Begin with: Inspect candidate AS origins, MED values, higher-priority attributes and effective route-selection rules.
Inspect IS-IS NETs, area IDs, level capabilities and Hello authentication on both interfaces. This check would diagnose IS-IS level-1 area adjacency, but would not first isolate the described BGP MED same-neighbor-AS comparison. Begin with: Inspect candidate AS origins, MED values, higher-priority attributes and effective route-selection rules.
A Huawei Datacom engineer is investigating the following situation: A multihomed site manipulates MED to affect a partner's inbound choice but compares paths from unrelated ASes under default assumptions. Which corrective action best resolves the specified issue?
Use MED as a lower-is-better hint only under the supported path-comparison policy and verify competing attributes. Technical basis: BGP MED is a nontransitive hint often compared among paths learned from the same neighboring AS. The measurable acceptance criterion is: The neighboring AS picks the intended ingress where the MED comparison is applicable.
Configure the actual authorized remote AS consistently with the peer's BGP OPEN identity. This is a legitimate response to the different issue of BGP peer autonomous-system mismatch, but it does not correct the specific BGP MED same-neighbor-AS comparison condition reported. The relevant technical distinction is: BGP MED is a nontransitive hint often compared among paths learned from the same neighboring AS.
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 MED same-neighbor-AS comparison condition reported. The relevant technical distinction is: BGP MED is a nontransitive hint often compared among paths learned from the same neighboring AS.
Apply appropriate RSTP edge-port and BPDU protection policies while preserving legitimate uplink roles. This is a legitimate response to the different issue of RSTP edge-port BPDU protection, but it does not correct the specific BGP MED same-neighbor-AS comparison condition reported. The relevant technical distinction is: BGP MED is a nontransitive hint often compared among paths learned from the same neighboring AS.
A team is validating a Huawei network repair: A multihomed site manipulates MED to affect a partner's inbound choice but compares paths from unrelated ASes under default assumptions. Which observable result provides the clearest evidence of success?
The neighboring AS picks the intended ingress where the MED comparison is applicable. This result directly tests whether the correct action worked: Use MED as a lower-is-better hint only under the supported path-comparison policy and verify competing attributes. This is explained by: BGP MED is a nontransitive hint often compared among paths learned from the same neighboring AS.
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 MED same-neighbor-AS comparison. The relevant observable outcome here is: The neighboring AS picks the intended ingress where the MED comparison is applicable.
Tagged management prefixes follow the intended permit/deny outcome without affecting unrelated production routes. That observation would support a separate case of BGP community filtering in routing control, not verification of the reported BGP MED same-neighbor-AS comparison. The relevant observable outcome here is: The neighboring AS picks the intended ingress where the MED comparison is applicable.
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 BGP MED same-neighbor-AS comparison. The relevant observable outcome here is: The neighboring AS picks the intended ingress where the MED comparison is applicable.
Consider the following Huawei Datacom deployment: A multihomed site manipulates MED to affect a partner's inbound choice but compares paths from unrelated ASes under default assumptions. Which technical principle best explains the observed behavior?
BGP MED is a nontransitive hint often compared among paths learned from the same neighboring AS. This mechanism explains the case-specific corrective step: Use MED as a lower-is-better hint only under the supported path-comparison policy and verify competing attributes. Confirm the mechanism by verifying: The neighboring AS picks the intended ingress where the MED comparison is applicable.
BGP ORIGIN ranks IGP ahead of EGP and Incomplete after preceding path-selection rules. This explains BGP origin attribute tie break, but not why the issue in this scenario occurs. The specific mechanism is: BGP MED is a nontransitive hint often compared among paths learned from the same neighboring AS.
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 MED is a nontransitive hint often compared among paths learned from the same neighboring AS.
PIM-SM any-source multicast uses a rendezvous point to connect new sources and receivers. This explains PIM-SM rendezvous-point mismatch, but not why the issue in this scenario occurs. The specific mechanism is: BGP MED is a nontransitive hint often compared among paths learned from the same neighboring AS.
A Huawei network is left in this condition: A multihomed site manipulates MED to affect a partner's inbound choice but compares paths from unrelated ASes under default assumptions. What direct operational or security risk is most relevant if it is not corrected?
Assuming MED always overrides LOCAL_PREF or applies across every AS can misroute traffic. This is the direct exposure created by BGP MED same-neighbor-AS comparison. Mitigate it through: Use MED as a lower-is-better hint only under the supported path-comparison policy and verify competing attributes. Then test: The neighboring AS picks the intended ingress where the MED comparison is applicable.
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: Assuming MED always overrides LOCAL_PREF or applies across every AS can misroute traffic.
IP ping success does not prove the BGP transport session is available. This consequence is associated more directly with BGP TCP reachability and port. For the stated conditions the immediate exposure is: Assuming MED always overrides LOCAL_PREF or applies across every AS can misroute traffic.
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: Assuming MED always overrides LOCAL_PREF or applies across every AS can misroute traffic.
Before changing the Huawei network configuration, an engineer investigates: A multihomed site manipulates MED to affect a partner's inbound choice but compares paths from unrelated ASes under default assumptions. Which diagnostic check should be performed first?
Inspect candidate AS origins, MED values, higher-priority attributes and effective route-selection rules. This check isolates the suspected cause before an unsafe change. If confirmed, the targeted action is: Use MED as a lower-is-better hint only under the supported path-comparison policy and verify competing attributes. Successful verification is: The neighboring AS picks the intended ingress where the MED comparison is applicable.
Inspect IGMP querier address, query intervals, group timers and receiver reports. This check would diagnose IGMP last-hop membership queries, but would not first isolate the described BGP MED same-neighbor-AS comparison. Begin with: Inspect candidate AS origins, MED values, higher-priority attributes and effective route-selection rules.
Inspect route-policy node IDs, if-match criteria, apply clauses and hit counts. This check would diagnose Route-policy permit and deny node order, but would not first isolate the described BGP MED same-neighbor-AS comparison. Begin with: Inspect candidate AS origins, MED values, higher-priority attributes and effective route-selection rules.
Inspect BGP aggregate configuration, contributor routes, specific exceptions and next-hop forwarding. This check would diagnose BGP prefix aggregation and specifics, but would not first isolate the described BGP MED same-neighbor-AS comparison. Begin with: Inspect candidate AS origins, MED values, higher-priority attributes and effective route-selection rules.
Please check your mailbox for a message from support@examlabs.com and follow the directions.
