Support of hardware VTEPs when using Universal Logical Switches

[JJBN]

Hi,

We were thinking to use Hardware VTEPs (through switches supporting OVSDB) on a NSX Cross-VC environment. The following questions arise:

• Does Universal Logical Switches support Hardware VTEPs?

• All Hardware VTEPs in DC1 and DC2 will have to be registered to NSX Manager on DC1 ? or the Hardware VTEPs in DC1 will have to be registered to DC1 NSX Manager and hardware VTEPs in DC2 to DC2 NSX Manager

• What happen when DC1 fails? Will DC2 get in charge of hardware VTEPs in DC1 or connectivity between VMware and the hardware VTEPs in DC1 will go down or the data plane will survive?

Thanks for your help.

Regards,

JJBN

[hansroeder]

I truly thought that it was supported, but then I read this: https://vwud.net/2016/12/07/hardware-vteps-design-considerations/‌‌. I will enquire about this, since I will need this for one of our customers as well

[JJBN]

Hi Hans,

thanks for the answer, yes I had the same feeling that it was supported and yes I saw that same port, that's why I asked as there is no official document saying it is not supported. My doubt on that post is that for example on that hardware support list for hardware VTEP (done by VMware) only shows 3 Arista switches and I have deployed it on Arista switches that are not in that list, but it is supported as Arista uses same OS for each device and claims that it is supported for all their switches supporting VXLAN... so not too sure what to think about the post...

Please let us know if you get more info if hardware VTEPs on Universal Logical Switches is supported or not and in case it is not supported when it will be.

Thanks.

JJBN

[hansroeder]

In our case we're dealing with Brocade VDX 6740 switches, which are supported. So that may be a thing

I will let you know as soon as I know more.

[JJBN]

The deployment with the not in the list switch worked very good, it was the Arista 7280R that's why that list is maybe only for the devices tested by VMware, which doesn't mean are the only wants that work with... but the Universal Spine story is for a future deployment, but I have the answer checking on a universal and standard logical switch, and it is not supported on NSX 6.2.4 :smileyangry:

Attached are the captures where it shows that you cannot mark on the universal logical switch to manage hardware bindings.

I would really appreciate if you get any info regarding when it will be available to have hardware VTEP on Universal Logical Switches

Thanks

Regards,

JJBN

[hansroeder]

I also found this useful link: https://telecomoccasionally.wordpress.com/2016/04/14/do-i-need-a-hardware-vtep-for-my-nsx-for-vspher...

I've also asked around about this, and I'm afraid that it is indeed not possible to use Hardware VTEP with Logical Switches connected to a Distributed Logical Router. It's simply not supported (and therefore does not work). You will need to connect the Logical Switch directly to a Edge Services Gateway instead of connecting it to a Distributed Logical Router.

Also, you are right in stating that there is no documentation that can be found that fully explains this shortcoming. At least not that I could find. I've looked up the documentation for numerous vendors but could not find any statement about it only being supported on ESGs and not on DLRs.

Looking at my own case, L2 Bridging on the DLR should be the way to go. Unfortunately I'm dealing with UDLRs, on which L2 Bridging is not supported. Oh well, back to the drawing board...

[bayupw]

As perNSX-V Multi-site Options and Cross-VC NSX Design Guide at the moment L2 bridging between local logical switches and physical VLANs via software or hardware gateway can be done, this is not currently available with universal logical switches.

In my opinion we can only wait until VMware supports bridging to universal logical switches on future NSX releases.

There are some workaround on what we can do for L2 Bridging Between Logical and Physical Network via ESG in page 56 on that Multi-site Options & Cross-VC Design Guide.