[c-nsp] Multihomed OTV on CSR Lab - Mac Address Issue

[quinn snyder]

This has been standard n7k operations since the platform
supported contexts. 
Much like ASA — interfaces need to be dedicated to a context from the management-plane perspective. 

OTV requires a separate context due to inability to have SVI and OTV in same context. OTV essentially becomes a part of the L2 domain on the inside — and L3 domain on the outside sending encap’d traffic. 

q. 

--
quinn snyder | snyderq at gmail.com

-= sent via iphone. please excuse spelling, grammar, and brevity =-

> On Jan 30, 2018, at 11:33, Aaron Gould <aaron1 at gvtc.com> wrote:
> 
> Ha, thanks Justin, I just read the answer to my question I just posted...
> OTV is cisco proprietary.  Is OTV gaining steam in the industry as a
> potential ietf standard ?
> 
> Interesting things you mention about assigning asics, and linecard
> dependancies...
> 
> -Aaron
> 
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/