Monday, October 8, 2018

Service chaining? Is this the new term for PBR/WCCP in the SD-WAN world?

I will be doing a Viptela migration soon. I already have approval and we are trying to get our equipment ordered. Reading documentation, all this stuff will fit in pretty easily with the rest of the network, advertising to the legacy network gear via OSPF and/or BGP to advertise routes. I'll be making the switches everywhere take over gateway duties and using OSPF. I'll retain an ISR at each location for voip related functions (DSPs, FXO, FXS ports etc). In my current deployment I have Riverbed appliances spread around the majority of my locations. They are all virtual inpath deployments using WCCP. From what I have read, vEdge's don't support WCCP and additionally my switches do not either. The other virtual inpath deployment option involves PBR. I don't really want to do that on my switches if I have to.

Lots of the docs talk about service chaining/Insertion. It sounds like what I want to do, it just seems like all the examples are for inserting a service located in a third site, when really I just want to hang my local steelhead off my local vEdges. If I have to I'll do PBR off my L3 switches. Anyone here have any experience with this? I know there is a lot of hate for WAN op appliances but I'm not ready to scrap them yet.



No comments:

Post a Comment