Repository navigation
EIGRP basic test setup
eigrpd(8) and eigrpctl(8) are available in the latest OpenBSD snapshots.
In this topology we have an EIGRP domain with four routers and a dummy OSPF domain used only to show the redistribution capabilities of eigrpd(8). All EIGRP routers are enabled for both IPv4 and IPv6, although only R2 and R3 are advertising IPv6 networks. R3 is redistributing the connected networks attached to the f1/1 interface and the OpenBSD router is creating a /22 summary for the 192.168.1/24 and 192.168.2/24 networks. This is a rather silly network but the goal here is to test some advanced features of eigrpd(8) using the smaller number of routers as possible.
The first step is to enable IPv4/v6 forwarding and set up the interfaces:
# sysctl sysctl net.inet.ip.forwarding=1 sysctl net.inet6.ip6.forwarding=1 # inet ifconfig em1 10.0.5.9/24 ifconfig em2 10.0.6.9/24 ifconfig em3 10.0.2.9/24 ifconfig em4 10.0.3.9/24 ifconfig em5 172.16.1.9/24 ifconfig em6 192.168.1.1/24 ifconfig em7 192.168.2.1/24 # inet6 (link-local addresses only) ifconfig em1 inet6 enable ifconfig em2 inet6 enable ifconfig em3 inet6 enable ifconfig em4 inet6 enable
Edit /etc/eigrpd.conf:
fib-priority-internal 28
fib-priority-external 52
fib-priority-summary 12
maximum-paths 2
variance 4
# default bandwidth (fast ethernet)
bandwidth 100000
address-family ipv4 {
autonomous-system 1 {
default-metric 100000 10 255 1 1500
redistribute ospf
interface em1 {
summary-address 192.168.0.0/22
}
interface em2 {
summary-address 192.168.0.0/22
}
interface em3 {
summary-address 192.168.0.0/22
}
interface em4 {
# 10M Ethernet
bandwidth 10000
summary-address 192.168.0.0/22
}
interface em6 {
passive
}
interface em7 {
passive
}
}
}
address-family ipv6 {
autonomous-system 1 {
interface em1
interface em2
interface em3
interface em4
}
}
Edit /etc/ospfd.conf
area 0.0.0.0 {
interface em5
}
R1:
hostname R1 ! ipv6 unicast-routing interface FastEthernet0/0 ip address 10.0.2.1 255.255.255.0 ipv6 enable ipv6 eigrp 1 ! ! interface FastEthernet1/0 ip address 10.0.1.1 255.255.255.0 ipv6 enable ipv6 eigrp 1 ! ! router eigrp 1 network 10.0.1.1 0.0.0.0 network 10.0.2.1 0.0.0.0 ! ipv6 router eigrp 1 !
R2:
hostname R2 ! ipv6 unicast-routing ! interface FastEthernet0/0 bandwidth 10000 ip address 10.0.3.2 255.255.255.0 ipv6 enable ipv6 eigrp 1 ! ! interface FastEthernet1/0 ip address 10.0.1.2 255.255.255.0 ipv6 enable ipv6 eigrp 1 ! ! interface FastEthernet1/1 ip address 10.0.7.2 255.255.255.0 ipv6 address 5000::2/64 ipv6 enable ipv6 eigrp 1 ! ! interface Serial3/0 ip address 10.0.4.2 255.255.255.0 ipv6 enable ipv6 eigrp 1 ! ! router eigrp 1 network 10.0.1.2 0.0.0.0 network 10.0.3.2 0.0.0.0 network 10.0.4.2 0.0.0.0 network 10.0.7.2 0.0.0.0 passive-interface FastEthernet1/1 ! ipv6 router eigrp 1 passive-interface FastEthernet1/1 !
R3:
hostname R3 ! ipv6 unicast-routing ! interface FastEthernet0/0 ip address 10.0.5.3 255.255.255.0 ipv6 enable ipv6 eigrp 1 ! ! interface FastEthernet1/0 ip address 10.0.6.3 255.255.255.0 ipv6 enable ipv6 eigrp 1 ! ! interface FastEthernet1/1 ip address 10.0.8.3 255.255.255.0 ipv6 address 6000::3/64 ipv6 enable ! ! interface Serial2/0 ip address 10.0.4.3 255.255.255.0 ipv6 enable ipv6 eigrp 1 ! ! router eigrp 1 default-metric 100000 10 255 1 1500 network 10.0.4.3 0.0.0.0 network 10.0.5.3 0.0.0.0 network 10.0.6.3 0.0.0.0 redistribute connected ! ipv6 router eigrp 1 redistribute connected default-metric 100000 10 255 1 1500 !
R4:
hostname R4 ! interface FastEthernet0/0 ip address 172.16.1.4 255.255.255.0 ! ! interface FastEthernet1/0 ip address 172.16.100.4 255.255.255.0 ! ! router ospf 1 network 172.16.1.4 0.0.0.0 area 0 network 172.16.100.4 0.0.0.0 area 0 !
Verify that all the configured interfaces are up:
$ eigrpctl show interface
AF AS Interface Address Linkstate Uptime nc
ipv4 1 em1 10.0.5.9/24 active 00:00:48 1
ipv4 1 em2 10.0.6.9/24 active 00:00:48 1
ipv4 1 em3 10.0.2.9/24 active 00:00:48 1
ipv4 1 em4 10.0.3.9/24 active 00:00:48 1
ipv4 1 em6 192.168.1.1/24 active 00:00:48 0
ipv4 1 em7 192.168.2.1/24 active 00:00:48 0
ipv6 1 em1 fe80::a00:27ff:fe06:47c/64
active 00:00:48 1
ipv6 1 em2 fe80::a00:27ff:fe82:88b5/64
active 00:00:48 1
ipv6 1 em3 fe80::a00:27ff:fefd:e3ff/64
active 00:00:48 1
ipv6 1 em4 fe80::a00:27ff:fe4b:7d79/64
active 00:00:48 1
Verify that all the required neighbor sessions were established:
$ eigrpctl show neighbor
AF AS Address Iface Holdtime Uptime
ipv4 1 10.0.5.3 em1 15 00:00:17
ipv4 1 10.0.6.3 em2 15 00:00:18
ipv4 1 10.0.2.1 em3 15 00:00:20
ipv4 1 10.0.3.2 em4 15 00:00:20
ipv6 1 fe80::c803:50ff:fe6d:0
em1 15 00:00:20
ipv6 1 fe80::c803:50ff:fe6d:1c
em2 15 00:00:20
ipv6 1 fe80::c801:50ff:fe4e:0
em3 15 00:00:16
ipv6 1 fe80::c802:50ff:fe5d:0
em4 15 00:00:16
If desired, it's possible to limit the output to a given address family (this is applicable to all "show" commands):
$ eigrpctl show neighbor family ipv4 AF AS Address Iface Holdtime Uptime ipv4 1 10.0.5.3 em1 15 00:00:25 ipv4 1 10.0.6.3 em2 15 00:00:26 ipv4 1 10.0.2.1 em3 15 00:00:28 ipv4 1 10.0.3.2 em4 15 00:00:28
Now the best part, verify the topology table:
$ eigrpctl show topology
AF AS Destination Nexthop Interface Distance
S ipv4 1 10.0.1.0/24 10.0.2.1 em3 30720/28160
F ipv4 1 10.0.1.0/24 10.0.3.2 em4 261120/28160
S ipv4 1 10.0.2.0/24 Connected em3 28160/-
S ipv4 1 10.0.3.0/24 Connected em4 258560/-
S ipv4 1 10.0.4.0/24 10.0.6.3 em2 2172416/2169856
F ipv4 1 10.0.4.0/24 10.0.5.3 em1 2172416/2169856
F ipv4 1 10.0.4.0/24 10.0.3.2 em4 2172416/2169856
S ipv4 1 10.0.5.0/24 Connected em1 28160/-
S ipv4 1 10.0.6.0/24 Connected em2 28160/-
S ipv4 1 10.0.7.0/24 10.0.2.1 em3 33280/30720
F ipv4 1 10.0.7.0/24 10.0.3.2 em4 261120/28160
S ipv4 1 10.0.8.0/24 10.0.6.3 em2 30720/28160
F ipv4 1 10.0.8.0/24 10.0.5.3 em1 30720/28160
S ipv4 1 172.16.100.0/24 Connected redistribute 28160/-
S ipv4 1 192.168.0.0/22 Connected summary 28160/-
S ipv4 1 192.168.1.0/24 Connected em6 28160/-
S ipv4 1 192.168.2.0/24 Connected em7 28160/-
S ipv6 1 5000::/64 fe80::c802:50ff:fe5d:0
em4 30720/28160
S ipv6 1 6000::/64 fe80::c803:50ff:fe6d:0
em1 30720/28160
F ipv6 1 6000::/64 fe80::c803:50ff:fe6d:1c
em2 30720/28160
The "all" keyword can be used to show all topology entries, including those that are neither successor nor feasible successors. Note: routes with an infinite metric are not stored in the topology table.
$ eigrpctl show topology all
AF AS Destination Nexthop Interface Distance
S ipv4 1 10.0.1.0/24 10.0.2.1 em3 30720/28160
F ipv4 1 10.0.1.0/24 10.0.3.2 em4 261120/28160
S ipv4 1 10.0.2.0/24 Connected em3 28160/-
ipv4 1 10.0.2.0/24 10.0.3.2 em4 263680/30720
S ipv4 1 10.0.3.0/24 Connected em4 258560/-
S ipv4 1 10.0.4.0/24 10.0.6.3 em2 2172416/2169856
F ipv4 1 10.0.4.0/24 10.0.5.3 em1 2172416/2169856
ipv4 1 10.0.4.0/24 10.0.2.1 em3 2174976/2172416
F ipv4 1 10.0.4.0/24 10.0.3.2 em4 2172416/2169856
S ipv4 1 10.0.5.0/24 Connected em1 28160/-
ipv4 1 10.0.5.0/24 10.0.6.3 em2 30720/28160
ipv4 1 10.0.5.0/24 10.0.3.2 em4 266240/33280
S ipv4 1 10.0.6.0/24 Connected em2 28160/-
ipv4 1 10.0.6.0/24 10.0.5.3 em1 30720/28160
ipv4 1 10.0.6.0/24 10.0.3.2 em4 266240/33280
S ipv4 1 10.0.7.0/24 10.0.2.1 em3 33280/30720
F ipv4 1 10.0.7.0/24 10.0.3.2 em4 261120/28160
S ipv4 1 10.0.8.0/24 10.0.6.3 em2 30720/28160
F ipv4 1 10.0.8.0/24 10.0.5.3 em1 30720/28160
ipv4 1 10.0.8.0/24 10.0.3.2 em4 268800/35840
S ipv4 1 172.16.100.0/24 Connected redistribute 28160/-
ipv4 1 172.16.100.0/24 10.0.3.2 em4 266240/33280
S ipv4 1 192.168.0.0/22 Connected summary 28160/-
ipv4 1 192.168.0.0/22 10.0.3.2 em4 266240/33280
S ipv4 1 192.168.1.0/24 Connected em6 28160/-
S ipv4 1 192.168.2.0/24 Connected em7 28160/-
S ipv6 1 5000::/64 fe80::c802:50ff:fe5d:0
em4 30720/28160
ipv6 1 5000::/64 fe80::c801:50ff:fe4e:0
em3 33280/30720
S ipv6 1 6000::/64 fe80::c803:50ff:fe6d:0
em1 30720/28160
F ipv6 1 6000::/64 fe80::c803:50ff:fe6d:1c
em2 30720/28160
ipv6 1 6000::/64 fe80::c802:50ff:fe5d:0
em4 40960/38400
A few notes regarding the output above:
- There is a feasible successor for the majority of the routes, which means that most topology changes wouldn't trigger the diffusing computation of EIGRP. This is typically the sign of a well-designed network, where the reconvergence time is kept to a minimum;
- The 5000::/64 network does not have have a feasible successor, so a bit of fine tuning the bandwidth/delay configuration would be required to fix this;
- The R2 neighbor is not the successor of any route. Even though the routes through R1 and R3 are one hop farther away, their composite metric is lower because of the slow bandwidth configured in the em4 interface.
Now verify the individual metric components of a few networks:
$ eigrpctl show topology 10.0.7.0/24
Network 10.0.7.0/24
Autonomous System 1, Address Family ipv4
DUAL State: Passive, Feasible Distance: 33280
Routes:
Interface em3 - Neighbor 10.0.2.1
Distance: 33280, Reported Distance: 30720, route is Internal
Vector metric:
Minimum bandwidth is 100000 Kbit
Total delay is 300 microseconds
Reliability is 255/255
Load is 1/255
Minimum MTU is 1500
Hop count is 2
Interface em4 - Neighbor 10.0.3.2
Distance: 261120, Reported Distance: 28160, route is Internal
Vector metric:
Minimum bandwidth is 10000 Kbit
Total delay is 200 microseconds
Reliability is 255/255
Load is 1/255
Minimum MTU is 1500
Hop count is 1
$ eigrpctl show topology 10.0.4.0/24
Network 10.0.4.0/24
Autonomous System 1, Address Family ipv4
DUAL State: Passive, Feasible Distance: 2172416
Routes:
Interface em1 - Neighbor 10.0.5.3
Distance: 2172416, Reported Distance: 2169856, route is Internal
Vector metric:
Minimum bandwidth is 1544 Kbit
Total delay is 20100 microseconds
Reliability is 255/255
Load is 1/255
Minimum MTU is 1500
Hop count is 1
Interface em4 - Neighbor 10.0.3.2
Distance: 2172416, Reported Distance: 2169856, route is Internal
Vector metric:
Minimum bandwidth is 1544 Kbit
Total delay is 20100 microseconds
Reliability is 255/255
Load is 1/255
Minimum MTU is 1500
Hop count is 1
Interface em2 - Neighbor 10.0.6.3
Distance: 2172416, Reported Distance: 2169856, route is Internal
Vector metric:
Minimum bandwidth is 1544 Kbit
Total delay is 20100 microseconds
Reliability is 255/255
Load is 1/255
Minimum MTU is 1500
Hop count is 1
$ eigrpctl show topology 6000::/64
Network 6000::/64
Autonomous System 1, Address Family ipv6
DUAL State: Passive, Feasible Distance: 30720
Routes:
Interface em2 - Neighbor fe80::c803:50ff:fe6d:1c
Distance: 30720, Reported Distance: 28160, route is External
Vector metric:
Minimum bandwidth is 100000 Kbit
Total delay is 200 microseconds
Reliability is 255/255
Load is 1/255
Minimum MTU is 1500
Hop count is 1
External data:
Originating router is 10.0.6.3
AS number of route is 0
External protocol is Connected
External metric is 0
Administrator tag is 0
Interface em1 - Neighbor fe80::c803:50ff:fe6d:0
Distance: 30720, Reported Distance: 28160, route is External
Vector metric:
Minimum bandwidth is 100000 Kbit
Total delay is 200 microseconds
Reliability is 255/255
Load is 1/255
Minimum MTU is 1500
Hop count is 1
External data:
Originating router is 10.0.6.3
AS number of route is 0
External protocol is Connected
External metric is 0
Administrator tag is 0
Verify in the R1 neighbor that our OpenBSD router really created a summary for the 192.168.x.0/24 networks:
R1#show ip eigrp topology
EIGRP-IPv4 Topology Table for AS(1)/ID(10.0.2.1)
Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
r - reply Status, s - sia Status
P 10.0.6.0/24, 1 successors, FD is 2174976
via 10.0.1.2 (2174976/2172416), FastEthernet1/0, serno 292
P 10.0.5.0/24, 1 successors, FD is 2174976
via 10.0.1.2 (2174976/2172416), FastEthernet1/0, serno 293
P 10.0.3.0/24, 1 successors, FD is 261120
via 10.0.1.2 (261120/258560), FastEthernet1/0
P 10.0.1.0/24, 1 successors, FD is 28160
via Connected, FastEthernet1/0
P 172.16.100.0/24, 1 successors, FD is 263680
via 10.0.1.2 (263680/261120), FastEthernet1/0
P 192.168.0.0/22, 1 successors, FD is 263680
via 10.0.1.2 (263680/261120), FastEthernet1/0
P 10.0.8.0/24, 1 successors, FD is 2174976
via 10.0.1.2 (2174976/2172416), FastEthernet1/0, serno 296
P 10.0.7.0/24, 1 successors, FD is 30720
via 10.0.1.2 (30720/28160), FastEthernet1/0
P 10.0.2.0/24, 1 successors, FD is 28160
via Connected, FastEthernet0/0
P 10.0.4.0/24, 1 successors, FD is 2172416
via 10.0.1.2 (2172416/2169856), FastEthernet1/0
Finally, verify that all the best routes were installed in the FIB. We configured before that the maximum number of paths for each destination is two, so even though the 10.0.4.0/24 network has three feasible successors, we only install two of them in the FIB:
$ eigrpctl show fib family ipv4 eigrp flags: * = valid, D = EIGRP, C = Connected, S = Static Flags Prio Destination Nexthop *D 28 10.0.1.0/24 10.0.2.1 *D 28 10.0.4.0/24 10.0.5.3 *D 28 10.0.4.0/24 10.0.6.3 *D 28 10.0.7.0/24 10.0.2.1 *D EX 52 10.0.8.0/24 10.0.5.3 *D EX 52 10.0.8.0/24 10.0.6.3 *D 12 192.168.0.0/22 127.0.0.1 $ eigrpctl show fib family ipv6 eigrp flags: * = valid, D = EIGRP, C = Connected, S = Static Flags Prio Destination Nexthop *D 28 5000::/64 fe80::c802:50ff:fe5d:0%em4 *D 28 5000::/64 fe80::c801:50ff:fe4e:0%em3 *D EX 52 6000::/64 fe80::c803:50ff:fe6d:1c%em2 *D EX 52 6000::/64 fe80::c803:50ff:fe6d:0%em1
Let's shutdown the em3 interface and see how eigrpd(8) behaves with respect to 10.0.1.0/24 network:
$ eigrpctl show topology 10.0.1.0/24
Network 10.0.1.0/24
Autonomous System 1, Address Family ipv4
DUAL State: Passive, Feasible Distance: 30720
Routes:
Interface em4 - Neighbor 10.0.3.2
Distance: 261120, Reported Distance: 28160, route is Internal
Vector metric:
Minimum bandwidth is 10000 Kbit
Total delay is 200 microseconds
Reliability is 255/255
Load is 1/255
Minimum MTU is 1500
Hop count is 1
Interface em3 - Neighbor 10.0.2.1
Distance: 30720, Reported Distance: 28160, route is Internal
Vector metric:
Minimum bandwidth is 100000 Kbit
Total delay is 200 microseconds
Reliability is 255/255
Load is 1/255
Minimum MTU is 1500
Hop count is 1
$ route -n show -inet | grep "10.0.1/24"
10.0.1/24 10.0.2.1 UG 0 0 - 28 em3
$ ifconfig em3 down
$ eigrpctl show topology 10.0.1.0/24
Network 10.0.1.0/24
Autonomous System 1, Address Family ipv4
DUAL State: Passive, Feasible Distance: 261120
Routes:
Interface em4 - Neighbor 10.0.3.2
Distance: 261120, Reported Distance: 28160, route is Internal
Vector metric:
Minimum bandwidth is 10000 Kbit
Total delay is 200 microseconds
Reliability is 255/255
Load is 1/255
Minimum MTU is 1500
Hop count is 1
$ route -n show -inet | grep "10.0.1/24"
10.0.1/24 10.0.3.2 UG 0 0 - 28 em4
As expected, the feasible successor was promoted to successor as soon as the em3 interface went down. Here is the famous subsecond reconvergence of EIGRP.
Now shutdown the em1 and em2 interfaces:
# ifconfig em1 down
# ifconfig em2 down
$ eigrpctl show neighbor
AF AS Address Iface Holdtime Uptime
ipv4 1 10.0.3.2 em4 15 01:04:10
ipv6 1 fe80::c802:50ff:fe5d:0
em4 15 01:04:11
$ eigrpctl show topology
AF AS Destination Nexthop Interface Distance
S ipv4 1 10.0.1.0/24 10.0.3.2 em4 261120/28160
S ipv4 1 10.0.2.0/24 10.0.3.2 em4 263680/30720
S ipv4 1 10.0.3.0/24 Connected em4 258560/-
S ipv4 1 10.0.4.0/24 10.0.3.2 em4 2172416/2169856
S ipv4 1 10.0.5.0/24 10.0.3.2 em4 2174976/2172416
S ipv4 1 10.0.6.0/24 10.0.3.2 em4 2174976/2172416
S ipv4 1 10.0.7.0/24 10.0.3.2 em4 261120/28160
S ipv4 1 10.0.8.0/24 10.0.3.2 em4 2174976/2172416
S ipv4 1 172.16.100.0/24 Connected redistribute 28160/-
S ipv4 1 192.168.0.0/22 Connected summary 28160/-
S ipv4 1 192.168.1.0/24 Connected em6 28160/-
S ipv4 1 192.168.2.0/24 Connected em7 28160/-
S ipv6 1 5000::/64 fe80::c802:50ff:fe5d:0
em4 30720/28160
$ eigrpctl show fib eigrp
flags: * = valid, D = EIGRP, C = Connected, S = Static
Flags Prio Destination Nexthop
*D 28 10.0.1.0/24 10.0.3.2
*D 28 10.0.2.0/24 10.0.3.2
*D 28 10.0.4.0/24 10.0.3.2
*D 28 10.0.5.0/24 10.0.3.2
*D 28 10.0.6.0/24 10.0.3.2
*D 28 10.0.7.0/24 10.0.3.2
*D EX 52 10.0.8.0/24 10.0.3.2
*D 12 192.168.0.0/22 127.0.0.1
*D 28 5000::/64 fe80::c802:50ff:fe5d:0%em4
*D EX 52 6000::/64 fe80::c802:50ff:fe5d:0%em4
We can see above that now all routes point to the R2 neighbor, the only neighbor still alive.
