I've recently started working at a MSP and the system's architect wants us to implement Microsoft HyperV Network Virtualisation as per microsoft's design guide below on a new platform:
I'm not experienced with VXLAN but this solution seems to involve running the HyperV hosts as the 'VTEPs' rather than running the VTEPs on the network equipment, using BGP as an underlay. It seems to have a software based controller that determines if the frame needs to be encapsulated and sent to another VTEP (via the HNV VLAN) or if it's external traffic that should be forwarded directly to the (transit network) gateway with no VXLAN encapsulation.
If this is the case, what are the benefits of running VXLAN on our network equipment or is there something fundamental that I am misunderstanding here? I can see how microsoft solution may work within one DC but don't see how this would be scalable across two or more DCs. It would also need to communicate into a VMWare environment so i'm concerned about inter-op there.
I'm trying to put together a justification for buying VXLAN capable network equipment which is proving difficult as the system's architect is stating that it's too expensive and not worth the cost when we can run it on the hosts. Has anyone else run into these kind of arguments and how did you justify the expensive network kit to management?
No comments:
Post a Comment