All right, it is time to configure this subnet that will be in VPN 10. As we
mentioned, we're
going to only deploy VPN 10 to the site. And we're looking at a very specific
subnet, it is 10
dot 10 for VPN 10, that's the second 10. And then 13 for the site, dot zero
slash 24, we know we've
got dot 50 on the host here, we've got dot 13 is written right there, but I'll
add it here dot 13
for edge 13 and dot 14 for edge 14. So we are going to be performing that
configuration here,
and also keep in mind that we are going to be performing VRRP between these. So
we're going to
need to make sure our VRP is in place. And we're also going to make sure that
dot 13 is the virtual
address that is shared between these two routers. So if edge 13 goes down, then
edge 14, we'll take
on the dot 13 address, remember, we entered dot 13 is the default gateway for
this host. So we're
going out this way, edge 13 goes down for some reason, edge 14 needs to respond
to dot 13, that
is what we're expecting VRRP to accomplish for us. So let's go ahead and enter
into the CLI here on
edge 13. And the first thing we're going to do first of all is just get into
config mode,
because we're in SD WAN operation, it's config -t. But from here, I can enter a
lot of just familiar
iOS commands. So recall, let's just click over here for a moment. To edge 11, I
lost it because
of the breakout connection, refreshing. So let's just log back in here, do a
show, run VRF.
Remember, we need to get this VRF definition in place. We don't have to
configure the IPv6
address family here. So let's just scroll back up a little bit. So we're
focusing in on getting
the VRF definition for VPN in place. And we do need to configure route
distinguish or route targets.
Now remember, this value is arbitrary. However, it does need to match
everywhere. And so the fact
that manager already gave us an RDA of one colon 10, that means that this is
the RDA that we will
have to use at site 13. Otherwise, it's not going to work. We also need to make
sure our
route targets export and import are configured correctly here. And then we'll
get onto the
interface and do some configuration as well. So let's go ahead and flip over to
edge 13
and get that configuration in place. So we're going to do a VRF definition for
10.
And then we'll go ahead and add the same description, customer 10. And now we
'll configure the RD.
And this is what must match what Cisco already put in place at the other sites.
From here,
now we got to get on to the address family for IPv4. This is Cisco's way of
allowing us to have
IPv4 and IPv6 configurations under the same VRF definition. But again, we're
only dealing with
IPv4 in our lab environment. So we'll just configure this one. And this is
where we enter the route
targets. So I'm going to say route target export 110. And then route target
import 110.
And then I can exit address family, get back to the VRF definition, then exit
one more time to
get to global config. Now I do need to commit this at some point. So I could go
ahead and commit
what we have done. But I do need to now configure the interface, their gigabit
ethernet three.
So let me go ahead and do that and get on to interface gigabit ethernet three,
tabbing over their helps a little bit. And then I can go and say no shut down.
But let's go ahead
and place this into VRF forwarding 10, meaning that it's going to participate
in our VRF 10.
And now I can give it an IP address of 10.10.13.13 /24. And lastly, the VRRP
configuration,
VRP IP 10.10.13.13. Or at least that might be what we'd expect because we're
running a lot of iOS
commands. Well, VRP is a little bit different here, where we're not just going
to configure it
using the traditional commands, but we actually have to specify the number here
, so we'll specify
one. And then we do have to specify the address family, because again, we're
building this out
to say whether it's IP before IPV six, pretty much every turn. So VRP one
address family IPV
four. And then the address here is going to be our 10.10.13. So I hit enter.
And now we're in VRP
operation, if or configuration mode, if I want to configure anything
additionally in here, I can do
so. But because the master's already set by the fact that we're using its IP
address, I don't need
to worry about preempt, I don't need to worry about priority, it simplifies
things a little bit
here. So could worry about timers maybe if we want to or tracking statement,
which is very useful for
making sure that everything upstream, if something happens there, we're
monitoring that, and then
we could possibly defer to the other side. Although again, we're a little bit
more limited when we're
using the master IP address, or we're using the same the physical IP address as
the master. So either
way, we are in good shape here. So let's go ahead and do a commit. And then we
'll end out of this.
So we should be in relatively good shape here, let's do a show IP in brief. So
now we have
giga ethernet three configured with 10 at 10 dot 13 dot 13. We can also go
ahead and flip over to
our Ubuntu host, and give it a ting. So 10 dot 10 dot 13 dot 13, let's see if
we can reach it. And
indeed, we can. And let's go back over to edge 13 and do a show VRRP. And we do
see that the state
is master so that's good. Here's our virtual IP address, everything seems to be
in pretty good
shape here, we just don't actually have anybody in the backup state because we
haven't configured
edge 14 yet. So let's go ahead and flip over to edge 14, wake it back up, log
in. And we're going
to do pretty much the same configuration set with just different IP addresses.
So we're going to say
VRF definition of 10, give it that same description, customer 10, give it the
route
extinguisher of one colon 10, enter into our address family for IP V four, and
give it the
route targets. So route target export 110, and route target import 110. From
here we can exit out.
And now do an interface gigabit ethernet three, and do similar configuration,
we're going to place
it into VPN 10. By doing VRF forwarding 10, give it an IP address 10 dot 10 dot
13 dot 14. This is
where the configuration varies just slightly here. Slash 24. And then we're
going to add VRRP. So
remember the whole command here. So our address family of IP before and then 10
dot 10 dot 13
dot 13, we're still entering the virtual IP address. We're not entering our own
IP address here. So
it is indeed dot 13. And I didn't specify the keyword address. There we go. All
right, so exit
out of this, let's go ahead and commit that configuration. And end, we should
be able to ping
dot 14 now, let's go over to Ubuntu, paying dot 14, and we can get it. And we
're going to come back
to edge 14, do a show VRRP. And so we are in the backup state here, we have the
master router is 10
dot 10 dot 13 dot 13. And that indicates that VRRP is working, we have our
virtual gateway address
in place here, we can ping both side are both of those routers. So now we just
want to make sure
that everything works in the event of specific failure scenarios.