This event had place on Wednesday 11th, December 2019 at 10hrs PDT;
;Juan Flores;is a Technical Consulting Engineer on the Software-Defined WAN team at the Customer Experience (CX) Center. Before he joined the SD-WAN team, he worked on the Routing Protocols team. Juan specializes in Routing Protocols, Service Provider technologies (MPLS), switching, Nexus administration with routing protocols, and SD-WAN technologies. Juan holds a degree in computer systems engineering from the University of the Valley of Mexico. He holds a CCNA R&S certification and he is pursing certifications in CCIE R&S and CCIE SP.
You can download the slides of the presentation in PDF format here.
A: More than looking into the competition terms. It is recommended to have a look at the requirements and needs the project is looking for. In the end, the most important thing is to meet the requirements and assure that the solution provides the required features, stability and availability
A: SD-WAN can provide the same topologies and traffic flows as DMVPN or FLEXVPN - it can be used. But, I would recommend to analyze other requirements as well.
A: I would not say its a complete replacement, but it certainly improves several of those mechanisms and bundles them together in a single solution. Remember all of them are individual protocols. therefore, many applications will exist for them, not only WAN.
A: I would recommend you to check this with your assigned account manager (if its out of dcloud).
A: I would not say that. MPLS is a transport (save costs using internet circuits). What you do is to augment your bandwidth transport using internet bound transport. But, for some applications, MPLS would offer a better SLA than regular internet connections.
A : Hello, thanks for your question, in fact, it is a Cisco Proprietary solution!
A: Please, check the end-to-end guide: https://www.cisco.com/c/dam/en/us/td/docs/solutions/CVD/SDWAN/SD-WAN-End-to-End-Deployment-Guide.pdf WAAS usually manipulates the TCP sessions. SD-WAN offers a TCP optimization as well. I would be careful in using both at the same time.
A: SD-WAN is a friendly solution, You could start using it even if you have CCNA, if you need to deploy other protocols such BGP, OSPF, you would have to have a deeper knowledge of that specific protocol.
A: You are right, its a typo. Thanks for the catch.
A: I would say that is the main feeling. IWAN efforts have been reduced in order to improve the SD-WAN fort after Viptela's acquisition.
A: If you need to improve your SD-WAN deployment you can always do it with policies, in that way you could have your whole full mesh or separated mesh networks.
A: SD-WAN is the ultimate Cisco's solution, it solves some limitations present in iWAN, such as having a HUB MC as a single point of failure, the Controllers are not centralized but in the cloud for example. SD-WAN will dynamically manage your traffic.
A: For IWAN the description is " Intelligent Wide Area Network".
A: Cisco SD-WAN works with Cisco and Viptela devices. It is not the same but it is part of Viptela. SD-WAN is Cisco proprietary and Viptela is part of Cisco.
A: Cisco SD-WAN support WAAS here
A: I'd say that in the case you have this scenario you should delimit your network with policies to design a hub-spoke. The tunnels will be there but you can limit what can be routed or no with the policies.
A: In SD WAN for cloud components we need the following controllers, vmanage, vbondd, vsmart.Specific to Cisco SD-WAN, you have three options when it comes to cloud:
Cloud onRamp for SaaS - extends the SD-WAN concept of “quality probing” to SaaS applications on the Internet. Al routers, automatically connect the new routers to your backend VPCs/VNets, then extend that connectivity to your SD-WAN cloud. In this method, SD-WAN connected sites now see AWS/Azure as another branch location and can build direct tunnels to the cloud.
SD-WAN can then be used to funnel traffic through the best performing colocations, apply policies to the traffic (in the form of running the traffic through a virtualized service chain of network equipment) and send it on its way to the cloud.
A: ZTP is used in SD-WAN in fact!
A: This is a good question, we have two parts, Underlay is the connection to your ISP and the Overlay is the virtual tunnels over underlay.
A: In CEDGE or VEDGE devices we can manipulate the traffic using specific metrics such as Local Preference to select the best path.
A:For SD-WAN we can connect to an internet cloud and we just need to complete basic connectivity with the Service Provider. We can use the default route or BGP to complete Underlay then over the Overlay we can establish virtual tunnels.
A: Yes, SD-WAN can integrate with ACI, im adding more information here: https://www.cisco.com/c/en/us/td/docs/switches/datacenter/aci/apic/sw/kb/Cisco-ACI-and-SDWAN-Integration.html
A: SD-WAN is a separate solution, however, I recommend you to contact your Cisco Sales Engineer and share this concern with him, he can have a more accurate answer for this one!
A: SD-WAN does not function with the traditional licensing model; here you have a Smart Account consolidating everything in there.
A: On SD-WAN solution the VEDGE/CEDGE devices that are the "Customer Edge" just need to have a connection with the ISP. in this way we save cost because we can use the Internet cloud. MPLS cloud is more expensive.
A: You can troubleshoot SD-WAN just like in the traditional way, via CLI but you can also troubleshoot it using vManage tools, some of these tools will be shown in the Live Demo!
A: The benefit of SD-WAN is that we can use an Internet clod with ISP instead of MPLS that is more expensive. The SD-WAN edge devices need to have basic connectivity with ISP PE, we can use a default route of BGP.
If the PE router is managed by your ISP or you, we just need to achieve basic connectivity in order to reach SD WAN controllers on the cloud.
A: Yes, all the configuration will be there in the routers, you can also SSH into each router to see it but they're configured via vManage and the vManage is the one who pushes the configurations to every router with a few clicks.
A: The configurations are saved in the vManage as Device Templates, there're 2 modes for the routers, CLI mode (traditional) and vManage mode, if you go for vManage mode you will have everything in the vManage no matter if you lose the router.
To complement: in CLI mode the configuration stays in the device (traditional way).
A: Some SLAs are configured, each SLA will have the jitter, delay and loss parameters with a % in there. Depending on your SLA the Policy will react and forward the traffic to any given link or color.
A: Yes but not with SD-WAN, the link between the CE and PE is a traditional link, such Internet or MPLS, but SD-WAN will create its own overlay above the underlay.
A: To monitor traffic on sd-wan we can use CFLOWD that is similar to Netflow or vAnalitics.
A: For SD-WAN we can use centralized policy and localized policy, this can affect all devices or specific devices.
A: For configuration, we have two options, vManage mode or CLI mode. The benefit of Sd-WAN is the possibility to use vManage mode that automatically can affect Edge devices. Here with a template, we can add QoS or ACL. This is an introductory session - we can go deep into many topics but time runs off quickly. We will definitely consider these questions for a later session (if possible). Thanks!
A: Yes, what matters is that it is a VNF/VM. Virtualized appliance.vEdge -> Viptela hardware vEdge cloud -> virtual appliance cEdge -> Cisco appliance running IOS-XE.
A: You can use cisco dcloud. Check the following URL: https://dcloud2-lon.cisco.com/content/catalogue?filters=s-enterprise-networks&search=sd-wan&screenCommand=openFilterScreen&isLoggingIn=true
A: CE and PE? Those are functions and roles in your network. For vEdge and cEdge devices: they have a chipset placed into them during manufacturing. For the controllers, they are provided and signed by Symantec and Digicert.
A: The capacity of the templates is related to the capacity of the vManage controller itself. Each vManage controller can have. Its up to 2000 devices if I remember well. (take this number with a grain of salt)
A: vMAnage will host the configuration, and that will be pushed down to the devices in the fabric.
A: It depends on the device. Hardware capabilities depend on licenses and hardware.
A: Once the template is created, you get to the left pane: templates. Edit it, and you will have, either the block of text to modify, or the feature templates to change values on.
A: EIGRP run only on CISCO devices “CEDGE” and OSPF can run on CEDGE and VEDGE because is an open standard, if Edge devices will connect internally with another vendor is necessary to use OSPF.