From: Hunt Lee (huntl@webcentral.com.au)
Date: Fri Dec 20 2002 - 04:16:12 GMT-3
Very strange indeed, I do have "no auto-summary" at R1 also
router eigrp 65001
network 172.16.0.0
network 192.168.1.0
network 192.168.2.0
no auto-summary
Hunt
-----Original Message-----
From: Swink, Dave [mailto:DSwink@protrader.com]
Sent: Friday, 20 December 2002 5:08 PM
To: Hunt Lee
Subject: RE: What if EIGRP routes have different masks than RIP?
Well, the actual boundary of the 192.168.1.0 network is on R1, so I would
guess that "no auto-summary" was not configured on it, but looking at the
routing table that you enclosed for r4, I can see 192.168.1.0 is being
advertised by R1 with a /29 mask. I'm stumped for the moment. I'll give it
thought. Please let me know if you figure it out.
Dave
-----Original Message-----
From: Hunt Lee
To: Swink, Dave
Sent: 12/20/02 12:16 AM
Subject: RE: What if EIGRP routes have different masks than RIP?
Here you go, and thanks so much for your help in advance =)
Current configuration : 1785 bytes
version 12.2
service timestamps debug datetime msec show-timezone
service timestamps log datetime msec show-timezone
no service password-encryption
!
hostname R4
!
logging buffered 4096 debugging
aaa new-model
!
!
aaa session-id common
enable secret 5 $1$idSP$T2SS4olEvKsFiSjL3czsx.
!
clock timezone PST -8
ip subnet-zero
no ip domain lookup
ip host member 10.1.1.88
ip multicast-routing
ip cef
!
!
interface Ethernet0
ip address 172.16.2.1 255.255.255.0
no ip mroute-cache
!
interface Serial0
ip address 192.168.2.2 255.255.255.0
encapsulation frame-relay
ip route-cache flow
no ip mroute-cache
no fair-queue
frame-relay interface-dlci 131
!
interface BRI0
no ip address
shutdown
router eigrp 65001
redistribute rip
passive-interface Ethernet0
network 172.16.0.0
network 192.168.2.0
default-metric 10000 10 10 1 10000
no auto-summary
no eigrp log-neighbor-change
!
router rip
redistribute eigrp 65001
passive-interface Serial0
network 172.16.0.0
default-metric 5
no auto-summary
!
ip classless
no ip http server
ip flow-export version 5 peer-as
ip flow-export destination 10.1.0.1 3389
!
!
logging 2.2.2.2
snmp-server view ViewA ifEntry included
snmp-server community SNMPhaha RO
snmp-server community CommunityA view ViewA RO
snmp-server enable traps tty
snmp-server enable traps syslog
snmp-server enable traps bgp
snmp-server host 10.1.1.1 SNMPhaha
snmp-server host 10.2.2.2 SNMPhaha tty
!
line con 0
line vty 0 4
access-class 1 in
password cisco
transport input telnet ssh
!
ntp authentication-key 1 md5 0256510B535629706F1C5B4D5646345E2E500B7E75
7
ntp authenticate
ntp trusted-key 1
ntp access-group peer 2
ntp access-group serve 3
ntp master 1
ntp server 10.1.0.1
end
R4#
Hunt
-----Original Message-----
From: Swink, Dave [mailto:DSwink@protrader.com]
Sent: Friday, 20 December 2002 3:52 PM
To: Hunt Lee
Subject: RE: What if EIGRP routes have different masks than RIP?
Hmmm, ok, now you're starting to creep me out! Can you send me the
config
on R4?
Dave
-----Original Message-----
From: Hunt Lee [mailto:huntl@webcentral.com.au]
Sent: Thursday, December 19, 2002 11:50 PM
To: Swink, Dave
Subject: RE: What if EIGRP routes have different masks than RIP?
Hi Dave,
I did have "no auto-summary" on R4 though...
router eigrp 65001
redistribute rip
passive-interface Ethernet0
network 172.16.0.0
network 192.168.2.0
default-metric 10000 10 10 1 10000
no auto-summary
no eigrp log-neighbor-changes
Best Regards,
Hunt Lee
-----Original Message-----
From: Swink, Dave [mailto:DSwink@protrader.com]
Sent: Friday, 20 December 2002 3:29 PM
To: Hunt Lee
Subject: RE: What if EIGRP routes have different masks than RIP?
Hunt,
Unless you configured "no auto-summary" under the EIGRP process on R4,
it
will automatically summarize all of its routes to their major networks
at
the EIGRP boundary. Thus 192.168.1.0 /29 will be automatically
summarized
to the major network; 192.168.1.0 /24. Try changing the subnet mask on
the
172.16.2.0 /24 interfaces to /25. You should lose the 192.168.1.0
subnet
from your RIP routing table, and you will have an interesting
redistribution
problem, trying to get routing to the 192.168.1.x /29 subnets going
again.
Dave Swink
-----Original Message-----
From: Hunt Lee [mailto:huntl@webcentral.com.au]
Sent: Thursday, December 19, 2002 9:40 PM
To: 'ccielab@groupstudy.com'
Subject: What if EIGRP routes have different masks than RIP?
Guys,
I'm sure this question has been asked many times before, but can someone
kindly explain to me again? There are some /25 routes & /29 routes in
EIGRP
that I need to redistribute into RIP v1. The serial frame relay link
that
connects R1 with R4 has a /24 mask, and so as the Ethernet link that
connects R4 & R5. How can I inject /25 & /29 EIGRP routes into a
classful
routing domain in a case such as this?
172.16.5.1 /25
---------------
|
R1
/ | \
/ | \
R2 R3 R4 --- R5
The entire Hub & Spoke network is EIGRP only, except R4 which is running
both EIGRP & RIPv1 (& mutual redistribution between the 2 protocols), &
R5
is running RIPv1 only.
R1's Multipoint interface to R2 & 3 - 192.168.1.1 /29
R1's P-2-P interface to R4 - 192.168.2.1 /24
R2's FR interface - 192.168.1.2 /29
R3's FR interface - 192.168.1.3 /29
R4's FR interface to R1 - 192.168.2.2 /24
R4's Ethernet to R5 - 172.16.2.1 /24
R5's interface - 172.16.2.2 /24
From what I read from Cisco books, since the RIPv1 network in this e.g.
is
/24, both routes 192.168.1.0/29 & 172.16.5.0/25 would need to be
summarized
into a /24 (at R1) before R4 would be willing to pass these routes to
R5.
However, on the moment, all I had at R1 is:-
interface Serial0/0.2 point-to-point
ip address 192.168.2.1 255.255.255.0
ip summary-address eigrp 65001 172.16.5.0 255.255.255.0 5
frame-relay interface-dlci 130
And you can see that R5 "somehow" managed to get the Frame-Relay route
(192.168.1.0/29) - into a /24, don't undersantd how.
R5#sh ip route
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, 4 subnets
R 172.16.5.0 [120/5] via 172.16.2.1, 00:00:24, Ethernet0
R 172.16.6.0 [120/5] via 172.16.2.1, 00:00:24, Ethernet0
C 172.16.2.0 is directly connected, Ethernet0
R 172.16.3.0 [120/5] via 172.16.2.1, 00:00:24, Ethernet0
10.0.0.0/24 is subnetted, 1 subnets
C 10.0.0.0 is directly connected, Dialer0
R 192.168.1.0/24 [120/5] via 172.16.2.1, 00:00:24, Ethernet0
R 192.168.2.0/24 [120/5] via 172.16.2.1, 00:00:24, Ethernet0
30.0.0.0/24 is subnetted, 1 subnets
C 30.3.3.0 is directly connected, Loopback0
R5#
Yet I can see it clearly that the Frame Relay routes were definitely a
/29
R1#sh ip route
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
1.0.0.0/32 is subnetted, 1 subnets
C 1.1.1.1 is directly connected, Loopback0
172.16.0.0/16 is variably subnetted, 5 subnets, 2 masks
D 172.16.5.0/24 is a summary, 03:55:51, Null0
C 172.16.5.0/25 is directly connected, Loopback1
D 172.16.6.0/24 [90/20640000] via 192.168.1.2, 03:53:17,
Serial0/0.1
D 172.16.2.0/24 [90/2195456] via 192.168.2.2, 03:54:30,
Serial0/0.2
D 172.16.3.0/24 [90/20640000] via 192.168.1.3, 03:56:00,
Serial0/0.1
192.168.1.0/29 is subnetted, 1 subnets
C 192.168.1.0 is directly connected, Serial0/0.1
C 192.168.2.0/24 is directly connected, Serial0/0.2
R1#
R4#sh ip route
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, 4 subnets
D 172.16.5.0 [90/2297856] via 192.168.2.1, 03:56:59, Serial0
D 172.16.6.0 [90/21152000] via 192.168.2.1, 03:55:45, Serial0
C 172.16.2.0 is directly connected, Ethernet0
D 172.16.3.0 [90/21152000] via 192.168.2.1, 03:56:59, Serial0
192.168.1.0/29 is subnetted, 1 subnets
D 192.168.1.0 [90/21024000] via 192.168.2.1, 03:56:59, Serial0
C 192.168.2.0/24 is directly connected, Serial0
R4#
Thanks in advance,
Hunt
.
Any and all information contained herein is intended only for the person
or
entity to which it is addressed and may contain confidential or
otherwise
sensitive privileged ProTrader(tm) business and/or financial
information. If
you have received this message in error, please contact the sender and
delete the message in its entirety. ANY UNAUTHORIZED REVIEW OR
RETRANSMISSION OF THE INFORMATION CONTAINED HEREIN IS STRICTLY
PROHIBITED.
Any and all information contained herein is intended only for the person
or
entity to which it is addressed and may contain confidential or
otherwise
sensitive privileged ProTrader(tm) business and/or financial
information. If
you have received this message in error, please contact the sender and
delete the message in its entirety. ANY UNAUTHORIZED REVIEW OR
RETRANSMISSION OF THE INFORMATION CONTAINED HEREIN IS STRICTLY
PROHIBITED.
Any and all information contained herein is intended only for the person or
entity to which it is addressed and may contain confidential or otherwise
sensitive privileged ProTrader(tm) business and/or financial information. If
you have received this message in error, please contact the sender and
delete the message in its entirety. ANY UNAUTHORIZED REVIEW OR
RETRANSMISSION OF THE INFORMATION CONTAINED HEREIN IS STRICTLY PROHIBITED.
.
This archive was generated by hypermail 2.1.4 : Fri Jan 17 2003 - 17:21:50 GMT-3