All right, we are going to do the exact same thing but now for EIGRP. So we want to make it so edge 13
forms an EIGRP neighborship with router 134. So we want to see that we are learning EIGRP
routes this way. I want to see that 90 dot etc. And then I want to get it to inject into OSPF.
And I need to make sure that I am turning around and injecting those OSPF routes back into EIGRP.
So the process is going to be very similar. At this point it's just a matter of learning syntax
and knowing how to do it in the graphical user interface. So I'm on edge 13 here. I'm going to
do my config dash t. And then the syntax for this is router EIGRP. So we're creating a routing
process. Also notice I'm not on the SD-WAN side. That's only for OSPF. So here I'm on router EIGRP.
And then I have to give this a name. This is interesting. Cisco at some point or one point a
while ago I guess changed the EIGRP configuration. We used to just configure an autonomous system
number here. But instead now it's a string. And we'll specify the AS within the config.
It makes the EIGRP a little more VRF aware and flexible with configs. So I'm just going to call
this EIGRP CBT. It's just a name. And from here I get on to the address family. And specifically
IPv4. And then let's specify unicast instead of multicast. So again keep the EIGRP
flexible here. But here's what's weird about this. You might think I'd hit enter here and get into a
sub-configuration mode. Instead this is going to be part of the config. So now I have to specify the
VRF. So VRF 10. And then the autonomous system number. And I'm going to go ahead and use 10 here.
This is not required but we'll go ahead and keep it in sync. And now I can hit enter. So I have to
specify all of this information. The address family, unicast versus multicast, the VRF,
and the AS number just to get on to the address family sub-configuration prompt.
All right. So now that we're here we can do a couple of things. First of all we need
a required configuration which is just topology base. We have to configure basically telling
EIGRP that there is a topology here. We're using the base type of topology. There aren't even other
topologies supported on this platform. But we do have to specify this. And next I have to
deploy the network statement. So 10.10.13.13 is the interface on edge 13 that I want to activate.
And then the way we do that in EIGRP is we use a wildcard mask of 000. Now if this seems a little
confusing or maybe you haven't had a lot of experience with EIGRP, the way network statements
work with EIGRP is that we are activating interfaces. It's exactly how it works with OSPF
but OSPF migrated to a model where we don't need network statements anymore just get on to the
interface like we did and said IP OSPF process ID and then area whatever. So we got away from
the network statements on OSPF but we haven't on EIGRP at least for IPv4. So in order to
activate an interface I just specify the IP address of the interface and I have to use a
wildcard mask of 0.0.0.0. I could maybe try to match the subnet but then that will activate
a bunch of interfaces and we just want to activate one interface. So let's just use a very specific
wildcard mask for a slash 32 IP address like 10.10.13.13. So that's it. I'm going to hit enter
and then commit those changes and we should see again this works pretty quickly that we've got
an EIGRP adjacency. So I'm going to end out of that and let's run some IP EIGRP config. So show
IP EIGRP VRF10 neighbors. I have to specify the VRF for EIGRP. I do see that I've got that 13.15
that's router 134 so that's really good and then I can do a show IP route for VRF10 and I would
expect to see remember EIGRP symbol is D here because E was already taken I believe. I assume
I don't know it's been a long time since Cisco deployed EIGRP and so we use D for EIGRP and we
do see that 90.90.90.90 which is exactly what we were expecting to get. So that is how we get EIGRP
up and running. Now how do we make it so Edge 11 is aware of this 90.90.90.90 and Edge 12 and all
the other edges? Well if I do a show SD-WAN OMP routes with OSPF that route showed up already.
With EIGRP no such luck. I see that the OSPF route is in there. I do not see the EIGRP route
and the reason for that is like we mentioned OSPF gets added by default but EIGRP does not.
So we have to explicitly configure this. So we're going to get back into config-t
get on to the SD-WAN side. This is an OMP configuration. All OMP configuration happens
under SD-WAN and then I need to get on to the address family for IPv4. We just did this for
OSPF external routes. The process is the same. I'm going to advertise EIGRP and commit that change.
So now if I end out and I run that same command show SD-WAN OMP routes hopefully it shows up in
our OMP table and there it is right there in the middle. We've got 90.90.90.90. I would expect I
can come over to edge 11 which has timed out and do a show IP route for vrf10. Hopefully see that
we do have 90.90.90.90. So that is how we do it. It's really very similar process. The more we do
this for one routing protocol the better we're going to understand how it works for other routing
protocols. We just need to know some of the caveats. EIGRP syntax is tricky so I'd recommend
practicing it a few times and then recognizing that we have to explicitly inject it into OMP
whereas OSPF that kind of happened for us which was pretty nice at the time. So let's go and see
how we do this with the graphical user interface. We are still on our feature templates tab here so
I'm going to add a template for my 8000v. Scroll down. Remember under this other templates is where
we found Cisco OSPF and we might be looking it's in alphabetical order here so where is Cisco EIGRP?
Well it's not there and the reason for that is because for some reason Cisco didn't actually put
Cisco in front of it. It's a Cisco proprietary protocol. You'd think they would have put Cisco
in front of EIGRP on like a not OSPF maybe but they just kind of named it differently. It is
what it is. So it is there. Just keep looking for it. Again we can call this like EIGRP vrf 10 or
I can always do that. We can call it vpn 10. EIGRP for vpn 10. Yeah vpns are just vrfs. So here we
see the EIGRP configuration. Again the goal here is to configure an EIGRP process so I'd probably
want to make this globally one autonomous system number. Now before we didn't have to worry about
network statements remember we added an area for OSPF and then we added the interface. Well we don't
get to do that with EIGRP. We have to use the network statements and it's a little bit hidden.
So under unicast address family we see this redistribute concept so I'm going to need to do
that. In fact let's go ahead and do that because I might want to redistribute OSPF or OMP back into
EIGRP and this is exactly where I do it. I'd click add and I'm injecting OMP routes back into EIGRP.
Which we haven't actually done yet on CLI so we'll go back and do that at the end. But we also can
click this sub tab here and we've got the network statement. So I'm going to click new network and
now I'm going to add the prefix. So here's where I could add 10.10.13.13.32. Notice we are using
slash notation. We're not doing anything with wildcard masks here which is really nice. So I
could click add here and now I have a network and I have OMP redistributing. So we've got to make
sure we get all of those configurations down. So now we need to add the interface and so we'll
just drop this down and show that we're going to connect on gigabit ethernet 3. This is a required
configuration even though we just configured the network statement. We need to specify this. It's
just part of the SD-WAN config. We could shut it down on this interface if we want to or we can
add a summary address which is an important part of EIGRP configuration. So I'm going to click add
and then from here I could add EIGRP authentication or I could change the timers if I so desire.
I'm just going to click save and now we have our EIGRP feature template. Let's see where we apply
it here in device templates. Edit my device template. So just like with OSPF we're going to
scroll down to the service VPN section, edit our VPN 10, and this is where we can add in EIGRP. Again
it's after all the Cisco's it's right here it doesn't say Cisco EIGRP it just says EIGRP.
I would pick my feature template and click save and then update the devices. So that is how we
would push out our configuration for EIGRP using SD-WAN manager.