OTV latency figures

[l33d5un1t3d]

Hi community,

What latency will OTV tolerate for DCI-to-DCI use cases please?

[cassiolange]

Hello,

Latency is not a problem for OTV. You need check with the server guys, what RTT the applications need to works.

Sample:
Long Distance vMotion requirement:
A RTT (round-trip time) latency of 150 milliseconds or less, between hosts.

https://kb.vmware.com/s/article/2106949

Regards,

[l33d5un1t3d]

Hi many thanks for the response, what's interesting for me is that Cisco is pushing ACI to use instead of OTV for DCI, but currently releases only support 50mS latency, this is a show stopper for DCI, however the roadmap for ACI 4.x is to deliver between 150 to 500mS.

[cassiolange]

Hello,

Just for clarify.

ACI is not a DCI solution. ACI is a SDN product for DC.

ACI use VXLAN to encapsulate layer 2 traffic and multiples control planes (COOP, ISIS and MP-BGP).

ACI has 2 solutions, one for Multi-Pods (Multiple Network Fault Domain within a Single Avalaible zone) and Multi-Site ( Multi-Fabric).

ACI Multi-Pod use multicast for BUM traffic between PODs. ACI Multi-Site use ingress replication for BUM traffic between sites.

Technicallly, multicast or ingress replication don't have any latency restriction.

I think, latency restriction for the ACI is a BU restriction.

Regards,

[l33d5un1t3d]

thanks for the reply as always.

RE: "ACI is not a DCI solution. ACI is a SDN product for DC." Cisco are pushing ACI as a replacement for OTV so are saying it is a DCI technology, just under another name?