DCNM 11 question

Started by LynK, December 14, 2018, 01:55:45 PM

Previous topic - Next topic

LynK

for those of you who have tested/deployed DCNM with your vxlan fabric. Do you know why, when you assign a leaf as a border leaf it removes the SVI configuration?

According to David Jansen in building networks with VXLAN BGP EVPN, he states a single leaf can perform all 3 functions of a leaf "service, border, and normal". Yet in DCNM, when you configure a border leaf it removes all SVIs.

I wonder if this is a bug, or if I should try wiping my leafs and re importing them fresh to see if there is a difference.
Sys Admin: "You have a stuck route"
            Me: "You have an incorrect Default Gateway"

wintermute000

Probably just the template its using. For border gateways (multi-site EVPN) SVIs are not supported and Cisco states its best practice to NOT host anything on borders.

LynK

@winter

correct, but that is for border-gateways for like you mentioned. I guess I will just try going back to the leaf profile, but I will plug in a router for testing to see if layer 3 works.
Sys Admin: "You have a stuck route"
            Me: "You have an incorrect Default Gateway"

LynK

btw, this is fixed in DCNM 11.1, as well as A LOT of other features (new templates, SVI support on borders, much more configuration options, DHCP relay for VXLAN, etc.)
Sys Admin: "You have a stuck route"
            Me: "You have an incorrect Default Gateway"