-
Notifications
You must be signed in to change notification settings - Fork 722
Some questions about redundant route reflectors #2166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
similar issue with 3 rr and 2 client and 1 nomal client
rr 192.168.189.213 config
rr 192.168.189.214 config
rr 192.168.189.215 config
rr-192.168.189.213
rr-192.168.189.214
rr-192.168.189.215
the client 192.168.251.145 not recive all route from rr rib.
on the gobgp 2.8.0 use kube-route same ploblem cloudnativelabs/kube-router#773 |
set cluster id diffrent on the rr config, 192.168.251.145 revice all the route from rr rib |
like frr, gobgp uses router-id as cluster-id if cluster-id is not configured. |
Networking:
Configure:
Configuring a route on client1:
The effect is as follows
RR1:
RR2
Here I want to ask the first question: Why does the adj-out of the neighbors to RR2 on RR1 not equal the adj-in of the neighbors to RR1 on RR2?
clent1:
There are three routes in client1. The latter two are learned from RR1 and RR2. According to my understanding, these two routes should not exist. I found that their Originator ID is wrong and should be the router ID of client1. That is, 172.16.20.32, so that when cleint1 receives these two routes, it will compare with its own router id, and the same will not be received.
Because of the above problem, I am restarting the client's bgp process, or executing :
#gobgp neigh 172.16.20.31 reset ; gobgp neigh 172.16.20.30 reset ; gobgp global rib del 2.2.2.0/24
I found that 2.2.2.0/24 still exists on client1, it has actually been deleted.
They are all released by RR. The RR has not been properly aged.
They should be deleted on RR1
=====================
Test FRR
I will use the same scene to test frr
After adding a route on client1:
There is only one route on client1, and it will not receive the route reflected by the RR.
And the Originator id of the route is 172.16.20.32 which equal to its router id.This is consistent with my experience.
The adj-out of the neighbors to RR2 on RR1 not equal the adj-in of the neighbors to RR1 on RR2, it's ok.
then, i executed the following command, which is equivalent to executing "#gobgp neigh 172.16.20.31 reset ; gobgp neigh 172.16.20.30 reset ; gobgp global rib del 1.1.1.0/24"
The routes on all nodes are cleared. This is consistent with my experience.
The text was updated successfully, but these errors were encountered: