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

Commissioning OSPF Routes

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

Prerequisites

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

Context

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

Figure 6-3 Typical networking for commissioning OSPF routes

Procedure

  1. Run the display ospf peer command on the commissioning device to view its OSPF neighbor information.

    <HUAWEI> display ospf peer
            OSPF Process 1 with Router ID 1.1.1.1
               Neighbors
    Area 0.0.0.0 interface 192.168.1.1(GigabitEthernet1/0/0)'s neighbors
    Router ID: 2.2.2.2  Address: 192.168.1.2 
    State: Full  Mode:Nbr is Slave  Priority: 1
    DR: None  BDR: None  MTU: 0
    Dead timer due in 35 sec
    Retrans timer interval: 5
    Neighbor is up for 00:00:05
    Authentication Sequence: [ 0 ]

    The command output in bold in the command output shows the OSPF neighbor information. Then check the number of neighbors, whether or not the neighbor relationships are in the Full state (indicating that the neighbors have finished LSDB synchronization and established the Full adjacency) and whether or not the neighbors can remain in the Up state for a long time. If a neighbor stays in the Up state for a short period of time, it indicates that the OSPF neighbor relationship has been recently interrupted. Pay attention to such a symptom.

  2. Run the display ospf routing command on the commissioning device to view information about the OSPF routing table.

    Intra-area OSPF routes:

    <HUAWEI> display ospf routing
              OSPF Process 1 with Router ID 1.1.1.1
                       Routing Tables
    
     Routing for Network
     Destination      Cost  Type       NextHop         AdvRouter       Area
     192.168.1.0/24   1     Stub       192.168.1.1     1.1.1.1         0.0.0.0
     2.2.2.2/32       1     Stub       192.168.1.2     2.2.2.2         0.0.0.0
     172.16.1.0/24   2     Stub       192.168.1.2     2.2.2.2         0.0.0.0
     Total Nets: 3
     Intra Area: 3  Inter Area: 0  ASE: 0  NSSA: 0

    In the command output, check the destination network addresses, route costs, destination network types, next-hop addresses, routers advertising the routes, AS numbers, and total number of networks of each type. The OSPF routes in the preceding command output are intra-area routes.

    Inter-area OSPF routes:

    <HUAWEI> display ospf routing
              OSPF Process 1 with Router ID 1.1.1.1
                       Routing Tables
    
     Routing for Network
     Destination        Cost  Type       NextHop         AdvRouter       Area
     192.168.1.0/24     1     Stub       192.168.1.1     1.1.1.1         0.0.0.0
     2.2.2.2/32         1     Stub       192.168.1.2     2.2.2.2         0.0.0.0
     172.16.1.0/24     2     Inter-area 192.168.1.2     2.2.2.2         0.0.0.0
    
     Routing for ASEs
     Destination        Cost      Type       Tag         NextHop         AdvRouter
     10.120.0.0/16     3         Type1      1           192.168.1.2     3.3.3.3
     10.0.0.0/24       3         Type1      1           192.168.1.2     3.3.3.3
    
     Total Nets: 5
     Intra Area: 2  Inter Area: 1  ASE: 2  NSSA: 0

    If the commissioning device has learned routes from other areas using OSPF, the routing table will contain them. The command output in bold in the command output shows that there are three inter-area routes and one AS external route.

  3. Run the display ospf interface command on the commissioning device to view its OSPF interface information.

    <HUAWEI> display ospf interface
    
              OSPF Process 1 with Router ID 1.1.1.1
                      Interfaces
    
     Area: 0.0.0.0          (MPLS TE not enabled)
     Interface           IP Address      Type         State    Cost    Pri
     GigabitEthernet1/0/0            192.168.1.1     Broadcast    DR       1       1
     Loop0               1.1.1.1         P2P          P-2-P    0       1    
    

    The command output in bold in the command output shows the OSPF interface information. Check that the type, state, and cost of the OSPF-enabled interface are correct.

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

    <HUAWEI> display current-configuration 
    #          
    ospf 1 vpn-instance comm_signal                                                  
     default-route-advertise always cost 1024 type 2                                
     import-route direct                                                            
     import-route static                                                            
     route-tag 100                                                                  
     area 0.0.0.0                                                                   
      network 192.168.1.0 0.0.0.255                                                    
      network 1.1.1.1 0.0.0.0
    #                                                                             

    The command output in bold in the command output shows the configurations that have taken effect. Check that the OSPF VPN is correctly configured by checking the configurations of the OSPF process ID, tag value, and default route delivery.

  5. Run the display ospf error command on the commissioning device to view OSPF errors.

    <HUAWEI> display ospf error
    OSPF Process 1 with Router ID 1.1.1.1                               
                      OSPF error statistics                                         
                                                                                    
    Interface : GigabitEthernet1/0/0 
    General packet errors:
     0       : IP: received my own packet     0       : Bad packet
     0       : Bad version                    0       : Bad checksum
     0       : Bad area id                    0       : Drop on unnumbered interface
     0       : Bad virtual link               0       : Bad authentication type
     0       : Bad authentication key         0       : Packet too small
     0       : Packet size > ip length        0       : Transmit error
     0       : Interface down                 0       : Unknown neighbor
    
    HELLO packet errors:
     0       : Netmask mismatch               0       : Hello timer mismatch
     0       : Dead timer mismatch            0       : Extern option mismatch
     0       : Router id confusion            0       : Virtual neighbor unknown
     0       : NBMA neighbor unknown          0       : Invalid Source Address
    
    DD packet errors:
     0       : Neighbor state low             0       : Extern option mismatch
     0       : Unknown LSA type               0       : MTU option mismatch
     0       : Router id confusion
    
    LS ACK packet errors:
     0       : Neighbor state low             1       : Bad ack
     9       : Duplicate ACK                  0       : Unknown LSA type
    
    LS REQ packet errors:
     0       : Neighbor state low             0       : Bad request
     0       : Empty request
    
    LS UPD packet errors:
     0       : Neighbor state low             0       : LSA checksum bad
     0       : Received less recent LSA       0       : Unknown LSA type
     0       : Newer self-generate LSA
     1       : Received LSA within LSA Arrival interval
    
    Opaque errors:
     0       : 9-out of flooding scope        0       : 10-out of flooding scope
     0       : 11-out of flooding scope
    
    Retransmission for packet over Limitation errors:
     0       : Number for DD Packet           0       : Number for Update Packet
     0       : Number for Request Packet
    
    Receive Grace LSA errors:
     0       : Number of invalid LSAs         0       : Number of policy failed LSAs
     0       : Number of wrong period LSAs
    
    Configuration errors:
     0        : Tunnel cost mistake
     0        : The network type of the neighboring interface is not consistent

    To locate OSPF faults, you can run this command to view OSPF error information. OSPF error information is a basis for OSPF fault diagnosis.

  6. Run the ping command on the commissioning device to test the availability of OSPF routes.

    <HUAWEI> ping 172.16.1.10
      PING 172.16.1.10: 56  data bytes, press CTRL_C to break
        Reply from 172.16.1.10: bytes=56 Sequence=1 ttl=255 time=5 ms
        Reply from 172.16.1.10: bytes=56 Sequence=2 ttl=255 time=1 ms
        Reply from 172.16.1.10: bytes=56 Sequence=3 ttl=255 time=1 ms
        Reply from 172.16.1.10: bytes=56 Sequence=4 ttl=255 time=1 ms
        Reply from 172.16.1.10: bytes=56 Sequence=5 ttl=255 time=1 ms
    
      --- 172.16.1.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 OSPF route to the network segment 172.16.1.10.

Troubleshooting

If the OSPF neighbor relationship is Down after OSPF is configured, complete the following:

  1. Check logs to find the cause of the Down OSPF neighbor relationship.

    Run the display logbuffer command, and you can find the following log information.

    If the log message is as follows:

    VRPV8 %%01 ospfv2comm/6/NBR_CHANGE(l):CID=[UINT];Neighbor changes event: neighbor status changed. (ProcessId=[UINT], NbrIpAddr=[IPADDR], NbrEvent=[UINT], NbrPreviousState=[UINT], NbrCurrentState=[UINT])

    It indicates that the neighbor status changes. Check the NbrEvent field which records the cause of the fault. The possible causes of the fault are as follows:

    • Inactivity (NbrEvent=7)

      The InactivityTimer event of the neighbor state machine occurs. If a device does not receive any Hello packet from its neighbor within the deadtime, the OSPF neighbor relationship becomes Down. In this case, go to Step 2.

    • LLDown (NbrEvent=6)

      The LLDown event of the neighbor state machine occurs. It indicates that the lower-layer protocol notifies the upper layer that the neighbor is unreachable. In this case, go to Step 2.

    • 1-Way Received (NbrEvent=4)

      The 1-Way Received event of the neighbor state machine occurs. A 1-Way Hello packet is sent from the remote end to the local end when the OSPF status on the remote end changes to Down. After receiving the packet, the OSPF status on the local end also changes to Down. In this case, check the remote end to rectify any possible fault.

    • Kill Neighbor (NbrEvent=5)

      This event indicates that the interface or BFD session becomes Down. Run the display interface [ interface-type [ interface-number ] ] command to check the interface status and rectify any possible fault.

    If the log message is as follows:

    VRPV8 %%01 ospfv2comm/6/OSPF_RESET(l):CID=[UINT];OSPF process or area reset. (CompCID=[UINT], Parameter=[UINT], ResetReason=[UINT])

    It indicates that the reset ospf process command has been run. Whether this command has been run can be known by checking the operation records or log information.

    In other cases, go to Step 9.

  2. Check that the link between the two ends works normally.

    Check that the link between the two ends is working normally, including the transmission devices. If the link works properly, go to Step 3.

  3. Check that the CPU usage is within the normal range.

    Check whether or not the CPU usage on the MPU or interface board of the faulty device is too high. If the CPU usage is too high, OSPF fails to receive and send protocol packets, causing the neighbor relationship to flap. In this case, rectify the high CPU usage fault. If the CPU usage is within the normal range, go to Step 4.

  4. Check that the interface status is Up.

    Run the display interface [ interface-type [ interface-number ] ] command to check the physical status of the interface. If the physical status of the interface is Down, rectify the interface fault.

    If the physical status of the interface is Up, run the display ospf interface command to check that the OSPF status of the interface is Up.

    <HUAWEI> display  ospf interface
    
              OSPF Process 1 with Router ID 1.1.1.1
                      Interfaces
    
     Area: 0.0.0.0          (MPLS TE not enabled)
     Interface           IP Address      Type         State    Cost    Pri
     GigabitEthernet1/0/0            192.168.1.1     Broadcast    DR       1       1
     Loop0               1.1.1.1         P2P          P-2-P    0       1    
    
    • If the OSPF status of the interface is Down, run the display ospf cumulative command to check whether the number of interfaces enabled with OSPF in the OSPF process exceeds the limit. If so, reduce the number of interfaces enabled with OSPF.

      <HUAWEI> display ospf cumulative
      
                OSPF Process 1 with Router ID 1.1.1.1
                        Cumulations
      
        IO Statistics
                     Type        Input     Output
                    Hello        17139      16805
           DB Description           89        140
           Link-State Req            1          0
        Link-State Update         2889       3494
           Link-State Ack         1701       1818
        
        Learnt-ASE: (Disabled)
      
        LSAs originated by this router  :
        Router: 1
        Network: 1
        Sum-Net: 0
        Sum-Asbr: 0
        External: 0
        NSSA: 0
        Opq-Link: 0
        Opq-Area: 47
        Opq-As: 0
        LSAs Originated: 49  LSAs Received: 127
      
        Routing Table:
          Intra Area: 18  Inter Area: 0  ASE: 0
      
        Up Interface Cumulate: 11
      
            Neighbor Cumulate:
        =======================================================
           Neighbor cumulative data. (Process 1)
        -------------------------------------------------------
        Down:        0 Init:         0 Attempt:     0 2-Way:    0
        Exstart:     0 Exchange:     0 Loading:     0 Full:     7
        Retransmit Count:0
      
            Neighbor cumulative data. (Total)
        -------------------------------------------------------
        Down:        0 Init:         0 Attempt:     0 2-Way:    0
        Exstart:     0 Exchange:     0 Loading:     0 Full:     7
        Retransmit Count:0
      
    • If the OSPF status of the interface is normal (for example, DR, BDR, DR Other, or P2P), go to Step 5.

  5. Check that the IP addresses of the two ends are on the same network segment.

    • If the IP addresses of the two ends are on different network segments, modify the IP address of one end.

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

  6. Check that MTUs of the interfaces on both ends are consistent.

    If ospf mtu-enable is enabled on the interfaces, the interface MTUs must be consistent. Otherwise, OSPF neighbors cannot negotiate with each other successfully.

    • If MTUs of the interfaces on both ends are inconsistent, run the mtu mtu command in the interface view to change MTUs of the interfaces on both ends to be consistent.

    • If the MTUs of the interfaces on both ends are consistent, go to Step 7.

  7. Check that there is at least one interface whose priority is not 0.

    On the broadcast and NBMA networks, there should be at least one interface whose priority is not 0, which ensures that a DR is elected correctly. Otherwise, the state of the OSPF neighbor relationship can only reach 2-Way.

    Run the display ospf interface command to view the interface priority.

    <HUAWEI> display ospf interface
    
              OSPF Process 1 with Router ID 1.1.1.1
                      Interfaces
    
     Area: 0.0.0.0          (MPLS TE not enabled)
     Interface           IP Address      Type         State    Cost    Pri
     GigabitEthernet1/0/0            192.168.1.1     Broadcast    DR       1       1
     Loop0               1.1.1.1         P2P          P-2-P    0       1    
    
  8. Check that OSPF configurations on two ends are correct.

    1. Check whether the OSPF router IDs of the two ends conflict.

      <HUAWEI> display ospf brief
                OSPF Process 1 with Router ID 1.1.1.1
                        OSPF Protocol Information
      

      If OSPF router IDs of the two ends conflict, correct the configurations. Otherwise, proceed with the following check.

    2. Check whether the OSPF area configurations on two ends are consistent.

      <HUAWEI> display ospf  interface
      
                OSPF Process 1 with Router ID 1.1.1.1
                        Interfaces
      
       Area: 0.0.0.0          (MPLS TE not enabled)
       Interface           IP Address      Type         State    Cost    Pri
       GigabitEthernet1/0/0            192.168.1.1     Broadcast    DR       1       1
       Loop0               1.1.1.1         P2P          P-2-P    0       1    
      
    3. Check whether other OSPF configurations on both ends are consistent.

      Run the display ospf error command every 10s for 5 minutes.

      <HUAWEI> display ospf error
      OSPF Process 1 with Router ID 1.1.1.1                               
                        OSPF error statistics                                         
                                                                                      
      Interface : GigabitEthernet1/0/0 
      General packet errors:
       0       : IP: received my own packet     0       : Bad packet
       0       : Bad version                    0       : Bad checksum
       0       : Bad area id                    0       : Drop on unnumbered interface
       0       : Bad virtual link               0       : Bad authentication type
       0       : Bad authentication key         0       : Packet too small
       0       : Packet size > ip length        0       : Transmit error
       0       : Interface down                 0       : Unknown neighbor
      
      HELLO packet errors:
       0       : Netmask mismatch               0       : Hello timer mismatch
       0       : Dead timer mismatch            0       : Extern option mismatch
       0       : Router id confusion            0       : Virtual neighbor unknown
       0       : NBMA neighbor unknown          0       : Invalid Source Address
      
      DD packet errors:
       0       : Neighbor state low             0       : Extern option mismatch
       0       : Unknown LSA type               0       : MTU option mismatch
       0       : Router ID confusion
      
      LS ACK packet errors:
       0       : Neighbor state low             1       : Bad ack
       9       : Duplicate ACK                  0       : Unknown LSA type
      
      LS REQ packet errors:
       0       : Neighbor state low             0       : Bad request
       0       : Empty request
      
      LS UPD packet errors:
       0       : Neighbor state low             0       : LSA checksum bad
       0       : Received less recent LSA       0       : Unknown LSA type
       0       : Newer self-generate LSA
       1       : Received LSA within LSA Arrival interval
      
      Opaque errors:
       0       : 9-out of flooding scope        0       : 10-out of flooding scope
       0       : 11-out of flooding scope
      
      Retransmission for packet over Limitation errors:
       0       : Number for DD Packet           0       : Number for Update Packet
       0       : Number for Request Packet
      
      Receive Grace LSA errors:
       0       : Number of invalid LSAs         0       : Number of policy failed LSAs
       0       : Number of wrong period LSAs
      
      Configuration errors:
       0        : Tunnel cost mistake
       0        : The network type of the neighboring interface is not consistent
      
      • Check the Bad authentication type field. If the value of this field continually increases, it indicates that the OSPF authentication types of two ends that establish the neighbor relationship are different. In this case, you need to set the same authentication type for both ends.
      • Check the Hello timer mismatch field. If the value of this field continually increases, it indicates that the value of the Hello timers on both ends that establish the neighbor relationship are different. In this case, you need to check the interface configurations of the two ends and set the same value for their Hello timers.
      • Check the Dead timer mismatch field. If the value of this field continually increases, it indicates that the value of the dead timers on both ends that establish the neighbor relationship are different. In this case, you need to check the interface configurations of the two ends and set the same value for their dead timers.
      • Check the Extern option mismatch field. If the value of this field continually increases, it indicates that the area types of the two ends that establish the neighbor relationship are different (the area type of one device is common area, and the area type of the other device is stub area or NSSA). In this case, you need to set the same area type for both ends.

    If the fault persists, proceed to Step 9.

  9. 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 devices
Translation
Download
Updated: 2019-01-02

Document ID: EDOC1100055014

Views: 4743

Downloads: 63

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