Cisco SD-WAN Custom Topology is what we will implement in this section. default SD-WAN topology is full mesh and in the last section we implemented hub and spoke and mesh topology. custom topology requires us to manipulate OMP routes and TLOC updates.
DetailsCisco SD-WAN Topology has a full-mesh topology by default. in other words all sites can communicate with each other without any limitation. In this section two other topologies, hub and spoke and mesh topology is implemented in cisco SD-WAN infrastructure.
DetailsCisco SD-WAN Route Policy is a tool for route manipulation. route filtering, changing metrics or metric type, adding community, and changing AS-Path are some of the manipulations that we can apply while receiving or advertising routes.
DetailsSD-WAN BGP Configuration in WAN Transport is what will be implemented in this section. Already default route is used in edge routers to access wan connectivity over internet and MPLS transport. but in most cases, it is necessary to implement BGP in WAN transport.
DetailsOSPF in Service VPN in Cisco SD-WAN is the target of this section which means to enable OSPF routing protocol (and also static route) between WAN Edge router in main Office in our SD-WAN infrastructure and enterprise datacenter which is also located in the main office and then redistribute routes between OSPF and OMP Routing Protocol. Therefore, users all over SD-WAN Infrastructure can communicate with different areas of Enterprise such as data center.
DetailsUnderstanding Cisco SD-WAN OMP routing concept is required to implement and troubleshoot policy-based routing or traffic engineering on SD-WAN infrastructure. Therefore, this section is dedicated to further details into SD-WAN OMP routing protocol.
DetailsCisco SD-WAN Service VPN are subnets and services distributed behind SD-WAN network which communicate over SD-WAN infrastructure. in other words, the LAN part of SD-WAN infrastructure that is not yet ready in our topology. This section is devoted to create LAN section of the SD-WAN infrastructure using Service VPN.
DetailsAdding a second transport in SD-WAN is what we will implement in this section. We have already set up an SD-WAN infrastructure via internet transport. In this section, our second transport, MPLS, will be added to our SD-WAN infrastructure. This is done through the vManage GUI interface since we have already changed the configuration modes from CLI to vManage.
DetailsIn the last section we changed the configuration mode of the WAN Edge Routers from CLI to vManage using SD-WAN template. In this section we change the configuration mode of the controller from CLI to vManage with the same concept.
DetailsThree controllers and four WAN routers within the SD-WAN infrastructure are already configured using CLI mode of course CLI mode cannot be scalable to configure, manage and monitor thousands of WAN routers. Therefore, in this section we will change the configuration mode of the WAN edge routers from CLI to vManage, so that all remaining configurations are carried out via vManage GUI interface and with the help of SD-WAN templates.
Details