As you know, I am behind Network Virtualization from the day one of Windows 2012. In the initial days, the information I got is that we don’t need any additional component for enabling network virtualization. But when we tried to test it out, it became clear that the key component to network virtualization successful is Network Virtualization Gateway.
For some reason, I felt like I was searching for a product which was never existing and in the grooming stage. The first positive I got was from Iorn Networks that they had a Virtualization gateway readily available. And later, I noticed that F5 got the Network Virtualization gateay ready along with F5 Big IP Local Traffic Manager. Currently, Network Virtualization Gateway for F5 LTM is only available in the virtual edition and appliance is expected for Q1 2014.
Though we had all these information about third party Network Virtualization Gateways, We missed out Microsoft Network Virtualizaiton Gateway. Microsoft named this product as Windows Server Gateway and is coming up with Windows Server 2012 R2.
Though network virtualization was introduced with Windows Server 2012, I really don’t think that any of the customer could adopt it and make a production network virtualized. The main road block was network virtualization gateway. As I mentioned in one of my previous post, lot many main stream networking giants are coming up with network virtualization gateway appliance for Hyper-V. But that could be an additional investment and may not be an easy option for everyone.
Even, We had unofficial information that Windows 2012 R2 will fix-up these mess. And seems its true. Windows Server 2012 R2 is coming up with an inbuilt gateway which is capable of Multi-tenant multi-site VPN gateway, NAT gateway for internet access and forwarding gateway for within the Datacenter.