This is a quick overview of SD routing that has been introduced in 2012 and 201712 release.

This feature
allows us to use a single network management system to monitor both SD-WAN and SD routing devices. This
help in simplifying solution deployments. This is the landing page of the SD1 manager. Once a user
authenticates. It provides a complete overview of the network. On the top left corner, it shows us the details
about the controllers followed by the Vanage devices. These vanage devices would include devices running
in controller mode and also SD routing mode. The options we see here are for SD1 and not everything is
applicable for SD routing. We can switch the mode on the SD1 manager to show things that are applicable
for SD routing only that we can do by clicking the Change mode icon on the top right hand corner and enable
SD routing mode. We can switch back and forth between SD1 and SD routing by toggling this button here.
Now let's begin by clicking the number under the manage devices. This takes us to the device monitoring
page. Nex devices running in SD routing mode would include a keyword SD routing next to the device
model, while the devices running in controller mode would have the device model name alone. On the right
hand side we have a context menu that is the 3 dots. By clicking that, it is going to show us the options that
are available for monitoring and troubleshooting the device. Let's select one of the devices from the list here.
This will take us to the device specific dashboard. We are seeing system status that shows us the details
about the system resources like control plane CPU, control plane memory. We have more options available
from the left panel here. Let's choose interface tab, and this page here shows all the interfaces available on
the device and the status associated with them. We can also see a graph which will provide us details about
the statistics on the interface. Now let's select the cross tab here. From the drop down, we have an option to
select the interface. As we scroll down further, it is going to provide us with a service policy which has all the
class maps configured. At this point we do not have any traffic flowing through the device, so we do not see
any statistics corresponding to the class map. Let's go to the real time tab and select one option from the
drop down control summary. Once we choose this option, the SDN manager will do a real-time query from
the device and provides us with the output information. We have more options that we can select from. Now
let's go to the troubleshooting tab. For SD routing, we have ping and trace route options. Let's choose a
source interface, provide a destination IP. And I'm going to choose an IP address from site 110. We can see
that the ping is successful because it transmitted 5 packets and received 5 packets. Everything looks good
here. Now let's check on how we can capture Adventech from the device. Let's go to the tools, operational
commands. We have this context menu. Let's click that context menu, generate admin tech. In the admin
tech we have options as to what we want to include like logs, core, and tech. For now I'm just going to select
logs. Generate We can close this tab. Select show admintech list. It's going to show us all the admin techs
that have been captured. Here we can see that the admin tech is in progress. Once the admin tech capture is
done, we'll be able to download this by clicking the down arrow here. We have captured an admin tech from
a different device earlier, so we can actually see by clicking this I can download it to my local system. And by
clicking this upload, we can actually upload this admin tech to a service request, provide the service request
number and the token ID, and then click upload. It's going to upload the admin tech directly to the service
request. Now let's go ahead and look at the workflows available. The quick connect workflow is going to help
us with the onboarding process. Let's select that. On this page, it outlines the steps involved in the
onboarding process. We have different methods on how we can import the device serial list to the SD one
manager. One is by syncing smart account. Other one is uploading the provisioning of the serial file. And the
next option is you can skip for now. Set up the device that we want on board. Click next. Let's fill in the
details. Apply Provide any optional tags. We'll skip that. On the summary page we can verify that the
information we provided is correct. Once we verify, let's click on board. Now the device details have been
added to the SD1 manager. Now let's go to the config devices. Export bootstrap config, provide the Van
interface. Enable SD routing, generate bootstrap. This is going to download the bootstrap file to your local
system. Copy this, uh, bootstrap to your device. I have already copied this. So this is the file. To onboard this
device we can actually Do this SD routing bootstrap load boot flash, Cisco SD1. CFD file. At this point, once I
select yes and click enter, it's going to load the conflict from the file. I'll do this and wait for a few minutes.
Let's go back to the monitoring page. Search for 124 QC. OK, we see that the device has been onboarded
and we see that this uh device model has SD routing information looks correct. So we have successfully
onboarded the device to the SD one manager. Now let's look at upgrade workflow. Select, let's do. Again,
this page is going to outline the steps involved in the upgrade process. Click next Choose a device that we
want to upgrade. But next Yes. Choose uh image. Download and upgrade at the same time. I want to
upgrade the device right away, so I'm going to select now and do next. In the summary page, verify that the
device that we are trying to upgrade is the right one. Also verify that the image is the right image and click
next. So we have successfully submitted a task for the software upgrade. We can click this check my
upgrade task to verify uh the task details. We can see that the task has been scheduled. It's going to start
any minute now. Let's go back to the overview page. In the upcoming releases, we are gonna be supporting
configuration using config groups and device templates. We would also have some security features that are
gonna be coming in. Thank you.