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

NE40E V800R010C10SPC500 Commissioning Guide

This is NE40E V800R010C10SPC500 Commissioning Guide
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).
Commissioning MPLS TE

Commissioning MPLS TE

Users can choose to configure a type of MPLS tunnel based on the actual network planning. This section describes how to commission MPLS TE.

Prerequisites

The following configurations are complete and the device is running normally:

Context

On the network shown in Figure 6-8, MPLS TE is configured on the network.

Figure 6-8 Typical networking for configuring MPLS TE

Procedure

  1. Run the display interface tunnel command on the commissioning device to view basic information about tunnel interfaces.

    <HUAWEI> display interface Tunnel 10
    Tunnel10 current state : UP
    Line protocol current state : UP
    Last line protocol up time : 2011-05-22 17:00:02
    Description: HUAWEI, Quidway Series, Tunnel10 Interface (ifindex: 171, vr: 0)
    Route Port,The Maximum Transmit Unit is 1500
    Internet Address is unnumbered, using address of LoopBack0(1.1.1.1/32)
    Encapsulation is TUNNEL, loopback not set
    Tunnel destination 2.2.2.2
    Tunnel up/down statistics 1
    Tunnel protocol/transport MPLS/MPLS, ILM is available,
    primary tunnel id is 0x1569, secondary tunnel id is 0x0
    Current system time: 2011-05-22 17:01:01
        300 seconds output rate 0 bits/sec, 0 packets/sec
        0 seconds output rate 0 bits/sec, 0 packets/sec
        0 packets output,  0 bytes
        0 output error
        0 output drop
        Last 300 seconds input utility rate:  0.00%
        Last 300 seconds output utility rate: 0.00%
    
    

    The command output in bold shows that the tunnel interface status and link-layer protocol status are both Up.

  2. Run the display mpls te tunnel-interface command on the commissioning device to view information about the tunnel interfaces on the local node.

    <HUAWEI> display mpls te tunnel-interface 10
        Tunnel Name       : Tunnel10
        Signalled Tunnel Name: -
        Tunnel State Desc : CR-LSP is Up
        Tunnel Attributes   :
        Active LSP          : Primary LSP
        Traffic Switch      : -
        Session ID          : 129
        Ingress LSR ID      : 1.1.1.1               Egress LSR ID: 2.2.2.2
        Admin State         : UP                    Oper State   : UP
        Signaling Protocol  : RSVP
        FTid                : 129
        Tie-Breaking Policy : None                  Metric Type  : None
        BypassTunnel Flag   : Not Supported
        Bfd Cap             : None                  Retry Int    : -
        Reopt               : Disabled              Reopt Freq   : -
        Auto BW             : Disabled
        Current Collected BW: -                     Auto BW Freq : -
        Min BW              : -                     Max BW       : -
        Tunnel Group        : -
        Interfaces Protected: -
        Excluded IP Address : -
        Is On Radix-Tree    : -                     Referred LSP Count: -
        Primary Tunnel      : -                     Pri Tunn Sum : -
        Backup Tunnel       : -
        Group Status        : -                     Oam Status   : -
        IPTN InLabel        : -
        BackUp LSP Type     : None                  BestEffort   : Disabled
        Secondary HopLimit  : -
        BestEffort HopLimit  : -
        Secondary Explicit Path Name: -
        Secondary Affinity Prop/Mask: 0x0/0x0
        BestEffort Affinity Prop/Mask: 0x0/0x0
        IsConfigLspConstraint: -
    
        Primary LSP ID      : 1.1.1.1:250
        LSP State           : UP                    LSP Type     : Primary
        Setup Priority      : 7                     Hold Priority: 7
        IncludeAll          : 0x0
        IncludeAny          : 0x0
        ExcludeAny          : 0x0
        Affinity Prop/Mask  : 0x0/0x0               Resv Style   :  SE
        Configured Bandwidth Information:
        CT0 Bandwidth(Kbit/sec): 20000           CT1 Bandwidth(Kbit/sec): 0
        CT2 Bandwidth(Kbit/sec): 0               CT3 Bandwidth(Kbit/sec): 0
        CT4 Bandwidth(Kbit/sec): 0               CT5 Bandwidth(Kbit/sec): 0
        CT6 Bandwidth(Kbit/sec): 0               CT7 Bandwidth(Kbit/sec): 0
        Actual Bandwidth Information:
        CT0 Bandwidth(Kbit/sec): 20000           CT1 Bandwidth(Kbit/sec): 0
        CT2 Bandwidth(Kbit/sec): 0               CT3 Bandwidth(Kbit/sec): 0
        CT4 Bandwidth(Kbit/sec): 0               CT5 Bandwidth(Kbit/sec): 0
        CT6 Bandwidth(Kbit/sec): 0               CT7 Bandwidth(Kbit/sec): 0
        Explicit Path Name  : -                                Hop Limit: -
        Record Route        : Disabled              Record Label : Disabled
        Route Pinning       : Disabled
        FRR Flag            : Disabled
        IdleTime Remain     : -
        BFD Status          : -
    
    

    Check that the tunnel configurations on the local node are correct. If CR-LSP is Up is displayed in the command output, it indicates that the tunnel has been established successfully.

  3. Run the display mpls te cspf tedb command to view TEDB information.

    <HUAWEI> display mpls te cspf tedb all
    Maximum Nodes Supported: 2000     Current Total Node Number: 2
    Maximum Links Supported: 8000     Current Total Link Number: 2
    Maximum SRLGs supported: 10000    Current Total SRLG Number: 0
    Id      Router-Id       IGP       Process-Id      Area             Link-Count
    1       1.1.1.1         ISIS      100             Level-2          1
    2       2.2.2.2         ISIS      100             Level-2          1
    

    Check whether the link information in the TEDB is correct.

  4. Run the display mpls rsvp-te interface command on the commissioning device to view RSVP-TE configurations on the interface.

    <HUAWEI> display mpls rsvp-te interface GigabitEthernet1/0/0
    Interface: GigabitEthernet1/0/0
     Interface Address: 192.168.1.1
     Interface state: UP                          Interface Index: 0x17
     Total-BW: 100000                             Used-BW: 20000
     Hello configured: NO                         Num of Neighbors: 1
     SRefresh feature: DISABLE                    SRefresh Interval: 30 sec
     Mpls Mtu: 1500                               Retransmit Interval: 500 msec
     Increment Value: 1
     Authentication: DISABLE
     Bfd Enabled: --                              Bfd Min-Tx: --
     Bfd Min-Rx: --                               Bfd Detect-Multi: --
     RSVP instance name: RSVP0
    

    The command output in bold shows RSVP-TE configurations. Check whether or not the interface enabled with RSVP-TE is configured correctly and is in the Up state. In addition, check that the total TE bandwidth on the interface and the used TE bandwidth meet the corresponding requirement.

  5. Run the display mpls rsvp-te peer command on the commissioning device to check whether or not an RSVP-TE neighbor relationship is established between the interfaces enabled with RSVP-TE.

    <HUAWEI> display mpls rsvp-te peer
    Interface GigabitEthernet1/0/0
     Neighbor Addr: 192.168.1.2
     SrcInstance: 0x8BDA7ADE                NbrSrcInstance: 0x0
     PSB Count: 0                           RSB Count: 1
     Hello Type Sent: NONE                  Neighbor Hello Extension: DISABLE
     SRefresh Enable: NO
     Authentication: DISABLE
     Last valid seq # rcvd: NULL
    
    Remote Node id Neighbor
     Neighbor Addr: 2.2.2.2
     SrcInstance: 0x8BDA7ADE                NbrSrcInstance: 0x0
     PSB Count: 0                           RSB Count: 0
     Hello Type Sent: NONE                  Neighbor Hello Extension: DISABLE
     SRefresh Enable: NO
     Authentication: DISABLE
     Last valid seq # rcvd: NULL
                                                                             
    
    

  6. Run the ping lsp command on the commissioning device to test the availability of the TE tunnel.

    <HUAWEI> ping lsp te Tunnel 10
      LSP PING FEC: TE TUNNEL IPV4 SESSION QUERY Tunnel10 : 100  data bytes, pres
    s CTRL_C to break
        Reply from 2.2.2.2: bytes=100 Sequence=1 time = 18 ms
        Reply from 2.2.2.2: bytes=100 Sequence=2 time = 8 ms
        Reply from 2.2.2.2: bytes=100 Sequence=3 time = 7 ms
        Reply from 2.2.2.2: bytes=100 Sequence=4 time = 6 ms
        Reply from 2.2.2.2: bytes=100 Sequence=5 time = 5 ms
    
      --- FEC: RSVP IPV4 SESSION QUERY Tunnel10 ping statistics ---
        5 packet(s) transmitted
        5 packet(s) received
        0.00% packet loss
        round-trip min/avg/max = 5/8/18 ms
    

Troubleshooting

If the established TE tunnel is in the Down state on a TE-deployed network, complete the following:

  1. Run the display current-configuration command on the TE-deployed node to check whether the tunnel configurations are committed.

    • If the tunnel configurations are not committed, commit the configurations.

    • If the tunnel configurations are committed, go to step 2.

  2. Check that CSPF has been successfully calculating paths.

    Run the display mpls te cspf destination ip-address explicit-path path-name command on the TE tunnel ingress. If command output is displayed, CSPF has been successfully calculating paths; if no command output is displayed, CSPF failed to calculate a path.

    • If CSPF failed to calculate a path, check whether routes to the destination of the TE tunnel exist.
      • If no route exists, rectify the route fault.

      • If reachable routes exist and they satisfy the requirements to establish a TE tunnel, rectify the fault by referring to the section "CSPF Calculation Fails."

    • If CSPF has been successfully calculating paths but the fault persists, go to Step 3.

  3. Check that RSVP is enabled on every device along the TE tunnel.

    The command output of display mpls te cspf destination ip-address explicit-path path-name in Step 2 contains a series of IP addresses. These IP addresses indicate the hops along the TE tunnel. On the interface mapped to each IP address, run the display current-configuration interface interface-name command to check if RSVP is enabled.

    • If an interface is not enabled with RSVP, enable RSVP on the interface.

    • If all interfaces are enabled with RSVP but the fault persists, go to Step 4.

  4. Check that devices along the TE tunnel have been successfully exchanging RSVP Path and Resv messages.

    Run the display mpls te tunnel-interface command on the TE tunnel ingress and check fields Ingress LSR ID, LSP ID, and Session ID in the command output. In Step 3, LSR A, LSR B, and LSR C represent the nodes along the TE tunnel.

    Complete the following to check that the RSVP Path message and RSVP Resv message are correctly transmitted:
    • Check that RSVP Path messages are correctly sent and received on every node along the LSP in the sending direction (LSR A -> LSR B -> LSR C).

      Run the display mpls rsvp-te psb-content command on every node the RSVP Path message travels through.

      • If the command output is not empty on any node, it can be concluded that RSVP Path messages are correctly sent and received between these nodes.

      • If the command output is empty on a node, it can be concluded that the node fails to receive RSVP Path messages from the upstream node.

    • Check whether RSVP Resv messages are correctly transmitted in the sending direction (LSR C -> LSR B -> LSR A).

      Run the display mpls rsvp-te rsb-content command on every node the RSVP Resv message travels.

      • If the command output is not empty on any node, it can be concluded that RSVP Resv messages are correctly transmitted.

      • If the command output is empty on a node, it can be concluded that the node fails to receive RSVP Resv messages from the upstream node.

    • If messages fail to be properly exchanged, follow the procedure described in "The Ping Operation Fails" in the HUAWEI NetEngine40E Universal Service Router Troubleshooting to rectify the message forwarding fault.

    • If messages are properly exchanged but the fault persists, go to Step 5.

  5. Collect the following information and contact Huawei technical support personnel:

    • Results of the preceding operation procedure
    • Configuration files, log files, and alarm files of the NE40E
Translation
Download
Updated: 2019-01-02

Document ID: EDOC1100055014

Views: 5527

Downloads: 74

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