Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

EIGRP ip problem - help!!!!!!!!!!!!!

Anybody ever seen this problem?

I have eigrp running on a cisco router with a default route configured out to my firewall. This router has stopped propogating the default route out to my remote sites over the WAN( Frame Relay). The eigrp neighbor relationship is established and I get all routes on the 10.0.0.0 network but not the 0.0.0.0 route. There are no access-lists/distribute lists applied to eigrp which would stop this from being passed out.

any ideas?

13 REPLIES
Silver

Re: EIGRP ip problem - help!!!!!!!!!!!!!

can you paste in a sh ip route

and a sh ip eigrp top 0.0.0.0 from the branch side

New Member

Re: EIGRP ip problem - help!!!!!!!!!!!!!

Newbridge#i sh ip ro

Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2

E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area

* - candidate default, U - per-user static route, o - ODR

P - periodic downloaded static route

Gateway of last resort is not set

172.16.0.0/24 is subnetted, 1 subnets

D EX 172.16.2.0 [170/10563072] via 10.66.31.1, 01:33:47, Serial0/0

172.30.0.0/24 is subnetted, 1 subnets

D EX 172.30.1.0 [170/43072000] via 10.66.31.1, 01:33:47, Serial0/0

10.0.0.0/8 is variably subnetted, 308 subnets, 3 masks

D 10.1.10.0/24 [90/12585472] via 10.66.31.1, 01:33:46, Serial0/0

D EX 10.8.0.0/16 [170/12073472] via 10.66.31.1, 01:33:46, Serial0/0

D 10.1.3.0/24 [90/12073472] via 10.66.31.1, 01:33:46, Serial0/0

D 10.2.0.0/16 [90/11564032] via 10.66.31.1, 01:33:47, Serial0/0

D 10.3.0.0/16 [90/12076032] via 10.66.31.1, 01:33:46, Serial0/0

D 10.1.2.0/24 [90/12073472] via 10.66.31.1, 01:33:46, Serial0/0

D EX 10.6.0.0/16 [170/11564032] via 10.66.31.1, 01:33:47, Serial0/0

D 10.202.6.0/24 [90/28714496] via 10.66.31.1, 01:33:53, Serial0/0

D 10.198.10.0/24 [90/11561472] via 10.66.31.1, 01:33:53, Serial0/0

D 10.199.10.0/24 [90/161561600] via 10.66.31.1, 01:33:53, Serial0/0

D 10.254.1.50/32 [90/41177600] via 10.66.31.1, 01:33:53, Serial0/0

D 10.198.11.0/24 [90/21536000] via 10.66.31.1, 01:33:33, Serial0/0

D 10.203.6.0/24 [90/42560000] via 10.66.31.1, 01:33:53, Serial0/0

D 10.254.1.61/32 [90/42201600] via 10.66.31.1, 01:33:53, Serial0/0

D 10.197.7.0/24 [90/11561472] via 10.66.31.1, 01:33:53, Serial0/0

D 10.203.9.0/24 [90/42560000] via 10.66.31.1, 01:33:53, Serial0/0

D 10.254.1.60/32 [90/21689600] via 10.66.31.1, 01:33:45, Serial0/0

D 10.197.6.0/24 [90/14894848] via 10.66.31.1, 01:33:55, Serial0/0

D 10.203.8.0/24 [90/47787776] via 10.66.31.1, 01:33:55, Serial0/0

D 10.202.9.0/24 [90/28714496] via 10.66.31.1, 01:33:55, Serial0/0

D 10.254.1.63/32 [90/21664000] via 10.66.31.1, 01:33:55, Serial0/0

D 10.199.7.0/24 [90/42048000] via 10.66.31.1, 01:33:55, Serial0/0

--More-- D 10.201.9.0/24 [90/28740096] via 10.66.31.1, 01:33:55, Serial0/0

D 10.198.6.0/24 [90/14869248] via 10.66.31.1, 01:33:55, Serial0/0

D EX 10.197.5.0/24 [170/11075072] via 10.66.31.1, 01:33:55, Serial0/0

D 10.254.1.62/32 [90/21152000] via 10.66.31.1, 01:33:55, Serial0/0

D 10.199.6.0/24 [90/42048000] via 10.66.31.1, 01:33:55, Serial0/0

D 10.198.7.0/24 [90/11535872] via 10.66.31.1, 01:33:55, Serial0/0

D 10.254.1.33/32 [90/41152000] via 10.66.31.1, 01:30:05, Serial0/0

D 10.254.1.35/32 [90/21664000] via 10.66.31.1, 01:32:47, Serial0/0

D 10.254.10.40/32 [90/11689472] via 10.66.31.1, 01:33:57, Serial0/0

D 10.254.1.34/32 [90/12175872] via 10.66.31.1, 01:33:57, Serial0/0

D 10.254.1.45/32 [90/41177600] via 10.66.31.1, 01:33:56, Serial0/0

--More-- D 10.254.1.44/32 [90/41152000] via 10.66.31.1, 01:32:43, Serial0/0

D 10.254.1.47/32 [90/54997248] via 10.66.31.1, 01:33:56, Serial0/0

D 10.208.0.0/16 [90/11587072] via 10.66.31.1, 01:33:57, Serial0/0

D 10.254.1.46/32 [90/41152000] via 10.66.31.1, 01:33:50, Serial0/0

D 10.199.17.0/24 [90/47275776] via 10.66.31.1, 01:24:06, Serial0/0

D 10.254.1.41/32 [90/21664000] via 10.66.31.1, 01:33:35, Serial0/0

D 10.197.19.0/24 [90/28228096] via 10.66.31.1, 01:33:56, Serial0/0

D 10.254.1.40/32 [90/11177472] via 10.66.31.1, 01:33:39, Serial0/0

D 10.197.18.0/24 [90/28740096] via 10.66.31.1, 01:33:56, Serial0/0

D 10.198.17.0/24 [90/54869248] via 10.66.31.1, 01:33:57, Serial0/0

D 10.197.17.0/24 [90/54894848] via 10.66.31.1, 01:33:56, Serial0/0

D 10.198.18.0/24 [90/28714496] via 10.66.31.1, 01:33:56, Serial0/0

D 10.254.10.32/32 [90/11177472] via 10.66.31.1, 01:33:57, Serial0/0

D 10.254.1.42/32 [90/22176000] via 10.66.31.1, 01:33:57, Serial0/0

D 10.198.19.0/24 [90/28202496] via 10.66.31.1, 01:33:57, Serial0/0

D 10.254.1.21/32 [90/11177472] via 10.66.31.1, 01:33:56, Serial0/0

D 10.254.10.30/32 [90/28330496] via 10.66.31.1, 01:33:57, Serial0/0

D EX 10.234.1.0/24 [170/47275776] via 10.66.31.1, 01:24:08, Serial0/0

D 10.254.1.20/32 [90/11689472] via 10.66.31.1, 01:33:36, Serial0/0

D 10.208.5.61/32 [90/47813376] via 10.66.31.1, 01:24:08, Serial0/0

D 10.254.1.23/32 [90/21177600] via 10.66.31.1, 01:33:57, Serial0/0

D 10.254.10.28/32 [90/28842496] via 10.66.31.1, 01:33:58, Serial0/0

D 10.254.1.17/32 [90/22176000] via 10.66.31.1, 01:33:47, Serial0/0

--More-- D 10.254.10.26/32 [90/28330496] via 10.66.31.1, 01:33:58, Serial0/0

D 10.254.1.16/32 [90/21664000] via 10.66.31.1, 01:33:47, Serial0/0

D 10.254.10.27/32 [90/28356096] via 10.66.31.1, 01:33:58, Serial0/0

D 10.254.1.19/32 [90/41664000] via 10.66.31.1, 01:32:44, Serial0/0

D 10.254.1.18/32 [90/41152000] via 10.66.31.1, 01:32:44, Serial0/0

D 10.254.10.25/32 [90/11663872] via 10.66.31.1, 01:33:58, Serial0/0

D 10.208.5.55/32 [90/162099200] via 10.66.31.1, 00:29:09, Serial0/0

D 10.254.1.29/32 [90/41177600] via 10.66.31.1, 01:33:57, Serial0/0

D 10.254.1.28/32 [90/42176000] via 10.66.31.1, 01:33:47, Serial0/0

D 10.254.10.23/32 [90/54997248] via 10.66.31.1, 01:33:58, Serial0/0

D 10.254.1.31/32 [90/12175872] via 10.66.31.1, 01:33:58, Serial0/0

D 10.254.10.20/32 [90/11177472] via 10.66.31.1, 01:33:58, Serial0/0

D 10.254.1.30/32 [90/27844096] via 10.66.31.1, 01:33:57, Serial0/0

D 10.254.1.25/32 [90/11663872] via 10.66.31.1, 01:33:41, Serial0/0

D 10.254.10.18/32 [90/11151872] via 10.66.31.1, 01:33:58, Serial0/0

D 10.254.1.24/32 [90/41152000] via 10.66.31.1, 01:32:45, Serial0/0

D 10.254.10.19/32 [90/11177472] via 10.66.31.1, 01:33:59, Serial0/0

D 10.254.1.27/32 [90/11177472] via 10.66.31.1, 00:19:50, Serial0/0

D 10.254.10.16/32 [90/11715072] via 10.66.31.1, 01:33:59, Serial0/0

D 10.254.1.26/32 [90/41177600] via 10.66.31.1, 01:33:59, Serial0/0

D 10.254.1.5/32 [90/11663872] via 10.66.31.1, 01:33:42, Serial0/0

D 10.254.10.14/32 [90/11715072] via 10.66.31.1, 01:33:59, Serial0/0

D 10.254.10.15/32 [90/11689472] via 10.66.31.1, 01:33:59, Serial0/0

--More-- D 10.254.10.12/32 [90/14997248] via 10.66.31.1, 01:33:59, Serial0/0

D 10.254.1.7/32 [90/11663872] via 10.66.31.1, 01:33:59, Serial0/0

D 10.254.1.1/32 [90/11689472] via 10.66.31.1, 01:33:38, Serial0/0

D 10.254.10.10/32 [90/11663872] via 10.66.31.1, 01:33:59, Serial0/0

D 10.254.10.11/32 [90/14997248] via 10.66.31.1, 01:33:59, Serial0/0

D 10.254.10.8/32 [90/28330496] via 10.66.31.1, 01:33:59, Serial0/0

D 10.254.1.3/32 [90/10639872] via 10.66.31.1, 01:34:00, Serial0/0

C 10.254.1.9/32 is directly connected, Loopback0

D 10.254.1.8/32 [90/41152000] via 10.66.31.1, 01:32:48, Serial0/0

D 10.254.1.11/32 [90/41152000] via 10.66.31.1, 01:34:01, Serial0/0

D 10.199.50.0/24 [90/41561600] via 10.66.31.1, 01:34:01, Serial0/0

--More-- D 10.254.1.10/32 [90/41177600] via 10.66.31.1, 01:34:01, Serial0/0

Newbridge# sh ip eigrp topology 0.0.0.0

% Route not in topology table

Newbridge#

Silver

Re: EIGRP ip problem - help!!!!!!!!!!!!!

If you go to the branch router and do a sh ip eigrp events you may be able to see what caused the 0.0.0.0 route to be flushed , It looks like a bug , what code are you running ?

New Member

Re: EIGRP ip problem - help!!!!!!!!!!!!!

Thanks, we are runnign 12.1(20) centrally and 12.1(18) at the branch end. I have tried the eigrp events but it doesn't mention 0.0.0.0. I have reset the neighbors and here is the eigrp events:-

Newbridge#sh ip eigrp events

Event information for AS 1:

1 22:27:50.833 Peer down end, handle: 0

2 22:27:50.833 NDB delete: 10.254.1.10/32 1

3 22:27:50.833 Poison squashed: 10.254.1.10/32 rt gone

4 22:27:50.833 RDB delete: 10.254.1.10/32 10.66.31.1

5 22:27:50.833 Not active net/1=SH: 10.254.1.10/32 0

6 22:27:50.833 FC not sat Dmin/met: 4294967295 41177600

7 22:27:50.833 Find FS: 10.254.1.10/32 41177600

8 22:27:50.833 NDB delete: 10.199.50.0/24 1

9 22:27:50.833 Poison squashed: 10.199.50.0/24 rt gone

10 22:27:50.833 RDB delete: 10.199.50.0/24 10.66.31.1

11 22:27:50.833 Not active net/1=SH: 10.199.50.0/24 0

12 22:27:50.833 FC not sat Dmin/met: 4294967295 41561600

13 22:27:50.833 Find FS: 10.199.50.0/24 41561600

14 22:27:50.833 NDB delete: 10.254.1.11/32 1

15 22:27:50.833 Poison squashed: 10.254.1.11/32 rt gone

16 22:27:50.833 RDB delete: 10.254.1.11/32 10.66.31.1

17 22:27:50.833 Not active net/1=SH: 10.254.1.11/32 0

18 22:27:50.833 FC not sat Dmin/met: 4294967295 41152000

19 22:27:50.833 Find FS: 10.254.1.11/32 41152000

20 22:27:50.833 NDB delete: 10.254.1.8/32 1

21 22:27:50.833 Poison squashed: 10.254.1.8/32 rt gone

22 22:27:50.833 RDB delete: 10.254.1.8/32 10.66.31.1

23 22:27:50.829 Not active net/1=SH: 10.254.1.8/32 0

24 22:27:50.829 FC not sat Dmin/met: 4294967295 41152000

25 22:27:50.829 Find FS: 10.254.1.8/32 41152000

26 22:27:50.829 NDB delete: 10.199.54.0/24 1

27 22:27:50.829 Poison squashed: 10.199.54.0/24 rt gone

28 22:27:50.829 RDB delete: 10.199.54.0/24 10.66.31.1

29 22:27:50.829 Not active net/1=SH: 10.199.54.0/24 0

30 22:27:50.829 FC not sat Dmin/met: 4294967295 47275776

31 22:27:50.829 Find FS: 10.199.54.0/24 47250176

32 22:27:50.829 NDB delete: 10.254.1.14/32 1

33 22:27:50.829 Poison squashed: 10.254.1.14/32 rt gone

34 22:27:50.829 RDB delete: 10.254.1.14/32 10.66.31.1

35 22:27:50.829 Not active net/1=SH: 10.254.1.14/32 0

36 22:27:50.829 FC not sat Dmin/met: 4294967295 21177600

37 22:27:50.829 Find FS: 10.254.1.14/32 21177600

38 22:27:50.829 NDB delete: 10.254.1.15/32 1

39 22:27:50.829 Poison squashed: 10.254.1.15/32 rt gone

40 22:27:50.829 RDB delete: 10.254.1.15/32 10.66.31.1

41 22:27:50.829 Not active net/1=SH: 10.254.1.15/32 0

42 22:27:50.829 FC not sat Dmin/met: 4294967295 28356096

43 22:27:50.829 Find FS: 10.254.1.15/32 28356096

44 22:27:50.829 NDB delete: 10.199.55.0/24 1

45 22:27:50.829 Poison squashed: 10.199.55.0/24 rt gone

46 22:27:50.829 RDB delete: 10.199.55.0/24 10.66.31.1

47 22:27:50.829 Not active net/1=SH: 10.199.55.0/24 0

48 22:27:50.829 FC not sat Dmin/met: 4294967295 47275776

49 22:27:50.829 Find FS: 10.199.55.0/24 47250176

50 22:27:50.829 NDB delete: 10.254.1.12/32 1

51 22:27:50.829 Poison squashed: 10.254.1.12/32 rt gone

52 22:27:50.829 RDB delete: 10.254.1.12/32 10.66.31.1

53 22:27:50.829 Not active net/1=SH: 10.254.1.12/32 0

54 22:27:50.829 FC not sat Dmin/met: 4294967295 41689600

55 22:27:50.829 Find FS: 10.254.1.12/32 41689600

56 22:27:50.829 NDB delete: 10.254.10.7/32 1

57 22:27:50.829 Poison squashed: 10.254.10.7/32 rt gone

58 22:27:50.829 RDB delete: 10.254.10.7/32 10.66.31.1

59 22:27:50.829 Not active net/1=SH: 10.254.10.7/32 0

60 22:27:50.829 FC not sat Dmin/met: 4294967295 28842496

61 22:27:50.829 Find FS: 10.254.10.7/32 28842496

62 22:27:50.829 NDB delete: 10.254.1.13/32 1

63 22:27:50.829 Poison squashed: 10.254.1.13/32 rt gone

64 22:27:50.829 RDB delete: 10.254.1.13/32 10.66.31.1

65 22:27:50.829 Not active net/1=SH: 10.254.1.13/32 0

66 22:27:50.829 FC not sat Dmin/met: 4294967295 12175872

67 22:27:50.829 Find FS: 10.254.1.13/32 12175872

68 22:27:50.825 NDB delete: 10.254.10.6/32 1

69 22:27:50.825 Poison squashed: 10.254.10.6/32 rt gone

70 22:27:50.825 RDB delete: 10.254.10.6/32 10.66.31.1

71 22:27:50.825 Not active net/1=SH: 10.254.10.6/32 0

72 22:27:50.825 FC not sat Dmin/met: 4294967295 28842496

73 22:27:50.825 Find FS: 10.254.10.6/32 28842496

74 22:27:50.825 NDB delete: 10.199.53.0/24 1

75 22:27:50.825 Poison squashed: 10.199.53.0/24 rt gone

76 22:27:50.825 RDB delete: 10.199.53.0/24 10.66.31.1

77 22:27:50.825 Not active net/1=SH: 10.199.53.0/24 0

78 22:27:50.825 FC not sat Dmin/met: 4294967295 47275776

79 22:27:50.825 Find FS: 10.199.53.0/24 47250176

80 22:27:50.825 NDB delete: 10.254.1.2/32 1

81 22:27:50.825 Poison squashed: 10.254.1.2/32 rt gone

82 22:27:50.825 RDB delete: 10.254.1.2/32 10.66.31.1

83 22:27:50.825 Not active net/1=SH: 10.254.1.2/32 0

84 22:27:50.825 FC not sat Dmin/met: 4294967295 10665472

85 22:27:50.825 Find FS: 10.254.1.2/32 10665472

86 22:27:50.825 NDB delete: 10.64.14.179/32 1

87 22:27:50.825 Poison squashed: 10.64.14.179/32 rt gone

88 22:27:50.825 RDB delete: 10.64.14.179/32 10.66.31.1

89 22:27:50.825 Not active net/1=SH: 10.64.14.179/32 0

90 22:27:50.825 FC not sat Dmin/met: 4294967295 46763776

91 22:27:50.825 Find FS: 10.64.14.179/32 46763776

92 22:27:50.825 NDB delete: 10.254.10.9/32 1

93 22:27:50.825 Poison squashed: 10.254.10.9/32 rt gone

94 22:27:50.825 RDB delete: 10.254.10.9/32 10.66.31.1

95 22:27:50.825 Not active net/1=SH: 10.254.10.9/32 0

96 22:27:50.825 FC not sat Dmin/met: 4294967295 21664000

97 22:27:50.825 Find FS: 10.254.10.9/32 21664000

98 22:27:50.825 NDB delete: 10.254.1.3/32 1

99 22:27:50.825 Poison squashed: 10.254.1.3/32 rt gone

100 22:27:50.825 RDB delete: 10.254.1.3/32 10.66.31.1

101 22:27:50.825 Not active net/1=SH: 10.254.1.3/32 0

102 22:27:50.825 FC not sat Dmin/met: 4294967295 10639872

103 22:27:50.825 Find FS: 10.254.1.3/32 10639872

104 22:27:50.825 NDB delete: 10.254.10.8/32 1

105 22:27:50.825 Poison squashed: 10.254.10.8/32 rt gone

106 22:27:50.825 RDB delete: 10.254.10.8/32 10.66.31.1

107 22:27:50.825 Not active net/1=SH: 10.254.10.8/32 0

108 22:27:50.825 FC not sat Dmin/met: 4294967295 28330496

109 22:27:50.825 Find FS: 10.254.10.8/32 28330496

110 22:27:50.825 NDB delete: 10.254.10.11/32 1

111 22:27:50.825 Poison squashed: 10.254.10.11/32 rt gone

112 22:27:50.825 RDB delete: 10.254.10.11/32 10.66.31.1

113 22:27:50.825 Not active net/1=SH: 10.254.10.11/32 0

114 22:27:50.825 FC not sat Dmin/met: 4294967295 14997248

115 22:27:50.825 Find FS: 10.254.10.11/32 14997248

116 22:27:50.821 NDB delete: 10.254.10.10/32 1

117 22:27:50.821 Poison squashed: 10.254.10.10/32 rt gone

118 22:27:50.821 RDB delete: 10.254.10.10/32 10.66.31.1

119 22:27:50.821 Not active net/1=SH: 10.254.10.10/32 0

120 22:27:50.821 FC not sat Dmin/met: 4294967295 11663872

121 22:27:50.821 Find FS: 10.254.10.10/32 11663872

122 22:27:50.821 NDB delete: 10.254.1.1/32 1

123 22:27:50.821 Poison squashed: 10.254.1.1/32 rt gone

124 22:27:50.821 RDB delete: 10.254.1.1/32 10.66.31.1

125 22:27:50.821 Not active net/1=SH: 10.254.1.1/32 0

126 22:27:50.821 FC not sat Dmin/met: 4294967295 11689472

127 22:27:50.821 Find FS: 10.254.1.1/32 11689472

128 22:27:50.821 NDB delete: 10.254.1.7/32 1

129 22:27:50.821 Poison squashed: 10.254.1.7/32 rt gone

130 22:27:50.821 RDB delete: 10.254.1.7/32 10.66.31.1

131 22:27:50.821 Not active net/1=SH: 10.254.1.7/32 0

132 22:27:50.821 FC not sat Dmin/met: 4294967295 11663872

133 22:27:50.821 Find FS: 10.254.1.7/32 11663872

134 22:27:50.821 NDB delete: 10.254.10.12/32 1

135 22:27:50.821 Poison squashed: 10.254.10.12/32 rt gone

136 22:27:50.821 RDB delete: 10.254.10.12/32 10.66.31.1

137 22:27:50.821 Not active net/1=SH: 10.254.10.12/32 0

138 22:27:50.821 FC not sat Dmin/met: 4294967295 14997248

139 22:27:50.821 Find FS: 10.254.10.12/32 14997248

140 22:27:50.821 NDB delete: 10.254.10.15/32 1

141 22:27:50.821 Poison squashed: 10.254.10.15/32 rt gone

142 22:27:50.821 RDB delete: 10.254.10.15/32 10.66.31.1

143 22:27:50.821 Not active net/1=SH: 10.254.10.15/32 0

144 22:27:50.821 FC not sat Dmin/met: 4294967295 11689472

145 22:27:50.821 Find FS: 10.254.10.15/32 11689472

146 22:27:50.821 NDB delete: 10.254.10.14/32 1

147 22:27:50.821 Poison squashed: 10.254.10.14/32 rt gone

148 22:27:50.821 RDB delete: 10.254.10.14/32 10.66.31.1

149 22:27:50.821 Not active net/1=SH: 10.254.10.14/32 0

150 22:27:50.821 FC not sat Dmin/met: 4294967295 11715072

151 22:27:50.821 Find FS: 10.254.10.14/32 11715072

152 22:27:50.821 NDB delete: 10.254.1.5/32 1

153 22:27:50.821 Poison squashed: 10.254.1.5/32 rt gone

154 22:27:50.821 RDB delete: 10.254.1.5/32 10.66.31.1

155 22:27:50.821 Not active net/1=SH: 10.254.1.5/32 0

156 22:27:50.821 FC not sat Dmin/met: 4294967295 11663872

157 22:27:50.821 Find FS: 10.254.1.5/32 11663872

158 22:27:50.821 NDB delete: 10.254.1.26/32 1

159 22:27:50.821 Poison squashed: 10.254.1.26/32 rt gone

160 22:27:50.817 RDB delete: 10.254.1.26/32 10.66.31.1

161 22:27:50.817 Not active net/1=SH: 10.254.1.26/32 0

162 22:27:50.817 FC not sat Dmin/met: 4294967295 41177600

163 22:27:50.817 Find FS: 10.254.1.26/32 41177600

164 22:27:50.817 NDB delete: 10.254.10.16/32 1

165 22:27:50.817 Poison squashed: 10.254.10.16/32 rt gone

Gold

Re: EIGRP ip problem - help!!!!!!!!!!!!!

Resetting your neighbors probably isn't going to help.... :-) On the router that's doing the redistribution, do this:

clear ip eigrp events

clear ip eigrp topo 0.0.0.0 0.0.0.0

Russ.W

Silver

Re: EIGRP ip problem - help!!!!!!!!!!!!!

Is the 0.0.0.0 in the topology table of the hub router ?

One of my coworkers had this happen a few months ago and he had to reload the hub box . If you do a clear ip eigrp neighbor , not neighbors it will reset the EIGRP process, If you can do this try it on the hub side to see if the routes come back.

Since it is not working anyway you can try to remove the static 0.0.0.0 and then replace it see if this starts the redistribution .

Gold

Re: EIGRP ip problem - help!!!!!!!!!!!!!

Resetting your neighbors probably isn't going to help.... :-) On the router that's doing the redistribution, do this:

clear ip eigrp events

clear ip eigrp topo 0.0.0.0 0.0.0.0

show ip eigrp topo 0.0.0.0

I'll almost bet it's back, but if it isn't, then do a:

show ip eigrp events

So we can see what that looks like.

The best bet: open a TAC case, if you can. :-)

Russ.W

Gold

Re: EIGRP ip problem - help!!!!!!!!!!!!!

Eigrp and IGRP do not understand 0.0.0.0, you need to define your external network in eigrp.

heres some more info:

http://www.cisco.com/en/US/customer/tech/tk365/tk80/technologies_q_and_a_item09186a008012d8f7.shtml

New Member

Re: EIGRP ip problem - help!!!!!!!!!!!!!

Yes, I am aware of this and we do have static route to the network 0.0.0.0 configured which is redistributed into EIGRP. The point is that this 0.0.0.0 route is not being propogated down to the remote sites in the routing updates!.

The central site is running 12.1(20) ios.

Gold

Re: EIGRP ip problem - help!!!!!!!!!!!!!

IGRP doesn't support the 0/0, but EIGRP does, so this should work.

Russ.W

Gold

Re: EIGRP ip problem - help!!!!!!!!!!!!!

I see you've pasted in show ip route for all of them, could you do this:

show ip route 0.0.0.0 0.0.0.0

sho ip eigrp topo 0.0.0.0 0.0.0.0

sho run | b eigrp

And make certain the static routes are in there as well as the EIGRP config. There are some bugs in this area, so I'd also like to know the version of code you're running, and what your config looks like. Perhaps CSCdz63695, if you're running with route maps. It could be something new if you are in new code....

Make certain, as well, that you have a default metric configured, or a metric on the redistribution statement.

Russ.W

Silver

Re: EIGRP ip problem - help!!!!!!!!!!!!!

on the hub side does the interface that the 0.0.0.0 is being advertised outsh up in the topology table ?

Could be bug CSCdz41087

New Member

Re: EIGRP ip problem - help!!!!!!!!!!!!!

From the previous messages, I have removed the default route 0.0.0.0 which was statically defined, typed a show ip eigrp topology 0.0.0.0 and can see the route 0.0.0.0 being learned over the lan from the other router. This update is now part of the routing update and has been passed out to the remote single-homed sites.

I will be raising a tac call with cisco as I agree, it could be a bug!

1456
Views
0
Helpful
13
Replies
CreatePlease login to create content