Why is VLAN 51 call underlay? All the leaf switches formes the overlay network and the underlay network in this topology is being formed by the Spine Switches. Could you explain? Base on my knowledge, the VTEP Switches are the overlay endpoint in this case all the leaf switches. So vlan 51 should be as well named as Overlay network cause it's connected to one of the leaf Switches. Secondly, you have eBGP configured and not iBGP so, why AD 200 instead of 20 or could you have an issue with your EOS? My humble observation.. After all, your lab is well elaborated and simplified. I do appreciate your effort for all your doings..Kudos Sir.
Thanks for the explanation, I have a question though why all the prefix in the Leaf routing table are showing as learned via iBGP with AD value of 200. You have eBGP running between Spine and leaf so it should show as eBGP routes with AD value of 20 isn't? Please respond
This is Arista EOS not Cisco IOS. Different vendors can have different ADs assigned to routing protocols. So if Cisco implements eBGP with AD 20 it doesn't mean it's the same for Juniper or Arista.
Thank you for this and thank you for including the basic configs, it gives a great starting point
Very knowledgeable video and explained in the easiest way. Thankyou Sir!
You are most welcome
ok so "redistribute connected " is doing the magic of advertising the loopback 1 into the BGP... cool
Hi. Great Video. One question though, is your topology running without mlag between the two spine switches?
Why is VLAN 51 call underlay? All the leaf switches formes the overlay network and the underlay network in this topology is being formed by the Spine Switches. Could you explain?
Base on my knowledge, the VTEP Switches are the overlay endpoint in this case all the leaf switches. So vlan 51 should be as well named as Overlay network cause it's connected to one of the leaf Switches.
Secondly, you have eBGP configured and not iBGP so, why AD 200 instead of 20 or could you have an issue with your EOS?
My humble observation..
After all, your lab is well elaborated and simplified. I do appreciate your effort for all your doings..Kudos Sir.
Excellent video. Thank you.
Thank you :)
what is the veos image version for arista?
Hello Arshad, I did this video couple of years back. I think I was using 17.3 that time
Thanks for the explanation, I have a question though why all the prefix in the Leaf routing table are showing as learned via iBGP with AD value of 200. You have eBGP running between Spine and leaf so it should show as eBGP routes with AD value of 20 isn't? Please respond
This is Arista EOS not Cisco IOS. Different vendors can have different ADs assigned to routing protocols. So if Cisco implements eBGP with AD 20 it doesn't mean it's the same for Juniper or Arista.
Is the arista veos limited to four interfaces only, may I know how to increase it?
sbshshsjdjhsjshdhdhdhshdhdhdhđhdhdhdh
duhdhduudhdudhhxhxxjjxjxhjxhxhxhxhxhxh
shzhzhzhxhxjdhzhzhzxhzhhzxhhxxhhxhxhx
dnjxhxhxhhzhzxhxhxhxxhhxhxhxhxhxhxhxhx
Hi do you have route reflector configured?
Hi Vijay I haven't configured route reflector.
In Arista you can configure it using "neighbor route-reflector-client" command
can you provide the topology file?
Hi Joshua, I am not sure whether it is available in my environment now. Let me check in my archives, but chances are less.
@@NetworkEvolution no worrie bro
@@joshualuna7112 :)
please give me the os file for extreme
Sorry, dont have it
Excellent work bro
Thanks Bro :)
shshjdjzhxhxhxhdhdhdhhdhhdhdhdhdhxhxh
đuhhdjdhdjhdhdhdhdjdhdjdhjdhđhdhhđhhhd
shshsjshsjhsjdjdhhdhdhdhhdhshdhshshdh