#Cisco ios xe eve ng dot1q how to#
#Cisco ios xe eve ng dot1q series#

Templates are the preferred method of manually configuring all aspects of edge devices as opposed to using the CLI. Feature templates are then combined into a вЂњdeviceвЂќ template and attached to individual devices. VPN and device configurations are done through вЂњfeatureвЂќ templates. In order to start passing user traffic across the SD-WAN fabric, you must define a Service VPN (any VPN other thanВ 0В orВ 512). With no customization, all SD-WAN devices have interfaces in VPN 0 (the transport VPN) and can reach each other in a full-mesh. When you initially set up the SD-WAN environment (as was done in the appendix), only default templates exist and no custom VPNs are defined. In other words, within the same SD-WAN fabric, you can have one VPN with a full-mesh topology, another with hub-and-spoke, and another with limited reachability only between selected sites (partial-mesh). Devices attached to an interface in one VPN cannot communicate with devices in another VPN unless policy is put in place to allow it.Д«y default, devices within a single VPN can reach any other device within the same VPN, and the topology across the SD-WAN fabric is full-mesh (any-to-any). Just like with VRFs, any particular interface (or subinterface) can belong only to a single VPN. Within the Cisco SD-WAN fabric, VPNs are very similar in concept to VRFs in traditional routing and maintain strict separation across the fabric by default. Throughout the lab topology, I made the system ID of all the SD-WAN devices one higher than one of the device IP addresses.

For example, in this lab topology, the cEdgeВ S100-CE1В will have an interface IP address ofВ 10.100.10.1, so I set the system ID toВ 10.100.10.2.

One common practice if you have spare IP addresses (and what is used in this lab) is to have a system ID value that is on the same IP subnet that the SD-WAN device participates in. The system ID is similar in concept to a loopback address or a routing protocol router ID, but the chosen address cannot be assigned to any interfaces on the SD-WAN device, and must be unique across the entire fabric. This allows you to potentially get more creative with the numbering scheme. The system IDs are only referenced within the SD-WAN fabric, so they can be any valid unicast IP address, even if itвЂ™s a public address that you donвЂ™t own. System IDs are also a 32-bit number, but follow the dotted decimal format and must be within the valid unicast IP address range. Sites are a 32-bit number (4.3 billion possibilities). Whether you are deploying Cisco SD-WAN in a lab or in production, you should take some time to carefully plan out the values youвЂ™ll use for sites and system IDs. Please refer to it if you are starting from zero. For a lab environment, standing up the controller infrastructure is not especially difficult, so I decided to include this labвЂ™s setup as an appendixВ at the end.

#Cisco ios xe eve ng dot1q series#

My friend Tim McConnaughyВ also has an incredible series of posts on understanding CiscoвЂ™s SD-WAN architecture and its components that you should read and bookmark. I highly recommend reading these posts by Alin IorgutaВ and Brad Searle.

#Cisco ios xe eve ng dot1q how to#

There are a few excellent resources available on how to stand up the controller infrastructure.

Cisco ios xe eve-ng dot1q