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

Commissioning EBGP Routes

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

Prerequisites

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

Context

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

Figure 6-6 Typical networking for commissioning EBGP routes

Procedure

  1. Run the display bgp peer command to view EBGP peer information.

     BGP local router ID : 1.1.1.1
     Local AS number : 100
     Total number of peers : 1             Peers in established state : 1
      Peer       V    AS  MsgRcvd  MsgSent  OutQ  Up/Down       State       PrefRcv
      2.2.2.2   4   200    274      207     0    03:07:01   Established       1

    The command output in bold shows EBGP peer information. Check that the EBGP peer address and AS number are correct. Normally, the EBGP peer relationship should be in the Established state.

  2. Run the display bgp routing-table command on the commissioning device to view EBGP routing information.

    • View all EBGP routing information:

      <HUAWEI> display bgp routing-table
      
      BGP Local router ID is 1.1.1.1 
      Status codes: * - valid, > - best, d - damped,               
                    h - history,  i - internal, s - suppressed, S - Stale               
                    Origin : i - IGP, e - EGP, ? - incomplete      
                                                                   
       Total Number of Routes: 4 
           Network            NextHop        MED        LocPrf    PrefVal Path/Ogn     
      *>   172.16.1.0       2.2.2.2          0                     0      200i 
      *>i  0.0.0.0           10.1.2.1        0          100        0      300i
      *>i  10.1.1.0           10.1.2.1        0          100        0      300i
      *>i  10.0.0.0          10.1.2.1        0          100        0      400i
      

      Check that the network addresses, next-hop addresses, metrics, and local preferences of BGP routes are correct.

    • View detailed information about the specified EBGP routes:

      <HUAWEI> display bgp routing-table 172.16.1.0
      
      BGP local router ID : 1.1.1.1
      Local AS number : 100
       Paths:   1 available, 1 best, 1 select
       BGP routing table entry information of 172.16.1.0/24:
       From: 2.2.2.2 (2.2.2.2)
       Route Duration: 00h00m33s
       Relay IP Nexthop: 192.168.1.2
       Relay IP Out-Interface: GigabitEthernet1/0/0
       Original nexthop: 2.2.2.2                                                  
       Qos information : 0x0
       Community:no-export
       AS-path 200, origin igp, MED 0, pref-val 0, valid, external, best, select, pre 255
       Not advertised to any peer yet

      The command output in bold shows detailed information about the specified EBGP routes. Check that the local router IDs, AS numbers, sources of EBGP routes, outbound interfaces, and next-hop addresses are correct. The EBGP routes in the command output have community attributes, which prevents router A from advertising the routes received from router B to other ASs.

    • View information about the routes with community attributes:

      <HUAWEI> display bgp routing-table community
      
       BGP Local router ID is 1.1.1.1
       Status codes: * - valid, > - best, d - damped,
                     h - history,  i - internal, s - suppressed, S - Stale
                     Origin : i - IGP, e - EGP, ? - incomplete
      
      
       Total Number of Routes: 1
            Network            NextHop        MED        LocPrf    PrefVal Community
      
       *>   172.16.1.0        2.2.2.2         0                     0      no-export
      

  3. Run the display bgp peer ipv4-address verbose command to view the configurations of GTSM and GR functions for EBGP.

    <HUAWEI> display bgp peer 2.2.2.2 verbose
    
             BGP Peer is 2.2.2.2,  remote AS 200
             Type: EBGP link
             BGP version 4, Remote router ID 2.2.2.2
             Update-group ID: 1
             BGP current state: Established, Up for 00h04m56s
             BGP current event: KATimerExpired
             BGP last state: Established
             BGP Peer Up count: 1
             Received total routes: 1
             Received active routes total: 1
             Advertised total routes: 0
             Port: Local - 179        Remote - 27225
             Configured: Active Hold Time: 180 sec   Keepalive Time:60 sec
             Received  : Active Hold Time: 180 sec
             Negotiated: Active Hold Time: 180 sec   Keepalive Time:60 sec
             Peer optional capabilities:
             Peer supports bgp multi-protocol extension
             Peer supports bgp route refresh capability
             Peer supports bgp 4-byte-as capability
             Address family IPv4 Unicast: advertised and received
     Received: Total 8 messages
                      Update messages                2
                      Open messages                  1
                      KeepAlive messages             5
                      Notification messages          0
                      Refresh messages               0
     Sent: Total 8 messages
                      Update messages                1
                      Open messages                  2
                      KeepAlive messages             5
                      Notification messages          0
                      Refresh messages               0
     Authentication type configured: None
     Last keepalive received:2011-05-22 15:32:02
     Minimum route advertisement interval is 30 seconds
     Optional capabilities:
     Route refresh capability has been enabled
     4-byte-as capability has been enabled
     Connect-interface has been configured
     GTSM has been enabled, valid-ttl-hops: 2
     Peer Preferred Value: 0
     Routing policy configured:
     No routing policy is configured
    

    The command output in bold shows that the GTSM function has been enabled, and the number of valid hops is 2, the BGP peer relationship is in the Established state, and the GR function is enabled for EBGP.

  4. Run the display bgp routing-table dampening parameter command and the display bgp routing-table dampened command to view the configured EBGP route dampening parameters and dampened EBGP routes respectively.

    <HUAWEI> display bgp routing-table dampening parameter
     Maximum Suppress Time(in second) : 3973
     Ceiling Value                    : 16000
     Reuse Value                      : 750
     HalfLife Time(in  second)        : 900
     Suppress-Limit                   : 2000
     Route-policy                     : dampen-policy     
    <HUAWEI> display bgp routing-table dampened
     Total Number of Routes: 1
      BGP Local router ID is 1.1.1.1
      Status codes: * - valid, > - best, d - damped,
                    h - history,  i - internal, s - suppressed, S - Stale
                    Origin codes: i - IGP, e - EGP, ? - incomplete
       Network          From        Reuse     Path/Origin
     d 10.1.2.0          2.2.2.2     00:09:33  200 i

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

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

    2.2.2.2 is the loopback address of router B.

Troubleshooting

If the BGP peer relationship cannot be established on a BGP-deployed network, complete the following:

  1. Run the ping command to check that BGP peers can ping each other successfully.

    • If they can ping each other successfully, it indicates that there are available routes between the BGP peers and that link transmission is normal. Then, go to Step 2.

      NOTE:

      Run the ping -a source-ip-address -is packetsize host command to detect the connectivity of each end. Because the source address is specified in this command, you can check whether or not routes between the two ends are accessible. By specifying the size of a Ping packet, you can also check whether or not long Ping packets can be normally transmitted over the link.

    • If the ping fails, find whether or not the routing tables of each end have available routes to each other.

  2. Check that no ACL is configured to filter packets whose destination port is TCP port 179.

    Run the display acl all command on two ends to check whether an ACL is configured to filter packets whose destination port is TCP port 179.

    <HUAWEI> display acl all
    Advanced Name ACL tcp, 1 rule
    ACL's step is 5
    ACL's match-order is config
      rule 5 deny tcp source-port eq bgp (0 times matched)
    
    • If an ACL is configured to filter packets whose destination port is TCP port 179, delete the ACL configuration.

    • If no ACL is configured to filter packets whose destination port is TCP port 179, go to Step 3.

  3. Check that the peer router ID does not conflict with the local router ID.

    Check information about BGP peers to ensure that their router IDs do not conflict. For example, if the IPv4 unicast peer relationship fails to be established, you can run the display bgp peer command to check whether or not the peer router ID conflicts with the local router ID. Take the following command output as an example:

    <HUAWEI> display bgp peer
    BGP local router ID : 172.16.10.109
     Local AS number : 41976
     Total number of peers : 12                Peers in established state : 4
    
      Peer            V          AS  MsgRcvd  MsgSent  OutQ  Up/Down       State PrefRcv
      10.10.11.101         4         100     1601     1443     0 23:21:56 Established   10000
      10.11.110.10       4         200     1565     1799     0 23:15:30 Established    9999
    NOTE:
    Check information about peers in other address families.
    • Run the display bgp vpnv4 all peer command to check information about all VPNv4 peers.
    • Run the display bgp ipv6 peer command to check information about IPv6 peers.
    • If the peer router ID conflicts with the local router ID, run the router-id command in the BGP view to modify the router IDs to agree. Generally, a loopback interface address is used as the local router ID.

    • If the peer router ID does not conflict with the local router ID, go to Step 4.

  4. Check that the peer AS number is configured correctly.

    Run the display bgp peer command on each end to check that the displayed peer AS number is the same as that of the remote end.

    <HUAWEI> display bgp peer
     BGP local router ID : 172.16.10.109
     Local AS number : 41976
     Total number of peers : 12                Peers in established state : 4
    
      Peer            V          AS  MsgRcvd  MsgSent  OutQ  Up/Down       State PrefRcv
      10.10.11.101         4         100     1601     1443     0 23:21:56 Established   10000
      10.11.110.10       4         200     1565     1799     0 23:15:30 Established    9999
    NOTE:
    Check information about peers in other address families.
    • Run the display bgp vpnv4 all peer command to check information about all VPNv4 peers.
    • Run the display bgp ipv6 peer command to check information about IPv6 peers.
    • If the peer AS number is configured incorrectly, change it to be the same as that the remote end.

    • If the peer AS number is configured correctly, go to Step 5.

  5. Check whether or not BGP configurations affect the establishment of the BGP peer relationship.

    Run the display current-configuration configuration bgp command to check BGP configurations.

    Table 6-2 Checklist for BGP configurations

    Item

    Description

    peer connect-interface interface-type interface-number

    If two ends use loopback interfaces to establish the BGP peer relationship, you need to run the peer connect-interface command to specify the associated loopback interface as the source interface that sends BGP packets.

    peer ebgp-max-hop hop-count

    If two directly connected devices use loopback interfaces to establish the EBGP peer relationship or two indirectly connected devices establish the EBGP peer relationship, you need to run the peer ebgp-max-hop command to specify the maximum hop count between them.

    • If two directly connected devices use loopback interfaces to establish the EBGP peer relationship, the hop count can be any number greater than 1.

    • If two indirectly connected devices establish the EBGP peer relationship, you need to specify the actual hop count.

    peer valid-ttl-hops hops

    If the peer valid-ttl-hops hops command is configured, check that the hops value is correct. The valid TTL range of the detected packet is [255 - hops + 1, 255]. hops specifies the hop count between BGP peers, and the hop count between two directly connected devices is 1.

    NOTE:

    The peer valid-ttl-hops command must be configured on both ends before setting up the BGP session.

    peer route-limit limit

    If the peer route-limit limit command is configured, check whether the number of routes sent by the peer exceeds the limit that is specified by limit. If the limit is exceeded, you need to reduce the number of routes from the peer, and run the reset bgp ip-address command to reset the BGP peer relationship and trigger the reestablishment of the BGP peer relationship.

    peer ignore

    If the peer ignore command is configured on the peer, it indicates that the peer is not required to establish the BGP peer relationship with the local end temporarily. To establish the BGP peer relationship between the remote peer and local peer, you can run the undo peer ignore command on the peer.

    Address family capability

    Check that the address family capabilities of on two ends match. For example, before establishing the BGP VPNv4 peer relationship, you need to configure the peer enable command in the BGP-VPNv4 address families of the two ends. If the peer enable command is only configured on one end, the BGP peer relationship of the other end is displayed as No neg.

  6. 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: 4707

Downloads: 63

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