All right, it is time for us to perform our initial configurations of these
devices.
So we're going to get onto the validator, the manager and the controller and do
a little
bit of config.
So let's notice a couple of things.
First of all, we have an interface for each one of these control objects that
is facing
VPN zero.
I went ahead and just aligned zero to zero.
So ethernet zero is in VPN zero with the slight caveat that with the validator,
remember
that runs a V edge software package.
It's different than manager and controller.
And so it actually has gig ethernet zero slash zero rather than ethernet zero.
So keep that in mind.
So the zeros face VPN zero, the ones face VPN 512, partly because it's just not
zero.
But I guess we could say there's a one in 512.
Why not?
Whatever helps us remember that.
And then the reachable subnet is going to be VPN 512.
And once we do our configurations, we'll be able to do configuration tests.
All these devices should be able to ping each other across both of the VPNs,
but we will
need to specify VPN 512 if we want to do a ping, because the configuration that
the
CLI always assumes we want to do pings and different operations in VPN zero.
And so we need to specify VPN 512 if we so desire.
Now one other thing that doesn't show up in the diagram is each one of our
controller
objects is going to need a system IP that is an unreachable IP address.
So we're just going to use one dot one dot one dot one for a validator two dot
two dot
two dot two for manager and three dot three dot three dot three for control.
It's just the last digit of the 171 172 173.
We just repeat that and we'll use that in our lab environment safely.
So let's go ahead and perform the configurations.
In order to do that, we could again, with CML, click on this and pull up the
CLI if we so
desired.
However, I'm just going to use the breakout tool.
And so we already covered how to access the breakout tool.
Once we fire up a new lab, we just come out here, click refresh, and then turn
it on.
And then we should be connected.
If I click on this, I should see the three devices, including, or I guess, in
addition
to the Ubuntu machine, all of those should be enabled and we see the port
numbers here.
So from here, we can go ahead and open up our console connection here.
And I should be able to open up CML ports 9000 through 9,000 three actually see
them
right here.
So I can just click 9000 and we see controller 01 log in.
Now Cisco gives us a couple of logins.
Admin is going to be the one we're going to want to use throughout this process
.
And then Cisco is the password.
And so from here, I can open up port 9001.
That should be our manager admin Cisco.
And then 9 2002 is going to be our validator.
So admin Cisco.
All right.
So let's go ahead and start with the validator, the V bond as we used to call
it.
We're going to perform configuration here.
The all three of these devices are running Viptela software.
It's not running iOS X E. And so it's going to feel a little bit different.
But at the same time, it's not that unfamiliar of a process.
But it does use this concept of performing configuration and then committing
that configuration.
In other words, with Cisco, if I get onto interface, ethernet, whatever, and I
apply
an IP address, soon as I hit enter, that IP address is live on the interface.
Well with a lot of systems, including Viptela, I can hit enter and that IP
address doesn't
go live until I commit that change or potentially a bunch of changes all at
once.
And so we're going to see how that comes together here.
So we do start with a configure.
In fact, config T works.
It is registered as that we could just type config.
We're going to start by going into the system config.
And here we could set the host name.
And so if you didn't do it as part of the original configuration, I could say
host
name and then whatever I want there, but we've already added the host name here
, the
primary thing I need to do two things.
First of all, set the system IP.
And I said for the validator, we're going to do 1.1.1.1.
Just use the one for the validator, the V bond, because it's the first device
in a lot of
the processes.
And then we do need to specify a site ID.
I'm just going to specify a site ID of one.
And lastly, an organization name, I'm going to use CBT and for all of our
organization
names.
Now you can use a different organization name for your lab environment.
However, especially when we get into certificates and such, we want to make
sure that the organization
name is consistent everywhere.
So feel free to use CBT and if you'd like, just pay attention to whether it's
upper
case or not, or you can use something that's a little more specific to your
situation.
So hit enter here.
And then we do still need or we also need this last thing is to configure our V
bond
IP address.
And yes, it does still use the V bond command.
We're not calling it a validator.
So V bond and then you just specify the IP address.
And this is important via VPN zero.
So that would be the dot 255.
And 171 is going to be our V bond or validator IP address.
Now because this is the V bond, it is our validator.
And you also need to specify local.
So it knows it is the V bond.
All right.
So that is the system configuration from here.
We're going to do configurations for VPN zero and VPN 512.
So let's start with VPN zero.
We're now in a different section of the configuration.
But again, we haven't committed any of this yet.
So we're just doing all the configuration up front.
And we're going to provide this configuration by the way in the skill itself.
So you can take notes here or you can go and copy it out of there.
But either way, we are going to now that we're in VPN zero.
First of all, I want to eject one of our interfaces.
So I'm going to say no VPN zero for interface.
And this is the V bond.
So we're going to kick out gig zero slash one.
So all interfaces start in VPN zero.
So I'm effectively kicking it out so then I can configure it in VPN 512 shortly
.
But that's just a little thing to get out of the way.
So from here, I'm going to go interface gig zero slash zero, give it an IP
address.
And again, we're in VPN zero.
So that's our 255 subnet once again, that one 71.
And I can use slash notation here to specify that.
Do a no shutdown and then eggs it out.
And from here, I'm still in my VPN zero configuration.
I'm going to give it a default route using slash notation.
And this will simply be 255 dot one, which is the IP address used by CML as the
net interface.
And then I also want to configure DNS so that it can go outbound if needed out
VPN zero
and it will need to go outbound and VPN zero and connect to Cisco.
So we definitely want to make sure the DNS is there.
Now we can get into VPN 512.
So this is the third and last section VPN 512.
We're going to get onto that interface that we kicked out of VPN zero.
So interface gig ethernet zero slash one.
This would flag an error if I hadn't kicked it out of VPN zero by the way.
So we don't necessarily have to worry about remembering it because we'll be
reminded if
we forget, but in order to configure it as part of VPN 512 again, I do have to
kick it
out of VPN zero because all interfaces start there.
So interface gig E zero slash one, I give it my IP address 192 dot 168 dot.
Now this is VPN 512.
So this is going to be my actual reachable IP address 17 dot 171 and enter here
.
Oops, I forgot the slash so slash 24.
And then no shot exit.
And now that the interface is configured, I just have to configure for this VPN
a default
route.
Well, it's actually pointed to an address 17 dot one.
And then also a DNS.
So a data data data data.
Once again, or whatever DNS we want to use.
So connects out of the VPN configuration at this point, I simply need to commit
all
of this.
And we have a handy configuration here that allows me to quit back to the
global configuration
or really privileged exact, I suppose, what I'll call that in Cisco terms.
But either way, we have now configured our validator.
So now we have to configure our V manage.
It's going to look very similar.
We're going to go a whole lot faster.
So let's pull up our manager.
And doing this a couple of times will actually really help us to identify the
process well.
Again, three sections, we start with system, we could do a host name if we want
the system
IP is two dot two dot two dot two, the site ID.
Going a little too fast here.
Site ID is one organization name, as we said, is CBTM throughout this whole
process.
And then I'm going to configure the V bond IP address, again, out VPN zero.
And importantly, I'm not going to specify local because it's not this system.
So now I get into VPN zero.
And I'm going to again, kick out ethernet one this time, specify interface, if
one.
And now I get on to ETH zero, specify an IP address.
And this IP address is my 172 address.
We'll do a no shutdown, give it a default route as well as DNS.
And again, since didn't specify the actual path, there we go.
And now DNS a dot eight dot eight.
And lastly, VPN 512.
And then interface, ethernet one this time, oops, ethernet one, there we go.
And then IP address 192 dot 168 dot 17 172.
So this is the reachable VPN 512 slash 24, no shut exit out of the interface.
Default route points to 17 dot one in my lab environment.
And this IP address is probably going to look different in your space.
And now I can do that commit and quit.
All right.
So one last one, we are almost there.
We're going to do the V smart or otherwise known as the controller now system.
We're going to do the system IP three dot three dot three dot three site ID of
one.
There's four things we have to do here.
And five, if we want to do a host name, we got to do the organization name and
then the
V bond address.
And we don't specify local.
So once again, we get into VPN zero, kick out the interface we're not going to
use.
So interface, ether one.
And then I get onto the interface I want to use, give it the IP address.
That two five five dot one 73.
No shut it.
Give ourselves a default route for this VPN.
And DNS.
And now get onto VPN 512.
So now we should be able to get on to each one.
Yep.
IP address.
That 17 dot one 73 slash 24.
No shot this exit.
Default route of that 17 dot one and DNS.
All right.
So that felt like potentially a lot, but we have now configured all three of
our control
devices.
So at this point, this is this is the big part right here is we expect to be
able to
access our V manager, our manager, graphical user interface.
Here's the slight problem with that.
It can take a long time to come online.
Now I fired these devices up and then I went off on my own for an hour and a
half and
came back.
So we're going to find out if it's actually ready to go or not.
We've got a command that we can run to find out.
And it is this we're going to do request NMS application server status.
Okay.
So this is going to tell us whether the web server is ready or not and enable
this true.
Cool.
So it has been running this whole time.
It says it's been up for well, 64 hundred seconds.
So that's a little more than what was the wait, 610.
Yeah.
So it's been up for quite a while actually at this point.
It's been up for about an hour and 20ish minutes, something like that.
My math is fast enough.
Here's the thing on your end, you just fired this up.
This might take a half an hour.
It might take 45 minutes.
My experience has varied on this of how long it takes for V managed to come
online.
So this is truly a go get a coffee moment.
If you run this command on your manager device and it says enabled is false.
No need to panic.
No need to do anything.
You should go get a coffee, maybe go take a walk around the block and come back
because
it does take a while for this to come online.
So we're going to go ahead and flip over now and point our web browser to our
IP address
right here.
We should be able to point to the reachable VPN 512 IP address that's going to
allow us
to log in to our V manage slash manager graphical user interface.
So I have pointed my web browser to that IP address.
We don't need to worry about the fact that this certificate is self signed in
this case.
And I'm going to log in with admin Cisco.
All right.
So now we're going to log in.
We're going to get some fun little pop up messages here that tell us that hey
we can do
this or that or the next thing and things are out of day.
Holy smokes.
Look at it all coming.
There's way too much.
So I'm just going to say don't show again.
That's useful.
We're going to skip for now with the smart account.
We're actually going to configure that later.
We're going to snooze all of these and there we go.
Now we've got access to our catalyst SD when infrastructure.
So we see the control components up here.
We only have access to the manager.
We haven't connected to the other devices yet.
In fact, we've got a little bit of time before that's actually going to show
that we are connected.