In order to configure OMP timers and such,
we're going to go down to our templates here in configuration,
look at the feature templates, and as we've looked at before,
we're going to add an OMP template.
So it's right here at the top, Cisco OMP,
and we'll scroll up to the top here.
So we can call this template name something like
OMP changes, something along those lines.
So this would be changes for OMP.
And when we look at the basic configuration,
this is where graceful restart timer is set,
and we do see the default value of that 43,200,
which equates to 12 hours.
Don't forget that this is also where we can set the send path limit
as well as the ECMP limit.
And then we can also enable and disable graceful restart right here.
So as much as anything,
it's nice to come in here and look at the defaults
to know that graceful restart is enabled by default.
we do see our limits and the fact that OMP is not shut down.
From here, we can scroll down and see those other three timers.
So our advertisement interval, which is every second,
hold time, which is 60 seconds, which always keep in mind,
keep-alives are sent every one-third of that,
so that would be every 20 seconds is the keep-alive,
and then the EOR timer here, the end of rib,
that is once again set to a default of 300 seconds,
which is five minutes.
So let's go ahead and have some fun.
and see what it looks like in the configuration.
So let's just change the hold time to be 120.
We'll change the advertisement interval to be 10.
EOR timer, we'll just double it and say 600 seconds.
And then we can also set the graceful restart timer here,
and we'll just make it, you know,
let's just make it a little smaller, actually.
Let's just make it 40,000.
So I'm going to save this configuration,
and now we've got this OMP type of feature template.
So go up to the top here, go to the device templates,
edit our device template, and then when we scroll down,
it's really right here at the top we see Cisco OMP,
and so I can scroll down and pick my feature template
that I just created.
So from here I'll click update and push this configuration down
to edges 11 and 12.
So there's no harm in going into doing this.
We'll just play around with the timers a little bit,
and the good news is then we can go and see
what happens at the CLI,
and then we can take that information
and configure one of the edges via CLI
that is not managed by manager here.
So we're just waiting a few moments
for the configuration to go through,
and once it goes through, we'll switch over
and take a look at the CLI.
All right, so there we go.
We can switch over to the CLI now,
and so edge 11 just received that configuration,
and let's go ahead and do a show SD-WAN run,
and this is where we can do the pipe
and extend our command a little bit.
We'll do section OMP.
This way we don't have to space through everything.
We can just look at the OMP section,
and this shows us what the configuration looks like.
So again, everything falls under OMP.
We do see the default send path limit and ECMP limit here.
That's just the nature of it being V-managed
or manager-managed is the fact
that we see a lot of default configurations in here,
such as graceful restart,
and then notice that timers go under its own section.
So I'd add timers or say timers
and then change the hold time.
So these are all of the custom values we just configured.
The hold time we set to 120,
advertisement interval to 10, and so on and so forth.
So then from there, we looked at this
in the earlier routing section.
You can see which of our routing protocols we're advertising,
keeping in mind that OSPF internal routes show up in here
while they're being advertised,
but it doesn't actually show up here.
So it's sort of in there by default.
So let's do some changes.
We'll flip over to Edge 13 here
and demonstrate this at the CLI.
So we'll do a config-t.
We'll get into the SD-WAN section,
and once again, it's under OMP
is where we do all of the configurations.
So I can do a question mark here.
We can see, for example,
that this is where I can set the ECMP limit
as well as the send path limit,
and then I can also enter the timers.
So I hit timers or type in timers and hit enter, question mark.
Now we see the four different timers in here
as well as another one for dampening.
We're not talking about that right now,
and so we can change the advertisement interval.
If I do advertisement interval, question mark,
the beautiful thing about this is it shows me the range
and also the current configuration.
Always keep that in mind,
that that is part of the VIP Telecode that Cisco's running
is it shows it to us in a different color.
So I could make it advertise interval five,
I could do an EOR timer,
which, once again, I can do a question mark
to see what we're currently at.
We'll say 600.
Graceful restart timer.
And we're currently 43,200.
Now watch this.
I'm going to say 45,000,
and let's see what ends up happening here.
And lastly, we'll do the hold time.
So hold time, you know, it's 300,
which means our keep-alives are every 100.
That means we'd have to set the hold time to 450 seconds
since the keep-alives are based on that.
So what's going to happen here is when I commit,
we're going to see an error.
Notice what it says here.
The value for our graceful restart timer of 45,000,
the IPSec rekey timer should be at least two times
the graceful restart timer.
That is very important.
So important, in fact, that Cisco requires us
to configure the IPSec rekey timer
to be at least twice as much.
It's not going to allow me to commit this
until I either change this timer
back to what it was or lower,
like we did earlier with the via vManage,
or if I raise the actual IPSec rekey timer,
which is an option that we'll take a look at in a little bit.
So understand that that is an option for now.
I'm going to abort these changes,
and we understand how to configure this at the CLI.
Now, lastly, let's take a quick look at the SD-WAN controller.
And always remember that the controller
is part of the control plane.
In fact, our edges don't form controller,
or really, OMP relationships with one another.
They only form OMP peerings with SD-WAN controllers.
So if I want to change the graceful restart timer for edges,
remember, the timer is told to the other side.
So if I want my edges to restart
or have a lower restart timer when a controller goes down,
then I need to configure it here on the controller.
And so a lot of our configuration is the same.
We just don't have to worry about going into SD-WAN mode
because on iOS, that's how we tell the iOS XE device
that we want to start to enter Viptela commands.
So with a Viptela software set like the SD-WAN controller,
I can just do a config space T to get into things,
and I don't need to do SD-WAN
because, again, we're already in SD-WAN operation.
I just need to type OMP.
I run my question mark,
and I see all of the timers and limits that we have talked about.
So that is how we go about changing the timers
both in graphical user interface and at the CLI,
and we're going to dive now a little bit deeper
into what it takes to change that rekey timer.