No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

ME60 Troubleshooting Guide V1.0 (VRPv8)

This document provides the maintenance guide of the device, including daily maintenance, emergence maintenance, and typical troubleshooting.
Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
SR-BE Troubleshooting

SR-BE Troubleshooting

This section describes how to troubleshoot common SR-BE faults.

An SR-BE LSP Goes Down

This section describes the troubleshooting flowchart and provides a step-by-step troubleshooting procedure for the fault that an SR-BE LSP goes Down.

Common Causes

This section describes common causes for the fault that an SR-BE LSP goes Down.

Common causes are as follows:

  • A forwarding entry fails to be delivered..

  • The SR-BE LSP configuration is incomplete.

  • A route is inactive.

  • A prefix or SID conflict occurs.

  • An SR next hop does not exist.

  • A prefix SID is not within the smallest SRGB range among all SR NEs on the primary LSP.

Troubleshooting Flowchart

This section describes the troubleshooting flowchart for the fault that an SR-BE LSP is Down.

Run the ping lsp [ -a source-ip | -c count | -exp exp-value | -h ttl-value | -m interval | -s packet-size | -t time-out | -v | -g ] * segment-routing ip destination-address mask-length version draft2 [ remote remote-ip ] command to check SR-BE LSP connectivity. The ping fails.

The fault locating roadmap is as follows:
  • Check whether a forwarding entry is successfully delivered.
  • Check whether the SR-BE LSP configuration is incomplete.

  • Check whether a route is active.

  • Check whether the prefix or SID conflicts.
  • Check whether an SR next hop exists.
  • Check whether a prefix SID is within the smallest SRGB range among all SR NEs on the primary LSP.

Figure 4-99 illustrates the troubleshooting flowchart.

Figure 4-99 Troubleshooting flowchart for the fault that an SR-BE LSP goes Down

Troubleshooting Procedure

This section describes the troubleshooting procedure for the fault that an SR-BE LSP is Down.

NOTE:

After the commands are configured to troubleshoot the faults, check the configuration validation mode to ensure that the configurations take effect. Unless otherwise specified, this manual defaults to immediate validation mode.

  • In immediate validation mode, the configurations take effect after the commands are entered.
  • In two-phase validation mode, after the commands are configured, the commit command needs to be run to commit the configurations.

Save the results of each troubleshooting step so that if your troubleshooting attempts fail to correct the fault, you will have a record of your actions to present to Huawei.

Procedure

  1. Run the display segment-routing prefix mpls forwarding command to check the label forwarding table for segment routing.

    <HUAWEI> display segment-routing prefix mpls forwarding
    i 
            Segment Routing Prefix MPLS Forwarding Information
            --------------------------------------------------------------
            Role : I-Ingress, T-Transit, E-Egress, I And Transit
    
    Prefix             Label      OutLabel   Interface         NextHop     Role     MPLSMtu   Mtu       State          
    ----------------------------------------------------------------------------------------------------------
    1.1.1.1/32         160001     3          GE1/0/1           20.1.1.1    I&T      ---       1500      Active  
    2.2.2.2/32         160002     NULL       Loop1             127.0.0.1   E        ---       1500      Active
    
    Total information(s): 2

    • If the destination prefix information exists, go to Step 8.

    • If the destination prefix information does not exist, go to Step 2.

  2. Check that the SR-BE LSP configuration is incomplete.

    Use IS-IS as an IGP. Run the display current-configuration command on each node. Check whether the node configuration is consistent with the following example. If any configuration is missing, the configuration on an NE is incomplete.

    #
    mpls lsr-id 1.1.1.1
    #               
    mpls            
    #               
    segment-routing 
     tunnel-prefer segment-routing
    #               
    isis 1          
     segment-routing mpls
     segment-routing global-block 160000 161000
    #               
    interface LoopBack1
     ip address 10.1.1.1 255.255.255.255
     isis prefix-sid index 30

    • If a configuration is missing, reconfigure it and run the commit command to make the modification take effect.

    • If the configuration is complete, go to Step 3.

  3. Check the SR status mapped to the destination address prefix.

    Run the display segment-routing state ip-prefix ip-prefix mask-length command on the ingress of the LSP. Check the SR status information based on the address prefix.

    # Display segment routing status information (IS-IS).
    <HUAWEI> display segment-routing state ip-prefix 10.1.1.1 32
       Segment Routing State IP-Prefix 10.1.1.1 32
    -----------------------------------------------------------------
    Protocol                                : ISIS-L1
    Process ID                              : 1
    Prefix-sid                              : 77
    Route active state                      : Y
    Eligible within process                 : Y
    Eligible between processes or protocols : Y
    SR nexthop exist                        : Y
    Prefix-sid within min SRGB range        : Y
    
    Protocol                                : ISIS-L2
    Process ID                              : 1
    Prefix-sid                              : 77
    Route active state                      : Y
    Eligible within process                 : Y
    Eligible between processes or protocols : NA
    SR nexthop exist                        : N
    Prefix-sid within min SRGB range        : Y

    • If the Route active state field value is N, the route is inactive. In this case, go to Step 4.

    • If the Eligible within process or Eligible between processes or protocols field value is N, a SID or IP prefix exists. In this case, go to Step 5.

    • If the SR nexthop exist field value is N, no SR next hop exists. In this case, go to Step 6.

    • If the Prefix-sid within min SRGB range field value is N, the prefix SID is not within the smallest SRGB range, causing a failure to generate a label. The smallest SRGB range is the smallest value of all SRGB ranges on all nodes (including the root) on a complete path. In this case, go to Step 7.

    • If the preceding issues do not exist, go to Step 8.
  4. Obtain an IGP route type and troubleshoot the route issues by following the procedure in OSPF Troubleshooting or IS-IS Troubleshooting.
  5. Check the SID and IP prefix configurations on each node to determine the conflict type.
    • If a SID conflict occurs, obtain an IGP route type and run the isis prefix-sid or ospf prefix-sid command to modify the SID configurations to ensure that no conflict occurs on each node.
    • If a prefix conflict occurs, run the ip address ip-address { mask | mask-length } command to modify the prefix configuration to ensure that no conflict occurs on each node.
  6. Troubleshoot the nonexistent SR next hop.

    If no SR next hop exists, some configurations are missing on a node of a primary LSP, or the SID or IP prefix conflict occurs.
    1. If some configurations are missing on the node of the primary LSP (for example, SR is not enabled or the SRGB is not configured), go to Step 2.
    2. If a SID or IP prefix conflict occurs, go to Step 5.

  7. Run the segment-routing global-block command to modify the SRGB range on a node.
  8. Collect the following information and contact technical support personnel.

    • Results of the preceding procedure
    • Configuration, log, and alarm files of the device

Relevant Alarms and Logs

This section describes relevant alarms and logs for the fault that an SR-BE LSP is Down.

Relevant Alarms

None (This applies only to V800R010C00.)

OSPF_1.3.6.1.4.1.2011.5.25.353.2.1 hwSrPrefixSidConflict (This applies only to V800R010C10 and later.)

Relevant Logs
IS-IS:
  • ISIS/4/IS_PREFIX_SID_CONFLICT
  • ISIS/4/IS_PREFIX_SID_NOT_ELIGIBLE
  • ISIS/4/IS_PREFIX_SID_OVER_RANGE
OSPF:
  • OSPF/4/OSPF_SRGB_OVERLAP
  • OSPF/4/OSPF_PREFIX_SID_NOT_ELIGIBLE
  • OSPF/4/OSPF_PREFIX_SID_OVER_NHP_RANGE
  • OSPF/4/OSPF_PREFIX_SID_OVER_PASS_RANGE
  • OSPF/4/OSPF_PREFIX_SID_OVER_RANGE
  • OSPF/4/OSPF_SR_NODE_UNSUPPORT
  • OSPF/4/OSPF_SR_OUTIF_UNSUPPORT
Translation
Download
Updated: 2019-06-11

Document ID: EDOC1000175918

Views: 4761

Downloads: 209

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next