Skip to main content

EIGRP – summarization – part 3

This is 3rd part from the EIGRP summariztion thread. Please read the previous two as well. I would like to test EIGRP stub feature to see what is the impact on EIGRP behavior.



Ever network behind R4, R5 and R6 we may consider as a stub network. If we lose access to one of them, there is no need to query other routers as any of them is a transit network.

I modify the configuration on R4-R6 routers:


R4#sh run | s eigrp
router eigrp TEST1
 !
 address-family ipv4 unicast autonomous-system 100
 !
 topology base
 exit-af-topology
 network 10.2.0.0 0.0.0.255
 network 10.2.1.0 0.0.0.255
 network 10.2.2.0 0.0.0.255
 network 10.2.3.0 0.0.0.255
 network 10.2.4.0 0.0.0.255
 network 10.2.5.0 0.0.0.255
 eigrp stub connected summary
 exit-address-family
R4#
 
 
Now it’s time to shutdown a loopback5 (network 10.3.5.0/24) and check what we see on R4:
 
 
*Jul 21 18:26:47.874: EIGRP: Received UPDATE on Fa0/0 - paklen 44 nbr 10.2.0.2
*Jul 21 18:26:47.874: AS 100, Flags 0x0:(NULL), Seq 401/92 interfaceQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/0
*Jul 21 18:26:47.878: {type = 602, length = 44}
*Jul 21 18:26:47.878: {vector = {afi = 1, tid = 0}
*Jul 21 18:26:47.878: {routerid = 10.3.5.5
*Jul 2
R4#1 18:26:47.878: {offset = 0, priority = 0, reliability = 255, load = 1,
*Jul 21 18:26:47.878: mtu = {1500:[00, 05, DC]), hopcount = 2,
*Jul 21 18:26:47.878: delay = 281474976710655, bw = 100000,
*Jul 21 18:26:47.878: reserved = 00, opaque_flags = 00}
*Jul 21 18:26:47.878: {nh:00000000}
*Jul 21 18:26:47.878: {180A0305}
*Jul 21 18:26:47.878: }
 
 
We don’t have summarization in place and R4 kept 10.3.5.0/24 subnet in its routing table. Once we shutdown it, R4 received update that the network is not reachable. What I can see R4 didn’t receive any query for that missing prefix. It sent own query asking for a backup path:
 
 
*Jul 21 18:26:47.898: EIGRP: Sending QUERY on Fa0/0 - paklen 44 tid 0
*Jul 21 18:26:47.902: A
R4#S 100, Flags 0x0:(NULL), Seq 94/0 interfaceQ 0/0 iidbQ un/rely 0/0 serno 269-269
*Jul 21 18:26:47.906: {type = 602, length = 44}
*Jul 21 18:26:47.906: {vector = {afi = 1, tid = 0}
*Jul 21 18:26:47.906: {routerid = 10.3.5.5
*Jul 21 18:26:47.910: {offset = 0, priority = 0, reliability = 255, load = 1,
*Jul 21 18:26:47.910: mtu = {1500:[00, 05, DC]), hopcount = 2,
*Jul 21 18:26:47.910: delay = 281474976710655, bw = 100000,
*Jul 21 18:26:47.914: reserved = 00, opaque_flags = 04}
*Jul 21 18:26:47.914: {nh:00000000}
*Jul 21 18:26:47.922: {180A0305}
*Jul 21 18:26:47.926: }
 
 
By enabling stub feature we limited the scope of the EIGRP query (without summarization). Now I re-enable summarization, do the same test and compare the output.
 
 
 
 
 
 
I repeated the test once again:
 
R5#conf t
Enter configuration commands, one per line. End with CNTL/Z.
R5(config)#int loop5
R5(config-if)#sh
R5(config-if)#
*Jul 21 18:49:42.930: %LINEPROTO-5-UPDOWN: Line protocol on Interface Loopback5, changed state to down
*Jul 21 18:49:42.934: %LINK-5-CHANGED: Interface Loopback5, changed state to administratively down
R5(config-if)#
 
 
 
and on R4 I can’t see any EIGRP message. So R4 wasn’t queried about the missing subnet and wasn’t notified about 10.3.5.0/25 outage as R5 summarize all networks and presents in one prefix:
 
 
D 10.3.0.0/16 [90/204800] via 10.2.0.2, 00:05:48, FastEthernet0/0
 
 
What is the difference then between scenario presented in part 2 (no stub but summarization) and here(stub and summarization)? In both cases we don’t see any EIGRP messages. I think you have better control with the stub feature. In some cases you may not have summarization in place due to limited number of prefixes or from different reasons and the stub feature helps you keep all unnecessary EIGRP messages away. 
 
 
 

Labels:

Comments

Post a Comment

Popular posts from this blog

What should you know about HA 'override enabled' setting on Fortigate?

High availability is mandatory in most of today's network designs. Only very small companies or branches can run their business without redundancy. When you have Fortigate firewall in your network you have many options to increase network availability. You can use Fortigate Clustering Protocol ( FGCP ) or Virtual Router Redundancy Protocol ( VRRP ). FGCP has two modes: 'override' disabled (default) and 'override' enabled . I'm not going to explain how to set up HA as you can find many resources on Fortinet websites: https://cookbook.fortinet.com/high-availability-two-fortigates-56/ https://cookbook.fortinet.com/high-availability-with-fgcp-56/ Let's recap what is the main difference between them. The default HA setting is 'override' disabled and this is an order of selection an active unit: 1) number of monitored interfaces - when both units have the same number of working (up) interfaces check next parameter 2) HA uptime - an ...
8 comments
Read more

FortiGate and GRE tunnel

Recently I worked on one project where a client requested to re-route web traffic to the GRE tunnel to perform traffic inspection. I would like to share with you what is required if you configure it on FortiGate. We need a new GRE interface and policy base routing (PBR) to change the route for specific source IPs. Of course you need firewall policies to permit the traffic. Let's start with GRE interface. Unfortunately you can't configure it using the GUI, only CLI is the option: config system gre-tunnel edit "gre1" set interface "port1" set local-gw 55.55.55.55 set remote-gw 44.44.44.44 next end When the end peer is Cisco router, you need to set the IP for the GRE interface: config system interface edit gre1 set ip 192.168.10.10 255.255.255.255 set remote-ip192.168.10.20 end In next step we need to fix routing. We need the alternate path via GRE but to keep the route in the active routing table you need to set the same AD (adminis...
Post a Comment
Read more

Inpection of asymmetric sessions on FortiGate

There is one feature available on FortiGate, and I think you should know it, as it modifies a bit what we know about stateful firewalls. In past every packet was treated individually and you had to create policies in both directions. With stateful firewalls we can track connections, and by checking couple of attributes, we can treat them as part of the same session. For example when you initiate connection from a host1 to host2, the returning connection from host2 to host1 will be treated as part of the same connection (session). They have to have the same source/destination and destination/source IPs, port numbers and interfaces.There is an exception from this rule and FortiGate in some specific cases can accept connections on port which was not used in the initial connection. Let me explain how it works on the below example:      The host1 has a default gateway on R1 (10.0.1.2), but you may notice that it is not the optimal path to host2 subnet. When we analyze ...
1 comment
Read more