I’ve seen a lot of setups where the spine and leaf topology is placed “unoptimal” and later on might cause trouble. If you want to know how to use NIC-Teaming on Windows Server 2016 simply go to google – there are tons of instructions (with LACP and without) but this setup uses one with LACP.īefore implementing EVPN-VXLAN you should carefully think about your setup. In case you already know EVPN and just want to take a look at the sample-config, you can jump at the end of this blog post, where I post the full code for the setup (excluding Windows Server NIC-Teaming with LACP). On top we will configure Winserver for multihoming: We will be looking at the following topology (designed on EVE-NG) and implement an EVPN-VXLAN spine and leaf config so that our virtual servers named Win and Winserver are able to communicate with each other. This blog post will show you how to do it and break down the important parts. What could be more refreshig than setting up a nice little EVPN-VXLAN on your vQFX just for fun?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |