You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Step1:- Create and configure dummy-interfaces on all invaders. Then make the necessary configuration changes in /etc/frr/bgpd.conf file
(The detailed files related to config of every invader are in the attachment below.)
Step2:- Restart the 'frr' service and check the 'frr' status.
Step3:- Wait for the convergence and check all the routes are converged using command "vtysh -c "sh ip route"" and neighbourships using command 'vtysh -c "sh ip bgp"'
Step4:- Also, check if there is any ping loss after configuration (including the leaf-leaf ping).
Step4:- Erase the bgp configuration on one Invader and reset it to default. Restart the 'frr' service and wait for a stipulated amount of time for the changes to reflect and then again check the neighbourships and routes
Step5:- Again bring the configurations back in that Invader and restart the 'frr' service to check whether the new changes are again reflected. Again , check the routes, neighbourships and ping-loss.
Now, the observation is that test-case is failing due to leaf-leaf routes not being visible in the routing table (and leaf-leaf ping issues). This case was verified manually by running the single playbook of this particular case isolately and it was passing.The inconsistency of these test-case is observed only in the regression.
Fix for this has been implemented the test case is now passing, but yet to be added in the regression.
Will be added most probably tomorrow or day after(max).
Will close it once the fix are added in the regression suite.
Build version:-
root@invader42:/home/rohan# goes vnetd -version
fe1: v1.1.3
fe1a: v1.1.0
vnet-platina-mk1: v1.0.0
root@invader42:/home/rohan# goes version
v1.1.1
BuildID[sha1]=5046b7c2cdea8604d331dd7e5dd2fb9c85fa21ff
Steps of the test-case:-
Step1:- Create and configure dummy-interfaces on all invaders. Then make the necessary configuration changes in /etc/frr/bgpd.conf file
(The detailed files related to config of every invader are in the attachment below.)
Step2:- Restart the 'frr' service and check the 'frr' status.
Step3:- Wait for the convergence and check all the routes are converged using command "vtysh -c "sh ip route"" and neighbourships using command 'vtysh -c "sh ip bgp"'
Step4:- Also, check if there is any ping loss after configuration (including the leaf-leaf ping).
Step4:- Erase the bgp configuration on one Invader and reset it to default. Restart the 'frr' service and wait for a stipulated amount of time for the changes to reflect and then again check the neighbourships and routes
Step5:- Again bring the configurations back in that Invader and restart the 'frr' service to check whether the new changes are again reflected. Again , check the routes, neighbourships and ping-loss.
Now, the observation is that test-case is failing due to leaf-leaf routes not being visible in the routing table (and leaf-leaf ping issues). This case was verified manually by running the single playbook of this particular case isolately and it was passing.The inconsistency of these test-case is observed only in the regression.
FRR-bgp_convergence.docx
The text was updated successfully, but these errors were encountered: