So let's flip over to our CML instance here.
And what we will find is when we go to our dashboard,
first of all, if you just deployed CML,
you're going to have absolutely no other labs here.
You have got quite a few labs here
from previous courses and such.
But what we're gonna do is one of two things.
I can either add my own lab,
and by creating my own lab,
I can click the button up here.
I can drag my own devices out here,
especially the controller and the manager
and the validator and so on and so forth.
And maybe there's value in doing that,
especially if you have a specific way
you want to set things up.
Or we can click the import button,
and after downloading the YAML file
that we provided here in the skill,
we can simply drag that over here,
click import and go to lab,
and that's a beautiful thing.
It's already all set up for us.
So what we have here is the diagram
that I essentially just laid out.
We have external connectors here.
This bridge option, which we look at config,
is set to bridge, the exT NAT, which is set to NAT here.
I have a couple of unmanaged switches.
So importantly, these are not managed.
We don't have to worry about VLANs or anything.
It's just a layer two connection
that allows these devices to all communicate.
We've got some IP address labels on here.
We're gonna again use .171, 172 and 173.
And importantly, this is the part where
you're going to need to adapt this to your own environment,
is making sure that you set up this subnet
to be one of your reachable IP addresses.
Very likely, not very likely.
What's required here is for it to be on the same subnet
as your VM for CML,
because that's what the exT bridge is going to do for us.
It's going to connect us out to the,
through the same connection that the VM is using.
Now, if you wanna change this IP address down here,
you're going to need to change that in your CML cockpit.
For the most part, again, because it's not a rounded IP address,
or a subnet, there's not really a strong reason to do so.
So we'll just use that as our VPN zero for the time being,
and probably in future labs.
Now you also see in Ubuntu server over here
that we're going to use.
We're gonna use that to generate a root certificate,
and that's the only purpose for it.
You don't have to use it,
and you can delete it once it's, we're done with it,
but at least it's here.
And then when we look at the configuration here,
the only thing I've done in this is give it names.
So validator zero one,
and we see that right here in the configuration,
and we're just gonna use admin or Cisco,
probably the admin account for all of our configurations.
Manager one is going to have the same situation,
as well as controller one over here.
If I can click on it, there we go.
Controller one, for example, has a host name as well.
And so there's not much to this.
What we wanna do is either create your own configuration
in your own environment, whether it's CML or otherwise,
or import this template.
And what I'd like to go ahead and do is go to lab
and start lab.
Let's get this thing fired up and ready to go.
So in the next video,
we can start to perform our configuration.
[ Pause ]