All right, we need to make sure that we understand this whole process.
Now you might have been following along as you went, but if you weren't, make
sure you
take the time to do the challenge.
And again, especially if you don't have access to some of the, maybe lab
equipment or the
CML or anything like that, then you're going to want to make sure that you're
thinking
through what this process looks like.
Again, we went into this skill knowing that we've already created the
identities for our
edge devices up in the Cisco cloud, the plug and play connect portal.
And then we knew that we had already applied that into the manage.
So the only thing we had to do was to more or less get those identity points
and get
some of that configuration, the certificates to trust onto our edge devices.
That's the part that we really need to think through is how is all of this
connecting together?
How does it work when a virtual device can be spun up?
It won't have a certificate.
It won't have an identification point because it's software could randomly
generate one,
but at the same time, manager would need to know what it is.
In order to simplify that process, we use the PNP connect cloud.
And what that allows us to do is to make the identity points, make the OTPs,
the one time
passwords and set the certificates.
And then we just need to manually apply those configurations via the bootstrap
concept.
And so remember that bootstrap concept consists of two separate configurations.
We go to configuration over here and we go down to the first of all, let's look
at the
certificates.
Remember, this is where the UUID and where the token is listed here.
And then what I do is I go to the devices on under when edges, I'm going to
export.
I did this last time to export the bootstrap configurations.
I'm really not sure where that's coming from.
I'm going to export it.
And this is going to tell me all the certificates that I should be trusting.
And then I'm also going to come over here and say that I want to, whoops, now
it's been
replaced because it's actually running.
I can look at the local configuration.
But remember, this is where I would generate that bootstrap configuration.
And so that bootstrap configuration is going to be applied in CML.
I come over here.
I pull up my device.
I go to the configuration.
And remember, I do need to merge the two concepts together.
So I'm going to get the UUID and one time password.
I'm going to get that from the, well, the, that's the specific configuration.
There we go, the bootstrap.
That was the word it was escaping me.
So it comes from the bootstrap configuration as well as a couple of these
others items.
And then the WAN interface on down.
This is part of the generic.
The problem is that the WAN interface being part of the generic messed me up as
far as
basing it into edge 14 completely forgot to change that.
And so that caused problems down the road.
And so instead, what we're going to do is want to make sure that we edit the W
AN interface.
But otherwise we can pretty well paste in all of the certificates that should
be trusted.
And that's going to allow the device to come online.
Now we're not quite done yet at that point because we should come down here as
well.
And we're going to want to make sure that we add some of this configuration.
So I'm going to paste some of this into our skills so that we've got the
ability to copy
and paste this out.
Just keep in mind that we're going to want to edit it for our own environment.
And again, like what we did with edge 14 over here, we do need to make sure
even though
part of that configuration was wrong.
This part of the configuration we did get right, which is making sure that the
correct
subnets and the correct IP addresses get applied to the correct interfaces.
So last but not least, we recall as we switch over here to the terminal that
once the device
is online, we've got some great commands we can run.
For example, we can do a show SD WAN running config.
That's going to allow us to especially look at this configuration up here once
it's been
downloaded and hey, if we aren't able to connect to the controller components,
then
we probably are not going to see much up here.
That'll indicate that something is wrong.
We can do our pings just using ping something out on the internet like our DNS
server.
Make sure we can ping device helper.cisco.com.
That's a good one to remember because if we can't connect to that, that is the
name that
or the DNS resolution that Cisco uses for all of their plug and play devices.
And lastly, a very important one to show SD WAN control connections.
You have to add the S on there.
And at that point, we're going to see that we've got, hopefully, connections as
well
as the type of connection that goes to our V smart, our V bond and our V manage
.
So that was a very quick overview of everything that we covered here in the
skill.
It's very important for us to understand this process and make sure we can
bring SD WAN edge
devices online.
We can do it by bootstrap configuration, which I've applied to real life.
If we have a site where we can't use ZTP or PNP directly, then we can go
through this
bootstrap process.
Otherwise certainly in a CML environment, we're going to require, we're going
to require
doing the bootstrap configuration here in CML to make it work.
I hope this has been informative for you and I'd like to thank you for viewing.