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 IS-IS Routes

Commissioning IS-IS Routes

Users can choose to configure a routing protocol based on the actual network planning. This section describes how to commission IS-IS routes.

Prerequisites

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

Context

On the network shown in Figure 6-4, IS-IS is configured on the network to ensure successful communication between the commissioning device and the network connected to router B.

Figure 6-4 Typical networking for commissioning IS-IS routes

Procedure

  1. Run the display isis peer command on the commissioning device to view its IS-IS neighbor information.

    <HUAWEI> display isis peer
                               Peer information for ISIS( 1 )
                               ------------------------------
    System Id       Interface          Circuit Id         State HoldTime Type     PRI
    0000.0000.0002  GigabitEthernet1/0/0           0000.0000.0002.01  Up    11s      L1       64
    Total Peer (s): 1
    

    The command output in bold in the command output shows IS-IS neighbor information. Check the number of IS-IS neighbors, whether or not the neighboring interface is in the Up state, and the IS-IS type.

  2. Run the display isis interface command on the commissioning device to view its IS-IS interface information.

    <HUAWEI> display isis interface
                                     Interface information for ISIS(3)                       
                           ----------------------------------                       
     Interface       Id      IPV4.State       IPV6.State     MTU  Type     DIS      
     Loop0           001         Up              Down        1500 L2        --      
     GigabitEthernet1/0/0       002          Up              Down        4470 L1/L2    NONO      
     GigabitEthernet1/0/1        003  Mtu:Up/Lnk:Up/IP:Up    Down        4470 L1/L2      --      
    

    The command output in bold in the command output shows IS-IS interface information. Check that IS-IS-enabled interfaces are correctly configured, the number of IS-IS-enabled interfaces are correct, and that the IPv4.State of the interfaces is Up.

  3. Run the display isis route command on commissioning device to view IS-IS routing information.

    <HUAWEI> display isis route
    
    
                              Route information for ISIS(1)
                              -----------------------------
    
                              ISIS(1) level-1 Forwarding Table
                              --------------------------------
    
     IPV4 Destination   IntCost   ExtCost ExitInterface     NextHop         Flags
    -------------------------------------------------------------------------------
    192.168.2.0/24      20        NULL    GigabitEthernet1/0/0          192.168.1.2     A/-/-/-
    192.168.1.0/24      10        NULL    GigabitEthernet1/0/0          Direct          D/-/L/-
    
           Flags: D-Direct, A-Added to RM, L-Advertised in LSPs, U-Up/Down Bit Set
    

    Focus on checking that the destination IP addresses, internal costs, outbound interfaces, next-hop addresses, and routing information flags are correct.

  4. Run the display current-configuration command on for commissioning device to check the configurations that have taken effect.

    <HUAWEI> display current-configuration 
    #          
    isis 1                                                                         
     cost-style wide                                                                
     flash-flood level-1                                                            
     flash-flood level-2                                                            
     network-entity 86.0001.2100.7800.0074.00                                       
     is-name ngn-r2-b-sxxa-2   
     import-route isis level-2 into level-1  //Route leaking is required only on the BR but not the AR.                    
     nexthop 192.168.1.2 weight 100  //An IS-IS weight is set correctly. (The next hop indicates the peer IP address.)          
     timer spf 1 50 50                                                              
     traffic-eng level-2  //Enable different levels of TE for different IS-IS processes. On the BR with TE not deployed, this command is not required.
      #                                                                             
    

    There is a description following each field in the command output to emphasize the point that needs to be paid attention to.

  5. Run the ping command on the commissioning device to test the availability of IS-IS routes.

    <HUAWEI> ping 192.168.2.10
      PING 192.168.2.10: 56  data bytes, press CTRL_C to break
        Reply from 192.168.2.10: bytes=56 Sequence=1 ttl=255 time=5 ms
        Reply from 192.168.2.10: bytes=56 Sequence=2 ttl=255 time=1 ms
        Reply from 192.168.2.10: bytes=56 Sequence=3 ttl=255 time=1 ms
        Reply from 192.168.2.10: bytes=56 Sequence=4 ttl=255 time=1 ms
        Reply from 192.168.2.10: bytes=56 Sequence=5 ttl=255 time=1 ms
    
      --- 192.168.2.10 ping statistics ---
        5 packet(s) transmitted
        5 packet(s) received
        0.00% packet loss
        round-trip min/avg/max = 1/1/5 ms                 

    The preceding command output shows that the commissioning device has a reachable IS-IS route to the network segment 192.168.2.10.

Troubleshooting

If the IS-IS neighbor relationship cannot be established after IS-IS is configured, complete the following:

  1. Check the status of IS-IS interfaces.

    Run the display isis interface command to check the state of interfaces enabled with IS-IS (the value of the IPv4.State or IPv6.State item).

    • If the state is Mtu:Up/Lnk:Dn/IP:Dn, go to Step 2.

    • If the state is Mtu:Dn/Lnk:Up/IP:Up, run the display current-configuration interface interface-type [ interface-number ] command to check the MTUs on the interfaces. Run the display current-configuration configuration isis command to check the lengths of LSPs in an IS-IS process.
      NOTE:

      If the lengths of LSPs cannot be viewed by using the display current-configuration configuration isis command, the default LSP lengths are used. The default LSP lengths can be viewed by using the display default-parameter isis command. The value of the LSP-Originate-Length field is the maximum length of an originated LSP, and the value of the LSP-Receive-Length field is the maximum length of a received LSP.

      On a P2P interface, the LSP length should not be greater than the MTU on the P2P interface. On a broadcast interface, the value obtained by the MTU on the interface subtracted by the LSP length should be equal to or greater than 3. If the condition is not met, run the lsp-length originate command in the interface view to change the MTU, or run the mtu command in the IS-IS view to change the LSP length.

      If the fault is still not rectified, go to Step 4.

    • If the state is Down, run the display current-configuration configuration isis command to check the configuration of the IS-IS process. Check whether the NET is configured in the IS-IS process. If not, configure the network-entity command in the IS-IS process.

      If the fault is still not rectified, go to Step 2.

    • If the state is Up, go to Step 4.

  2. Check that the interface status is Up.

    Run the display ip interface [ interface-type [ interface-number ] ] command to check the status of specified interfaces.

    • If the interface link status (Line protocol current state field in the output information ) is not Up, troubleshoot the interface fault. See the section "Physical Connection and Interfaces" or "L2 Network".

      If the fault is still not rectified, go to Step 3.

    • If the interface status is Up, go to Step 3.

  3. Check that the IP addresses of the two interfaces at both ends of the link are on the same network segment.

    • If the IP addresses of the two interfaces are on different network segments, change the IP addresses of the two interfaces to ensure that the two IP addresses are on the same network segment. If the fault is still not rectified, go to Step 4.

    • If the IP addresses of the two interfaces are on the same network segment, go to Step 4.

  4. Check that IS-IS can normally receive and send Hello packets.

    Run the display isis statistics packet [ interface interface-type interface-number ] command to check whether IS-IS can normally receive and send Hello packets.
    NOTE:

    The default interval at which IS-IS sends Hello packets is 10s. Therefore, run this command every 10s to check whether the packet statistics increase (L1 IIH or L2 IIH).

    On a broadcast interface, Hello packets have IS-IS levels, and therefore you can view the statistics about Hello packets based on the levels of established neighbor relationships. On a P2P interface, Hello packets have no IS-IS levels and are recorded as L2 IIH packets.

    • If the number of received Hello packets does not increase for a certain period, check whether the IS-IS packets are lost.

      • For Broadcast interface, run the debugging ethernet packet isis interface-type interface-number command. The following information indicates the interface can normally receive and send IS-IS Hello packets.
        *0.75124950 HUAWEI ETH/7/eth_rcv:Slot=1;Receive an Eth Packet, interface : Ethernet1/0/0, eth format: 3, length: 60, protoctype: 8000 isis, src_eth_addr: 00e0-fc37-08c1, dst_eth_addr: 0180-c200-0015
        *0.75124950 HUAWEI ETH/7/eth_send:Slot=1;Send an Eth Packet, interface : Ethernet1/0/0, eth format: 3, length: 112, protoctype: 8000 isis, src_eth_addr: 00e0-fc26-f9d9, dst_eth_addr : 0180-c200-0015
      NOTE:
      If the DIS field shown in the output of the display isis interface interface-type interface-numbercommand is "--", it indicates the interface type is P2P. Otherwise, the interface type is Broadcast.

      If the device can not normally receive and send Hello packets, go to Step 9.

    • If the device can normally receive Hello packets, go to Step 5.
      • If the interfaces at both ends of the link are trunk interfaces, check whether the numbers of the member interfaces in the Up state in the trunk interfaces are the same. If numbers of the member interfaces in the Up state in the trunk interfaces are different, add the required physical interfaces to the Trunk interface correctly. Otherwise, go to Step 2.
      • If the interfaces at both ends of the link are not trunk interfaces, go to Step 2.
  5. Check that the devices at both ends of the link are configured with different system IDs.

    Run the display current-configuration configuration isis command to check whether the system IDs of the two devices are the same.

    • If the system IDs of the two devices are the same, set different system IDs for the two devices.

    • If the system IDs of the two devices are different, go to Step 6.

  6. Check that the IS-IS levels of the two devices at both ends of the link are consistent.

    Run the display current-configuration configuration isis | include is-level command to check the levels of the IS-IS processes on the two devices. Then, run the display current-configuration interface interface-type interface-number | include isis circuit-level command to check whether the IS-IS levels of the interfaces at both ends of the link match. The IS-IS neighbor relationship can be established only when the IS-IS levels of the two interfaces match.

    NOTE:

    If the IS-IS levels of the two interfaces cannot be viewed by using the display current-configuration interface interface-type interface-number | include isis circuit-level command, the two interfaces use the default IS-IS level. The default IS-IS level can be viewed by using the display default-parameter isis command. The value of the Circuit-Level field is the default IS-IS level.

    The matching rules of interface levels are as follows:
    • If the level of the local interface is Level-1, the level of the remote interface must be Level-1 or Level-1-2.

    • If the level of the local interface is Level-2, the level of the remote interface must be Level-2 or Level-1-2.

    • If the level of the local interface is Level-1-2, the level of the remote interface can be Level-1, Level-2, or Level-1-2.

    • If the IS-IS levels of the two devices do not match, run the is-level command in the IS-IS view to set matching IS-IS levels for the two devices, or run the isis circuit-level command in the interface view to change the levels of related interfaces.

    • If the IS-IS levels of the two devices are consistent, go to Step 7.

  7. Check that the area addresses of the two devices at both ends of the link are the same.

    NOTE:

    If two devices at both ends of a link establish a Level-1 neighbor relationship, ensure that the two devices are in the same area.

    An IS-IS process can be configured with a maximum of three area addresses. As long as one of the area addresses of the local IS-IS process is the same as one of the area addresses of the remote IS-IS process, the Level-1 neighbor relationship can be established.

    When the IS-IS Level-2 neighbor relationship is established between two devices, you do not need to determine whether the area addresses of the two devices match.

    • If the area addresses of the two devices are different, run the network-entity command in the IS-IS view to set the same area address for the two devices.

    • If the area addresses of the two devices at both ends of the link are the same, go to Step 8.

  8. Check that the authentication configurations of the two devices at both ends of the link are the same.

    Run the display current-configuration interface interface-type interface-number | include isis authentication-mode command to check whether the IS-IS authentication configurations of the two interfaces at both ends of the link are the same.

    • If the authentication types on the two interfaces are different, run the isis authentication-mode command in the view of each of the two interfaces to set the same authentication type for the two interfaces.

    • If the authentication passwords on the two interfaces are different, run the isis authentication-mode command in the view of each of the two interfaces to set the same authentication password for the two interfaces.

    • If the authentication configurations of the two devices are the same, go to Step 9.

  9. Collect the following information and contact Huawei technical support personnel.

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

Document ID: EDOC1100055014

Views: 4814

Downloads: 63

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