EIGRP Design

[oxfordxbrogues]

Hello Gents,

I am working with a network that is using EIGRP 50 for connection of both onsite and offsite Data Centers along with access for remote locations. They are using an ELAN to connect their remote locations back to HQ and offsite DC's.

For WAN, they have on the core routers EIGRP 50 with the outside firewalls inside interface IP scope put it does not look like EIGRP is configured on the ASA nor is there any other routing protocol present. 

There is failover on the firewalls but manual automation is needed to be made to point the default gateway to the secondary ISP. 

How should something like this be laid out correctly or is this actually correct? I would think both DC would have their own Autonomous system ID but then how would the other networks know how to get to the other systems on the other AS? 

[Julio E. Moisa]

Hi

It can be done with a EEM script, once any event occurs the script will be executed as you desire.  

It is an example, if one of these messages (or sequence of words) is received the script will set up a delay of 5000 to the G0/0

event manager applet EIGRP1
event tag cua syslog pattern "is down"
event tag pri syslog pattern "100"
event tag qui syslog pattern "holding time expired"
event tag sec syslog pattern "Neighbor 10.0.0.1"
event tag ter syslog pattern "GigabitEthernet0/0"
trigger occurs 1 period 10
correlate event pri and event sec and event ter and event cua and event qui
action 1.0 cli command "enable"
action 2.0 cli command "conf t"
action 3.0 cli command "GigabitEthernet0/0"
action 4.0 cli command "delay 5000"
action 5.0 cli command "exit"
action 6.0 cli command "end"

event manager applet EIGRP2
event tag cua syslog pattern "is down"
event tag pri syslog pattern "777"
event tag qui syslog pattern "Interface PEER-TERMINATION received"
event tag sec syslog pattern "Neighbor 10.0.0.1"
event tag ter syslog pattern "GigabitEthernet0/0"
trigger occurs 1 period 10
correlate event pri and event sec and event ter and event cua and event qui
action 1.0 cli command "enable"
action 2.0 cli command "conf t"
action 3.0 cli command "GigabitEthernet0/0"
action 4.0 cli command "delay 5000"
action 5.0 cli command "exit"
action 6.0 cli command "end"

event manager applet EIGRP3
event tag cua syslog pattern "is down"
event tag pri syslog pattern "100"
event tag qui syslog pattern "Peer goodbye received"
event tag sec syslog pattern "Neighbor 10.0.0.1"
event tag ter syslog pattern "GigabitEthernet0/0"
trigger occurs 1 period 10
correlate event pri and event sec and event ter and event cua and event qui
action 1.0 cli command "enable"
action 2.0 cli command "conf t"
action 3.0 cli command "GigabitEthernet0/0"
action 4.0 cli command "delay 5000"
action 5.0 cli command "exit"
action 6.0 cli command "end"

**The config could vary depending of the Platform.  

Now you cannot communicate 2 different EIGRP AS unless you make mutual redistribution. It can be done on one router (more robust):

router eigrp 1

redistribute eigrp 2

router eigrp 2

redistribute eigrp 1

Hope it is useful

:-)