OTV and VXLAN

First thing, which is important, is that OTV is Cisco Proprietary and is limited to N7K.  VXLAN is vendor-neutral.

This is a good place to get a more thorough answer...

https://communities.vmware.com/thread/430316

You mean you are facing the hard choice between display and monitor?

I have read this. I want to know from some one who has really implemented these solutions & their feedback.
Wanted to know what is reason they have deployed & what they have achieved by implementing these solutions.

L2 tunelling is known for long as bridging over vpn.
It does not get lower latency by renaming or re-standartising.

I think the answer is self-explanatory.  Use OTV if your kit is Cisco and it supports it, otherwise use VXLAN.

Is VXLAN be implemented within the data center & OTV can be used between the data center.
Let me know if this difference is right...

It is true either way. None of Layer 2 tunneling protocols mentioned is limited to single location

Can VXLAN be implemented between 2 Data centers ?

I've requested that this question be closed as follows:

Accepted answer: 0 points for SrikantRajeev's comment #a40060786

for the following reason:

Thanks

Thanking yourself is not an answer. Was Craig helpful? Me?

Thanks

Not really....

Was our help useful or not?

Based on the above, recommended disposition is PAQ/Refund.

I noticed that above, noone seemed to fully answer on the original question;
If the answers were all merely helpful but no correct answer is found, and
the question is trivially answerable, then no response should be accepted.

Certainly, the question is not self-explanatory, and telling the author to go to some other
forum for an answer is no answer to the question.
I would say: original question remains unanswered as written.

By the way, there is not much overlap between the most appropriate use cases for VXLAN and OTV.
The latter is a datacenter interconnect,  the former (VXLAN) is an overlay networking technology that
has ongoing standards work within IETF to enable that use case in the future, but right now VXLAN is not very suitable for
L2 extension across geographical regions.


VXLAN's primary use case is virtual networking within the datacenter to create an arbitrary number of virtual networks, without requiring a VLAN per network between all virtualization hosts.   This is the use case where it shines.

VXLAN is needed to scale to a large number of virtualization hosts in a datacenter, while allowing any VM to be run on any host,  without VLANs shared between all VM hosts.

OTV is an encapsulation and Layer 2 extension technology  designed for extending a L2 boundary between datacenters; for example: OTV divides the spanning tree domain,  and offers some protection against broadcast storms crossing boundaries.

VXLAN does not protect against such failure scenarios crossing datacenters, but instead could exacerbate (potentially) such failure modes,  and VXLAN implementations also don't provide a mechanism to implement the "Default Gateway Split" like OTV does,   to avoid problems where L3 routed traffic trombones and follows inefficient paths.

Thanks