All right, we are logged into Manager and we're going to push configuration
down for
edge devices.
In order to do that, we're going to go to configuration all the way back down
to templates.
And we're going to need to modify our device template with new feature
templates.
We're actually going to have to create four different new templates, two of
which will
be VPNs and two of which will be interfaces.
Let's go ahead and just see this to put it all together.
We're going to start by adding a new template.
I'm going to search for my 8000 V, whatever type of device we have in our
environment.
Scrolling down to the VPN section, we see Cisco VPN.
And so we're going to create two of these.
We also see that familiar Cisco VPN interface ethernet.
So keep in mind how feature templates and device templates work.
A device template is sort of, we can think of it as if it's a virtual instance
of the
device we're going to be pushing the configuration down to keeping in mind.
There might be multiple different types of devices, which is why we had to
specify the
type of device up front.
But that one device, device template can be used to push to many different
devices.
Well, that again, when we think about it as if it's sort of this virtual device
, we need
to plug in the different configurations into this virtual device that then gets
pushed
down as actual configurations.
If it's a configuration that can apply to all of them, great.
If it has to be different per device, then we have to specify that as a
variable.
So we saw that earlier with this VPN interface ethernet, we use this to
configure our tunnel
interfaces upstream.
But now notice what it says here, we've got the ability to deploy this for our
win links,
which we already did, but also our land links, which would be our service side.
So again, we'll create two VPNs.
We'll create two VPN interfaces that will get mapped to gig three and gig four.
And from there, we'll modify the device template.
So let's go ahead and get started here.
So we're going to go to the VPN side.
As always, Cisco manager gives some pop ups, we have to clear, but also starts
us at the
bottom of the list.
So it's called all the way up to the top.
Maybe that's just my machine.
I have no idea.
But either way, we're going to give this a template name.
We'll keep it simple VPN 10.
We're creating VPNs 10 and 20.
Keep in mind, as a description, I'll just say VPN 10 can have a space in there
since
it's a description.
And from here, we scroll down just a little bit and we see the VPN has a global
ID setting.
We're going to call this VPN 10.
So from here, we could give this a name.
And so let's just go ahead and do that.
Let's give it a name here.
I'm going to set it to global.
And let's just call it something like customer 10.
Now, it's a name for the VPN.
Maybe I'm a service provider and I've got multiple customers.
And so we're just going to map customer 10 to VPN 10.
But that's it.
That's all we have to do.
We've got other options for advanced configurations, but we just want to create
a VPN and apply
it.
So I'm going to click save.
And now we see that we've got, well, once it's done refreshing here, we've got
VPN 10
as a feature template.
I'm going to click add template to add the second VPN again, type 8000 v Cisco
VPN.
And once it's done loading, we're simply going to add VPN 20.
So give it a few moments here.
And we can scroll all the way up.
Again, template name is VPN 20.
And then the description is VPN space 20.
Give it an idea of 20 and change it to a name, which is customer 20 in our case
.
So we click save.
So those are our two VPNs or two VPN templates haven't been attached yet.
And that's fine.
We'll get to that.
First of all, we want to create those interfaces.
So now I'm going to create a different type of feature template.
Scroll down here and click again, this interface ethernet.
We're going to create a template for gigabit ethernet three.
So when we think about coming back here to our topology, gig three is going to
be VPN
10 gig four is going to be VPN 20.
So we've got the VPNs configured again, think about it from a Cisco device.
We've got those VRF's configured separately.
But now we need to apply interface configuration that includes the VPN.
So I'm going to scroll all the way up here.
As always again, I don't know why it does that, but either way, we're going to
give
this a template name.
We'll just say this is a gig three on gig three underscore VPN 10 with a
description
of VPN 10 for gig three.
Now from here, we'll need to make sure we've got settings in place.
I'll allow this interface to come online, the first of which is just making
sure that
it's set to no shut down.
So that's a good start to that.
And then the interface name has to be specific.
Fortunately, again, as we saw earlier, they give us the format here.
So I simply have to type in three after selecting gigabit ethernet.
I could add a description here if I wanted to.
So thanks, we're going to configure an IP address.
We need to make it a specific IP address per device.
We're going to make it device specific.
And remember, this key is a variable.
We want to change the variable to include a tag.
Since this is gigabit ethernet three, we'll make the tag three here.
And so now the variable has a three at the end, which tells us that when it
asks for
this, this key or this variable, then we can know that we're talking about the
gig
three interface.
And we'll see that in action coming up.
So I'm going to click save here.
All right.
So that's three of our four feature templates.
We've got our two VPNs.
Now we just need the last interface, which will be for gig four and VPN 20.
So scroll down, select Cisco VPN interface ethernet once again.
Scroll all the way back up to the top template name.
We'll keep the same format, gig four underscore, and then VPN 20.
This one will say VPN 20 for gig four.
Scroll down a little ways.
Again, we'll say global, no shut.
And then the interface name will select gigabit ethernet at a four.
Scroll down IP address, make a device specific.
It's gig four.
So we'll add a four here.
And that should all be all we need.
So we're going to click save.
And now we have our four feature templates in place.
So that was quite a bit.
But if we're keeping up or keeping track of what we're doing here, we're just
making
sure that we have the configurations in place.
And now we can come over to device templates and add them.
So we're going to click the ellipses and go to edit.
We're going to edit our lab device template.
And again, I don't want to change anything here other than adding in our VPNs.
So we scroll all the way down here and there's this service VPN section.
And by the way, we could have clicked that link at the top as well.
You can click service VPN right here and be taken right to it.
Either way, we see that this is where we're going to add those service VPN.
So I'm just going to say add VPN.
And we're going to add one VPN at a time because we'll see we need to specify
the interface.
I'm going to add VPN 10 first and click next.
And then I'm going to add my interface for VPN 10, which should be gig three
and scroll
all the way to the bottom, gig three VPN 10 and click add.
And now we see that we've got the VPN 10 template as well as the sub template
type.
Unfortunately, it doesn't confirm for us that we picked the right one here, but
we just
have to trust that we did click it correctly.
From here, I'm going to select VPN 20.
And next, and then add in the interface ethernet here, which should be gig four
all the way
at the bottom.
Now notice that we do have other options for adding in ways of routing within
this VPN.
So yes, we're adding a connected interface.
We also see that we could configure, for example, OSPF and BGP and ways of, you
know, ERP is
on here as well now, thanks to Cisco's acquisition.
And so we have ways of adding in routes.
But for right now, we're just focused on getting those interfaces spun up.
So I have selected the VPN and the associated interface.
I'm going to click update.
All right.
So next we have to provide the IP addresses for our interfaces.
Now keep in mind, again, that we made sure to use variables that made sense for
us.
So we see IP address four, even though it's listed first, that would be gig
ethernet for
which is tied to VPN 20.
This is why it's so important for us to distinguish between, for example, gig
four and gig three
here.
So we know which IP addresses to use on which interfaces for hosts or really
edge 12 and
edge 11.
So when we look at our configuration, we recall that edge 11 is going to have
these
interfaces for VPNs 10 and 20.
But we didn't actually assign an IP address to them.
We said that the hosts would be dot 50.
But that's because we're just going to use dot 11 for edge 11 and dot 12 for
dot 12.
We like to use the same number to keep things simple on all of the interfaces.
So we can use dot 12 on both of these interfaces.
Could not only are they in different subnets, but they're in altogether
different VRFs anyways,
same with that 11 here on both gig three and gig four.
So with that in mind, for our variable ending in four, that's gig four, that
would be VPN
20.
So VPN 20 is 10 dot 20.
And then the site, which is 12 and then edge 12 gets dot 12.
And we have to remember to put slash 24 for the prefix length.
So next is edge 11.
So 10 dot 20 still VPN 20, but now side 11 edge 11 slash 20.
Scroll to the right a little bit.
Now we're on gig ethernet three, and we're talking about VPN 10.
So that'd be 10 dot 10 dot 12 dot 12 slash 24 and 10 dot 10 dot 11 dot 11 slash
24.
And so that should be it for our variables.
Everything else should be in good shape.
All of these other remember reapplying the device templates.
So we could get in here and do some edits on IP addresses.
If we wanted to, again, we've got two and one for gig ethernet two and gig
ethernet one,
but naturally we don't want to do that here.
We're just going to click next until Cisco that yes, indeed, we do want to push
this
configuration down to these two devices.
So we wait a few moments here.
We see that it's in progress at the top and we just have to wait for the all
clear for
manager.
And so we'll pause the video until everything is up and running.
And indeed, it only took a few moments and everything pushed successfully.
So that's great.
So we could trust that this took effect or we could actually go to the CLI and
take a
look there.
So let's go ahead and do that.
We'll flip over to our terminal here.
So we're going to want to get on to edge 11 here.
So according to that breakout cable, that would be port 9001 username is Cisco
and
Cisco.
And now I'm going to do a show run on that interface gig three and take a look
at that.
I told you it was a VRF.
So we do see that the VPN 10 that we configured got deployed to a Cisco device
as VRF 10.
So we're in a separate VRF forwarding instance on this interface.
The IP address got applied correctly.
It's a slash 24.
So that's good.
I can do the same thing for gig four here.
Yes, VRF 20 or VPN 20 is good.
And then I swap over here to edge 12 show run interface on gig three.
So gig three VPN 10 perfect 12 12 on edge 12.
And then I look at four and we also see 10 that 20 and VPN or VRF 20.
So it looks like the configuration pushed down correctly.
Now we just want to perform perform perform some verification and for that
matter, see
Get those Ubuntu machines can't ping one another.