12-06-2023 02:05 AM
We have faced routing issue related to ibgp and ebgp peering. simple topology has attacded.
main purpose is customer site1's network must reach customer site2 network and vice verse. we can ping from R4 to R3.
R3 and R4 are ASR920 , R1 and R2 Cisco N540.
Ibgp peering between R2 and R3, ebgp peering bw R1 and R2, ebgp peering bw R1 and R4
Bu we know that router dont recevie routes from ibgp peer when it sees itself's AS. How we can do it that we solve this issue. which optimal solution we can choose that we can do it
Solved! Go to Solution.
12-06-2023
06:22 AM
- last edited on
12-13-2023
01:12 AM
by
Translator
Hi @ElshanMammadli5597 ,
On R2, you need to allow updates containing the local coming from R1 as follow:
router bgp 65038
neighbor 10.82.32.13
address-family vpnv4 unicast
allowas-in
You will need to do the same on other routers needing to accept updates containing their own AS as well.
Regards,
12-06-2023 02:16 AM
Ibgp peering between R2 and R3
Here issue I think'
1-First since both ibgp use
Bgp- Redistrubte-internal
2- you need to use next hop self between two ibgp
That it
Check point above abd I think your issue will solved
MHM
12-06-2023
02:38 AM
- last edited on
12-13-2023
01:11 AM
by
Translator
Hello @MHM Cisco World
I did it but result is same
R2 bgp config
router bgp 65038
neighbor 10.82.32.13
remote-as 65038
update-source Loopback0
address-family vpnv4 unicast
route-policy allow in
route-policy allow out
next-hop-self
soft-reconfiguration inbound always
!
R3 bgp config
router bgp 65038
bgp router-id 10.82.32.13
bgp log-neighbor-changes
neighbor 10.82.32.101 remote-as 65038
neighbor 10.82.32.101 update-source Loopback0
!
address-family ipv4
neighbor 10.82.32.101 activate
exit-address-family
!
address-family vpnv4
neighbor 10.82.32.101 activate
neighbor 10.82.32.101 send-community both
neighbor 10.82.32.101 next-hop-self
neighbor 10.82.32.101 route-map azercell_out out
exit-address-family
!
address-family ipv4 vrf 4G_RAN
redistribute connected
exit-address-family
12-06-2023 02:49 AM
There is big mess here
Why there is vpnv4 and ipv4 address family.
Above two points need check and also vrf target import export
MHM
12-06-2023 03:10 AM
We use vpnv4 address familiy. ipv4 peering is down.
vrf target import export values are same on both routers. But i am not sure that that this value must be same or different
12-06-2023
03:48 AM
- last edited on
12-13-2023
01:12 AM
by
Translator
The design must be
Ipv4vrf-vpnv4-Ipv4vrf
The vpndv4 even with route export/import not work without ipv4vrf.
Can you show me where vpnv4 start and where it end.
MHM
12-06-2023 04:38 AM
12-06-2023
06:22 AM
- last edited on
12-13-2023
01:12 AM
by
Translator
Hi @ElshanMammadli5597 ,
On R2, you need to allow updates containing the local coming from R1 as follow:
router bgp 65038
neighbor 10.82.32.13
address-family vpnv4 unicast
allowas-in
You will need to do the same on other routers needing to accept updates containing their own AS as well.
Regards,
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide