Before changing the Huawei network configuration, an engineer investigates: A campus sees repeated IS-IS LSP churn from the same system ID after frequent interface flaps. Which diagnostic check should be performed first?
Inspect source system ID, LSP sequence, remaining lifetime and interface flap history. This check isolates the suspected cause before an unsafe change. If confirmed, the targeted action is: Examine LSP sequence numbers and lifetime behavior and correct the root flooding or instability problem. Successful verification is: Newer LSPs supersede outdated versions and a stable LSDB yields the intended routing path.
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 IS-IS LSP sequence and aging. Begin with: Inspect source system ID, LSP sequence, remaining lifetime and interface flap history.
Inspect neighbor phase, LSR retransmission lists, relevant LSAs and interface loss. This check would diagnose OSPF LSDB synchronization failure, but would not first isolate the described IS-IS LSP sequence and aging. Begin with: Inspect source system ID, LSP sequence, remaining lifetime and interface flap history.
Check attached bits in LSPs, candidate L1/L2 routes and default forwarding behavior. This check would diagnose IS-IS L1 default to nearest attached L1L2, but would not first isolate the described IS-IS LSP sequence and aging. Begin with: Inspect source system ID, LSP sequence, remaining lifetime and interface flap history.
A Huawei Datacom engineer is investigating the following situation: A backbone expands link costs beyond the narrow-metric range but several Huawei routers retain incompatible IS-IS metric styles. Which corrective action best resolves the specified issue?
Use a supported consistent IS-IS metric style and cost plan across affected peers. Technical basis: IS-IS metric encoding capability influences which costs can be advertised and interpreted. The measurable acceptance criterion is: Every device interprets intended link costs and SPF selects the documented shortest paths.
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 IS-IS metric-style consistency condition reported. The relevant technical distinction is: IS-IS metric encoding capability influences which costs can be advertised and interpreted.
Repair the allowed IS-IS database synchronization exchanges and check CSNP/PSNP and LSP sequence handling. This is a legitimate response to the different issue of IS-IS CSNP and PSNP database sync, but it does not correct the specific IS-IS metric-style consistency condition reported. The relevant technical distinction is: IS-IS metric encoding capability influences which costs can be advertised and interpreted.
Use a documented full-mesh or route-reflector design rather than expecting ordinary iBGP transit advertisement. This is a legitimate response to the different issue of iBGP split-horizon route propagation, but it does not correct the specific IS-IS metric-style consistency condition reported. The relevant technical distinction is: IS-IS metric encoding capability influences which costs can be advertised and interpreted.
A team is validating a Huawei network repair: A backbone expands link costs beyond the narrow-metric range but several Huawei routers retain incompatible IS-IS metric styles. Which observable result provides the clearest evidence of success?
Every device interprets intended link costs and SPF selects the documented shortest paths. This result directly tests whether the correct action worked: Use a supported consistent IS-IS metric style and cost plan across affected peers. This is explained by: IS-IS metric encoding capability influences which costs can be advertised and interpreted.
The neighboring AS picks the intended ingress where the MED comparison is applicable. That observation would support a separate case of BGP MED same-neighbor-AS comparison, not verification of the reported IS-IS metric-style consistency. The relevant observable outcome here is: Every device interprets intended link costs and SPF selects the documented shortest paths.
A stack-link fault produces the designed protective isolation with one coherent active forwarding system. That observation would support a separate case of Switch stacking split-brain, not verification of the reported IS-IS metric-style consistency. The relevant observable outcome here is: Every device interprets intended link costs and SPF selects the documented shortest paths.
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 IS-IS metric-style consistency. The relevant observable outcome here is: Every device interprets intended link costs and SPF selects the documented shortest paths.
Consider the following Huawei Datacom deployment: A backbone expands link costs beyond the narrow-metric range but several Huawei routers retain incompatible IS-IS metric styles. Which technical principle best explains the observed behavior?
IS-IS metric encoding capability influences which costs can be advertised and interpreted. This mechanism explains the case-specific corrective step: Use a supported consistent IS-IS metric style and cost plan across affected peers. Confirm the mechanism by verifying: Every device interprets intended link costs and SPF selects the documented shortest paths.
EVPN Type 2 carries MAC or MAC/IP reachability; Type 5 is used for IP-prefix reachability. This explains EVPN Type-2 MAC/IP route interpretation, but not why the issue in this scenario occurs. The specific mechanism is: IS-IS metric encoding capability influences which costs can be advertised and interpreted.
IS-IS uses Level-2 routing for inter-area exchange between Level-1 domains. This explains IS-IS level-2 backbone continuity, but not why the issue in this scenario occurs. The specific mechanism is: IS-IS metric encoding capability influences which costs can be advertised and interpreted.
Uncontrolled mutual route import can form routing feedback loops and unstable route selection. This explains Route import feedback loop, but not why the issue in this scenario occurs. The specific mechanism is: IS-IS metric encoding capability influences which costs can be advertised and interpreted.
A Huawei network is left in this condition: A backbone expands link costs beyond the narrow-metric range but several Huawei routers retain incompatible IS-IS metric styles. What direct operational or security risk is most relevant if it is not corrected?
Mismatched metric styles can hide prefixes or distort shortest-path selection. This is the direct exposure created by IS-IS metric-style consistency. Mitigate it through: Use a supported consistent IS-IS metric style and cost plan across affected peers. Then test: Every device interprets intended link costs and SPF selects the documented shortest paths.
An otherwise live router can remain a dead-end gateway without relevant upstream tracking. This consequence is associated more directly with VRRP uplink tracking and priority decrement. For the stated conditions the immediate exposure is: Mismatched metric styles can hide prefixes or distort shortest-path selection.
Unrestricted leaking can expand LSDB size and introduce unintended route preference. This consequence is associated more directly with IS-IS selective L2-to-L1 route leaking. For the stated conditions the immediate exposure is: Mismatched metric styles can hide prefixes or distort shortest-path selection.
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: Mismatched metric styles can hide prefixes or distort shortest-path selection.
Before changing the Huawei network configuration, an engineer investigates: A backbone expands link costs beyond the narrow-metric range but several Huawei routers retain incompatible IS-IS metric styles. Which diagnostic check should be performed first?
Check metric-style configuration, TLVs, interface costs and selected SPF paths. This check isolates the suspected cause before an unsafe change. If confirmed, the targeted action is: Use a supported consistent IS-IS metric style and cost plan across affected peers. Successful verification is: Every device interprets intended link costs and SPF selects the documented shortest paths.
Compare received candidate paths, LOCAL_PREF values, route policy and installed best path. This check would diagnose BGP local preference internal egress, but would not first isolate the described IS-IS metric-style consistency. Begin with: Check metric-style configuration, TLVs, interface costs and selected SPF paths.
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 IS-IS metric-style consistency. Begin with: Check metric-style configuration, TLVs, interface costs and selected SPF paths.
Inspect source system ID, LSP sequence, remaining lifetime and interface flap history. This check would diagnose IS-IS LSP sequence and aging, but would not first isolate the described IS-IS metric-style consistency. Begin with: Check metric-style configuration, TLVs, interface costs and selected SPF paths.
A Huawei Datacom engineer is investigating the following situation: An upgraded IS-IS domain receives routes with unexpected costs because wide metrics are inconsistently deployed. Which corrective action best resolves the specified issue?
Use a supported consistent IS-IS metric style and cost plan across affected peers. Technical basis: IS-IS metric encoding capability influences which costs can be advertised and interpreted. The measurable acceptance criterion is: Every device interprets intended link costs and SPF selects the documented shortest paths.
Examine LSP sequence numbers and lifetime behavior and correct the root flooding or instability problem. This is a legitimate response to the different issue of IS-IS LSP sequence and aging, but it does not correct the specific IS-IS metric-style consistency condition reported. The relevant technical distinction is: IS-IS metric encoding capability influences which costs can be advertised and interpreted.
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 IS-IS metric-style consistency condition reported. The relevant technical distinction is: IS-IS metric encoding capability influences which costs can be advertised and interpreted.
Restore an appropriate contiguous Level-2 IS-IS inter-area backbone path and verify level participation. This is a legitimate response to the different issue of IS-IS level-2 backbone continuity, but it does not correct the specific IS-IS metric-style consistency condition reported. The relevant technical distinction is: IS-IS metric encoding capability influences which costs can be advertised and interpreted.
A team is validating a Huawei network repair: An upgraded IS-IS domain receives routes with unexpected costs because wide metrics are inconsistently deployed. Which observable result provides the clearest evidence of success?
Every device interprets intended link costs and SPF selects the documented shortest paths. This result directly tests whether the correct action worked: Use a supported consistent IS-IS metric style and cost plan across affected peers. This is explained by: IS-IS metric encoding capability influences which costs can be advertised and interpreted.
The neighboring AS picks the intended ingress where the MED comparison is applicable. That observation would support a separate case of BGP MED same-neighbor-AS comparison, not verification of the reported IS-IS metric-style consistency. The relevant observable outcome here is: Every device interprets intended link costs and SPF selects the documented shortest paths.
Level-2 adjacencies carry the required inter-area reachability between participating regions. That observation would support a separate case of IS-IS level-2 backbone continuity, not verification of the reported IS-IS metric-style consistency. The relevant observable outcome here is: Every device interprets intended link costs and SPF selects the documented shortest paths.
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 IS-IS metric-style consistency. The relevant observable outcome here is: Every device interprets intended link costs and SPF selects the documented shortest paths.
Consider the following Huawei Datacom deployment: An upgraded IS-IS domain receives routes with unexpected costs because wide metrics are inconsistently deployed. Which technical principle best explains the observed behavior?
IS-IS metric encoding capability influences which costs can be advertised and interpreted. This mechanism explains the case-specific corrective step: Use a supported consistent IS-IS metric style and cost plan across affected peers. Confirm the mechanism by verifying: Every device interprets intended link costs and SPF selects the documented shortest paths.
IS-IS Level-1 neighbor relationships require compatible area addressing while Level-2 uses broader backbone reachability. This explains IS-IS level-1 area adjacency, but not why the issue in this scenario occurs. The specific mechanism is: IS-IS metric encoding capability influences which costs can be advertised and interpreted.
EVPN Type 2 carries MAC or MAC/IP reachability; Type 5 is used for IP-prefix reachability. This explains EVPN Type-2 MAC/IP route interpretation, but not why the issue in this scenario occurs. The specific mechanism is: IS-IS metric encoding capability influences which costs can be advertised and interpreted.
In AC+Fit AP WLAN architectures the AC centrally manages AP configuration over CAPWAP. This explains WLAN AC and Fit AP CAPWAP, but not why the issue in this scenario occurs. The specific mechanism is: IS-IS metric encoding capability influences which costs can be advertised and interpreted.
A Huawei network is left in this condition: An upgraded IS-IS domain receives routes with unexpected costs because wide metrics are inconsistently deployed. What direct operational or security risk is most relevant if it is not corrected?
Mismatched metric styles can hide prefixes or distort shortest-path selection. This is the direct exposure created by IS-IS metric-style consistency. Mitigate it through: Use a supported consistent IS-IS metric style and cost plan across affected peers. Then test: Every device interprets intended link costs and SPF selects the documented shortest paths.
Unrestricted leaking can expand LSDB size and introduce unintended route preference. This consequence is associated more directly with IS-IS selective L2-to-L1 route leaking. For the stated conditions the immediate exposure is: Mismatched metric styles can hide prefixes or distort shortest-path selection.
Removing all protocol authentication to restore routing exposes adjacencies to spoofed updates. This consequence is associated more directly with OSPF authentication-key mismatch. For the stated conditions the immediate exposure is: Mismatched metric styles can hide prefixes or distort shortest-path selection.
Isolated Level-1 areas cannot reach unrelated areas without a working Level-2 path. This consequence is associated more directly with IS-IS level-2 backbone continuity. For the stated conditions the immediate exposure is: Mismatched metric styles can hide prefixes or distort shortest-path selection.
Before changing the Huawei network configuration, an engineer investigates: An upgraded IS-IS domain receives routes with unexpected costs because wide metrics are inconsistently deployed. Which diagnostic check should be performed first?
Check metric-style configuration, TLVs, interface costs and selected SPF paths. This check isolates the suspected cause before an unsafe change. If confirmed, the targeted action is: Use a supported consistent IS-IS metric style and cost plan across affected peers. Successful verification is: Every device interprets intended link costs and SPF selects the documented shortest paths.
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 IS-IS metric-style consistency. Begin with: Check metric-style configuration, TLVs, interface costs and selected SPF paths.
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 IS-IS metric-style consistency. Begin with: Check metric-style configuration, TLVs, interface costs and selected SPF paths.
Compare interface MTU, DD packet MTU fields, and OSPF neighbor transition logs. This check would diagnose OSPF MTU stalls ExStart, but would not first isolate the described IS-IS metric-style consistency. Begin with: Check metric-style configuration, TLVs, interface costs and selected SPF paths.
Please check your mailbox for a message from support@examlabs.com and follow the directions.
