Mailing List Archive: ACI vs Segment Routing in DC

Classification:Public

Hi Guys,

Anybody has experience of deploying Segment Routing in DC. Have seen its deployment in WAN. But just couldn't understand its future in DC as ACI is already an established product in DC...

Amy thoughts would be great

Thanks!

This email is classified as Public by Harivishnu Abhilash
Disclaimer: This electronic message and all contents contain information from Mannai Corporation which may be privileged, confidential or otherwise protected from discloser. The information is intended to be for the addressee only. If you are not addressee, any disclosure, copy, distribution or use of the contents of this message is prohibited. If you have received this electronic message in error please notify the sender immediately and destroy the original and all copies.
_______________________________________________
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

> Harivishnu Abhilash
> Sent: Friday, November 1, 2019 11:45 AM
>
> Classification:Public
>
> Hi Guys,
>
> Anybody has experience of deploying Segment Routing in DC. Have seen its
> deployment in WAN. But just couldn't understand its future in DC as ACI is
> already an established product in DC...
>
> Amy thoughts would be great
>
Well ACI is Cisco specific, Juniper has Contrail, Arista has ..whatever, as
you can see each one of these vendor has its own proprietary, DC only,
solution along with the whole ecosystem for automation.

Now SR in DC is no different to SR in any other MPLS core/WAN. Same as VXLAN
or MPLSoUDP/GRE is going to look and feel the same wherever it's deployed.
-the difference is only in the vendor's proprietary complete vertical
automation stack you'll get with the vendor's solution.
(and currently none of the DC automation vertical stacks out there can then
be extended to manage your MPLS core or any other parts of your
infrastructure.)

Comparison of SR vs ACI(VXLAN) on a technical level,
VXLAN does not support Traffic-Engineering (TE) (note: service chaining is
traffic engineering)
VXLAN does not have any solution for mice vs elephant flows (no support for
TE)
VXLAN does not have any solution for micro-segmentation (the answer is use
lengthy access-lists like in 90's -but this time around ACLs are automated
so don't worry )
VXLAN to MPLS interface is clumsy to say at least.
- In MPLS networks all the above is solved with the use of MPLS labels.

adam

_______________________________________________
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/