Alright, so let's go ahead and get those Ubuntu machines connected and the
networks defined.
So we're going to add a device and we'll find as we scroll down that we have
the option
to add an Ubuntu server.
We're going to pull this out.
In fact, we're going to pull four of them out.
One, two, three, and four.
We want to arrange them in a way that's going to allow us to have clean
connections, clean
and clear connections to the edge devices.
So what I'm going to do is place the top one kind of parallel lined up with the
edge 11
and then put the other one just down and to the right.
So it should look the same on both in both sites.
So from here, we're just going to connect.
So let's add links, connect them in.
Importantly, we've got to track which one is going to which interface but gig
three and
gig four on the respective edges.
Those are what we're going to use for VPNs 10 and 20.
So specifically, gig three here is going to be VPN 10 and then gig four is
going to be
VPN 20.
So we're going to name the hosts to try to help us to keep track of which host
is which
here.
So we're looking on it, we can go to settings over here and I can change the
name of the
host.
So this first one we're going to call host 10 dash 11 and this will line up
with the
IP addressing that we're going to use as well.
What we're saying here is that this is a host in VPN 10 and it's at site 11.
And from here, we'll just name all four of these real quick.
So this one, this other one at the same site will be the other one at host 11
and it'll
just be in VPN 20.
So host 20 dash 11 and then this will be at site 12.
So host 10, yes, 12.
And this will be host 20 dash 12.
Okay, so we've got those names in place.
From here, we need to do the network configuration.
Now again, as I said before, I had promised you wouldn't have to worry if you
're not a
Linux guru, fortunately, we can just copy and paste configuration and CML
allows us
to do this.
So I can go over to the config tab here and we'll see some things in here that
we need
or that we can take a look at, for example, the default logging in here
username and password.
Importantly, we do want to change the host name so that it shows this way on
the terminal.
So host 10 dash 11.
And then let's go ahead and click save.
And then we are going to use the configuration file drop down to select the
network config.
At this point, we're going to take a look at adept because in adept, we
actually have
the configurations all laid out for us.
So if we click over to adapt and we see host 10 dash 11 here, I'm just going to
click the
copy button to copy this configuration.
And then when I go back to CML, I can just highlight it all and paste it in.
Now I want to emphasize something here.
The spacing in this section or in this copy and paste is very, very important.
This is going to use a YAML file to effectively configure the Ubuntu machine as
it fires up.
And if any of the spaces are incorrect, it can cause errors.
So this is why it's probably best just to copy and paste it from adept in each
case to
make sure that the spacing is correct.
For example, this version line has two spaces, Ethernet has two spaces, ether
nets technically.
And then we move down, we see two more spaces and then two more spaces.
And so we just want to be very careful with how we have this configured.
We also start to see that this host 10 dash 11 has the IP address of 10 and 11
in there,
again, representing VPN 10 and site 11.
And they all end with that 50.
But then this allows us to keep track of which hosts are in which subnet as
well.
So I can click save here.
Go to host 20 dash 11.
It's just remind ourselves how to do this.
So we want to put the host name in first, click save, switch over to network
config, go
to adept, and we should see 20 dash 11 here, copy, paste and save.
And so that's all we have to do.
We just have to do this a couple of more times.
Select 10 dash 12, save, change, copy and paste, click save again, never forget
to click
save there.
Or we might lose our configuration.
So last one, 20 dash 12, copy, I got a save, go to network config, paste it in
and save.
So there we go.
That's all there is to it.
We have our configurations in place and our Ubuntu machines dropped into the
topology
as well.
Now we want to boot up all of these devices.
And so we can either individually go around, click settings here and click
start.
And so that's what we'll do in this case.
You could also just go up and say, you know, lab, start lab, and that'll start
everything
that hasn't been started.
But just in case we've got devices out there that we don't want started, we
might just
be in the habit of doing it this way.
Now next we do need to pay attention to the breakout tool.
So anytime we have the breakout tool right here, we're using it to connect to
all of these
devices via our favorite terminal software, whether that's putty or secure CRT
or something
else, then at that point, we're going to want to use the breakout tool.
So how do we use the breakout tool in this case?
Well, once these devices are a little bit more online, we should be able to
come over to
the breakout tool and click the refresh button.
Now by clicking the refresh button here, just demonstrate it real quick, it's
going to sync
back up now to our CML instance.
Notice it automatically turned it off.
It actually disconnects all of our active sessions.
So be aware of that.
And when we click refresh here, we're going to have to re-enable this.
Let's just make sure our hosts are all online.
Okay, good.
They're all there.
You can click home here and then turn this on.
Don't forget to turn it back on.
I've definitely been in a place where I've clicked refresh, trying to log into
devices.
None of them are responding.
What's going on?
Oh, yeah, I forgot to click this button.
So let's go ahead and flip over to our configs and make sure the Ubuntu
machines are online.
And the breakout tool told me that our first host is on port 9,005.
And there we go.
So remember that login is just Cisco Cisco.
And so we are logged into an Ubuntu machine.
Again, if you're not familiar with Linux, no worries at all.
All we're going to do is use ping type of commands.
And before we leave here, we could type IP address and make sure that ENS2 here
, our
ethernet port that's part of this virtual machine is configured with the IP
address that we wanted.
So it looks like we're good to go here.
We've provided with an IP address and a default gateway.
I could look at the next one over.
This would be port 9,006 on my end.
Cisco Cisco.
And it looks like everything is good to go at this point.
So IP address here.
And we've got again, I can match up 1012 to the middle to subnets, make sure
that yes,
we are configured with the right subnet and dot 50.
And maybe we check the other two as well.
So again, we are fired up in our live environment with Ubuntu machines, but we
have yet to actually
deploy those VPNs on those interfaces.
So now we're going to log into manager and get that part configured.