Re: EIGRP not accepting route in network command

theviking693 · ‎07-18-2018

Hi All,

I've recently implemented EIGRP between 2 switches, which works fine - Networks being advertised.

Although I've created a new SVI which is covered in the network command, but this hasn't propagated into EIGRP (10.66.88.1 /24)

This is the EIGRP config:

LON-VSS-CORE#sh run | s router eigrp
router eigrp 10
network 10.10.0.0 0.0.255.255
network 10.20.0.0 0.0.255.255
network 10.21.0.0 0.0.255.255
network 10.27.0.0 0.0.255.255
network 10.42.0.0 0.0.255.255
network 10.46.0.0 0.0.255.255
network 10.47.0.0 0.0.255.255
network 10.66.0.0 0.0.255.255
network 10.99.0.0 0.0.255.255
network 10.100.66.0 0.0.0.255
network 10.100.70.0 0.0.0.255
network 10.151.0.0 0.0.255.255
network 10.152.0.0 0.0.255.255
network 10.153.0.0 0.0.255.255
network 10.160.0.0 0.0.255.255
no auto-summary
passive-interface default
no passive-interface Vlan166
no passive-interface Vlan170

This is the SVI:

LON-VSS-CORE#sh ip int br | i 10.66.88
Vlan888 10.66.88.1 YES manual up up

However this never makes it to the EIGRP topology table

LON-VSS-CORE#sh ip eigrp topology 10.66.88.0/24
% EIGRP-IPv4 (AS 10): Route not in topology table TID(0)

I've ran a debug ip eigrp but didn't receive any messages. Does this require a reset of the neighbors?

Any ideas?

Many Thanks!

Chris

Georg Pauwen · ‎07-18-2018

Hello,

what does your topology look like (VSS in your switch hostname suggests you have VSS configured), and what switch models do you have ?

theviking693 · ‎07-18-2018

Hi Georg,

Thanks for your response -

Yeah this switch uses VSS between 2 6506's

It has 2 EIGRP neighbor's: One on VLAN 166 (Cisco Router) and another on VLAN 170 (Cisco 4500)

This network 10.66.88.0/24 is on LON-VSS-CORE itself - It just doesn't get injected into EIGRP - Not even on its own topology table.

Georg Pauwen · ‎07-18-2018

Odd indeed. Can you post the full output of the routing and the topology table ?

theviking693 · ‎07-18-2018

of course!

ROUTING

Gateway of last resort is 10.100.66.1 to network 0.0.0.0

100.0.0.0/32 is subnetted, 1 subnets
D EX 100.10.10.10 [170/2586112] via 10.100.66.1, 3w1d, Vlan166
172.16.0.0/27 is subnetted, 1 subnets
D 172.16.10.0 [90/3072] via 10.100.70.1, 4w4d, Vlan170
172.28.0.0/16 is variably subnetted, 7 subnets, 2 masks
D EX 172.28.4.0/24 [170/281856] via 10.100.66.1, 4w4d, Vlan166
S 172.28.0.0/16 [1/0] via 10.100.66.1
D EX 172.28.2.0/24 [170/281856] via 10.100.66.1, 3w1d, Vlan166
D EX 172.28.124.0/24 [170/281856] via 10.100.66.1, 4w4d, Vlan166
D EX 172.28.1.0/24 [170/281856] via 10.100.66.1, 4w4d, Vlan166
D EX 172.28.208.0/24 [170/281856] via 10.100.66.1, 4w4d, Vlan166
D EX 172.28.3.0/24 [170/281856] via 10.100.66.1, 3w1d, Vlan166
93.0.0.0/32 is subnetted, 2 subnets
D EX 93.187.16.226 [170/281856] via 10.100.66.1, 3w5d, Vlan166
D EX 93.187.16.240 [170/281856] via 10.100.66.1, 3w5d, Vlan166
10.0.0.0/8 is variably subnetted, 86 subnets, 6 masks
C 10.66.46.0/23 is directly connected, Vlan644
C 10.160.0.0/16 is directly connected, Vlan160
S 10.165.0.0/16 [1/0] via 10.100.66.1
C 10.66.44.0/23 is directly connected, Vlan643
C 10.66.12.0/24 is directly connected, Vlan612
D EX 10.128.0.0/16 [170/2586112] via 10.100.66.1, 1w5d, Vlan166
D EX 10.129.0.0/16 [170/2586112] via 10.100.66.1, 1w5d, Vlan166
D EX 10.131.0.0/16 [170/2586112] via 10.100.66.1, 3w1d, Vlan166
C 10.153.0.0/16 is directly connected, Vlan153
C 10.66.61.0/24 is directly connected, Vlan661
D EX 10.110.127.0/24 [170/2586112] via 10.100.66.1, 1w5d, Vlan166
C 10.151.0.0/16 is directly connected, Vlan151
D EX 10.65.202.0/24 [170/281856] via 10.100.66.1, 4w4d, Vlan166
D 10.65.10.0/24 [90/3072] via 10.100.66.1, 4w4d, Vlan166
C 10.66.42.0/23 is directly connected, Vlan642
S 10.204.0.0/16 [1/0] via 10.66.11.101
S 10.201.0.0/16 [1/0] via 10.66.11.101
D 10.65.40.0/24 [90/3072] via 10.100.66.1, 4w4d, Vlan166
C 10.66.40.0/23 is directly connected, Vlan641
D EX 10.240.115.0/24 [170/281856] via 10.100.66.1, 3w1d, Vlan166
D EX 10.208.0.0/16 [170/281856] via 10.100.66.1, 10:20:52, Vlan166
D EX 10.211.0.0/16 [170/2586112] via 10.100.66.1, 1w0d, Vlan166
D 10.100.68.0/24 [90/3072] via 10.100.66.1, 4w4d, Vlan166
C 10.66.38.0/23 is directly connected, Vlan635
C 10.42.0.0/16 is directly connected, Vlan3
C 10.46.0.0/16 is directly connected, Vlan46
C 10.47.0.0/16 is directly connected, Vlan47
D EX 10.51.0.0/16 [170/2586112] via 10.100.66.1, 3w1d, Vlan166
D EX 10.14.140.242/32 [170/2586112] via 10.100.66.1, 3w1d, Vlan166
D 10.65.151.0/24 [90/3072] via 10.100.66.1, 4w4d, Vlan166
D EX 10.14.140.250/32 [170/2586112] via 10.100.66.1, 3w1d, Vlan166
C 10.100.70.0/24 is directly connected, Vlan170
D EX 10.5.0.0/16 [170/2586112] via 10.100.66.1, 3w1d, Vlan166
C 10.66.36.0/23 is directly connected, Vlan634
D EX 10.7.0.0/16 [170/2586112] via 10.100.66.1, 3w1d, Vlan166
D EX 10.8.0.0/16 [170/2586112] via 10.100.66.1, 3w1d, Vlan166
D EX 10.9.0.0/16 [170/2586112] via 10.100.66.1, 3w1d, Vlan166
C 10.10.0.0/16 is directly connected, Vlan10
D EX 10.11.0.0/16 [170/2586112] via 10.100.66.1, 3w1d, Vlan166
D EX 10.13.0.0/16 [170/2586112] via 10.100.66.1, 5d02h, Vlan166
D EX 10.14.0.0/16 [170/2586112] via 10.100.66.1, 1w1d, Vlan166
D EX 10.15.0.0/16 [170/2586112] via 10.100.66.1, 3w1d, Vlan166
D EX 10.16.0.0/16 [170/2586112] via 10.100.66.1, 3w1d, Vlan166
D EX 10.18.0.0/16 [170/281856] via 10.100.66.1, 4w2d, Vlan166
C 10.21.0.0/16 is directly connected, Vlan2
C 10.20.0.0/16 is directly connected, Vlan1
C 10.27.0.0/16 is directly connected, Vlan202
C 10.99.0.0/16 is directly connected, Vlan999
D 10.65.2.0/28 [90/3072] via 10.100.66.1, 4w4d, Vlan166
C 10.66.34.0/23 is directly connected, Vlan633
D EX 10.126.0.0/16 [170/2586112] via 10.100.66.1, 3w1d, Vlan166
D EX 10.124.0.0/16 [170/2586112] via 10.100.66.1, 1d01h, Vlan166
D EX 10.122.0.0/16 [170/2586112] via 10.100.66.1, 3w1d, Vlan166
D EX 10.121.0.0/16 [170/2586112] via 10.100.66.1, 3w1d, Vlan166
D EX 10.68.0.0/16 [170/281856] via 10.100.66.1, 4w4d, Vlan166
D EX 10.69.0.0/16 [170/281856] via 10.100.66.1, 4w4d, Vlan166
C 10.100.66.0/24 is directly connected, Vlan166
D 10.65.0.0/24 [90/130816] via 10.100.66.1, 4w4d, Vlan166
S 10.65.0.0/16 [1/0] via 10.100.66.1
C 10.66.32.0/23 is directly connected, Vlan632
S 10.67.0.0/16 [1/0] via 10.100.66.1
C 10.66.0.1/32 is directly connected, Loopback0
C 10.152.12.0/24 is directly connected, Vlan152
C 10.66.30.0/23 is directly connected, Vlan631
C 10.66.252.0/22 is directly connected, Vlan252
C 10.66.60.0/24 is directly connected, Vlan660
D 10.65.13.0/24 [90/3072] via 10.100.66.1, 4w4d, Vlan166
C 10.66.13.0/24 is directly connected, Vlan613
D 10.65.90.0/24 [90/130816] via 10.100.66.1, 4w4d, Vlan166
D 10.100.169.0/24 [90/3072] via 10.100.66.1, 4w4d, Vlan166
D 10.65.11.0/24 [90/3072] via 10.100.66.1, 4w4d, Vlan166
C 10.66.11.0/24 is directly connected, Vlan611
D EX 10.165.197.0/28 [170/281856] via 10.100.66.1, 3w2d, Vlan166
C 10.66.88.0/24 is directly connected, Vlan888
D EX 10.240.163.0/24 [170/281856] via 10.100.66.1, 3w1d, Vlan166
D EX 10.208.208.0/22 [170/281856] via 10.100.66.1, 4w4d, Vlan166
D EX 10.65.11.42/32 [170/281856] via 10.100.66.1, 4w4d, Vlan166
D EX 10.121.197.0/28 [170/2586112] via 10.100.66.1, 3w1d, Vlan166
D 10.100.165.0/24 [90/3072] via 10.100.66.1, 4w4d, Vlan166
D 10.65.20.0/24 [90/3072] via 10.100.66.1, 4w4d, Vlan166
C 10.66.20.0/24 is directly connected, Vlan20
C 10.66.50.0/24 is directly connected, Vlan650
D EX 10.124.208.0/22 [170/281856] via 10.100.66.1, 4w4d, Vlan166
D EX 10.65.208.0/22 [170/281856] via 10.100.66.1, 4w4d, Vlan166
C 10.66.48.0/23 is directly connected, Vlan645
S 10.100.67.0/24 [1/0] via 10.100.66.1
S 192.168.67.0/24 [1/0] via 10.100.66.1
12.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
D EX 12.76.0.215/32 [170/281856] via 10.100.66.1, 2w0d, Vlan166
D EX 12.76.0.0/24 [170/281856] via 10.100.66.1, 2w0d, Vlan166
D*EX 0.0.0.0/0 [170/281856] via 10.100.66.1, 3w1d, Vlan166

EIGRP TOPOLOGY

LON-VSS-CORE#sh ip eigrp topology
EIGRP-IPv4 Topology Table for AS(10)/ID(10.66.0.1)

Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
r - reply Status, s - sia Status

P 0.0.0.0/0, 1 successors, FD is 281856
via 10.100.66.1 (281856/281600), Vlan166
P 10.10.0.0/16, 1 successors, FD is 2816
via Connected, Vlan10
P 10.11.0.0/16, 1 successors, FD is 2586112, tag is 13879
via 10.100.66.1 (2586112/2585856), Vlan166
P 10.8.0.0/16, 1 successors, FD is 2586112, tag is 13879
via 10.100.66.1 (2586112/2585856), Vlan166
P 10.9.0.0/16, 1 successors, FD is 2586112, tag is 13879
via 10.100.66.1 (2586112/2585856), Vlan166
P 10.14.0.0/16, 1 successors, FD is 2586112, tag is 13879
via 10.100.66.1 (2586112/2585856), Vlan166
P 10.15.0.0/16, 1 successors, FD is 2586112, tag is 13879
via 10.100.66.1 (2586112/2585856), Vlan166
P 93.187.16.240/32, 1 successors, FD is 281856
via 10.100.66.1 (281856/281600), Vlan166
P 10.13.0.0/16, 1 successors, FD is 2586112, tag is 13879
via 10.100.66.1 (2586112/2585856), Vlan166
P 10.208.208.0/22, 1 successors, FD is 281856
via 10.100.66.1 (281856/281600), Vlan166
P 10.7.0.0/16, 1 successors, FD is 2586112, tag is 13879
via 10.100.66.1 (2586112/2585856), Vlan166
P 10.5.0.0/16, 1 successors, FD is 2586112, tag is 13879
via 10.100.66.1 (2586112/2585856), Vlan166
P 10.65.90.0/24, 1 successors, FD is 130816
via 10.100.66.1 (130816/128256), Vlan166
P 10.27.0.0/16, 1 successors, FD is 2816
via Connected, Vlan202
P 93.187.16.226/32, 1 successors, FD is 281856
via 10.100.66.1 (281856/281600), Vlan166
P 10.18.0.0/16, 1 successors, FD is 281856
via 10.100.66.1 (281856/281600), Vlan166
P 10.16.0.0/16, 1 successors, FD is 2586112, tag is 13879
via 10.100.66.1 (2586112/2585856), Vlan166
P 10.110.127.0/24, 1 successors, FD is 2586112, tag is 13879
via 10.100.66.1 (2586112/2585856), Vlan166
P 10.20.0.0/16, 1 successors, FD is 2816
via Connected, Vlan1
P 10.21.0.0/16, 1 successors, FD is 2816
via Connected, Vlan2
P 10.42.0.0/16, 1 successors, FD is 2816
via Connected, Vlan3
P 10.46.0.0/16, 1 successors, FD is 2816
via Connected, Vlan46
P 10.47.0.0/16, 1 successors, FD is 2816
via Connected, Vlan47
P 10.100.70.0/24, 1 successors, FD is 2816
via Connected, Vlan170
P 10.100.68.0/24, 1 successors, FD is 3072
via 10.100.66.1 (3072/2816), Vlan166
P 10.100.66.0/24, 1 successors, FD is 2816
via Connected, Vlan166
P 10.100.67.0/24, 0 successors, FD is Inaccessible
via 10.100.66.1 (3072/2816), Vlan166
P 10.51.0.0/16, 1 successors, FD is 2586112, tag is 13879
via 10.100.66.1 (2586112/2585856), Vlan166
P 12.76.0.0/24, 1 successors, FD is 281856
via 10.100.66.1 (281856/281600), Vlan166
P 10.65.11.0/24, 1 successors, FD is 3072
via 10.100.66.1 (3072/2816), Vlan166
P 10.65.10.0/24, 1 successors, FD is 3072
via 10.100.66.1 (3072/2816), Vlan166
P 10.66.11.0/24, 1 successors, FD is 2816
via Connected, Vlan611
P 10.66.12.0/24, 1 successors, FD is 2816
via Connected, Vlan612
P 10.66.13.0/24, 1 successors, FD is 2816
via Connected, Vlan613
P 10.65.13.0/24, 1 successors, FD is 3072
via 10.100.66.1 (3072/2816), Vlan166
P 10.67.0.0/16, 0 successors, FD is Inaccessible
via 10.100.66.1 (281856/281600), Vlan166
P 10.65.2.0/28, 1 successors, FD is 3072
via 10.100.66.1 (3072/2816), Vlan166
P 10.66.0.1/32, 1 successors, FD is 128256
via Connected, Loopback0
P 10.65.0.0/16, 0 successors, FD is Inaccessible
via 10.100.66.1 (281856/281600), Vlan166
P 10.65.0.0/24, 1 successors, FD is 130816
via 10.100.66.1 (130816/128256), Vlan166
P 10.68.0.0/16, 1 successors, FD is 281856
via 10.100.66.1 (281856/281600), Vlan166
P 10.69.0.0/16, 1 successors, FD is 281856
via 10.100.66.1 (281856/281600), Vlan166
P 10.66.30.0/23, 1 successors, FD is 2816
via Connected, Vlan631
P 10.240.163.0/24, 1 successors, FD is 281856
via 10.100.66.1 (281856/281600), Vlan166
P 10.66.20.0/24, 1 successors, FD is 2816
via Connected, Vlan20
P 10.65.20.0/24, 1 successors, FD is 3072
via 10.100.66.1 (3072/2816), Vlan166
P 172.28.208.0/24, 1 successors, FD is 281856
via 10.100.66.1 (281856/281600), Vlan166
P 10.66.40.0/23, 1 successors, FD is 2816
via Connected, Vlan641
P 10.66.42.0/23, 1 successors, FD is 2816
via Connected, Vlan642
P 10.65.40.0/24, 1 successors, FD is 3072
via 10.100.66.1 (3072/2816), Vlan166
P 10.66.44.0/23, 1 successors, FD is 2816
via Connected, Vlan643
P 10.66.46.0/23, 1 successors, FD is 2816
via Connected, Vlan644
P 10.66.32.0/23, 1 successors, FD is 2816
via Connected, Vlan632
P 10.99.0.0/16, 1 successors, FD is 2816
via Connected, Vlan999
P 10.65.11.42/32, 1 successors, FD is 281856
via 10.100.66.1 (281856/281600), Vlan166
P 10.165.197.0/28, 1 successors, FD is 281856
via 10.100.66.1 (281856/281600), Vlan166
P 10.66.34.0/23, 1 successors, FD is 2816
via Connected, Vlan633
P 10.66.36.0/23, 1 successors, FD is 2816
via Connected, Vlan634
P 100.10.10.10/32, 1 successors, FD is 2586112, tag is 13879
via 10.100.66.1 (2586112/2585856), Vlan166
P 10.66.38.0/23, 1 successors, FD is 2816
via Connected, Vlan635
P 10.122.0.0/16, 1 successors, FD is 2586112, tag is 13879
via 10.100.66.1 (2586112/2585856), Vlan166
P 10.14.140.250/32, 1 successors, FD is 2586112, tag is 13879
via 10.100.66.1 (2586112/2585856), Vlan166
P 10.121.0.0/16, 1 successors, FD is 2586112, tag is 13879
via 10.100.66.1 (2586112/2585856), Vlan166
P 10.126.0.0/16, 1 successors, FD is 2586112, tag is 13879
via 10.100.66.1 (2586112/2585856), Vlan166
P 10.66.60.0/24, 1 successors, FD is 2816
via Connected, Vlan660
P 10.66.61.0/24, 1 successors, FD is 2816
via Connected, Vlan661
P 10.124.0.0/16, 1 successors, FD is 2586112, tag is 13879
via 10.100.66.1 (2586112/2585856), Vlan166
P 10.66.48.0/23, 1 successors, FD is 2816
via Connected, Vlan645
P 10.14.140.242/32, 1 successors, FD is 2586112, tag is 13879
via 10.100.66.1 (2586112/2585856), Vlan166
P 10.66.50.0/24, 1 successors, FD is 2816
via Connected, Vlan650
P 10.65.202.0/24, 1 successors, FD is 281856
via 10.100.66.1 (281856/281600), Vlan166
P 10.240.115.0/24, 1 successors, FD is 281856
via 10.100.66.1 (281856/281600), Vlan166
P 10.131.0.0/16, 1 successors, FD is 2586112, tag is 13879
via 10.100.66.1 (2586112/2585856), Vlan166
P 10.128.0.0/16, 1 successors, FD is 2586112, tag is 13879
via 10.100.66.1 (2586112/2585856), Vlan166
P 10.129.0.0/16, 1 successors, FD is 2586112, tag is 13879
via 10.100.66.1 (2586112/2585856), Vlan166
P 10.153.0.0/16, 1 successors, FD is 2816
via Connected, Vlan153
P 12.76.0.215/32, 1 successors, FD is 281856
via 10.100.66.1 (281856/281600), Vlan166
P 10.65.208.0/22, 1 successors, FD is 281856
via 10.100.66.1 (281856/281600), Vlan166
P 10.151.0.0/16, 1 successors, FD is 2816
via Connected, Vlan151
P 10.152.12.0/24, 1 successors, FD is 2816
via Connected, Vlan152
P 10.124.208.0/22, 1 successors, FD is 281856
via 10.100.66.1 (281856/281600), Vlan166
P 10.160.0.0/16, 1 successors, FD is 2816
via Connected, Vlan160
P 10.165.0.0/16, 0 successors, FD is Inaccessible, tag is 13879
via 10.100.70.1 (256025856/256025600), Vlan170
via 10.100.66.1 (281856/281600), Vlan166
P 172.28.1.0/24, 1 successors, FD is 281856
via 10.100.66.1 (281856/281600), Vlan166
P 172.28.2.0/24, 1 successors, FD is 281856
via 10.100.66.1 (281856/281600), Vlan166
P 172.28.3.0/24, 1 successors, FD is 281856
via 10.100.66.1 (281856/281600), Vlan166
P 172.28.4.0/24, 1 successors, FD is 281856
via 10.100.66.1 (281856/281600), Vlan166
P 10.66.252.0/22, 1 successors, FD is 2816
via Connected, Vlan252
P 172.16.10.0/27, 1 successors, FD is 3072
via 10.100.70.1 (3072/2816), Vlan170
P 10.121.197.0/28, 1 successors, FD is 2586112, tag is 13879
via 10.100.66.1 (2586112/2585856), Vlan166
P 10.100.169.0/24, 1 successors, FD is 3072
via 10.100.66.1 (3072/2816), Vlan166
P 10.100.165.0/24, 1 successors, FD is 3072
via 10.100.66.1 (3072/2816), Vlan166
P 172.28.124.0/24, 1 successors, FD is 281856
via 10.100.66.1 (281856/281600), Vlan166
P 10.211.0.0/16, 1 successors, FD is 2586112, tag is 13879
via 10.100.66.1 (2586112/2585856), Vlan166
P 10.208.0.0/16, 1 successors, FD is 281856
via 10.100.66.1 (281856/281600), Vlan166
P 10.65.151.0/24, 1 successors, FD is 3072
via 10.100.66.1 (3072/2816), Vlan166

Georg Pauwen · ‎07-18-2018

Hello,

what if you announce:

network 10.66.88.0 0.0.0.255

theviking693 · ‎07-18-2018

That looks to have worked thanks.....Although not sure why the original network command didn't cover it....

You come across this before?

Cheers,

Chris

Richard Burts · ‎07-18-2018

Chris

That is quite odd. I see that other 10.66.x.0 subnets are in the table. So the network statement seems to be working. I wonder if you remove the network statement for the /24 if the route would still be in the topology table or would be missing. I also wonder with the original network statement if a shut and no shut of the vlan interface might have gotten the entry into the table.

HTH

Rick

HTH

Rick

paul driver · ‎07-18-2018

Hello

The best way to avoid any confusion when adverting networks in eigrp is be as specific as possible.

Here you have advertised a summary prefix of /16 in the eigrp process for a network that is a /24 , I would suggest even go further and just advertise the host address of the svi and eigrp will apply the correct network from the svi interface its applied to.

Issues can arise when you have the likes of summary routes being advertised, filtering applied, or just auto-summerisation enabled in the routing stanza.

res

Paul

res

Paul

res

Paul

Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

Georg Pauwen · ‎07-18-2018

Actually, it should work as you originally designed it. The 6506 is end of sale/end of life for quite a few years, so it could just be an outdated or buggy IOS...

theviking693 · ‎07-26-2018

Thanks all for your input - Yeah looks like a quirk with the IOS maybe. Removing the network statement 10.66.88.0 0.0.0.255 hasn't removed it from the EIGRP topology.

Richard Burts · ‎07-28-2018

It is good to know that removing the network statement for the /24 and leaving the original network statement results in the network remaining in the topology table. I guess that we will never know what the original quirk was. Glad to know that it is working correctly now.

HTH

Rick

HTH

Rick