Page 211 - CIT-TW

The iWAN Solution is Complex to Implement & Maintain

• Traffic classes and probing configuration is centralized, but only

one profile can be configured centrally

• DMVPN overlays needed for each WAN path, and creation is
not centralized

• Requires two independent routing domains, base plus one for

PfR

• Example: latest iWAN design guide needs 250+ pages to

explain DMVPN, PfR, QoS, and Netflow set up

– The design guide doesn’t cover details of the individual elements, but

rather how to make them work together

– It does not cover WaaS, AVC/NBAR, or management

“I’m sure there is situations where Cisco iWAN might be more
flexible, but it’s really really complex. For 90% of clients I can’t see

Citrix SDWAN having a problem there.” – Cisco/Citrix Partner

333 © 2017 Citrix | Confidential