vn-segment 40000\r\n\r\n<\/b><\/pre>\nvrf context management<\/b>\r\nvrf context vrfvx_v100<\/b>\r\n vni 30000<\/b>\r\n rd auto<\/b>\r\n address-family ipv4 unicast<\/b>\r\n route-target both auto<\/b>\r\n route-target both auto evpn<\/b>\r\nvrf context vrfvx_v200<\/b>\r\n vni 40000<\/b>\r\n address-family ipv4 unicast<\/b>\r\n route-target both auto<\/b>\r\n route-target both auto evpn<\/b><\/pre>\nThus we need to create a VLAN 100 and assign it to vrf vrfvx_100 and _200.<\/p>\n
Before we do this we need to make note of the MAC addresses the PVE is giving to the VNETs we configured. This will be under the “sdn” file in the “interface.d” folder. This ensures that the gateways we create will have the same MAC addresses, so if you were to migrate a VM it will not have a conflict between ARP entries and MAC addresses on the different leaf it now resides.<\/p>\n
In our case we will use the static method or manual MAC configuration. Another way is to use MAC aliasing.<\/p>\n
Now we can configure both VLANS:<\/p>\n
interface Vlan100\r\n no shutdown\r\n mac-address bc24.11e7.f432<\/strong> \r\n vrf member vrfvx_v100\r\n ip address 10.100.1.1\/24 \r\n fabric forwarding mode anycast-gateway<\/strong>\r\n\r\ninterface Vlan200\r\n no shutdown\r\n mac-address BC:24:11:58:A1:F9<\/strong>\r\n vrf member vrfvx_v200\r\n ip address 10.200.1.1\/24\r\n fabric forwarding mode anycast-gateway<\/strong><\/pre>\nNotice that we defined the mac addresses for each VNET and then we use the any-cast gateway command.<\/p>\n
The interfaces should be up and if the PVE allowed this you would be able to ping across VNIs. How to allow access across VNIs will be a topic for another blog.<\/p>\n
Cheers,<\/p>\n
Ciao.<\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
Hello, This is a follow up to my previous blog regarding PVE SDN and NXOS\u00a0. Astute readers which all of you are, would have realized that in order to go across\u00a0 VXLAN segments, the default gateway for each VNET is located at the PVE nodes. This is not really a an efficient way of routing … <\/p>\n
Continue reading “PVE SDN NXOS Follow Up!”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-710","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/blog.miguelsarmiento.com\/index.php?rest_route=\/wp\/v2\/posts\/710","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.miguelsarmiento.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.miguelsarmiento.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.miguelsarmiento.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.miguelsarmiento.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=710"}],"version-history":[{"count":8,"href":"https:\/\/blog.miguelsarmiento.com\/index.php?rest_route=\/wp\/v2\/posts\/710\/revisions"}],"predecessor-version":[{"id":718,"href":"https:\/\/blog.miguelsarmiento.com\/index.php?rest_route=\/wp\/v2\/posts\/710\/revisions\/718"}],"wp:attachment":[{"href":"https:\/\/blog.miguelsarmiento.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=710"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.miguelsarmiento.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=710"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.miguelsarmiento.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=710"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}