Great demo! I am getting this error when connecting to Cumulus VX? fatal: [cumulus-1]: FAILED! => {"changed": false, "msg": "Error in pending config. You may want to view `net pending` on this target."}
cumulus5 & cumulus6 do not learn each others loopback IP via BGP. The playbook is stuck at "RUNNING HANDLER [reload interfaces] . Can you check if it is behaving similarly for you.
Hey, Rajesh. Device R3 and R4 will not learn each others loopbacks, nor will device R5 and R6 since they are in the same AS (same pod). This behaviour is a BGP loop prevention mechanism since since R3 gets an advertisement from R4 it learns it via the spine, and it already sees its own AS-PATH (65002 in this case) and suspects a loop. To avoid this behaviour you can manually override with the allowsas-in command. Although I would just recommend you make the 4 leaf devices all have separate AS numbers. Change the host vars so that R3 is something like 66663, R4 is 66664, R5 is 66665 and R6 is 66666. That way the loop prevention will not be in play and you can stretch vlans across all devices. Regarding the playbook stuck at reload handler, I havent experienced that! It runs just like the video for me ie no issues! Hope that was somewhat helpful and thanks for the comment :) -John
Github link to the lab: github.com/IPvZero/EVPN-VXLAN-Cumulus
More network automation: learn.gg/adv-net
Keep them coming. Thanks for the great work.
Thank you, Zadkiel! I really appreciate it :)
Great work, John! Thanks for the brilliant content!
Thanks, Kamil! Appreciate it brother!
Great content as always
Thanks Derek. I appreciate it :)
Great demo! I am getting this error when connecting to Cumulus VX? fatal: [cumulus-1]: FAILED! => {"changed": false, "msg": "Error in pending config. You may want to view `net pending` on this target."}
great content keep it up
Thanks, John :)
I tried this with cumulus before. But are there other brands that can do bgp unnumbered yet? Juniper?
I'm not sure of other vendors implementing BGP unnumbered, Sliddjur! I'd have to check that :)
cumulus5 & cumulus6 do not learn each others loopback IP via BGP. The playbook is stuck at "RUNNING HANDLER [reload interfaces] . Can you check if it is behaving similarly for you.
Hey, Rajesh. Device R3 and R4 will not learn each others loopbacks, nor will device R5 and R6 since they are in the same AS (same pod). This behaviour is a BGP loop prevention mechanism since since R3 gets an advertisement from R4 it learns it via the spine, and it already sees its own AS-PATH (65002 in this case) and suspects a loop. To avoid this behaviour you can manually override with the allowsas-in command. Although I would just recommend you make the 4 leaf devices all have separate AS numbers. Change the host vars so that R3 is something like 66663, R4 is 66664, R5 is 66665 and R6 is 66666. That way the loop prevention will not be in play and you can stretch vlans across all devices.
Regarding the playbook stuck at reload handler, I havent experienced that! It runs just like the video for me ie no issues!
Hope that was somewhat helpful and thanks for the comment :)
-John