Alright, let's go ahead and set some quick goals for what we're trying to
accomplish
here from a configuration perspective.
What we want to do is we want to configure edges 11, 12, and 14 with this
concept of
max control connections.
We're going to see that very clearly in both the CLI and the graphical user
interface
configuration.
So when we look at our MPLS cloud down here, what we see is that edge 14 needs
configuration
on gig one and then edges 11 and 12 need their configurations on gig two.
Now keep in mind, when we performed the initial configuration, we drew a line
in the sand and
we said edges 13 and 14 are going to be configured via CLI and edges 11 and 12
will be configured
via graphical user interface.
So that's what we're going to do here as well.
We're going to start by getting onto edge 14, changing gig one to have that
concept of
the max control connections being set to zero and from there we'll go into the
graphical
user interface and edit our configurations for edges 11 and 12 and hopefully
start to
see some data plane connections forming across our MPLS circuit.
So let's start by getting onto the CLI for edge 14.
I'm going to do my config dash T and then enter into SD WAN configuration mode
and from
here we're going to get onto the interface.
Now again for edge 14, this is gigabit ethernet one in our lab environment and
then I want
to get onto the tunnel interface.
This is the goal.
No, we had to go through a lot to get here, but we're trying to get into the
tunnel interface
configuration, which is where we deployed our encapsulation type and
importantly our color
and it's where we can enable and disable tunnel services that come into this
interface outside
of the tunnel.
But the other thing we can do here is set this max control connections to zero.
We're going to hit enter and then we're going to commit this and type end in
order to be
done and then I can do a show run SD WAN, whoops, I flipped that show SD WAN
run based
down to the bottom.
All right.
Now let's scroll up a little bit and look at interface gig one.
So again, interface gig one and getting onto the tunnel interface.
This is again where the encapsulation color are set, but notice now we have max
control
connections.
So that's great for edge 14, but that's not going to help it form any data
plane tunnels
yet because we don't have anything or we don't have that same configuration set
yet on edges
11 and 12.
So for that, let's switch over to our manager or our V manage and we're going
to go to configuration
and scroll down to our templates, recall how this configuration works.
We have this device template that is currently attached right here to two
different devices
that be a edges 11 and 12.
And the way we perform configuration on this one device template is with
individual feature
templates.
And we have two different interface feature templates as well as that triple A
that we
configured so that we could still log into the devices on our CLI.
But we've got to make sure that we're editing the right ones.
Let's make sure that we look and see, okay, this is the MPLS one interface MPLS
config.
This is why naming and descriptions are so important.
We don't want to have to guess which interfaces which so MPLS is the second one
.
I'm going to come all the way over here to the ellipses and select edit.
So once it loads here, and always it starts us at the very bottom, we're going
to scroll
all the way to the top here.
And from here, we can click on tunnel right here or we can scroll down a little
bit more
from there.
But either way, we see that we've got the tunnel interface configuration in
place.
Our color is MPLS.
And then if I look down just a little bit more, we see maximum control
connections.
So rather than leaving this on the default, I'm going to select global and say
zero.
So from here, I'm going to update this.
And then click next and configure devices.
Now this is going to alert me to the fact that yes, I'm about to push real
configuration
down to live devices.
So always keep in mind, anytime we're doing configuration changes, this is
something that
we want to be very careful of because this is not just me being on one device
CLI and
possibly making a mistake.
I'm about to push this configuration down to two devices or 20 devices or
whatever it
is, I'm pushing that to a lot of devices.
So be careful with this in actual production networks.
We don't want to make a mistake and push it down, maybe push it down to one
first and
then see, but either way, we're just going to go and push it down to two.
All right.
So this is in progress.
We'll just wait very briefly while this comes together.
And then once the configuration is pushed out there, we will be able to pull
everything
up and hopefully start to see some tunnels being formed.
All right.
So we see some success here.
I paused the video and it was only about five seconds later that it came up.
So it didn't take very long.
So I'm going to come over to monitor, go to overview.
And we will hopefully start to see some tunnels come up.
Let's see if they're already up yet.
Looks like not quite yet.
And so we'll give it a few moments here to see, but let's go ahead and flip
over to
the CLI as well and make sure our configuration took place.
So here we are an edge 11.
Let's just do a quick show SD WAN run face all the way down to the bottom.
Take a look at interface gig ethernet to this is our MPLS interface.
And we do see that our configuration was successfully deployed with max control
connections
being set to zero.
So let's go ahead.
It's been a few moments.
Let's see if we have some tunnels will do a show SD WAN BFD sessions.
And look at that.
We do have tunnels.
I see MPLS connecting to biz internet.
Now notice MPLS to biz internet is down.
Why is it down?
Because they have no way to communicate.
They just know that there's a another let's see here.
So from MPLS trying to connect to edge 12 on its biz internet.
We understand that it's trying to connect but it can't connect.
There's no IP connectivity between MPLS and the internet in at least in our lab
environment.
But we would see a tunnel form here if those connections existed.
Now from here we scroll back up just a little bit and we should see yes right
here.
So edge 11 can connect to edge 12.
Is its system IP?
So it's able to connect to edge 12 from its MPLS color to the remote MPLS color
.
It can also connect to edge 14 MPLS to MPLS.
So our data plane connections have come online and that is a very good thing.
So that is what we set out to accomplish.
Wanted to make sure that we bring up data plane connections even though this T
lock doesn't
actually have the capability of forming control plane tunnels or can really ton
orchestration
plane and management plane but it's unable to form tunnels to its control
components.
That's fine because we set max connections to zero it's not expecting us to be
able to
form those connections and therefore it has brought up the data plane
connections even
without those other connections in place.