So what we want to accomplish here is we want to build the topology that I have
drawn out in the upper left here.
And we're going to end up forming tunnels out this direction.
So gig 4.14 on edge 13 is going to form tunnels this way, and this will be
targeting the MPLS transport.
And then we also need to be able to form tunnels this way.
From edge 14's perspective it needs to be able to extend out gig 4.13 targeting
the internet.
So basically internet devices up here need to be able to come in and form
tunnels this way.
And likewise MPLS connections that are coming in through edge 14, we want them
to be able to form connections up to edge 13.
So this is the goal of what we're trying to accomplish here.
So let's go ahead and start with edge 13 configuration. We're going to do a
config -t.
And then we're going to get onto interface gigabit ethernet 4.13.
So this is a sub interface configuration. I don't need to specify the VRF
because it's VPM0, which is the default VRF, which is really nice.
So I'm going to specify my IP address of 10.13.13.1. Again, edge 13 will be .1
on these individual key lock extension subnets, and it's a /30.
And then I need to specify encapsulation .1 queue and then the VLAN tag.
So I'm going to use the VLAN tag of 13 for the link on the left and 14 for the
link on the right, which is, I think, fairly intuitive.
We'll just pick that middle subnet or middle pair of subnets.
And by the way, I could make that a native just by adding the keyword native
here if I wanted to, but because of the iOS V L2 switch underneath running VLAN
s 13 and 14, we're not going to use the native default VLAN there.
And so then I'll do a no shutdown as well. So from here, let me exit out and do
the other interface.
So interface gigabit ethernet for .14 specify the IP address of 10.14.14.1/30.
And then encapsulation, this one is using encapsulation .1 queue 14 and then a
no shut.
So then I'll exit out of this and we need to form our tunnel connection.
So remember, we're forming tunnels. So I'm on edge 13. I need to allow our
tunnels up here to be able to form, which means that I need a tunnel interface
command on this interface under SD WAN configuration.
And then I also need a tunnel on the backside and the iOS side.
So just like we did before, I'm going to create an interface for tunnel 2, 0
and 1 are kind of in use on at least 14.
13 only using one of them. We'll just use tunnel 2 on both. And now I'm going
to preemptively do a no shot.
And then an IP unnumbered command, which allows it to use the same IP address
as gigabit ethernet for .14.
Hit enter and then also tunnel source gigabit ethernet, which unfortunately
does not allow us to tab over here.
So we need to make sure that we type it out without typos as well here and then
tunnel mode SD WAN and then exit out of this.
Now we could commit here, but let's go and finish out the configuration. It
requires, it would flow an error anyways because we don't have the SD WAN side
of this configured.
So I might as well just do it all at once. So interface gigabit ethernet for .
14.
And this is where I need to specify that tunnel interface command and give it
some information such as encapsulation IP sec.
And again, this is edge 13 trying to form a T lock extension. So I'm going to
specify the color as being MPLS.
Edge 13 in our diagram there trying to use 4.14 to form MPLS connections.
Whew, and there we go. Now we do need one other component in all of this. Let's
go ahead and exit out, get out of SD WAN mode.
And that is once again asking that question, how does edge 13 know where the MP
LS subnet lives?
The MPLS subnet is 192.168.254.0/24. Try to squeeze that in there as fast I can
.
And so edge 13 needs to know where this subnet is. I'm just going to give it a
static route of 192.168.254.0/24.
And it's connected via 10.13.13.2, which would be our edge 14 interface right
here.
Whoops, everyone. You may have noticed I pointed to the right interface, but I
actually typed in the wrong IP address.
So we're just going to go ahead and point out that it should be 10.14.14.2, not
the other one that I entered.
And from here I've got it fixed on my end, but moving forward you're just going
to want to make sure if you're following along
that you do type in the correct IP address. It needs to match the external path
that will take when forming a tunnel.
With that, back to the show. So I'm going to hit enter and commit, and let's
see if it all goes through.
Ah, you know what? There's some legacy configuration on here. I believe
remember.
We can only specify a color one time on a device. Now edge 13 only has an
internet connection, but for some reason
there's an old, maybe we did some demo config early. I don't really remember
honestly some configuration on gigabit ethernet 2.
So we're going to need to get rid of that. So let me just default that color
configuration.
And so I'm going to get into the SD win configuration, get onto interface gig
abit ethernet 2 tunnel interface
and say that this is color default. So let's just commit from here. See if that
goes through. Everything looks like it's going through now.
Very good. So it's just a reminder of how important it is to understand how
everything comes together
and the fact that we can really only have one color represented by one
interface on an edge device.
Otherwise an error like that might really throw us off. So let's go ahead and
come over to edge 14 and I'm going to go ahead
and speed this configuration up. We're basically doing the same thing as before
, but I will go ahead
and make some comments afterwards about what exactly I did.
[typing]
Alright, so let's talk about what I just did. So first of all, what we're doing
here is
we're applying basically the same configuration. So we apply 13.13.2 to gigabit
ethernet 4.13 and 4.14 here,
14.14.2 for example interface tunnel 2 same thing. This time we're targeting
sub interface 4.13 over here.
And so we want to make sure we're referencing the right interface. And then
lastly we get into SD win configuration
for this interface. So we can apply the tunnel interface configuration, which
is to specify encapsulation and the color,
which again we're connecting to the internet here, and it's the color biz
internet. Now lastly we ended with a couple of static routes.
Why are we including static routes? Because again with edge 14 we already have
a connection to the .255 subnet, which is a slash 24.
It's a direct connection and it's, we can't just tell it not to have it because
it uses it to connect to our control components as we said.
So what are we going to do instead? Well we're going to specify some slash 32
routes that say that edges 11 and 12 exist out this link right here.
So I'm saying .13.13.1 down here is how we can get out to edges 11 and 12. So
13.13.1 is our destination. It's a slash 32 and we're targeting edges 11 and 12
,
letting it know it can reach out that way. All right, so at this point we're
going to commit.
Hopefully everything takes looks like it did.
Now we're not quite done because we do need to configure edges 11 and 12.
Specifically they need static routes in order to connect to edges 13 and 14.
So let's flip over to edge 13 and do a quick connectivity test. I'm going to do
a ping to 10.13.13.2, which would be edge 14 on the other side of the link and
that looks good.
And we'll ping 14.14.2, make sure both are in good shape and it looks like they
are. So those links are up. Again, let's go ahead and switch over to our UI and
make it so that edges 11 and 12 have static routes.
All right, so what we want to do in order to create a static route is we're
going to go to configuration and we're going to look at our templates.
And when we click over to feature templates, recall that we created VPN 10 and
VPN 20, but we never actually created VPN zero. If we look at device templates
and we edit our current device template, we'll look at the transport and
management VPN.
We see that we created Biz internet and MPLS templates for the interfaces and
that all belongs to VPN zero. But notice that we are using a default VPN zero
feature template.
So we're going to go ahead and create a new one. Go to configuration templates
feature templates add. We're going to specify the platform and pick Cisco VPN.
We're going to create a VPN zero feature template and that's going to allow us
to create a static route. We're going to scroll all the way up here template
name VPN zero description VPN zero.
The global configuration defaults to zero so that's good there. And there's not
a whole lot we have to do here other than scroll down and create a new IP
before route.
Now from here, I'm going to enter the prefix 10 dot 13 dot 13 dot zero, and
then slash 30. Now keep in mind, let's look at our CML.
And remember that edge 11 and edge 12, they need to know where specific, where
specific subnets are here. So this is our wrong one T lock extension right here
. So these two subnets the 10 13 13 and the 10 14 14, both of which
belong to each one of these links because these are trunked links. So we need
to advertise where they are. Well, edge 11 here. And edge 12 they're both going
to need to see that the Internet one is located via the Internet next top.
And then the MPLS one is found via the MPLS. In other words here, 10 dot 13 dot
13 dot zero slash 30 needs to be known by this next top.
Furthermore, then our other interface here, which we can, I guess right here 10
dot 14 dot 14 dot zero slash 30.
This is used for the MPLS circuit, which means that we're really targeting this
internal interface here. And so we're going to want to advertise it via this
next top.
So 10 dot 14 dot 14 dot zero is going to be known by remember MPLS is 192. Well
, it's right here, but 168 dot 254.
And so dot 14. This is our next top for that subnet and our for, yeah, for this
subnet here, whereas for 10 dot 13 dot 13 dot zero, its next top is going to be
up here in this subnet 192 dot 168 dot 255 dot 13.
So let's go ahead and add a next top for 10 dot 13 dot 13 dot zero. We're going
to 192 dot 168 dot 255 dot 13 that's available via the Internet and click add.
And we'll add that route. And then we'll add another route.
Scroll down again for 10 dot 14 dot 14 dot zero slash 30 at a next top.
And this is available via MPLS, so it'll be 192 dot 168 dot 254 and then dot 14
, because again it's available via MPLS on edge 14.
So click add and add. And then lastly, we're going to add a default route
because again, this is a template that's going to push down and overwrite our
existing configuration.
So let's go ahead and configure a default route and next top and our next top
will continue to be via the Internet 255 dot one and click add.
Alright, so we're going to go ahead and save this template.
And now we can go over to device templates, edit our device template, and then
we're going to scroll down to VPN zero and select the one we just configured.
Didn't work. And right there. And we'll click update.
And click next and then configure devices and yes, we're going to push this
down to the two different devices. So we're going to let this grind a little
bit and once it's ready, we'll progress.
Alright, so everything is looking good. Let's go ahead and switch over to our
view here.
And we will take a look. Let's say edge 11 here.
Show IP route. We should now see static routes. So we've got our default route
in here. We've got static routes to exactly where we said we wanted to go for
finding edges 13 and 14, specifically these subnets.
And then whether we want to force that through the Internet connection or force
it through MPLS. And so once again over on edge 12 show IP route, it should
also have these as well.
So at this point, what we've done is we've extended the underlay between edges
13 and 14. Next up, we need to configure the T lock extensions that will allow
them to build the data plane tunnels.