Hello Everyone
I have configured L2 VPN in VMware vCloud platform where L2 VPN between two different DC via 1 Gbps MPLS link.
As we are facing network slowness issue between Dc’s via L2 VPN(network speed max usage is 200 Mbps),However using same MLPs, when we do test of vms between DCs, without L2 VPN, we see good network performance/complete bandwidth utilization
Note: Edge gateway version is 6.3.6
So is there any know issues causing performance/limiting bandwidth usage over L2 VPN? Any configuration issue ?
Please some one can direct me in right direction
Thanks in advance
Hi there,
Whats the size of your edge?
Can you test traffic trough the ESG (maybe with some new interfaces to see whats the performance you get without the vpn) or create a new edge and test this. Sometimes this is related and underlaying issue where you are getting less performance that you should and l2vpn should not affect the numbers that bad.
Also, what do you have at the other end?
Thanks Nicolas for your response and information .
Edge Gateway configuration is Quad Large and enabled with High Availability .
We did VMs network tests already between Dc's/sites with new interface, without L2 VPN and it’s very good and can see 100 % bandwidth utilization ,But with L2 VPN over same MPLS link,performance is very slow,(Not exceeding more than 200 Mbps) .
Other end(Site-B),we do have L2 Appliance installed and configured
Did you test this performance also going through the EDGE appliances? The idea is to know if the edge, whether with or without l2pn feature can deliver the desired thoughput to you.
Hi,
Thanks for your response and assistance
Did you test this performance also going through the EDGE appliances? Yes,test on VMs via L2 VPN routed sub interface of Edge which is giving slow performance.
Another network test of vms b/w DC/Sites without Edge and via direct datanet link using same MPLS which give good performance
What is the latency between sites ? If you are using the SSL based transport and latency is high you will see improved performance using L2T (although this needs to be configured using the API and also requires upgrading to NSX-v 6.4.2 or newer: