NSX-T Edge Multi-TEP Flow-Cache Bug
NSX-T supports Multi-TEP just like NSX-V. But this feature was limited to ESXi hosts and it was not supported for Edge Nodes. Since NSX-T version 2.4 Multi-TEP is supported for Edge Nodes as well, which optimizes the North-South network performance.
Starting with NSX-T 2.4 the Multi-TEP was supported but not recommend from reference design guide perspective. The recommendation was added after the reference design guide was updated for NSX-T 2.5. Since then a deployment with a single NVDS vor VLAN and Overlay transport zones combined with Multi-TEP for ESXi and Edge Nodes is recommended.
vCloud Director 10 NSX-T backed OVDC – Add externel based network with dedicated physical NIC
With the release of vCloud Director 10, NSX-T integration is also available. Our colleague Steven Schramm shows you in this article which limitations there are for NSX-T supported OVDCs compared to NSX-V supported OVDCs and how you can handle it.
vCloud Director 10 – SAML Authentication with Keycloak as Identity Provider
This article describes how to configure vCloud Director 10 to consume authentication information from a SAML identity provider using Keycloak.
If you will provide your customers access to more than one system, it might be helpful to have a single point of authentication. The advantages to have a central system for all authentication requests are reduced configuration overhead, troubleshooting complexity and the possibility to implement Single Sign-On.
NSX-T Edge Appliance Deployment Regulations
This article describes the regulations, if deploying NSX-T Edges as appliance and show the supported deployment scenarios.
Following a short overview about the three deployment scenarios.
NSX-T Edge appliance on NSX-T prepared host with just N-VDS
NSX-T Edge appliance on NSX-T prepared host with VDS and N-VDS
NSX-T Edge appliance on different vSphere cluster not prepared for NSX-T