OTV and VXLAN

SrikantRajeev
SrikantRajeev used Ask the Experts™
on
I would like to understand where to use overlay technologies & where to use VXLAN technologies.

Both the technologies looks the same but would like to know where to use these 2 technologies.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Top Expert 2014

Commented:
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
Top Expert 2015

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

Author

Commented:
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.
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Top Expert 2015

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

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

Author

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

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

Author

Commented:
Can VXLAN be implemented between 2 Data centers ?

Author

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

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

for the following reason:

Thanks
Top Expert 2015

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

Author

Commented:
Thanks
Top Expert 2015

Commented:
Not really....
Top Expert 2014

Commented:
Was our help useful or not?

Commented:
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.
Top Expert 2014
Commented:
Well actually, Mysidia, the OP said this:

I would like to understand where to use overlay technologies & where to use VXLAN technologies.

Both the technologies looks the same but would like to know where to use these 2 technologies.

The question here was clear... understand where to use the two technologies.  The question was not the author's second comment, which read:

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.

So, providing a link to information relating to the question being asked was both helpful and did provide an answer to 'the question', therefore the question WAS answered.  Within the linked page was also more information and links relating to the very same subject.  That is something that I could not have possibly summarized within this thread.

In essence, the OP asked where to use either and I gave a clear indication as to the constraints which would normally make the decision for you, if you chose to use either technology at all.

As well as that, OTV is in fact an overlay technology, hence its name; Overlay Transport Virtualization.  We can use it to extend a layer2 segment across routed networks.  Similarly, VXLAN is a way in which we can extend layer2 boundaries over layer3 networks, although it works differently and is used differently.  Incidentally, you can run OTV and VXLAN at the same time if you want to.

Here's an excellent link which will undoubtedly clear up any discrepancies in terminology and goes a long way to explain the use cases for each technology:

http://blogs.cisco.com/datacenter/vxlan-deep-dive-part-2-looking-at-the-options

Author

Commented:
Thanks

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial