Alright, next up we're going to have some fun really exploring whether or not
we remember
how to perform configurations.
Our emphasis is going to be on CLI configurations, a little harder to do
graphical user interface
configs.
And so I would recommend taking this quiz, but then also going back and making
sure you
know where to configure all of these parameters inside of the graphical user
interface via
the manager manager.
So let's go and start with this question.
What configuration commands are used to deploy the MPLS color to a T lock
include the parameter
that prevents tunnels forming to non MPLS colors.
Alright, so I've popped the solution here onto the screen.
Once we do our config -t, we're going to enter the SD win command.
This is very important.
This basically tells us to go from iOS mode to Viptela mode because that's
where all of
the Viptela commands exist.
So then we're going to go into our interface, get onto the tunnel interface,
and then not
only do we specify the color, but again, we said we want to prevent tunnels
forming to
non MPLS colors, we need that restrict command.
So that is how we perform this specific configuration, applying the MPLS color
to a T lock via the
restricted format.
Okay, next question.
What critical command is required when establishing data plane tunnels on an
interface that has
no access to the control components?
This is something we explored a few different times and in the real world, this
can easily
happen.
We could have cloud controllers up here and then we've got an edge device that
has access
to the internet, which of course gives it access to the control components, but
then maybe
it has something like MPLS.
And so it's able to form tunnels this way, but not this way.
And the reason for that is because by default edges must be able to reach the
control components
out in interface for it to form data plane tunnels.
So the critical command that's required to bring these connections online would
be that
max connections concept.
So max control connections and then we set that to zero.
And this allows us to be able to tell the SD-WAN environment not to expect any
control
connections out this link and therefore the data plane tunnels can then come
online.
And three, what command is used to verify connectivity to the control
components?
So a few of these are really good.
One of them doesn't actually exist.
That would be a B is our answer show SD-WAN again on a V edge.
We wouldn't include this SD-WAN parameter.
We'd just say show control connections, but because we're on an iOS in this
scenario,
at least we're clearly on an iOS command line interface.
And therefore we have to include the SD-WAN.
So show SD-WAN control connections.
That's a great way to verify our control plane connectivity.
The other two commands are really good.
They're just focused on data planes.
So BFD sessions and show SD-WAN IPsec outbound connections.
Both of these are really good for seeing what is happening at the data plane.
Next up, what configuration parameters used to make routes distinct from one
another when
multiple VPNs are in use in OMP?
So we spent quite a bit of time talking about this.
This is going to come down to route targets versus route distinguishes.
And the parameter that makes them unique from one another is B the route
distinguishes.
And it's right there in the word the distinguishes we talked about is basically
a way of saying
that hey, this is a way to make a parameter unique or distinct from one another
.
So what exactly is the RD?
Well, again, I might have an edge device that's configured to connect to two
different VPNs.
In our case, maybe VPN 10 and VPN 20, and these represent two different
customers.
So if there's a 10.0.0.0/24 on one customer, certainly the other customer might
also have
that same subnet.
So when we advertise these two, 10.0.0.0/24 and 10.0.0.0/24/24, those are the
same route.
So we have to make them distinct from one another.
And so we include the route, Distinguisher along with the route and that makes
it unique.
The route targets are an important part of this process.
It informs OMP where to insert and where to, well, really import and where to
export our
different route distinguishes.
And so that's important as well.
However, the actual parameter that makes the routes unique is the route, Dist
inguisher.
All right, another film, the blank question here.
I highly encourage you to pause the video and make sure that you can jot this
down or even
pull up a CLI and enter the commands until you figure it out.
Either way, the question here is to insert the correct, it's not a question, I
guess.
It's a declaration.
We are to insert the correct configuration commands into the Cisco CLI VPN or
VRF configuration.
And we're told what to use this 10 colon 10 as the route Distinguisher.
So once again, I have popped the solution onto the screen here.
We are to enter VRF definition 10 and then specify the route Distinguisher as
part of
that VRF.
We then get onto the address family and this is where again, we said route
targets are
very important.
It tells us where to export and where to import based on the RD.
And then lastly, get onto the interface and it's VRF forwarding 10.
So make sure we understand globally we have to define the VRF on the interface.
We must specify which VRF is actually in a forwarding state.
All right, just two more questions as part of this quiz.
Up next, question number six, which VPN is used to build out T-lock extensions?
Now we mentioned this earlier.
I said that we always use VPN zero to build out tunnels and that is true here
as well.
The answer is A. And that's because T-lock extensions are basically an
extension of the
underlay.
And if it's one thing we should absolutely have locked in, it's that the under
lay is bound
to VPN zero, which by the way, on a Cisco iOS device is simply the default VRF.
All other VPNs get different VRF tags.
However, VPN zero belongs to the default VRF and it's how we build out our
underlay.
So if I have adjacent edges here at a site and I have WAN connections, I'm
going to have
some kind of connection between the two, possibly two so they can both build
out T-lock extensions.
And yes, these are going to be part of VPN zero because I am truly building out
the underlay
and extending the underlay to the other edge as part of this configuration.
Okay, last question.
It's another fill in the blank.
And again, I would recommend that you pause the video and make sure you can
answer this
question.
So CLI configuration commands are used to deploy T-lock extension.
Assume that a adjacent edge is on gig one and the WAN link is on gig two.
So a picture is worth a thousand words here.
We have those adjacent edges.
We just drew them onto the diagram before.
And so I've got, let's say it's from this left edges perspective, I have gig
one as connecting
to the edge, to the adjacent edge, and gig two is the WAN link to the transport
network.
So we're extending this transport network to edge two over here, edge one on
the left,
edge two on the right.
So here's the question, how would we perform this configuration given this top
ology?
All right, I have popped the answer onto the screen here.
Let's interface gigabit ethernet one so we get onto the downstream interface
and we
specify this T-lock extension as part of it.
Now notice we're not applying it to a tunnel interface.
This goes directly onto the interface itself.
This is part of the underlay, but we're not building tunnels.
This is not something that edge one is going to build a tunnel down to edge two
or anywhere
else.
Instead, edge one is going to form tunnels this way out gig two and edge two is
going
to form tunnels this way via its interface.
But notice gig one here and edge one is not forming any tunnels.
Therefore we don't need the tunnel interface command.
Instead we are simply essentially connecting this interface down to the
transport interface
of gig two and the way we do that is we get onto that interface, gig one, and
we specify
the T-lock extension targeting the WAN link, which in this case is gig two.
So that brings us to the end of our quizzing.
As far as configuration is concerned again, I would recommend spending some
time on the
CLI if any of these questions were difficult.
Just go through the same configuration, practice configurations over and over
again until we've
got that down and then also get onto the graphical user interface like we said
and make sure
that you know how to get onto it, how to configure tunnel interfaces, how to
configure
T-lock extensions, how to do all that configuration via manager because in the
real world we might
be using manager more or we might be using the CLI more.
It's really kind of split out there and so we have to know both ways of
performing configurations
in an SD WAN environment.