IBGP MPLS AR 2240

Latest reply: Aug 21, 2018 06:31:49 337 1 0 0

I  have an issue while stablishing iBGP and MPLS, i can receive the routes as the bgp vpnv4 all sum command displays, however when i try to see the vrf routing talble, it does not show anything but the local routes

this is the configuracion



<TFE-D-OTR48220-TFJA-MPLS_OFI_ADM_PRIM>disp cu
[V200R007C00SPC900]
#
 sysname TFE-D-OTR48220-TFJA-MPLS_OFI_ADM_PRIM
 
router id 10.206.1.128
#
 lldp enable
#
ip vpn-instance MONITOREO
 ipv4-family
  route-distinguisher 50:50
#
ip vpn-instance TFJA
 ipv4-family
  route-distinguisher 65500:6580
  vpn-target 65500:6580 export-extcommunity
  vpn-target 65500:6582 65500:6581 import-extcommunity
#
mpls lsr-id 10.178.169.200
mpls
 lsp-trigger all
#
mpls ldp
#

#
interface GigabitEthernet0/0/1
 description CONEXION-IBGP AR1
  ip address 192.168.100.5 255.255.255.252
 mpls
 combo-port auto
 mpls ldp
#
interface GigabitEthernet0/0/2
 shutdown
#

interface LoopBack10
 ip address 10.206.1.158 255.255.255.255
#
interface LoopBack15
 description LOOPBACK_PRUEBAS_HUGO
 ip binding vpn-instance TFJA
 ip address 10.101.100.24 255.255.255.255
#
bgp 65523
 router-id 10.178.169.200
 peer 10.206.1.159 as-number 65523
 peer 10.206.1.159 description IBGP-TO-SECUNDARIO
 peer 10.206.1.159 timer keepalive 7 hold 21
 peer 10.206.1.159 connect-interface LoopBack10
 #
 ipv4-family unicast
  undo synchronization
  network 10.206.1.158 255.255.255.255
  peer 10.206.1.159 enable
  peer 10.206.1.159 label-route-capability
 #
 ipv4-family vpnv4
  peer 10.206.1.159 enable
  peer 10.206.1.159 route-policy IBGP_ROUTES import
  peer 10.206.1.159 next-hop-local
  peer 10.206.1.159 advertise-community
 #
 ipv4-family vpn-instance TFJA
  network 10.101.100.24 255.255.255.255
  
#

route-policy IBGP_ROUTES permit node 10
 apply local-preference 50

#
ip route-static 10.206.1.159 255.255.255.255 GigabitEthernet0/0/1 192.168.100.6
ip route-static vpn-instance MONITOREO 0.0.0.0 0.0.0.0 GigabitEthernet0/0/0.659 10.253.156.1
#

return
<TFE-D-OTR48220-TFJA-MPLS_OFI_ADM_PRIM>

=====================================================================================================================

<TFE-D-OTR48220-TFJA-MPLS_OFI_ADM_PRIM>disp bgp pee

 BGP local router ID : 10.178.169.200
 Local AS number : 65523
 Total number of peers : 2                Peers in established state : 1

  Peer            V          AS  MsgRcvd  MsgSent  OutQ  Up/Down       State PrefRcv

  10.178.169.193  4       65500        0        0     0 01:50:36        Idle       0
  10.206.1.159    4       65523       43       35     0 00:03:38 Established       1
<TFE-D-OTR48220-TFJA-MPLS_OFI_ADM_PRIM>disp bgp vpnv4 all pee

 BGP local router ID : 10.178.169.200
 Local AS number : 65523
 Total number of peers : 3                Peers in established state : 1

  Peer            V          AS  MsgRcvd  MsgSent  OutQ  Up/Down       State PrefRcv

  10.178.169.193  4       65500        0        0     0 01:50:40        Idle       0
  10.206.1.159    4       65523       43       35     0 00:03:42 Established      66

  Peer of IPv4-family for vpn instance :

 VPN-Instance TFJA, Router ID 10.178.169.200:
  192.168.201.3   4         1.6        0        0     0 01:50:20        Idle       0
<TFE-D-OTR48220-TFJA-MPLS_OFI_ADM_PRIM>disp ip routing vpn TFJA
Route Flags: R - relay, D - download to fib
------------------------------------------------------------------------------
Routing Tables: TFJA
         Destinations : 2        Routes : 2

Destination/Mask    Proto   Pre  Cost      Flags NextHop         Interface

  10.101.100.24/32  Direct  0    0           D   127.0.0.1       LoopBack15
255.255.255.255/32  Direct  0    0           D   127.0.0.1       InLoopBack0

<TFE-D-OTR48220-TFJA-MPLS_OFI_ADM_PRIM>   
  • x
  • convention:

Created Aug 21, 2018 06:31:49 Helpful(0) Helpful(0)

Hello,

When the AS number in the Update message to be received by the EBGP-enabled device is the same as the AS number on the device, the device does not receive the Update message. This prevents routing loops. In some scenarios, the device needs to receive a Update message that carries the same AS number as the AS number on the device. In Hub and Spoke networking, when the Hub-PE and Hub-CE use EBGP, the Update message received by the Hub-CE contains the AS number of the Hub-PE. To prevent the Hub-PE from discarding such Update message, run the peer allow-as-loop command to set the number of times for the repeated AS number.

bgp 65523
router-id 10.178.169.200
peer 10.206.1.159 as-number 65523

Command details:
http://support.huawei.com/hedex/pages/EDOC1000085855AEG05127/13/EDOC1000085855AEG05127/13/resources/dc/peer_allow-as-loop.html?ft=0&fe=10&hib=10.1.9.8.93&id=peer_allow-as-loop&text=peer%20allow-as-loop&docid=EDOC1000085855

  • x
  • convention:

“We only get answers to the questions that we ask.” physicist Werner Heisenberg

Reply

Reply
You need to log in to reply to the post Login | Register

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " Privacy."
If the attachment button is not available, update the Adobe Flash Player to the latest version!

Login and enjoy all the member benefits

Login
Fast reply Scroll to top