04-22-2019 12:24 AM
I use a Cisco 9000 router I have a issue with a client, everything works fine. I have a 10G interface, we have created two sub-interfaces (VLAN2 and VLAN 3) the ping test works well and we use a loopback interface for the session bgp my issue is that the bgp session works with the vlan 2 but not with vlan 3 when I remove the route IP vlan 2 the session bgp switches to vlan3. i want the bgp session to work on both vlan 2 & 3 at the same time and if a vlan goes down automatically the other vlan must take the hand.
Int TenGigE0 / 6/3 / 0.2
Address IPv4 192.168.1.225 255.255.255.252
dot1q vlan 2
!
Int TenGigE0 / 6/3 / 0.3
Address IPv4 192.168.1.230 255.255.255.252
dot1q vlan 3
!
197.16.12.249/32 192.168.1.226
197.16.12.249/32 196.168.1.230
Anyone have any ideas? Thanks for your time,
Abdoulka
04-22-2019 12:47 AM
Hello,
if you peer with loopback addresses, the loopback address must be reachable through both Vlans. Post a schematic drawing of your topology, as it is unclear from your brief description how your network is configured...
04-22-2019 01:56 AM
Hi,
the loopback address is reachable through both Vlans.
197.16.12.249/32 192.168.1.226
197.16.12.249/32 196.168.1.230
i wanna the loopback addresses communicate with both vlans at the same time
04-22-2019 02:07 AM
AS suggested we need to more information of the config to look and see what is wrong
On high level, if this is routing table ?
197.16.12.249/32 192.168.1.226
197.16.12.249/32 196.168.1.230 <<- is this belowing to other side loopback - the route should be point to other router, its pointing to local interface.
this is my assumption ? but we can only confirm seeing your config,
04-22-2019 02:23 AM
The ip of the loopback interface that I use is the client that propagated me it's his address to him.
Int TenGigE0 / 6/3 / 0.2
Address IPv4 192.168.1.225 255.255.255.252
dot1q vlan 2
!
Int TenGigE0 / 6/3 / 0.3
Address IPv4 192.168.1.230 255.255.255.252
dot1q vlan 3
!
ip route 197.16.12.249/32 192.168.1.226
ip route 197.16.12.249/32 196.168.1.230
This is my BGP config :
router bgp XXX
neighbor 197.16.12.249
remote-as YYY
ebgp-multihop 2
timers 2 3
password encrypted 02350B561F0303010F6A235D40
description Customer1
update-source Loopback0
address-family ipv4 unicast
route-policy c1-INBOUND in
maximum-prefix 1000000 75
route-policy c1-OUTBOUND out
send-extended-community-ebgp
default-originate
soft-reconfiguration inbound
!
04-22-2019 05:16 AM
can you post both the side config which include loopback interface information, also show ip route both the sides
04-22-2019 06:22 AM - edited 04-22-2019 12:30 PM
Hello
The most simplistic would be to use an igp for NLRI (ripv2 would be approx) and advertise the vlan subnets and the loopback and establish a peering session on the loopbacks. the only problem you may encounter is the failover using subinterfaces due to the physical interfaces still being seen as up even if you had failure on the subinterface so you may need to adjust the igp timers to accommodate.
example:
router rip
ver 2
timers basic 15 45 45 60
no auto
network <your loopback>
network < vlan x>
network < vlan y>
router bgp xx
neigbour <remote loopback>
neigbour < ebgp-multihop x>
neighbour update-source < your loopback>
04-23-2019 10:32 PM
Hello,
For information my client is in another country than my country, can i use IGP or RIP in my situation.
04-24-2019 02:42 AM - edited 04-24-2019 06:25 AM
Hello
@Abdoulka wrote:
Hello,
For information my client is in another country than my country, can i use IGP or RIP in my situation.
nt TenGigE0 / 6/3 / 0.2
Address IPv4 192.168.1.225 255.255.255.252
dot1q vlan 2
!Int TenGigE0 / 6/3 / 0.3
Address IPv4 192.168.1.230 255.255.255.252
dot1q vlan 3
ip route 197.16.12.249/32 192.168.1.226
ip route 197.16.12.249/32 196.168.1.230
If these two subnets are reachable between sites I cannot see why not - The example provided should provide you with the resiliency you desire
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: